gamescope VS dxvk

I think your information is quite outdated. The HWC overlay planes are heavily used, you can see this trivially just doing a 'dumpsys SurfaceFlinger' or grabbing a systrace/perfetto trace. When it falls back to GPU composition it's very obvious as there's a significant hit to latency and more GPU contention.

The overlay capabilities of the modern Snapdragons are also quite absurd. They support like upwards of a dozen overlays now and even have FP16 extended sRGB support. Some HWCs (like the one in the steam deck) even have per plane 3D LUTs for HDR tone mapping (ex https://github.com/ValveSoftware/gamescope/blob/master/src/d... )

The composition is bandwidth heavy of course, but for static scenes there's a cache after the HWC in the form of panel self refresh.

One of the unfortunate things about Wayland is every compositor will have its own quality of implementation affecting things like latency.

With XOrg, especially in the pre-compositing days, you could choose whatever WM you want and it wouldn't have any impact on the rendering performance of X clients. Once the Composite extension was added and everyone started running composited X desktops, that started to change, and the increased latency already started appearing - in an arguably worse architecture than Wayland because there were often three processes involved with lots of IPC per draw: X-Client->X-Server->X-Compositor->X-Server->CRTC. At least in Wayland it's more like Wayland-Client->Wayland-Compositor->CRTC.

If you're unhappy with the rendering latency of your Wayland sessions, it may be worth trying alternative compositors... they likely vary significantly. The Valve/Steam folks have made a minimal one specifically optimized for games/low-latency [0]. I doubt the SteamDeck would be seeing as much success as it is if Wayland were so problematic in this department.

[0]: https://github.com/ValveSoftware/gamescope

While streaming from the Deck to another device (phone with Steam Link app or another PC running steam), taking a screenshot on the Deck (hold the steam or ... button, and press R1) crashes the session (https://github.com/ValveSoftware/gamescope/issues/961). This one also impacts Decky Recorder. If you're recording the screen or have replay mode on and take a screenshot, you'll have a crash.

Mangohud (GOverlay), libstrangle, gamescope. Pick your poison.

I have an Intel GPU (HD Graphics 520) and gamescope doesn't work for me under arch Linux :( https://github.com/ValveSoftware/gamescope/issues/356

Hopefully someone more experienced in troubleshooting than me can chime in to help, since I don't wish to leave you on a "Works on my machine™" but I really don't know how to help since I don't use Ubuntu. In the meantime, try opening an issue on gamescope's issue tracker.

Take a second look at the github page; there is information on how to set the right resolution with Steam launch arguments. A quick cursory glance at the documentation gives me the impression that support for Nvidia GPU's is limited. I wouldn't bother with it if you consider yourself a Linux noob, the small performance up lift in not going to out way the frustration to make it work properly.

I'm unfamiliar with gamescope, never heard of it before. I found their github... I'm guessing "command" needs to be a compatibility layer like proton or wine calling the game's executable, huh?

In a nutshell, the video stack is held back because of compositor ; YMMV, but, if you'd like to try one designed primarly for games, use gamescope, the one made for the Steam Deck: https://github.com/ValveSoftware/gamescope

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​​.

Give DXVK a try https://github.com/doitsujin/dxvk/releases, use 32bit d3d9.dll

Vulkan is an alternative to DX which isn't MS-proprietary. I wouldn't be surprised if there was a Vulkan implementation for windows which uses DX under the hood, just as dxvk is a DX implementation that uses Vulkan under the hood.

I solved. I install all libraries manually. https://github.com/jp7677/dxvk-nvapi/releases/tag/v0.6 https://github.com/lutris/d3d_extras/releases/tag/v2 https://github.com/HansKristian-Work/vkd3d-proton/releases/tag/v2.9 https://github.com/doitsujin/dxvk/releases/tag/v2.2