On Sun, Oct 27, 2002 at 04:44:34PM +0100, Felix Kühling wrote:

 > But this way you waste lots of CPU cycles on frames which are never
 > displayed. Wouldn't be waiting (IRQ) for the pageflip to occur before
 > you render the 3rd frame in the above example a better approach?

 What's the point of trying to display 120 Hz if you monitor can only do
 85 Hz?  On SGIs, which sync to vblank per default, there's a query
 which sort of tells you "how much time you have before the next swap
 happens".  In that way you can decide if you want to wait for it or
 miss it.  If you let it fly by, you can use the extra time to keep
 doing stuff in your simulation.

 The way I understood triple buffering the intention is to avoid hanging
 there for long times waiting for the vblank.  You get the benefits from
 sync-to-vblank (no tearing) while paying a somewhat smaller price.

-- 
Marcelo


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to