Can confirm the same thing is happening on my Framework 13 7640U, works just fine on my primary NVIDIA 3080 setup.
I'm running Ubuntu 25.04. The game doesn't detect my Dualsense or Xbox Core controllers. I'm able to use these controllers in other games (provided the games support them). My first time starting up, I got a message basically saying the controller was supported (I also got this message the first time starting up in Windows), but since the game was running with Steam Input, I may not see the correct button prompts. I've tried disabling Steam Input, forcing it, etc. Nothing works.
Performance seems acceptable with a few occasional hitches/stutters (some but not all seems potentially related to traversal). Just trying the first stage, I seem to get 100-130+ fps. The average performance under Windows is somewhat higher but also doesn't have the stutters and hitches.
I sometimes see short delays of texture loads... This doesn't happen in Windows. That being said, the game is running off of a Gen 4 NVME and I'm using an RTX 4090.
On my laptop with a 13th Gen Intel GPU, mobile RTX 4090, and Ubuntu 25.004, the performance is all over the place. It seems the vsync settings aren't applied as the fps will commonly go well above the refresh rate of the screen. Controllers also don't work on the laptop.
The laptop has Optimus, and both systems are running Wayland.
I haven't tried it too much, but seems to run at least "alright" on Steam Deck. The controller (which is just the built-in controller of the machine) also actually works.
Can confirm crashing here on 780M (framework 16 igpu) and Rog Ally X. works on my desktop and works on my framework 16 dgpu (7700S), mesa 25.2.2 as well as vulkan from mesa-git
-edit- looks like its fixed in latest proton experimental (bleeding edge) -- now working on both my framework and rog ally x
-edit- looks like its fixed in latest proton experimental (bleeding edge) -- now working on both my framework and rog ally x
Wouldn't say "fixed", it gets in game now but upon loading the campaign, it simply renders a black screen with some hud elements. FW13
Sounds like it may be a combination of Distro, HW and software.
I share the issue of the game failing to launch on my Rog Ally X, even using Proton Expirimental branch(Bazzite F42.20250903).
However on my Asus TUF A15 FA507UI, I have dissabled the Discrete RTX 4070, and am using the 780M Integrated chip.
no config changes or proton switching, works fine with no issues (Endeavour OS, Arch based, Up to date).
Something interesting though, I expected the drivers to be the same.
I loaded up steam in big picture on the A15 to check what the system thinks its using and it reports "AMD OpenSource 2.0.349" as the video driver, this is using the Kwin compositor under Wayland if that helps.
Replying to https://github.com/ValveSoftware/Proton/issues/9011#issuecomment-3255453620
AMD OpenSource 2.0.349 that is not the RADV/Mesa driver. Some 3rd party drivers are installed on your system.
This is what the RADV driver looks like
Replying to https://github.com/ValveSoftware/Proton/issues/9011#issuecomment-3255958370
So maybe Mesa is the problem then?
wouldn't be the first time.
I couldn't tell you what the third party driver is though, setup is pretty simple.
EndeavourOS, (Arch base)
Installed Nvidia Open Proprietary drivers,
Kernel: 6.16.4-arch1-1
added repo: [g14]
Server = https://arch.asus-linux.org (restores acpi control over Asus HW)
Nvida Rtx 4070 disabled in kernel using supergfxctl from g14 repo.
Anyone else now having issues with anti cheat? Getting kicked from ever game on gears reloaded after a minute or two.
I tested on both my PC and SteamDeck ..
proton experimentalx2 2025-09
Compatibility Report
System Information
GPU: Radeon 780M
Video driver version: Mesa 25.2.1
Kernel version: 6.15.9-116.bazzite
Link to full system information report as Gist: https://gist.github.com/RoundedMecha/d6bb20807f5a5abd059a45b77bad25c4
Proton version: Experimental, 9.04
I confirm:
steam-2523720.log
Symptoms
Game will begin to launch with the Easy Anti-Cheat Splashscreen then go to a blackscreen and close any attempts to open afterwards will follow a similar pattern except after the intial splashscreen a dialouge box pops up stating 'Last launch did not complete sucessfully. Revert to default settings?' with the option yes or no neither options makes a difference as it will go to a black screen and crash.
Reproduction
Try and launch game
Notes
I have attempted to use the SteamDeck=1 command as the game doesnt seem to have this issue on the steam deck, this command apparently also helps with an issue on desktops where the game will launch but the user wont be able to proceed at the title as the game will try and launch the Xbox account linking feature but fail with the command this can be skipped and the game will work just like the steam deck, unfortunatly this did not make a difference on my machine which lead me to believe it could be a bazzite specific issue however I have also seen reports of users on the steam discussion forum mentioning having this issue with the Steam OS version of the legion go S which means this may not be the case.