Open adlainewson opened 5 months ago
Hmmm w/ nvidia 535 driver, I’ve also seen that message when running glxgears on gamescope …
What happens when you run gamescope -- vkcube
?
If that crashes/hangs, what about DISABLE_GAMESCOPE_WSI=1 gamescope -- vkcube
?
Hmmm w/ nvidia 535 driver, I’ve also seen that message when running glxgears on gamescope …
What happens when you run
gamescope -- vkcube
? If that crashes/hangs, what aboutDISABLE_GAMESCOPE_WSI=1 gamescope -- vkcube
?
Interesting; running without the flag seems normal, running with DISABLE_GAMESCOPE_WSI=1
appears to replicate the stuttering, but without the xwm error messages.
@adlainewson
When running gamescope nested,
I suggest you put
gamescope -h 1440 -H 1440 -- %command%
In the launch options, instead of running steam ontop of gamescope
thank you, sometimes running steam in gamescope gets around some errors - in this case there is no difference if gamescope runs steam or steam runs gamescope.
Please see videos for the issue: Majesty 2: https://github.com/ValveSoftware/gamescope/assets/10458698/9942fd2a-704b-436c-864f-b01ce6b065d8
Zero Protocol (free demo): https://github.com/ValveSoftware/gamescope/assets/10458698/ef8f1ba4-df60-4079-a6a1-1c19b8b7d8e4
Problem description
xwm: got the same buffer committed twice, ignoring.
as the problem occursMESA_VK_DEVICE_SELECT
) and igpu (intel)Debugging info
--rt
,--force-composition
--synchronous-x11
and various numbers for-r
and--framerate-limit
to no availFollowing is an example log from
gamescope -h 1440 -H 1440 -- steam
then running Zero Protocol and loading into a saved game, where the problem occurs (log cut after at the relevant error spamming log)following is some system info: