If you think you have found something that's not working.........

[flyblueskies]

Further to my report above...

Letting CLIVE run the comms and he has the same exact problem. If I confirm to CLIVE that I have the runway in sight, he will transmit that we have the runway in site...however, MCE will respond by initiating Runway NOT in sight.

I hope this helps...

[FS++]

26 minutes ago, flyblueskies said:

Further to my report above...

Letting CLIVE run the comms and he has the same exact problem. If I confirm to CLIVE that I have the runway in sight, he will transmit that we have the runway in site...however, MCE will respond by initiating Runway NOT in sight.

I hope this helps...

Definitely not a speech recognition issue.

Will be looked at.

Meanwhile, Just to make sure MCE is receiving the ATC menu options as expected. Before you transmit, ask co-pilot "confirm atc options". A voice should read out aloud the content of the ATC menu (option lines only). Make sure they match and which one is where, as that's what he's expected to use for selection.

maybe because they are too similar "in sight", "Not in sight" is getting him confused and will require adjustment on MCE side..

[flyblueskies]

"Before you transmit, ask co-pilot "confirm atc options"."

 

Ok,

 

When I confirm ATC options, it reports two separate options for position 2 (position two). It reports back:

1. Request vector to next waypoint

2.  Select a new ifr destination

2. Report runway in sight

3. Report Runway not in sight

4 [SELECT ANOTHER APPROACH]

5. Cancel IFR

 

NOTE: I've noticed the double meaning with position 2 on other CONFIRM ATC OPTIONS as well. It would report Select a new IFR destination (even though it was not displayed) along with the correct displayed option.

Edited December 29, 2021 by flyblueskies

[FS++]

21 hours ago, flyblueskies said:

"Before you transmit, ask co-pilot "confirm atc options"."

 

Ok,

 

When I confirm ATC options, it reports two separate options for position 2 (position two). It reports back:

1. Request vector to next waypoint

2.  Select a new ifr destination

2. Report runway in sight

3. Report Runway not in sight

4 [SELECT ANOTHER APPROACH]

5. Cancel IFR

 

NOTE: I've noticed the double meaning with position 2 on other CONFIRM ATC OPTIONS as well. It would report Select a new IFR destination (even though it was not displayed) along with the correct displayed option.

That explains it 🙂

He;s intent on selecting the second option (report runway in sight) as he should, but hitting the wrong one because of the invisible intruder line (select a new ifr destination).

Needless to say, will be looked at.

Edited December 30, 2021 by FS++

[flyblueskies]

Thanks Gerald!

I've noticed with IFR flights, there are other hidden second options. I'll try to report them as I find them...

[flyblueskies]

Good morning (here) Gerald,

I have another IFR flight plan double position 2 ATC options:

 

1. Request Vector to next waypoint

2. SELECT ANOTHER IFR DESTINATION (HIDDEN!!)

2. SELECT ANOTHER APPROACH

3. Cancel IFR

 

 

Edited December 30, 2021 by flyblueskies

[FS++]

On 12/17/2021 at 9:32 PM, deltgam88 said:

Beech B58

1. Ask FO to set altimeter to "29.95" or any setting and it sets to "27.99"

 

Get the patch

Manually replace files as pe folder structure. baro dialling should be fixed

[FS++]

On 12/30/2021 at 1:52 PM, flyblueskies said:

Good morning (here) Gerald,

I have another IFR flight plan double position 2 ATC options:

 

1. Request Vector to next waypoint

2. SELECT ANOTHER IFR DESTINATION (HIDDEN!!)

2. SELECT ANOTHER APPROACH

3. Cancel IFR

 

 

Should be fixed in latest patch

[flyblueskies]

4 minutes ago, FS++ said:

Should be fixed in latest patch

Thanks Gerald!

Will check it out and report back!

[flyblueskies]

I wanted to get back and provide feedback on the latest patch. It's working well, but to be honest, it seems the latest MSFS 2020 does not have any of the double (hidden) options...at least I have not been able to find them.

So, I have not been able to test against the hidden options.

But, so far, so good!

[FredFF]

I use MCE with native MSFS ATC; AI ATC Voices is turned off in MSFS and MCE copilot handles the ATC. When I ask for instance for touch and go, my MCE copilot initiates the request with ATC. But the answer to ATC is given by both my MCE copilot and the MSFS copilot (whoch should be turned off). Is it a known bug or am I missing something ? Thank you 

[FredFF]

53 minutes ago, FredFF said:

I use MCE with native MSFS ATC; AI ATC Voices is turned off in MSFS and MCE copilot handles the ATC. When I ask for instance for touch and go, my MCE copilot initiates the request with ATC. But the answer to ATC is given by both my MCE copilot and the MSFS copilot (whoch should be turned off). Is it a known bug or am I missing something ? Thank you 

I mean the msfs pilot voice rather than the msfs copilot voice

[FS++]

1 hour ago, FredFF said:

I mean the msfs pilot voice rather than the msfs copilot voice

Understood.

Users should ask Asobo to provide an option to mute co-pilot voice for this type of scenario..

[ayousry]

Hello 

am new to mce for msfs2020 and as i enjoy it so much , i have an outstanding issues

1- i dont have cabin crew voices or interaction at all

2-vox script saving is very random , sometimes it saves what i edited and sometimes not , and if i edited the Vcr flow file in notepad and saved it , next time i run mce , it randomly changes my edits

3-sometimes the copilot excutes random action although am not talking at all (most common is changing ADF freq) 

4-when fo checking chk items , sometimes it get it wrong and i dont know how to fix that 

foe example( bleed valves is on auto as stated in the chk , and he insists its not)

i tried to untick ‘check chk items’ option

but its as if not saved , nothing changed

Am using the aerosoft crj exclusively 

 

thanks

[djxmdjxm]

Hi everyone, 

thanks to FS++ for this great piece of work that I now could get to work decently with MSFS (a reinstall with both main install and patch helped to detect the correct aircraft). 

I have noticed a few few glitches with the Flybywire A32NX (experimental build (!)): 

The following switches do not work for me: 

• "retract landing lights" doesn't switch
• "nose switch to takeoff" (T.O.) - not recognized - cannot switch to takeoff setting at all
• dome light dim / brt / off - does not do anything
• emergency exit lights is reversed (ON is OFF | OFF is ON)
• NAV & LOGO lights settings "2", "1" and "OFF" (turning OFF doesn't work)
• WIPER is reversed (FAST is SLOW | SLOW is FAST)

If this is normal with the experimental build then ignore me. But it actually works quite well. 

I'm running MCE on v2.9.61

Thanks for looking into it!

Edited April 8, 2022 by djxmdjxm