Originally posted by dimko
View Post
Announcement
Collapse
No announcement yet.
XWayland 23.2 Released With Tearing Control, Resizable Rootful, EI Support
Collapse
X
-
Originally posted by ridge View PostNegative, I do not have a VRR monitor. It's very old.
Refresh rate of the monitor vs power of the machine is also critical. Lot of games and programs do better not rendering a frame half way across a sync with sub 75 Hz monitors. Remember to get a tear you have to have rendered at output. Higher monitor hz without VRR more likely to have a tearing event.
Nvidia gpu drivers also have their own tear countering tech as well that can be enabled again costs performance.
Under wayland in the protocol now you have allow tearing with the default being some form of tearing mitigation enabled this is a lot simpler place than X11 where you have multi tearing mitigations that all have to be off to have no tearing mitigations to see tearing and remember each one enabled under x11 adds its own bit of output latency problem.
Yes enabling Xwayland allow tearing feature does not equal you will see tearing either. Its really simple to miss that different game engines and other software have built in tearing mitigation as well when they can get vsync timing information.
Wayland always existing vsync= always able to get vsync timing information even when tearing is allowed. This is one of the problems with X11 bare metal at times is that vsync timing information can be cut off from applications by either the x11 server or the X11 compositor when tearing is allowed so blocking applications running own interal mitigations against rendering across vsync... Please note I said at times this is not always its how you have everything configured.
X11 bare metal has way too many settings for tearing mitigations that all basically control code that duplication other code functionality that all add latency and at worse result in increased memory usage(including leaking memory) and latency..
Comment
Comment