Originally posted by ayumu
View Post
Announcement
Collapse
No announcement yet.
Mesa 23.3 Lands Optional Support For Allowing Game Tearing On Wayland
Collapse
X
-
Originally posted by ayumu View PostThe one promise of Wayland to never show imperfect frames... broken.
Microsoft did the same with their new (well, by now not very new) DX12 presentation model. Always perfect frames. Then game devs made them realize what a dumb mistake that was and introduced a tearing mode later on. The way it works now on Windows is that the application cannot override user preference. If the user wants every frame to be synced, they force it in the driver control panel. The game is unable to tear. If the user wants to game to control whether or not it tears, they set the option to "application preference." It's not rocket science.Last edited by RealNC; 12 September 2023, 05:42 AM.
- Likes 9
Comment
-
Originally posted by RealNC View Post
A promise made by people who don't have any clue whatsoever about PC gaming
Microsoft did the same with their new (well, by now not very new) DX12 presentation model. Always perfect frames. Then game devs made them realize what a dumb mistake that was and introduced a tearing mode later on. The way it works now on Windows is that the application cannot override user preference. If the user wants every frame to be synced, they force it in the driver control panel. The game is unable to tear. If the user wants to game to control whether or not it tears, they set the option to "application preference." It's not rocket science.
Comment
-
Originally posted by geearf View Post
What makes no tearing a dumb mistake? Isn't better quality a good thing? Or does it potentially make a game unplayable when it could be playable with tearing?
- Likes 11
Comment
-
Originally posted by ayumu View PostThe one promise of Wayland to never show imperfect frames... broken.
They could have focused their efforts into making triple buffering work really well, as well as dynamic refresh such as freesync.
But no, they instead settle for the usual mediocrity.
Also... variable refresh rate for Wayland already works. Perhaps not every DE has it, but some do. And, GNOME 44 is supposed to support triple-buffering with Wayland.Last edited by schmidtbag; 12 September 2023, 01:35 PM.
- Likes 6
Comment
-
Originally posted by geearf View Post
What makes no tearing a dumb mistake? Isn't better quality a good thing? Or does it potentially make a game unplayable when it could be playable with tearing?
Tearing and unplayable also depends on your hardware and in-game settings. If you're able to get greater than 60 FPS, you can turn off vsync and enable tearing to get lower input latency. If you're unable to get a steady 60 FPS, like it dips down to 45-50 in that one part of the level but the rest of the time it's normally fine, sometimes you don't want to be hit with 33ms of lag when sub-60 v sync occurs, because that is noticeable, turning on tearing is an alternative to latency/FPS jumping between 33ms/30FPS and 16ms/60FPS.Last edited by skeevy420; 12 September 2023, 10:33 AM.
- Likes 7
Comment
-
Originally posted by AnAccount View Post
But this is not that.... this is allowing for someone else (the game developers) to break my frames on my computer. It would be a different thing, if there were a user switch to allow/disallow it. But as it is now, this extension allows a thirdparty to break my frames.
- Likes 7
Comment
-
Originally posted by ayumu View PostThe one promise of Wayland to never show imperfect frames... broken.
They could have focused their efforts into making triple buffering work really well, as well as dynamic refresh such as freesync.
But no, they instead settle for the usual mediocrity.
Comment
Comment