Won't Restart Beechcraft Baron

[Goofeyfoot]

If I tell the copilot to shut down the engines, then tell him to autos tart them, he doesn't do it. He says "starting engines", but he doesn't do it.

Thanks.

Michael

[Gangrel]

Will look into this. Strange as we use the API for the adjustments here, so what should disable should enable it. Is it just *this* specific command or others that you also have issue with?

[Goofeyfoot]

There are other things in this plane. If you are sitting on the tarmac and say "set altitude to 10,000 feet" you get a different number every time. Completely haphazard. I just got this thing yesterday so I'm sure there are other issues that I haven't found yet. Thanks.

[Gangrel]

When you say that you get a diffferent number every time, is the *COMMAND* recognised in the VA log window *correct*

ie: Recognised "Set altitude to 10,000 feet" but it then tries to set it to a different number

or is it

Recognised "set altitiude to <incorrect value> feet"? (Incorrect value would be what VA *THINKS* it heard)

First one would be down to us.

2nd one, would actually be a result of VA *thinking* that you said something different (but it set it to the correct value).

Potential Solutions for 2nd example:
Voice Attack Settings -> Recognition Tab
1) Take Command Weight Value down
2) Turn the Minimum recognised Confidence level Up
3) Enable/Disable Adaptive Recognition (restart required)
4) Enable/Disable Acoustic Echo Cancellation (restart required)

Voice Attack Settings -> Hotkeys
1) enable Voice Attack to listen when you have a keyboard/joystick button (need to enable and assign joystick here) held down

If all else fails, and VA is still mishearing you when nothing is said, then it could well be a case of training up a new speech recognition profile (Voice Attack settings -> Recognition -> Utilities -> Speech Control Panel -> Advanced Speech Options

[Goofeyfoot]

It recognizes what I say exactly. 6000 feet is recognized. The setting which the copilot performs is what is screwed up.

[Goofeyfoot]

...And yeah, the guy won't start the engines still. Recognizes exactly what I am saying then promptly doesn't do it.

[Gangrel]

Can you post a screenshot of your VA window when it starts up please.

This will give us some information as to if it is hooking up the SimConnect API correctly or not.

Will be looked into, but if it is hooking up the API correctly, then it should be doing it correctly (unless the plane has a quirk where some things are wired up incorrectly in the first place). But for *stock* planes these should have been accounted for in the first place. (Note: the profile should work with no issues for *STOCK* standard planes that came with the simulator. 3rd party alternatives / variations of a plane can have their own quirks which we cannot account for).

Will look into this more though for you though.

It is annoying in that we have to use a 3rd party API to do the hooking up for things, where we are (in most cases) up to the whims of the plane developer to make sure that they have stuff wired up correctly so that it reports / accepts them correctly.

Please note: That for some planes they require a check list for you to go through before the engines will be started. What command are you using to start the engines?

"Auto start the engines" should be the one that you are using if you are on the ground (there is no automated check list / guided alternative for this).

Have you tried going through the check list via voice (instead of just using the "auto start" version)?

This can help narrow down specifically what is happening / not happening correctly (A screenshot showing the commands recognised / not recognised can also help here as well)