| |||||||||||||
X: 25 years and still lacking vsync'ed double bufferingX: 25 years and still lacking vsync'ed double bufferingPosted Oct 1, 2009 20:32 UTC (Thu) by dlang (✭ supporter ✭, #313)In reply to: X: 25 years and still lacking vsync'ed double buffering by dion Parent article: LPC: 25 years of X
actually, I thought that tearing referred to the problem that (especially on older, cheaper video cards) if you updated the screen while it was being drawn it corrupted the video output so that the screen sync failed. The better video cards used dual-ported ram that could be accessed by two chips at the same time so that it could be updated and read without causing tearing.
just displaying part of the old image and part of the new image is not the same thing.
(Log in to post comments)
X: 25 years and still lacking vsync'ed double buffering Posted Oct 2, 2009 18:26 UTC (Fri) by dion (subscriber, #2764) [Link]
That's a new definition for me.
It doesn't matter what it's called though, doing updates to the screen at any other time that during vsync looks like ass.
X: 25 years and still lacking vsync'ed double buffering Posted Oct 2, 2009 21:03 UTC (Fri) by hrydgard (guest, #54085) [Link]
That's a new one - never heard of that problem, unless it's related to
"snow", which would happen if you changed the palette during parts of the frame under various EGA and VGA graphics modes and has similar causes.
X: 25 years and still lacking vsync'ed double buffering Posted Oct 2, 2009 23:09 UTC (Fri) by cortana (subscriber, #24596) [Link]
Here's a picture illustrating the effects of tearing:
http://forum.i3d.net/attachments/technische-hulp-cod4/943...
|
|||||||||||||
