[info-performer] __GL_SYNC_TO_VBLANK

From: Dorosky, Christopher G (christopher.g.dorosky++at++lmco.com)
Date: 03/04/2003 15:32:18

• Next message: Herbert Gartner: "[info-performer] pfv & stereo & multi-pipe/channel?"
• Previous message: Terry Welsh: "[info-performer] Can .flt loader throw texture coords"

Hi,

I am running Linux Redhat 7.3, and Performer 2.5.2
I have Linux tuned sufficiently, so that I can run standard perfly, with
flint.sv (a ./share model)
and get 60Hz constantly.

I actually edited perfly to use pfGetTime() between pfSync and pfFrame, and
compare the new time to
last frames time. If over 17ms, I tally an overrun.

If I run in locked mode, I get no overruns at all, over the coarse of 10
min.
If I enable __GL_SYNC_TO_VBLANK=1, then I get an overrun about every
15-20seconds.

Why, why, why?????

Also, forgetting __GL_SYNC_TO_VBLANK, if I run limit, or free_run, then I
get overruns all the time?

Why is lock more stable in preventing overruns at 60Hz?

Thanks,

Christopher Dorosky
Lead Electronic Systems Engineer - Real Time Simulation, TOPSCENE
Lockheed Martin Missiles and Fire Control - Dallas
christopher.g.dorosky++at++lmco.com
972-603-2349

• Next message: Herbert Gartner: "[info-performer] pfv & stereo & multi-pipe/channel?"
• Previous message: Terry Welsh: "[info-performer] Can .flt loader throw texture coords"

This archive was generated by hypermail 2b29 : Tue Mar 04 2003 - 15:37:27 PST

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.