[Foil]

Hey, everybody.  This is my first post here, although I've been involved over at PlanetDescent and the DescentBB for a while.

I just recently installed Freespace and Silent Threat on my new box (P4 2.8GHz, WinXP, ATI x300 card with newest drivers).  I installed Freespace first, then Silent Threat, then patched to the most recent version (1.4, if I remember correctly).

Everything works beautifully, but I'm having problems with the afterburner in-game.  When I hit/hold the afterburner button, I immediately get the winding-down "afterburner-used-up" sound (or at least it sounds like it), and no speed boost whatsoever.  This is really frustrating.

The button I have bound to the afterburner is button 10 (down by the throttle control) on my MS Sidewinder Precision-Pro.  I've checked the button, and it's working fine according to the Control Panel properties.

I'm guessing that this could be some kind of framerate issue...

Any suggestions?

[Edit: Oh, and I've also tried the FS2 demo (patched to most current), and I get the exact same problem.]

[phreak]

run in Win98 Compatibility.

[Ghost]

Just use default like the rest of us. Tab= best afterburner position in any flight game. If that still don't work, then follow Phreak's advice.

[karajorma]

Hmmm. Just noticed that my FAQ only had the explaination in the FS2 section

The afterburner/energy transfer system has stopped working. I hear the sound but don't go any faster. What can I do?

This had many people purplexed for a while but turned out to be due to a bug in the FS2 code. All the cases I've seen of it so far have occured on Windows XP or Windows 2000. The problem can be solved for XP users by running FS2 in compatability mode. Open up your Freespace folder and look for FS2.exe. Make a short cut for this file and position it wherever you like (Desktop or Startmenu). Right click on icon and choose properties. Click on the Compatability tab and choose which ever mode you like (I've heard that Windows 95 works best but you might find otherwise). Use the icon to run FS2 from now on.
Since Windows 2000 lacks compatability mode I'm not certain how to solve the problem there. But running FS2_Open will also fix this problem as the bug has been corrected.

That pretty much applies to FS1 too. Just change the file names.