Proton VS gamescope

The "Metaverse" is a complete joke, and among gamers, Valve has a way better reputation than Meta. Why would they want to dilute that brand?

They already have their own platform (Steam), OS (SteamOS), VR headset (Index), their own Windows translation layer (Proton, https://github.com/ValveSoftware/Proton), their own partnership with cloud gaming (Steam Cloud Play using GeForce Now , https://partner.steamgames.com/doc/features/cloudgaming), etc.

IMO: As someone with thousands of games on Steam, there's no way in hell I'd want that linked to Facebook. I think they eventually removed the requirement to have a FB account to use a Quest, but they still require a Meta account. Yuck.

This reeks of Facebook recognizing the Metaverse as the failure that it was and opening it up because it's no longer relevant...

Or Valve's Proton[0], a tool for playing Windows games on Linux.

https://github.com/ValveSoftware/Proton

Did you mount it with the correct flags?

there is a hack to try and use your existing windows game install from an NTFS drive, but i don't recommend it as steam will try to save file names that are not allowed on NTFS...plus ext4 is faster.

From a quick search, here's what I found. It looks like you're encountering some common issues that can occur with games running on Linux through Proton, especially with the recent updates to games like Satisfactory that might affect compatibility. The log entries you're seeing related to D3DCompile2 failing to compile shader and the issues with Ternary operator and LinearToSrgbBranching not being defined, suggest that there's a problem with shader compilation. This can often be related to the version of Proton or the graphics drivers you are using. Some users have reported that the game does launch with the -vulkan option but with graphical glitches and lower performance, which indicates that the Vulkan renderer is working but possibly not optimally on your setup. From the discussions in the community, users have suggested ensuring that the latest drivers for your graphics card are installed and, if using an Intel GPU, that the Mesa drivers are up to date since Intel XeSS references were found in the logs. If you're using NVIDIA graphics, make sure you have the latest drivers and possibly set the PROTON_ENABLE_NVAPI=1 %command% to enable DLSS if you're under Vulkan. If you're using an Optimus laptop with both Intel and NVIDIA GPUs, make sure your Optimus setup is correctly configured. Some users have found success by specifying DXVK_FILTER_DEVICE_NAMES=GeForce to force the game to use the NVIDIA GPU. It's also worth noting that if you're encountering issues with DirectX 11, you might want to try forcing the game to use DirectX 10 if possible or look into DXVK configurations that could resolve compatibility issues. Lastly, if none of these solutions work, you could try running a trace with apitrace to gather more detailed logs that might point to the specific issue. If you're still stuck, it would be a good idea to report the issue to the Proton GitHub page or seek further assistance in the game's community forums where others might have encountered and solved similar issues. For more information and to find others who might have resolved similar issues, check out the community discussions on GitHub​​, Steam Community​​, and the DXVK GitHub page​​.

Maybe gamesope can help? Games are nested into it to allow for better control.

Well I suppose you should start taking Wayland seriously then, because gamescope, the compositor on the Steam Deck, uses Wayland. https://github.com/Plagman/gamescope/blob/master/src/wlserver.cpp

Mini-update: I spoke with Josh (and Strudel, who referenced me to the PR), and this has been already merged into gamescope.

Valve staff is also aware they cannot force developers to retrofit 16:10 support into existing games (some do, many don't), so they even go the extra mile to provide extra functionality in gamescope to improve the 16:10 gaming experience for games that only support 16:9 natively.

Source: https://github.com/Plagman/gamescope/issues/474

The ganescope github has all the commands and how to use them: https://github.com/Plagman/gamescope

I'm trying out gamescope on my laptop, and I came across ChimeraOS's fork of it. I'm not sure why I would choose one over the other. ChimeraOS mentions something about "session switch", but I'm not sure what that's about.

You can use gamescope on the desktop, I use it for a ton of games like No Man's Sky, Bethesda games, and any others that have alt tab instability.

For those that don't know (like me, three minutes ago) gamescope [1] is a Wayland compositor custom-written for games (and, I believe, what the Steam Deck uses). it's open source, and under the "BSD 2-clause" license.

[1]: https://github.com/Plagman/gamescope

I assume that this is because I'm still using ye olde steamos-compositor (https://github.com/ValveSoftware/steamos-compositor/.) I'm interested in switching to gamescope (https://github.com/Plagman/gamescope) but I'm getting the feeling it won't work on my 20.04 vintage Ubuntu; the required version of meson isn't available and I can't find a PPA that contains gamescope. My instinct act this point is to just live with the pain, as fully dealing with this will likely involve just switching all the way to Arch to more closely match the newest SteamOS and I just don't want to do that right now. Anyone know if there is a middleground that will support a modern steam big picture mode without having to totally redo everything?