So for like 2 weeks now after reinstalling everything as something I have been wanting to do for a while and having crew working fine. She now is throwing hissy fits for no apparent reason. Half the time I go into the sim and there is no clickspot to open it in the VC or I get an SDK error. When this happens I either have to reinstall crew or sp3 or both sometimes or sometimes I can get away with going into the manager and resetting the voice control option. Then it works for a coupe flights. Also lately the FO will not start the 2 engine. The voice display keeps thinking I am saying start number 1 but I am not. This is after starting number 1. This was working fine at first but now not so hot. I do performance testing in the NGX so allot of slewing and taking off and exiting the sim in midair lately. I don't know if that would have anything to do with it. I am following all the protocols like start in VC and all that.

 

Thanks

 

Marc

Hi Marc,

 

SDK issues:

 

Please see this thread: http://forum.avsim.net/topic/375833-big-issues-with-14/

 

 

Engine #2: What do you see in the Green Bar? Please run the voice training again.

 

 

Main Panel in VC: You've probably added extra windows to the Panel.CFG, which can result in this behavior.

 

Solution is this:

 

You can also assign a Keyboard or Joystick button to open and close the Main Panel.

 

• To create your "Toggle Main Panel" assignment, create a joystick or keyboard button assignment for 'AUTOFEATHER (ARM/OFF)' in the FSX 'SETTINGS - CONTROLS' menu
  

• You can select any Joystick or Keyboard assignment (or both).
  

IMPORTANT: Your PMDG 737 NGX

cannot

use the same key assignment for any PMDG 737 NGX Key Command function, or the Main Button will not work!

 

So, for example, if you use "C" as your keyboard assignment for the Main Button, you cannot use "C" for any PMDG 737 NGX KEY ASSIGNMENTS.

 

 

 

 

Like I said I am following all the protocols that your link says. This keeps happening every 3 flights or so for no reason. I have to reinstall sp3 or fs2crew or toggle voice in the manager. The green bar says start engine number 1 when I say start engine number 2. Engine 1 starts fine which is the first one I start allways. My voice is trained and like I was saying has been for a while, it worked fine in the beginning. If it was a voice issue it would not have worked from the start and gotten better. So I am at a loss here. I have followed all your suggestions from the beginning before I even posted here.

 

Thanks

 

Marc

Hi Marc,

 

What are you installing/changing on your system between the times it working and the times it stops working?

 

Computer code doesn't generally just break by itself; something must be changing on your system if it works, then stops working.

 

If the green bar says "start engine one" when you're saying start engine two, I'm not sure.

 

Perhaps your microphone is damaged?

 

Are you using the exact phrase:

 

"Start engine one"

 

"Start engine two"

 

 

Cheers,

hi,

 

The SDK and other issues went away so far. I am not installing anything but am using the NGX for performance testing so entails allot of exiting the sim in mid flight so maybe that screwes it up.

 

The lasting issue however is that he never responds to start engine 2. I have to do that and the after start flow for him and manually set the UI to the next step. He does everything else perfectly just not this one thing. And this is after many many times where he would start number 2 flawlessly. I have not changed the procedure at all so I have no idea. The dialog green bar allways says start engine 1 when I say start engine 2. He starts engine 1 just fine and that is the first one I start. This is a pretty imprtaint part and it's got to be something. It worked before and like SO many things in FSX just mysteriously stop working after a while like the ghost in the machine. Can you help with this at all. It will probably start working again by itself just by you responding. :Idea:

Hi Marc,

 

Glad you made progress.

 

For "Start Engine Two": Make sure you say the phrase clearly and distinctly. Try saying it with an American accent if you're not American.

 

You can also try this method:

 

http://forum.avsim.n...ords-like-auto/

As you are starting No 2 AFTER No 1, that implies you are doing an External Air Start rather than an APU start.

 

Are you sure you are following all the dialogue steps and ground-crew flow items properly? I only ask because I had exactly this problem yesterday and it was me at fault, not FS2Crew. I just wish I could remember specifically where I'd gone wrong [failing to wait for the go-ahead to start the 2nd engine from the ground-crew probably].

His problem is a speech recognition issue since he can't get "start engine two" to appear in the green bar.