Up: SGI performer Frequently Asked Questions (FAQ)
Next: -62- 1.2 Bug Billboard normals and intersections
Previous: -60- 2.0 Bug pguide/libpf/C/lpstate sample program
Subject: -61- 2.0 Bug pfInitClock() and Video Rate on 250MHz IMPACT
Date: 12 Dec 95 00:00:01 EST
The clock period determined by pfInitClock() on 250MHz IMPACT
systems is apparently inconsistent with the true clock period. It
seems that the actual clock period is that of a 200MHz system.
Consequently, pfGetTime() will return a time that is .8 (200/250)
that of the true time.
Among other things, this invalidates the calculations done by
Performer to determine the current video rate.
As a workaround, you can specify an alternate clock period with the
PFCLOCKPERIOD environment variable. If set, PFCLOCKPERIOD
specifies the clock period, in picoseconds, to be used by
pfInitClock(). For proper behavior on 250MHz IMPACT systems, use
40000 for the period.
Up: SGI performer Frequently Asked Questions (FAQ)
Next: -62- 1.2 Bug Billboard normals and intersections
Previous: -60- 2.0 Bug pguide/libpf/C/lpstate sample program