Proton 5.13-4 not suspending compositing when lauching games

[doogie544]

All of the games I have tried are not suspending the desktop compositing/compositor when the game is launched. This is a new issue with 5.13-4. It was not present in 5.13-3 and checking proton version 5.0-10 shows that desktop effects are being properly suspended when launching games so this should not be related to an update to the Desktop Environment.

I am using Arch with KDE/Plasma and have the compositor set to allow applications to disable it. All native games do this properly and all Proton games do as well using older versions of proton (I also checked GE's Proton version 5.21 based on a newer version of WINE that Proton 5.13-4 is to make sure it was likely not related to an upstream WINE issue and it worked as well)

It looks like there was a regression in the current version of Proton 5.13 that is causing this issue. I also checked Experiential Proton to see if the regression was fixed and it the compositor was not properly suspended with it.

[intelligentgaming]

Which desktop environment?

[doogie544]

Umm, I'm not sure what GitHub did to the body of my report but I did include more information than just the title.

I'm using KDE plasma.

This was not an issue with proton 5.13-3 and games run on wine through lutris suspend compositing properly so it's not an issue with my desktop environment or with anything in Arch apparently. Even testing proton 5.0 works properly. I also tested proton experimental and it did not work either so it appears there is some regression present in 5.13.4 up.

I did try to edit my issue rather than posting a extremely long comment but there was no body there nothing for me to edit, the only editing option I can get was to edit the title

[intelligentgaming]

OK, well I use Kubuntu rather than Arch, but I'll test it tonight and see if I can replicate the issue.

[aeikum]

How are you determining whether compositing is disabled? What game(s) are you seeing this issue with? What display settings are you using in those games? Do you have multiple monitors?

The logic we use in Proton is we request the WM disable compositing when a fullscreen window is being displayed. Possibly something changed so that the windows are not being fullscreened?

[doogie544]

It is All games that are run under proton 5.13-4. Off the top of my head I've checked Borderlands 1 and 2, deceit, the blackout club, monster hunter world, lightless- the 21st sacrifice, probably more but those are the only ones I recall checking

You can visibly see the composting being disabled as the screen flickers as well as the fact that all desktop effects stop when the compositor is disabled, but I have also verified the it has not been by manually disabling it as well and know for sure it is not being disabled by proton 5.13-4. Using the same verification I can day for sure that the compositor Is being disabled by proton 5.0 with the same display settings applied to the game. I know for sure that borderlands 2 and the blackout club are fullscreen, I believe that all my other games are fullscreen as well but a few might be a fullscreen borderless window. I don't run any of my games in a smaller than fullscreen window.

I know proton 5.13-4 is recognizing the games as fullscreen as the way the games display when launched is visibly different if proton sees them as fullscreen. If windowed fullscreen they just start, but if true fullscreen there's is a noticable difference as they start since the first release of 5.13 as the new fullscreen feature introduced in that release is applied.

I'm pretty confident that the compositor was being properly disabled in 5.13-3 bur I have no way to easily verify that as using that is not as straightforward as reverting to 5.0 or 4.11. I can say however, that all of the GE custom protons I have tried disable the composter correctly as well.

As I don'tchange any settings in the game display between testing proton versions and at least two older proton versions have properly disabled the compositor whatever fixed was done in 15.3-4 to allow cyberpunk 2077 to be played must have caused an unwanted effect or a regression of some kind.

[aeikum]

Interesting, thanks for the thorough explanation. I can't think of anything that changed in 5.13-4 to affect this, but your results are pretty conclusive. I'll see if we can reproduce this issue.

[doogie544]

If I recall correctly 5.13-3 was not out very long before they had to release 5.13-4 as a hot fix for cyberpunk. I suppose it is possible that be compositing issue was introduced in 5.13-3 and I just didn't notice it in the few days before 5.13-4 was released.

So it's possible I could be incorrect as to the exact milestone this was released but I'd be willing to put money on the fact that it was working with 5.13-2 and would just about eat my keyboard raw if it was not working in 5.13-1 1

[oliverklee]

I experience the same problem with The Elder Scrolls Online: #556 (comment)

[zaps166]

Just tested Witcher 3 and NieR:Automata, openbox + qdre-compositor + fullscreen + proton 5.13-4: works properly.

Compositor logs on alt+tab (it uses _NET_WM_BYPASS_COMPOSITOR for fullscreen windows):

Unredirect fullscreen window: 37759747
Redirect fullscreen window: 37759747

Also screen tearing in game can be observed when vsync is off (so it is working properly).

[intelligentgaming]

Just tested Witcher 3 and NieR:Automata, openbox + qdre-compositor + fullscreen + proton 5.13-4: works properly.

Compositor logs on alt+tab (it uses _NET_WM_BYPASS_COMPOSITOR for fullscreen windows):

Unredirect fullscreen window: 37759747
Redirect fullscreen window: 37759747

Also screen tearing in game can be observed when vsync is off (so it is working properly).

How or where can you check the compositor logs?

[zaps166]

@intelligentgaming It depends on the compositor. Try to run compositor (usually the window manager like KWin, because most WMs has integrated compositor) from command line.

I use qdre-compositor (currently AUR qdre-git package, I'll separate it soon) with OpenBox window manager.

[intelligentgaming]

@intelligentgaming It depends on the compositor. Try to run compositor (usually the window manager like KWin, because most WMs has integrated compositor) from command line.

I use qdre-compositor (currently AUR qdre-git package, I'll separate it soon) with OpenBox window manager.

The reason is I'm seeing OPs issue now, you play a full screen game, either normal full screen or windowed full screen the compositor is not getting disabled.

I have a dual monitor setup with a window open on the second monitor, and the edge of the window are still composed, which I can check by disabling the compositor with Alt + Shift + F12.

This is with Kubuntu 20.10 with latest Proton 5.14-3.

EDIT: Using build 5.0-10 also does not disable compositor, however using Proton-5.21-GE-1 does.

[intelligentgaming]

After doing some experimentation, I got the compositor to automatically disable again with Proton 5.14-3 but it involves me turning off Force Composition Pipeline in the nVidia X Server application which causes screen tearing in all my games.

Clearly something has happened between either the Kwin compositor, the nVidia driver and Proton itself but as I mentioned before, it still disables the compositor if I use Proton-GE.

[doogie544]

So I just checked my settings. I don't have "force composition Pipline" enabled. It still has to have something to do with how Proton 5.14 is reporting the fullscreen game to kwin. As it was not as issue in 5.14 and I'm pretty sure it was not happening in the earlier versions of 5.14 and it works correctly in 5.0.

I would suspect that it might have something to do with an update of runtime soldier but GE Proton 5.21 is based on an earlier version of 5.14 and it works properly still and it relies on and calls solider as well

Upon further testing, enabling "force composition pipeline" and "force full composition pipeline" did not result in the compositor to be disabled.