From: Damien Gerhardy (damien.gerhardy++at++sydac.com.au)
Date: 02/19/2006 18:16:16
Using the latest windows version of Performer (3.2.1) do you still
have to set PFCLOCKPERIOD?
I have a 2.4 GHz processor (dual xenon) and if I dont set it performer
indicates its using a PFCLOCKPERIOD of a huge negative number.
So I try setting the value correctly.
Given:
1 second = 1'000'000'000'000 pico seconds
2.4 GHz = 2'400 MHz = 2'400'000 Hz
PFCLOCKPERIOD = (1 / (2'400'000)) / (1'000'000'000'000)
= (1'000'000'000'000) / (2'400'000)
= 416'666.6666..
However, if I set PFCLOCKPERIOD=416666 performer will often lock up.
Performer will run for a while but once I start loading all of the
models and placing them in the world it seems to go in an infinite
loop inside pfFrame and never returns (using 100% of one of the CPU's).
If I set PFCLOCKPERIOD to a different number it fixes the problem.
I accidently set PFCLOCKPERIOD to the clock frequency before
(ie: 2400000000000) when I wasn't sure what I was doing and everything
seems to load ok.
So...
1) Do I still have to set PFCLOCKPERIOD on Performer 3.2.1?
2) Am I calculating PFCLOCKPERIOD correctly?
3) Why is pfFrame never returning?
Thanks
-Damien
Damien Gerhardy
SYDAC Pty Ltd
Simulating a Better Reality
113-115 King William Street
Adelaide, SA, 5000
Australia
tel: +61 8 8239 3600
fax: +61 8 8212 0334
damien.gerhardy++at++sydac.com.au
Caution - This e-mail and its contents contain privileged information that
is intended solely for the recipient. If you are not the intended recipient
you are hereby notified that any use, dissemination, distribution or
reproduction of this e-mail is prohibited. If you have received this e-mail
in error please notify the Postmaster at sydac++at++sydac.com.au immediately. Any
views expressed in this e-mail are of the sender and may not necessarily
reflect the views of Sydac Pty Ltd.
This archive was generated by hypermail 2b29 : Sun Feb 19 2006 - 18:26:17 PST