Hey all,
I have an application where there is a timeline that updates some
texture positions. In the new-frame callback I also calculate the FPS.
This showed a nice ~60FPS with occasional drops to 45FPS. These drops
where visible in the movement of the textures, you could notice it was
not smooth. So i hacked the glx backend to use a swap interval of 2
instead of one. This caused the FPS to drop to a stable 30 , as expected
and wanted.
Now I have moved to clutter 1.6.6, and it seems the new-frame is not in
sync with the VBLANK. I see FPS as high as 80 and it doesn't seem to
matter if i set CLUTTER_VBLANK to dri, glx or none.
Is new-frame supposed to by in sync with VBLANK or was I just lucky it
worked like that?
Any hints on how I can debug this in case it is a bug ?
TIA,
Erwin
_______________________________________________
clutter-app-devel-list mailing list
[email protected]
http://lists.clutter-project.org/listinfo/clutter-app-devel-list
