From: Andreas Ekstrand (Andreas.Ekstrand++at++saab.se)
Date: 02/21/2002 06:45:17
Hi Performers!
I've got a problem with a huge post-draw (or "the time spent after
pfDraw()" as you really should call it), stretching over several
milliseconds though I don't really do anything after pfDraw() except for
drawing the statistics.
I have attached a screen dump of my statistics. The time for drawing
statistics should be included in the dotted line after postdraw, so that
couldn't be the problem. I also notice the problem (30Hz instead of
60Hz) even when I don't draw the statistics.
I'm aware of the large pre-app (or time spent before pfFrame()) and
that's something that I'm working on. But that couldn't really be
important in this issue, could it?
Now the really wierd fact: When I measure the time spent after pfDraw()
using pfGetTime() I only get some 0.03 ms! Furthermore, I get a huge
pfSync() of some 26 ms.
Does anyone recognize this behaviour? What am I missing here? I'd
appreciate any comment, suggestion or solution.
Regards,
Andreas Ekstrand
-- --------------------------------------------------------- FDM-AE Andreas Ekstrand |E-mail: Andreas.Ekstrand++at++saab.se Saab AB |Phone: +46 (0)13 - 18 40 42 SE-581 88 Linkoping |Fax: +46 (0)13 - 18 41 77 SWEDEN | ---------------------------------------------------------
This archive was generated by hypermail 2b29 : Thu Feb 21 2002 - 06:45:25 PST