Cool concept.
better than german version, but also much to theoretic and more confusing than it really is. examples would be better
Limitations of double buffering should be in double buffering and it dosent sound very professional.
"If the system always renders buffers in less time than it takes to display a buffer once on the monitor, the computer will wait for the monitor regardless of how many buffers there are." This doesn't strictly have to be the case. In this scenario, unused frames are dropped (overwritten). Computer is flipping between two buffers that are not currently read, overwriting it's own frames. The main point of triple buffering (as stated at the beginning of the article) is to decouple the producer from the consumer with respect to timing. —Preceding unsigned comment added by 77.101.218.35 ( talk) 06:58, 25 July 2008 (UTC)
A bit confusing, and should be written better.
24.115.42.98 (
talk)
15:42, 1 February 2009 (UTC)
Cool concept.
better than german version, but also much to theoretic and more confusing than it really is. examples would be better
Limitations of double buffering should be in double buffering and it dosent sound very professional.
"If the system always renders buffers in less time than it takes to display a buffer once on the monitor, the computer will wait for the monitor regardless of how many buffers there are." This doesn't strictly have to be the case. In this scenario, unused frames are dropped (overwritten). Computer is flipping between two buffers that are not currently read, overwriting it's own frames. The main point of triple buffering (as stated at the beginning of the article) is to decouple the producer from the consumer with respect to timing. —Preceding unsigned comment added by 77.101.218.35 ( talk) 06:58, 25 July 2008 (UTC)
A bit confusing, and should be written better.
24.115.42.98 (
talk)
15:42, 1 February 2009 (UTC)