4 minutes ago, DrumsArt said:

Do you run it with the new PF3 update ?

Regards,

Actually I'm still on the last PF3 Beta 3.4.8 (which should be similar to the 3.5 release version though - but you never know, I will update PF3 for my next flight).

Can I confirm that you mean the PF3 Auto mute must be now checked? am I reading the comment below correctly?

"After running tests with extreme traffic at Heathrow, it's obvious there is no way one can do without that PF3 mute key.

Therefore, from now on, MCE will ensure the option (Hotkey 22) is always enabled."

Maybe once all the dust settles with the latest updates and new releases we could have a standard setup document produced to confirm what we actually need to activate or deactivate to get MCE and PF3 to interface correctly. So far I am just trying to piece the installation together from snippets of posts. 

Rob

I think with "PF3 mute key" the PF3 PTT hotkey (which suspends AI chatter for the given time) is meant.

The Automute function of PF3 (which suspends the PF3 pilot's voice) should be irrelevant for use with MCE now because the pilot's voice in PF3 is set to "None" anyway.

 

16 minutes ago, RALF9636 said:

I think with "PF3 mute key" the PF3 PTT hotkey (which suspends AI chatter for the given time) is meant.

The Automute function of PF3 (which suspends the PF3 pilot's voice) should be irrelevant for use with MCE now because the pilot's voice in PF3 is set to "None" anyway.

 

My understanding, the Mute key also tells PF3 to refrain from transmitting for the pre-set duration.

Right now, when FO makes a transmission, he starts by sending a PF3 Mute Hotkey, and there should be no interference from AI or controller for the next 12 seconds (default).

 

7 minutes ago, FS++ said:

My understanding, the Mute key also tells PF3 to refrain from transmitting for the pre-set duration.

Is that the PPT mute, or the Auto Mute that you need to use the tick box your referring to? This is where it gets confusing

Rob

4 minutes ago, FS++ said:

My understanding, the Mute key also tells PF3 to refrain from transmitting for the pre-set duration.

Right now, when FO makes a transmission, he starts by sending a PF3 Mute Hotkey, and there should be no interference from AI or controller for the next 12 seconds (default).

 

Correct. And that works fine now with the latest version.

 

To make it clear: The PF3 hotkey 22 you are talking about is called "PTT hotkey" in PF3 - in fact it really is a "Mute key" as you name it. But it has nothing to do with the "Automute" function of PF3.

When requesting a clearance to final Approach at pilot's discretion the FO says "... requesting clearance to". The end of the phrase is missing.

The respond from Tower was a clearance for touch and go. So instead of hotkey 1 apparently hotkey 5 was sent.

 

1 hour ago, Helix1250 said:

Is that the PPT mute, or the Auto Mute that you need to use the tick box your referring to? This is where it gets confusing

Rob

Hotkey 22 must be enabled.

Under heavy traffic conditions, it's almost impossible for FO to transmit without being interrupted midway. Enabling hotkey ensures Fo can use it (best to use Caps Lock), and keep PF3 quiet for the duration of the transmission.

Don't know what the Auto-mute does.

 

11 minutes ago, FS++ said:

Don't know what the Auto-mute does.

 

As i said above. It suspends the PF3 pilot's voice when the PF3 PTT hotkey is pressed right before another PF3 hotkey.

It was needed with the old MCE to switch between talking to ATC yourself - by pressing the MCE PTT button (so you don't want to hear the PF3 pilot's voice) and have your FO talk to ATC - for example with a voxkey command via MCE (so you needed the PF3 pilot's voice to hear him talk).

 

It is not needed anymore with the new MCE, because now we have the MCE FO voice talking to ATC and can set the PF3 pilot's voice to "None".

 

22 minutes ago, FS++ said:

Hotkey 22 must be enabled.

Under heavy traffic conditions, it's almost impossible for FO to transmit without being interrupted midway. Enabling hotkey ensures Fo can use it (best to use Caps Lock), and keep PF3 quiet for the duration of the transmission.

Don't know what the Auto-mute does.

 

Thanks for the reply, I'll change my PTT key to caps lock for tonight's flight. 

Cheers Rob

The FO seems to forget his duties from time to time. Whereas he handles ATC fine most of the time, sometimes he stops responding to ATC. When I say "you have ATC" again, he starts working again.

 

He also misses some frequency changes. He did not change from Approach to Tower but contacted "Tower" anyway - on the Approach frequency. The same after landing: He did not change to Ground frequency but asked for Taxi to Gate while still on Tower frequency (strangely enough the PF3 Tower gave the taxi clearance).

 

Not sure if MCE meanwhile also might have caught some sound and falsely recognized it as "I have ATC". I noticed that happened now and then. Maybe the switch of the ATC duties can be made critical commands that need confirmation?

 

Quote

The FO (in "You have ATC" - mode) still contacts Tower for landing immediately after being told to contact Tower when established - even though still far away from final.

 

Quote

I did not succeed in making my FO ask for landing clearance in "I have ATC" mode. I said "request landing clearance" but he requested "we like to starter engage engine". I tried that several times - everytime with that result. I had to manually press hotkey 1 to get landing clearance.

 

Both problems persist.

I would appreciate very much if this would be moved up on the list because it really spoils every approach for me.

 

On 6/12/2017 at 10:28 PM, RALF9636 said:

 

 

Both problems persist.

I would appreciate very much if this would be moved up on the list because it really spoils every approach for me.

 

Should be sorted in this patch V2.7.1.5

Lets hope that's a couple of the irritating things of your list RALF9636 :)

On 12/06/2017 at 2:34 AM, DrumsArt said:

With this last patch the FO transmits my requests but no longer responds to ATC, he does not automatically change the frequencies or squawk when Atc responds.

My hotkey is to <Caps Lock>

Use Closed Caption mode checked

Auto Mute checked

Btw, there is a new PF3 update but I doubt it has anything to do with the problem. So, just in case, below some lines from the Pdf concerning MCE + PF3 :

"ADDED support for using MCE's FO - Obviously if you don't use MCE this will mean
nothing to you. If you do use MCE this might mean something to you but it won't
actually work with MCE until they make any necessary changes to their code. A new
file will now be created in your main PF3 folder named PF3_MCE.INI, within which
there will be three entries - Active=0, Logged=0 and PF3Transmitting=0. The first
entry 'Active' is off by default so you need to change it to read Active=1. Once
actiaveted PF3 will write certain ATC messages to a new file named 'Clearance.log'
within the PF3/Logs folder and this is what MCE will use instead of you having to
activate PF3's Closed Caption feature. You can have that feature enable too if you
wish but some users prefer no to but still wish use the new MCE feature which uses
their FO voice to talk with PF3's ATC. The other two entries are for MCE use only and
you will have no need to change them at all."

Thank you and Regards,

 

Hi,

I have always the problem described above in my previous post. I deinstalled Mce, reinstalled the 2.7.0.6 version and patched it with the 2.7.1.5 version. The problem persist for me. Please any idea what happens ?

Thank you and Regards,