Mike Lawrence wrote: > Just got a reply from a colleague (John Christie) citing Sol's work as > well: > > "What your finding is what would be predicted. Sol discovered this > same problem some time ago in OpenGL based software in general. What > happens is that the double buffer is asynchronous when it can be. So, > if the buffers are clear and there's no pending request then the call > returns immediately. But, if the buffers are full, i.e. already > processing a flip, then control doesn't return to the program until > the flip is done. > > So, at values of <=1 you'll get proper behaviour. There's a simple > and obvious solution of course... always start one frame back and > redraw your current image and then immediately draw the subsequent > one. The call will return at the border of a refresh."
Yes. The moral of the story is that measuring the time of the function call return is no substitute for measuring the time when something gets displayed on screen. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
