Bernard Leclerc (bleclerc++at++cae.ca)
Fri, 15 Nov 1996 16:51:08 -0500
Assuming
a) pfFrame() will call pfSync() if you don't do it.
b) pfSync() will call pfAppFrame() if you don't call it explicitly.
It turn out the main simulation loop should look like this:
while (!done) {
...
pfAppFrame();
...
pfSync();
...
pfFrame();
...
}
The two previous assumptions are based on the man page pfFrame(3pf). Here
are two excerpts:
pfFrame will automatically call pfSync if the application did not
call
pfSync before calling pfFrame. This means the application need not
call pfSync.
If pfAppFrame is not invoked directly, pfSync or pfFrame invokes it
automatically.
It's not clear whether pfAppFrame() gets called from pfSync() or
pfFrame().
My interpretation is pfFrame() calls pfSync() if you haven't done it. And
pfSync() calls pfAppFrame() in you omit to do it.
If you have nothing to do between these calls, the main simulation loop
can be simplified to
while (!done) {
...
pfFrame();
}
I'm asking about the ordering of these 3 particular functions because I
need to understand what are the critical factors in maintaining the
latency to a minimum.
Now the question: can the Performer team confirm what is the correct
ordering of these 3 function calls in the main simulation loop?
Again, thanks in advance pfBuddies.
--
Bernard Leclerc CAE Electronics Ltd., 8585 Cote De Liesse
Technical Leader Saint-Laurent, Quebec, Canada, H4L-4X4
3-D Graphics Applications tel: +1 514 341 2000 extension 2275
bleclerc++at++cae.ca fax: +1 514 340 5496
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:53:57 PDT