The first BETA for SuperTux v0.7.0 is out now! You can download it from https://github.com/SuperTux/supertux/releases/tag/v0.7.0-beta.1

Check out the development summary for 0.7 on https://www.youtube.com/watch?v=PczyNWV8gI0 for all the changes!

Please try it out and report issues on GitHub here: https://github.com/SuperTux/supertux/issues

Thank you all for playing SuperTux and supporting us throughout the years!

submitted by /u/SuperTuxTeam_Tobbi
[link] [comments]

I've been thinking about how Valve could potentially solve the linux kernel level anti cheat issue. While there is technically anti cheat support on linux already, it just runs in user space in a free environment making it not as good at preventing cheats as kernel level anticheat on windows. This may be one of the reasons why some game devs choose to not support linux currently, even if it's as easy as flipping a toggle on their side.

However I also don't think it's a good idea to just reimplement those kernel level anticheat solutions on linux. Game devs won't bother doing this for the relatively small portion of linux users, and this creates additional security vulnerabities (afaik Microsoft is also looking into ways to reduce third party code in the kernel).

So I think one of the ways to accomplish a better linux anticheat solution is by locking the system down while you play such a competitive game.

The basic idea would be a 2 tier system:

Default - This is what we basically have now. Games run in Steam's existing container runtime, you can use any distro, modding works fine. It's not really resistant against determined cheaters due to anticheat engines running in user space and allowing all sorts of different environments (kernel, drivers etc.) but it's fine for casual play.

Competitive - When you play a game that requires a higher level of anticheat (battlefield etc.), Steam does a quick warm reboot into a locked down, Valve signed environment. Essentially like temporarily booting into a console-like state for that game. Secure boot + TPM measured boot lets servers verify the client booted the expected build (including kernel and shipped runtime stack). If the environment is modified, the attestation should fail. On a game level I think you could make the game directory immutable or detect changes with fs-verity.

The key points are:

• You only do the reboot when you play these competitive games with strict anticheat. Your daily driver can still be used for less competitive games (like now).
• Game devs don't need to ship kernel drivers. They just set a Steamworks policy saying "ranked requires Competitive Session" and the Steam backend then does the check that the system is not tampered with using TPM attestation.
• Existing anticheat (EAC/Battleye) still does the actual cheat detection work, but now it's running in a known good environment instead of trying to reason about thousands of different distro configurations which could inject cheats in various parts of the stack (kernel, mesa etc.).
• Valve could roll this out on Steam Deck first where they control the hardware, then expand to linux PCs as an optional boot partition.

The goal of this would be is just getting linux to parity with what kernel anticheat provides on windows, without the downsides of a persistent kernel driver on your daily OS.

Unfortunately it would only work with TPM hardware support, but I don't think there is an easy way to make it work without TPM in a way that doesn't compromise the efficacy.

So why do this over booting into windows?

• It should often be faster end to end than rebooting into windows and spinning up Steam, because the competitive environment can be minimal and purpose built.
• No windows maintenance needed: no updates randomly installing, no dealing with two separate OS configurations, no windows bloat / data harvesting.

submitted by /u/RandomTrollface
[link] [comments]

submitted by /u/_riyann
[link] [comments]

Disclaimer: I've no other frame of reference, as I've never booted this in Windows or on a console, but I have also never seen this in any screenshot or review video on the game. This is so minor and inconsequential, but being unable to solve it is driving me insane.

You may need to click the photo below to expand it. On the top right corner, there is a small square. I have no idea what the hell it is, or how to get rid of it, but it is always there. It never goes away. It never expands into usefulness, either. I really have no idea what on earth this is.

I've tested GE-Proton 10-27, cachyOS 10.0.20251126. I've tried with no launch parameters, but generally run with: PROTON_FSR4_UPGRADE=1 %command% -NoStartupMovies

Why? WHY?

I am running:

Ryzen 7 5700X3D
Radeon RX 9070 XT
CachyOS, fully up to date, KDE 6.5.4

Does anyone else have this? Any idea what on earth it could be!? Thank you!

submitted by /u/sluzi26
[link] [comments]

So I have Street Fighter 6 installed via Steam on Ubuntu Noble Numbat. The game runs greatly but I want to install some mods. Nothing too gooney, just a bunch of shirtless versions for the male characters. The readme files sadly tell me to use Fluffy Mod Manager to install the mods, but there's no Linux version. Do I have to emulate it with wine? There's a functional Linux alternative? Or there's a file path where I can just manually move them?

submitted by /u/rickleon3
[link] [comments]