MCE PF3 TFDI 717 Fo does not acknowledge receipt

[DrumsArt]

Hi,

First, I know that the Tfdi B717 is not yet interfaced with MCE.

Is this the reason why the FO with this aircraft does not acknowledge receipt of messages from the Atc (Clearance, Ground, Tower, Center and so...) ?

I thought there might be a problem with some callsigns. This is not the case since other planes with the same callsign work perfectly...

If I request to FO to contact Center, he does the job. Confirm Atc options works too. The FO changes Freqs and Squawk very well.

The FO works perfectly with other aircraft including some that are not interfaced.

P3Dv4.1, MCE v2.7.4.2, PF3 v3.7.2

Thank you and Regards,

[FS++]

59 minutes ago, DrumsArt said:

Hi,

First, I know that the Tfdi B717 is not yet interfaced with MCE.

Is this the reason why the FO with this aircraft does not acknowledge receipt of messages from the Atc (Clearance, Ground, Tower, Center and so...) ?

I thought there might be a problem with some callsigns. This is not the case since other planes with the same callsign work perfectly...

If I request to FO to contact Center, he does the job. Confirm Atc options works too. The FO changes Freqs and Squawk very well.

The FO works perfectly with other aircraft including some that are not interfaced.

P3Dv4.1, MCE v2.7.4.2, PF3 v3.7.2

Thank you and Regards,

The ATC feature should be independent of aircraft.

Acknowledgments of clearances is mainly driven by ability for MCE to see those "closed captions" and whether FO has the COMMs or not.

Id FO able to dial VHF 1 and Transponder code with that aircraft? It is expected, even on non-fully supported aircraft, as plane developers rarely if ever use custom variables for these. And why should they.

 

[DrumsArt]

6 hours ago, FS++ said:

The ATC feature should be independent of aircraft.

Acknowledgments of clearances is mainly driven by ability for MCE to see those "closed captions" and whether FO has the COMMs or not.

Id FO able to dial VHF 1 and Transponder code with that aircraft? It is expected, even on non-fully supported aircraft, as plane developers rarely if ever use custom variables for these. And why should they.

 

Thank you for these clarifications.

Now what can prevent MCE to see those "closed captions" knowing that FO has communications, specially with this aircraft ?

The symptoms are similar to those I met here :

Where you finally found 2 bugs :

"We finally got to the bottom of this elusive issue.

There were actually 2 bugs.

One caused by MCE looking in caption for messages that start with "Cessna Golf Bravo Alpha Foxtrot Mike" or "Roger Cessna Golf Bravo Alpha Foxtrot Mike", when PF3 was displaying them as either "Cessna Golf Bravo Alpha Fox-trot Mike" or "Roger Cessna Golf Bravo Alpha Fox-trot Mike", causing the FO to see these as intended for other traffic (different call sign).

The other bug is too technical to explain. Let's just say, it was causing the FO to "occasionally" drop an acknowledgment and appearing to only have received previous one.

Anyway, this patch (V2.7.1.7) wil get you going.

IMPORTANT: The patch above is a single manual file replacement. It assumes you already have installed latest release package V2.7.1.6

Needless to say, the package on website will be updated ASAP.

Happy flying all."

I do not think/know the reasons are the same, but again my FO transmits my requests but no longer responds to ATC...So, it seems there is a "glitch" somewhere.

Thanks and Regards,

 

 

[DrumsArt]

Ok, think I found the problem...MCE FO does not accept Call-sign with letter...

Example :

-Jetstar "JS33" (Juliet Sierra three three)>>>No FO acknowledge receipt.

-Jetstar "33" (three three)>>>FO acknowledges receipt like expected !

Thanks and Regards,

[FS++]

1 hour ago, DrumsArt said:

Ok, think I found the problem...MCE FO does not accept Call-sign with letter...

Example :

-Jetstar "JS33" (Juliet Sierra three three)>>>No FO acknowledge receipt.

-Jetstar "33" (three three)>>>FO acknowledges receipt like expected !

Thanks and Regards,

I think "Jetstar JS33" is an invalid call-sign for an airliner. It should be "Airline_Name + Flight_Number" 

 

[DrumsArt]

37 minutes ago, FS++ said:

I think "Jetstar JS33" is an invalid call-sign for an airliner. It should be "Airline_Name + Flight_Number" 

 

So, what are the valid or invalid call sign ? I have the same problem with No Airline + for example JS or whatever  + Flight Number...

Regards,

[FS++]

14 hours ago, DrumsArt said:

So, what are the valid or invalid call sign ? I have the same problem with No Airline + for example JS or whatever  + Flight Number...

Regards,

Go to ATC tab in MCE user interface and check what call-sign MCE is seeing. "Jetstar three three"??

A good call-sign for an airliner "Jetstar 33", "Jetstar 4356". "Airline_Name + up_to_four_digits_flight_number".

In real life, sometimes a single letter can be appended at the end. "Speedbird 4325 Bravo" for example