5 ms·
I don’t get how some people don’t see it. I remember running a very weird compiz setup just to alleviate screen tearing, many years ago. It was such a relief t
by dontlaugh 3y ago
I don’t get how some people don’t see it. I remember running a very weird compiz setup just to alleviate screen tearing, many years ago.
It was such a relief the first time I used Mac OS X. Finally a unix that renders to the screen without artifacts.
- p_l 3y agoBecause screen tearing is something that honestly showed up pretty late, around the time of i3/i5/i7 with IGP, as before that tearing was mitigated at least a little with VSync. (There's the issue that X11 didn't expose good sync primitives, but that's workable with extension, not total replacement)
- dontlaugh 3y agoEven with vsync it happened on X11 on dedicated GPUs. Plus a number of other buffer management artefacts. It didn’t help that the drivers for everything were closed course, but even with perfect drivers X11’s design can’t deliver perfect frames.
- p_l 3y agoThe design can deliver perfect frames - it's extensible so pretty much you need to provide a way to handle double buffering right - and guess what, extensions for that were proposed (Present extension by Keith Packard, building on top of X Synchronization extension)
- LoganDark 3y ago> It was such a relief the first time I used Mac OS X. Finally a unix that renders to the screen without artifacts. That was one of the reasons I used macOS too. Not for artifact-free rendering but for the fact that it's a real production-ready desktop OS with first-party app support from most companies, while being a true Unix with all the powerful Unix capabilities, like being able to run Valgrind and etc. without nesting virtual machines.