In 99 percent the lockup happens at approach and touchdown, with a high rate of wav-files being played: Numerous Air Traffic Control- and AutoPilot-wavs. In addition there are many wavs which simulate engine- and general environment-sounds.
At approach I get some minor and (really) unnoticable lock-ups, but at landing - and when engaging the reverse thrusters (playing thrust reverser-wav) the system halts for 1/3 second. This happens in 99 percent of the tests I've done.
To solve my problem, I have tried to edit the wav-files into smaller sizes, adjusted hardware acceleration, installed latest drivers, and optimized my system.
I have the same software installed on another machine - AMD 1.3 Ghz, with 356MBRam. I never get the system lock-ups there, but I guess it is due to higher Ram.
So - what can I do to avoid this lockup, which really is a major problem when trying to simulate reality. The general approach is smooth and fine with 15-16 fps. When getting a 1/3 second sytem halt at touchdown, it is really a major setback for the overall feeling of realism.
Ø. Jensen, Oslo, Norway
<P ID="edit"><FONT SIZE=-1><EM>Edited by Mr767 on 02/14/02 05:39 AM.</EM></FONT></P>
If you are only getting 13-16 fps on a game, I would highly recommend you lower your detail settings or buy a better graphics card. I do not believe that it is a sound problem as the SB can handle anything that Flight Simulator 2002 can throw at it. Try lowering your detail settings or screen resolution to the lowest setting and then, If you still are having problems, go to the graphic cards section and ask for their advice. When a game gets below 13fps, it very likely will freeze. With the processor that you have, I would recommend the Radeon 8500 or a normal Geforce 3 to power your games, I think you will see a huge improvement in performance over you Geforce MX.