6 hours ago, CaptainPrecious said:

While you're at it - is there an option to stop FO asking about runway in use? I tell him and he says roger and 30 sec later he asks again...

Maybe unexpected verbiage.

How do you tell him the runway in use when prompted?

 

4 hours ago, FS++ said:

Maybe unexpected verbiage.

How do you tell him the runway in use when prompted?

 

Tried various things:

"one eight"

"eighteen"

"runway one eight"

"runway in use is one eight"

...

and each time he replies "runway one eight". But some 30 seconds later he asks again.

My point is - I don't need that particular feature, would be cool to be able to turn it off.

Best regards

Hi, I might have a little problem. The call sign "Eurowings 1WP" isn't read back by the FO. "Eurowings 9396" is no problem. I've seen this with other callsigns with a letter in them, like "New Zealand 99P".

@FS++ What about the listening copilot while muted? Is there any hotfix yet?

1 hour ago, Alex Walker said:

@FS++ What about the listening copilot while muted? Is there any hotfix yet?

Should have new files this week.

23 hours ago, d.tsakiris said:

Hi, I might have a little problem. The call sign "Eurowings 1WP" isn't read back by the FO. "Eurowings 9396" is no problem. I've seen this with other callsigns with a letter in them, like "New Zealand 99P".

Sorry for the delay, required seeing it under the debugger.

What's happening is that when it sees a letter when it expects a flight number, it is dropping the airline name altogether and viewing it as GA traffic.

Agree, in real life you may have a single letter at the end of a flight number.

Will see what can be done in next patch.

Great, thanks!

On 5/11/2020 at 6:14 PM, Alex Walker said:

@FS++ What about the listening copilot while muted? Is there any hotfix yet?

There you go.

Download this patch

Manually replace 3 files in \Multi Crew X-Plane\ installation folder.

From now on, once you mute all MCE reco with ScrollLock (or optionally with Numlock), you won't be able to transmit to ATC or test commands in MCE Voxsript panel. 

Should get an on-screen text reminder about ScrollLock being engaged when you try to do that (visible, unless X-Plane menu covers it).

Let's hope we don't get reports such as "I tried to test a command in Voxscript and nothing's happening" 😛

 

On 5/12/2020 at 6:40 AM, d.tsakiris said:

Great, thanks!

You're welcome.

Grab the patch related to MCE and P3D or FSX

You should be able to use callsigns such as "Eurowings 1WP"

Since you're fond of Eurowings and it doesn't appear to have been recorded by various voice actors, took the liberty to translate it to "Europe wings" (it sounds close) and the Fo can utter it instead of just "one whiskey Papa"

 

4 hours ago, FS++ said:

There you go.

Download this patch

Manually replace 3 files in \Multi Crew X-Plane\ installation folder.

From now on, once you mute all MCE reco with ScrollLock (or optionally with Numlock), you won't be able to transmit to ATC or test commands in MCE Voxsript panel. 

Should get an on-screen text reminder about ScrollLock being engaged when you try to do that (visible, unless X-Plane menu covers it).

Let's hope we don't get reports such as "I tried to test a command in Voxscript and nothing's happening" 😛

 

@FS++ The copilot can still hear me, when scroll lock is active 😞 

18 hours ago, Alex Walker said:

@FS++ The copilot can still hear me, when scroll lock is active 😞 

Patch needs to be applied on top of very latest version.

Since MCE is running as a background app, outside X-Plane process for better simulator stability, it doesn't directly catch "ScrollLock".

It's rather "xpInsider64.xpl" plugin running inside X-Plane that does that and forwards it to MCE.

Un-install MCE via Window Control panel. Then download latest version

When done, manually replace 3 files in \Multi Crew X-Plane folder, using the supplied patch.

Other than that, if you're making heavy use of LUA scripts or automated things like that, make sure none of them triggers ScrollLock by accident.

 

5 hours ago, FS++ said:

Patch needs to be applied on top of very latest version.

Since MCE is running as a background app, outside X-Plane process for better simulator stability, it doesn't directly catch "ScrollLock".

It's rather "xpInsider64.xpl" plugin running inside X-Plane that does that and forwards it to MCE.

Un-install MCE via Window Control panel. Then download latest version

When done, manually replace 3 files in \Multi Crew X-Plane folder, using the supplied patch.

Other than that, if you're making heavy use of LUA scripts or automated things like that, make sure none of them triggers ScrollLock by accident.

 

I have version 1.5.38

Is this the latest version?

1 hour ago, Alex Walker said:

I have version 1.5.38

Is this the latest version?

Affirmative. It is AFTER you apply the patch. But need to install V1.5.3.2 from website so you have the correct files in the sim.

Go to \X-Plane\Resources\Plugins\ folder and open "xpInsider.cfg"

To make sure only "Numlock" is let through, ensure 

[OPTIONS]

CatchNumlock=0

CatchScrollLock=1

If you can't afford to use ScrollLock because of some other plugin that is hard coded to use that key, can use "NumLock" instead. In that case, use this config

[OPTIONS]

CatchNumlock=1

CatchScrollLock=0

X-Plane restart is required before changes take effect.

Edited May 14, 20206 yr by FS++

Thanks, Gerald. At least for me it seems to be working so far...

In the past there were questions about triggering flows or callouts at certain speeds / altitudes or possibly at the push of a button.

Is this technically possible to add to MCE?

On 5/14/2020 at 8:11 PM, CaptainPrecious said:

Thanks, Gerald. At least for me it seems to be working so far...

In the past there were questions about triggering flows or callouts at certain speeds / altitudes or possibly at the push of a button.

Is this technically possible to add to MCE?

which specific call-outs are we talking about?