The compositor has to support tearing too I believe (I’m not sure all of the main 3 do, and e.g. wlroots only very recently got most/all of the pieces and I’m not sure sway supports controlling it) and will probably be where the option is exposed. And this is specifically about XWayland, where the support is even more recent. So I wouldn’t necessarily expect it to work yet, but maybe Plasma is ahead of things here.
Iirc the dev who largely pushed this tearing proposal implemented it first on KDE. First as a proof of concept and for a while it’s been merged upstream.
Sounds like FW Updater here is adding support for NAVI 3x which is the 5nm / RDNA 3 chips, AKA Ryzen RX 7000 series (for example RX 7600). Does this mean you can now update the firmware for the chip? Does it mean FWUpd will automatically handle firmware updates for you?
Bonus challenge if you wanna talk to me about what some of the linux firmware lingo means.
It’s exciting that with Fwupd 1.9.6+ it’s now possible to update AMD discrete graphics card firmware under Linux rather than having to resort to Windows or other environments. This new Fwupd plug-in works with Navi 3x on recent versions of the Linux kernel where the AMDGPU driver has the necessary interfaces to make the firmware updating happen. Specifically this firmware updating is focused on flashing the graphics card’s Integrated Firmware Image (IFWI).
So you could not update the firmware on Navi 3x before this update arrived to Fwupd? Err you could update the card outside of Linux by booting up windows?
Okay got it. Thank you! I just started using desktop linux, I’m on Nobara so I have some expectation that things will be handled for me and I’m not always sure about when I need to tweak things. The extent of my troubleshooting so far is using ProtonDB.
I’ll add that firmware updates for GPUs are pretty uncommon (my current card has had zero in the 3 years since it was launched). And an AMD driver dev confirmed as much, that it is just there in case it’s needed.
And fwupd is a standard way to update firmware etc on a variety of hardware that doesn’t require DOS boot drives or using Windows, more commonly used on laptops and some servers and prebuilt clients. Which is obviously quite nice from a Linux user’s perspective.
Adding to other comments, fwupd is integrated into Gnome Software and probably other software centers. There’s also a systemd servivce or fwupd can be run from the terminal.
So as far as I know it’s not necessarily run automatically on all distros.
Haha, yes! Ctrl+Z sends a TSPT signal to a terminal process, while this script sends a STOP signal to every process in a game’s process tree. Both get resumed with a SIGCONT so they’re kinda similar.
On a similar note, has anyone tried the Audeze Maxwell on Linux? It has both 2.4ghz and I believe BT LC3 audio support, which Pipewire is starting to support too (although most people won’t have a BT adapter that supports it).
Go into Steam Settings > Compatibility, and turn on “Enable Steam Play for all other titles”, Steam will then ask to restart. Install your game (which should now not complain because it’s getting the Windows version for proton) then go change the setting back.
Edit: Added the correct settings section and proper option name, because I was originally winging it, writing this comment on mobile.
Valve should consider making it the default at this point, and just give the user a warning the first time they launch a non-supported game. Because these issues happen often enough that people may be left with a bad impression of Linux (and Steam) game support.
I’ve only ever had to deal with this issue when it comes to installing a demo of something. Generally Steam already knows if there is only a Windows build of a game or not and acts accordingly. If this is the thing that causes a bad impression of gaming on Linux, then you’ve probably already overlooked (or been blind to) other annoying situations.
You must already have the setting enabled (as do I). But on a new install of Steam, only games that have been approved by Valve will run. And that’s using the old system, and not the new system that the Deck uses. So there’s is only a small amount of games supported.
Because can you imagine the outrage if GTA6 or the latest Call of Duty is called “an unsupported game”?
I can see the youtube titles now: “SHOTS FIRED!!! Gabe Newell attacks Ubisoft by warning gamers about buggy games” with a nice video of someone launching the latest tom clancy wankfest and showing the pop-up.
Same with all the fun “quirks” that make sites like protondb so useful. You don’t want someone to accidentally play Dragon’s Dgoma with no cutscene audio or Kingdoms of Amalur with busted ass shaders.
I can see the youtube titles now: “SHOTS FIRED!!! Gabe Newell attacks Ubisoft by warning gamers about buggy games” with a nice video of someone launching the latest tom clancy wankfest and showing the pop-up.
They already do this with the deck verified system. I’m not sure how it would be more of a problem on desktop.
I tried running it with steamtinkerlaunch wich does open fenix.exe but it seems to crash as it immediately exits when i choose to run only custom command. The log of stl is of no help either
<span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - setRunProtonFromUseProton - Updating RUNPROTON for USEPROTON 'proton-unknown-999' from '/home/xxx/.steam/root/steamapps/common/SteamLinuxRuntime_sniper/_v2-entry-point --verb=waitforexitandrun -- /home/xxx/.steam/root/steamapps/common/Proton - Experimental/proton' to '/home/xxx/.steam/root/steamapps/common/Proton - Experimental/proton'
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - setRunProtonFromUseProton - Set RUNPROTON to '/home/xxx/.steam/root/steamapps/common/Proton - Experimental/proton'
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - extProtonRun - Continuing with RUNPROTON='/home/xxx/.steam/root/steamapps/common/Proton - Experimental/proton'
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - extProtonRun - No external program args here it seems
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - extProtonRun - Starting '/home/xxx/.steam/root/steamapps/compatdata/1250410/pfx/drive_c/Program Files/FenixSim A320/Fenix.exe' forked into the background
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - restoreOrgVars - Restoring previously cleared Variables
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - launchCustomProg - Changing pwd into previous directory
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - checkCustomLaunch - ONLY_CUSTOMCMD is set to 1 means only custom program '/home/xxx/.steam/root/steamapps/compatdata/1250410/pfx/drive_c/Program Files/FenixSim A320/Fenix.exe' is supposed to start - exiting here
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - checkCustomLaunch - ## CUSTOMCMD STOPPED after '1' seconds playtime
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - closeSTL - closing STL
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - updateConfigEntry - Emptying 'CUSTOMCMD' for '/home/xxx/.config/steamtinkerlaunch/default_template.conf'
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - updateConfigEntry - Option 'CUSTOMCMD' is updated with the new value 'echo' in config 'default_template.conf'
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - closeSTL - Creating '/dev/shm/steamtinkerlaunch/steamtinkerlaunch-closing.tmp'
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - checkPlayTime - The game was not started via 'steamtinkerlaunch' but directly from Steam - skipping Crash Requester
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - closeSTL - Game 'Microsoft Flight Simulator (1250410)' exited - cleaning up custom processes if necessary
</span><span style="color:#323232;">So 8. Okt 18:26:07 CEST 2023 INFO - closeTrayIcon - Closing TrayIcon '169695'
</span><span style="color:#323232;">So 8. Okt 18:26:08 CEST 2023 INFO - closeSTL - Removing '/dev/shm/steamtinkerlaunch/steamtinkerlaunch-closing.tmp'
</span>
It is a huge database for all games available on steam. So far, no one has made any reviews, but if you get it working, please write there how (you can include --start-options, drivers, distro etc.). Even if it is not working, write that and what you tried already. This way other people can spend more time on trying to get it working without doing the same steps all over again.
Also, it might be worth checking out in a few days when more people have added their workarounds and comments. Usually, this takes 1-2 weeks.
Hey, so the game is installed and I just played through some of the demo. And I posted on ProtonDB but it seems the post will take some time before it appears there. Cheers!
I guess it’s kind of useful for some very specific configurations? Maybe geared towards stock Ubuntu users. Wayland shouldn’t be having issues with this in the first place.
My guess: Since Steam Deck’s Plasma desktop mode uses X11 and Gamescope uses Wayland, the two environments may cause different behaviors in games and this is a quick way to align both.
linux_gaming
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.