I have recently updated to Fs2 Crew Voice version 1.5. I am not sure whether I had this issue previously but I don't remember. It may be something I am doing or not doing but this is definitely very odd.

 

Everything is fine with the voice commands on the NGX737-800. However, several times now, when I am on the approach and give a speed command to lower the speed as in "set speed 150" with the A/T armed and SPEED set, the IAS/MACH indicator flactuates rapidly between 100 and top speed and often remaining at 340. If I manually try to reset it, it would go back to its highest setting or winds down to 100. At that point I would desperately unarm the AT and try and control the speed manually, often unsuccessfully for landing. Today the the HEADING command went crazy and and kept going round and round without stopping.

 

With the update, I did reinstall the NGX SP1c. It may be other processes running in the background that is causing this anormality. However since this problem occurs mainly with the SPEED command, (today though the HEADING had a mind of its own as well) I am reluctant to blame this on other programs.

 

At most times, Fs2 crew behaves nicely and I am very happy with it. However this latest problem is very frustrating. Does anyone know how to totally disable FS2Crew while flying the NGX if one needs to? I couldn't find it under processes in the Task manager.

 

Thank You,

 

Charles Macelli

Hi Charles,

 

You can always use the speech phrase: "CANCEL LAST COMMAND" to deal with runaways like that.

 

Also, make sure when you're making voice commands that you use the correct syntax as described in the manual.

 

Say the numbers individually... "one three zero".... don't say " one thirty".

 

And run the voice training again.

 

Best,

Hi Charles,

 

You can always use the speech phrase: "CANCEL LAST COMMAND" to deal with runaways like that.

 

Also, make sure when you're making voice commands that you use the correct syntax as described in the manual.

 

Say the numbers individually... "one three zero".... don't say " one thirty".

 

And run the voice training again.

 

Best,

I will remember that especially the "cancel last command" command which I had entirely forgotten. I wish though that there is a way to totally disengage Fs2Crew entirely from FSx, not merely muting the microphone (HM) in cases like this when the FO appears intoxicated.

You can also press the "VOICE" button to effectively shut-down FS2Crew.

 

But there are safeguards in the program to prevent runaways like you described, so I'm not sure how you're even getting them, especially if you're using the correct syntax.

 

If you ever get a runaway again, please send me your speech CVR log so I can see what you said.

 

The Log is available via the Config Manager.

 

Another though... are you putting a lot of pressure on your system... what are your frame rates like?

I get them to even saying the numbers one by one. FSCrew if very finiky. I just got a CTD with it as soon as I said the command, "set heading one eight zero" bam...CTD. Sucks

You shouldn't get CTDs with FS2Crew.

 

CTDs can come from multiple sources, and from experience 3rd party scenery is often the source.

 

A lot can be cured by moving your sliders a little to the left.

 

Also, run the voice training and check your mic settings.

 

FS2Crew voice commands are not finicky in my experience.

 

Simconnect is finicky, but not the speech commands.

I AM using the correct syntax and regarding the pressure on the system, it may be that I was multitasking at the time (can't remember) and another program might have upset Fs2Crew. My system is pretty powerful at 12 GB RAM and an i7-980 processor. Still, the frame rates, with the 737NGX are normally between 25-30, slightly less on the ground .

 

The runaway with the speed occured at least twice and at the time I had absolutely no control on the speed settings even if I manually turned the dial. The only option was to disengage the AT but often too late to regain control of the plane. The Heading also went beserk, just once and kept going round and round after I gave a "set heading to xxx". But this only happened once and kept going even when I landed the aircraft and it was stationary.

 

Thanks, I will certainly send you the log next time this occurs. I have flown several times since then, with no problem whatsoever.

 

I appreciate the replies from all.

 

Charles Macelli VATSIM 817692

If it only happened a couple times, I wouldn't worry about it.

 

You can always use the command "CANCEL LAST COMMAND" if it ever happens again.

 

The NGX is programmed so you should never get a runway, so I'd be interested to see how you somehow triggered it in those couple instances.

 

Cheers,

I get the run away speed commands a lot with your program regardless if you think we can or not. And I am using the correct syntax, "set speed one three zero". As well I temporarily lost manual control of the speed dial.

 

The CTD happened after I said, "after takeoff checklist", the f/o started his flows but before he started reading back the checklist flow to me, I said set heading one eight zero. Bam, CTD.

 

Sent from my Samsung Galaxy Note 2

Eric,

 

Hate to pass the buck, but it sounds like you have system problems.

 

If you get a runaway speed, please email me the CVR log so I can see how you triggered it, but I've personally never had one in the NGX version.

 

Again, you can stop any runaways using the command "Cancel last command".

 

 

If you get a CTD, pls do this:

 

1. Run "Event Viewer"... google it if you you're not familiar with it.

2. You'll see what's associated with the CTD... like 'uiautomationcore', etc.

3. Google what you find.

4. You'll probably find a solution.

 

 

From experience, most CTDs can be solve by:

 

1. Installing Pete Dowson's FSUIPC.... it helps solved the GDI error a lot FSX users get.

2. Install UIAutomationcore into your FSX folder. Google it.

3. Move your sliders and LOD down a notch. Some people are just pushing FSX way too hard... some modern day 3rd party scenery can really tax FSX. The're mega detailed... very graphic intensive, but there's a price... they eat up tons of resources.

4. Run ******* Bojoto's FSX tweaker... the himem fix is important.

5. Update all drivers.

6. Check your hardware.. maybe it has problems (dust, etc). Or viruses, etc.

 

 

Finally, please sign your posts with your real name or PM me if you don't want your real name used.

 

 

Thanks,