Open L0WR1D3Rz opened 1 month ago
It's likely the games are failing to work in current main because Gamescope updated to 3.14.4, which forces on the VK_EXT_swapchain_maintenance1 extension for DXVK/VKD3D-Proton, which it seems that the current graphics driver in main doesn't seem to like. I made an issue about it on the Gamescope repo which was responded with and stated that a gpu driver update is in the works to hopefully fix that particular issue: https://github.com/ValveSoftware/gamescope/issues/1256 . Also the cursor issue is another thing with the gamescope update that seems to be an issue with there being a new input api for use in gamescope which the current public steam client doesn't have support for: https://github.com/ValveSoftware/gamescope/issues/1255
It's surprising how long it has taken them to fix this.... Usually it was a matter of 1-2 days but it's been quite sometime that the 3.6 build is completely borked. Is there any way to roll back to an earlier 3.6?
You shouldn't use the development branch as a daily driver unless you have more than one device. Switch to any of the other channels.
You shouldn't use the development branch as a daily driver unless you have more than one device. Switch to any of the other channels.
Thanks for your really useful comment 😂 some of us report issues so they get fixed for the sake of continuous improvement. You can stick to the stable build and to posting such value adding comments. 😂
Seems fixed since 3.6 updated and moved to BETA
Your system information
Please describe your issue in as much detail as possible:
It looks like the latest version has broken compatibility with a large number of games. The following games crash when launched through game mode, but work if launched through desktop mode Ender lilies, pathologic 2, no rest for the wicked, risk of rain returns, unsighted, system shock remake. Additionally games that require a cursor like fallout new Vegas while it launches in the launcher it's impossible to navigate the menu as the cursor becomes invisible. All of the above problems are eliminated if one rolls back to stable channel and steam os 3.5
Steps for reproducing this issue: