Make sure you turn the HS (headset) button off before you close out FSX or it hangs. It must only happen with certain USB headsets or soundcards since not everybody has the issue.

 

Hmmmm....I leave my HS button on and FSX doesn't hang on shutdown for me.

 

Maybe as you say it's hardware specific.

I know this is an old topic somewhat but I had the same issue and figured out what was preventing FSX from shutting down.

 

Make sure you turn the HS (headset) button off before you close out FSX or it hangs. It must only happen with certain USB headsets or soundcards since not everybody has the issue.

 

Perfect, Ill try that!

I tried it last night, turned off the HS button before shutdown and voila, FSX closed without issues...

You might be on to something here.)

Glad it worked for you. Took me a few months to figure the issue out. Now if I just the FO to control the speed without running away with it I'd be happy still trying to figure that one out.

 

About to buy the new multiset Bryan just released with the discount. Looking forward to voice in the J4100.

Hello Nigge - I have from time to time the same issue but use GA planes and no headphones on the fsx computer. So it must be a fsx / addon caused issue. For my setup the suspect is RealityXP who have produced a fix for their product which mostly fixes the problem. If I exit FSX in a hurry and immediately go to another window it seems more prevalent.

 

To save having to reboot - CTRL ALT DEL for windows task manager then click on the PROCESSES tab find fsx app and stop it.

 

For the record I use windows 7 64bit on an overclocked 2700K with 8gb memory.

 

Gordon

I just the FO to control the speed without running away

 

If you ever get a runaway, use the command: "CANCEL LAST COMMAND".

 

That'll stop the FO in his tracks.

 

It's useful if you say, for example, "set speed 190" but somehow the speech system hears something like "set speed 290".

 

Ensure you're using the correct syntax for autopilot commands.

Confirm.

I have had no trouble at all since switching the HS button to off before closing FSX.

I use a Microsoft USB headset.

Hmmmm, weird one.

 

Good news is I'm now able to reproduce this, which means I can easily address it.

 

In the next update, which will probably come out the same time as Emergency NGX! (hopefully very soon!), I'll address this issue.

 

Cheers,

I just fixed it.

 

In the mean time, if this ever happens you, just ensure the HS (heaset) button on the FS2Crew Main Panel is "off" before shutting down flightsim.

I just fixed it.

 

In the mean time, if this ever happens you, just ensure the HS (heaset) button on the FS2Crew Main Panel is "off" before shutting down flightsim.

 

Hello Brian,

 

I have this anoying problem too, Where is the the fix????

 

Do I have to download a new installer also for Emergency NGX

 

 

Regards Robert

I have this anoying problem too, Where is the the fix????

 

Do I have to download a new installer also for Emergency NGX

 

If you have Emergency NGX, you have the latest version.

 

If FSX is hanging when it's shutting down, the problem is probably coming from another addon.

 

However, it's good practice to manually turn of the HS button on the FS2Crew Main panel prior to shutdown anyway.

Thanks Bryan for your quick answer.

 

But I have this problem a long time now!

 

I also did a compleet new installation of FSX a view months ago and the problem is still there!

 

I know manually turn of the HS button works but I sometimes forget!

 

Is there no way you can make this button to reset to off postition before closing?

 

Don't get me wrong but I really do not know what could cause this other than FS2Crew.

 

I guess I have to live with it!

 

Regards Robert

 

 

Is there no way you can make this button to reset to off postition before closing?
 
Don't get me wrong but I really do not know what could cause this other than FS2Crew.

 

It's complex, but FS2Crew does actually shut HS off prior to shutdown - but computers don't all behave the same way.

 

People are running a zillion addons... it could be any of them.