With latest 535 on xorg there seems to be some issue with ForceCompositionPipeline/ForceFullCompositionPipeline which affects both proprietary and open source.
During gaming(mostly noticeable if you cap the game to monitor’s refresh rate) screen tearing occurs despite either of the two options to be enabled, note this didn’t happen on 530 and there also is slight “hiccup” at times where the game as if the frame pacing drops and corrects itself(which when inspected via mangohud isn’t the case).
Note that this does have a very similar horizontal tear at the top to what occurs in a wayland session - 535.54.03 Screen tearing while gaming on Wayland session - #19 by hmpfkafka
Perhaps 535 broke how vsync/frames are presented ?
EDIT: Wanted to update that the most obvious game where you can experience the “hiccup” and the tearing would be CS GO or CS2 via proton experimental - you would see how the picture gets choppy as if there is sort of hiccup in the animations and the way you move the camera(most visible when moving the mouse around) and is best observed when the game is capped to the monitor refresh rate - so for example using mangohud or strangle to cap it to 165hz in my case.
System information:
Operating System: EndeavourOS
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.5.3-273-tkg-bore-eevdf (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 31,3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2
| NVIDIA-SMI 535.43.09 Driver Version: 535.43.09 CUDA Version: 12.2 |