Hi, Rudolf wrote: > Hi again, >> I don't really see why that is useful. maybe you can explain more >>clearly. Thanks. > > the whole concept of this double buffering described below? What I don't get: Where is the third buffer? Why not just draw into the offscreen buffer then page flip? Blit from front buffer to the back one so the two buffer be identical at this moment. >>Rudolf wrote: >> >>>Hi, >>> >>>a small update on that 'other' doublebuffering: >>> >>> >>> >>>>Only good solution: double buffering entire screen and blit to >>>>offscreen memory only, then switch offscreen onscreen during >>>>retrace, >>>>then blit now onscreen memory to now offscreen buffer. Repeat when >>>>needed. 8-) >>> >>>I would say make it triple buffering so things keep transparant to >>>existing apps and BDirectWindow for example. >>>1. have a normal screen, that's never shown. Here everything is >>>drawn >>>into, so also by apps. >>>2. have the pageflipping doublebuffering in place, that gets its >>>content from 1. >>> >>>->I think it would be nice if such a feature, if ever implemented, >>>should preferably also be an option. Just ask driver if it can do >>>this, >>>and if not, fallback to single buffering as it is now. (Depends on >>>graphicsRAM available, and engine capabilities for virtual height) Maybe if I better understand what you want... bye, Adi.