Hi,
On Freitag 04 März 2005 16:20, Curtis L. Olson wrote:
I know this is hard to do with standard system level calls. For
instance setitimer() in unix allows you to specify a very fine
resolution sleep/wakeup time. However, the OS only checks the thread
during a kernel interrupt which
Drew wrote:
Hey All,
I'm running flightgear on Windows, and have noticed that it seems to
use up all of the available processing time, and because of this, it
seems to get jumpy when other applications are being used while
FlightGear is running. I noticed that I can try to bump up the
priority of
Quoting Erik Hofman :
Drew wrote:
Hey All,
I'm running flightgear on Windows, and have noticed that it seems to
use up all of the available processing time, and because of this, it
seems to get jumpy when other applications are being used while
FlightGear is running. I noticed that
Frederic Bouvier wrote:
There is the property /sim/frame-rate-throttle-hz that could be used to limit
the framerate but the source should be modified to call a system sleep method (
with a fine resolution, for example pthread_cond_timedwait ) instead of looping
wildly.
I know this is hard to do
Erik Hofman wrote:
Drew wrote:
Hey All,
I'm running flightgear on Windows, and have noticed that it seems to
use up all of the available processing time, and because of this, it
seems to get jumpy when other applications are being used while
FlightGear is running. I noticed that I can try to bump
Curtis L. Olson wrote:
Frederic Bouvier wrote:
There is the property /sim/frame-rate-throttle-hz that could be
used to limit the framerate but the source should be modified
to call a system sleep method ( with a fine resolution, for
example pthread_cond_timedwait ) instead of looping
Quoting Andy Ross:
* Hopefully in a CPU-friendly way. I know that older versions of
the NVidia drivers did this by spinning in a polling loop
inside the driver. I'm not sure if this has been fixed or not.
From my experience, the latest non-beta Windows NVidia driver seems to eat CPU
There is the property /sim/frame-rate-throttle-hz that could be used to limit
the framerate but the source should be modified to call a system sleep method
(
with a fine resolution, for example pthread_cond_timedwait ) instead of
looping
wildly.
-Fred
Just tried this, and I can make it
Frederic Bouvier wrote:
Quoting Andy Ross:
* Hopefully in a CPU-friendly way. I know that older versions of
the NVidia drivers did this by spinning in a polling loop
inside the driver. I'm not sure if this has been fixed or not.
From my experience, the latest non-beta Windows NVidia
Frederic Bouvier writes:
Quoting Andy Ross:
* Hopefully in a CPU-friendly way. I know that older versions of
the NVidia drivers did this by spinning in a polling loop
inside the driver. I'm not sure if this has been fixed or not.
From my experience, the latest non-beta Windows
Hey All,
I'm running flightgear on Windows, and have noticed that it seems to
use up all of the available processing time, and because of this, it
seems to get jumpy when other applications are being used while
FlightGear is running. I noticed that I can try to bump up the
priority of
To: FlightGear developers discussions
Subject: [Flightgear-devel] Making FlightGear more deterministic
Hey All,
I'm running flightgear on Windows, and have noticed that it seems to use
up all of the available processing time, and because of this, it seems
to get jumpy when other applications are being used
12 matches
Mail list logo
