FO radio transmissions not excepted by PF3

[Abcdeflijus]

Hello pilots,

 

Well, lately I have noticed, that I am having an issue with FO radio transmissions not being heard by PF3, and before I will start reinstalling everything, I thought I will  better ask if someone is experiencing something similar and knows how to cure that? Here's what's basically happening.

I am flying in P3D and MSFS, using MCE and PF3 all together. Mostly flying only two aircrafts, PMDG 737NGXu and Majestic Q400. All of the mentioned are latest versions and I always trying to keep everything up to date. Well, everything goes well, while I am still on the ground, FO does all the communications well and everything just works fine. Until I take off...

I have noticed, that very often know, almost every flight, when I am handed over to departure, center/control, I see that FO is changing the frequency on the radio, establishes a verbal connection, but it appears, that it is not heard by PF3 and I end up getting a call "Traffic at flight level XXX, squawking XXXX, contact... etc." Then FO does it again and it only works sometimes, but most of the time, I need to press 0, which is check in Hot key for PF3.

This is a little bit annoying, as I need to look after all situation and especially harder, when this happens on hand over to approach, where things are getting busy. I understand it might be issues with PF3, so it would be worth to ask Dave on his forum also, but for some reason I felt like I want to ask you guys in here, first 😊

So if anyone knows what's going on here, I would like to know it too.

Thanks in advance!

 

Viktor.

 

 

[Fighter Guy]

I posted this also in the MCE PF3 thread, but haven't received a response yet. If your PF3 was recently updated this might be the cause.

 

Hi Gerald,

 

FYI, PF3 had an update a couple of days ago and now the MCE copilot is not giving the proper frequencies when requested (i.e. ground, tower, clearance delivery). Here is one of the new changes in PF3 ver 3.17.0 that might be applicable to the problem.

"CHANGED the location where the PF3_Freqs.dat file is created. This used to be in a folder named PF3_Display which was created inside the main FS folder. However, since the PF3 Display utility no longer requires WideFS when running on a client machine this file is no longer accessed directly. Subsequently, we now create this file in the main PF3\Data folder."

 

Tony J

[Abcdeflijus]

Hi Tony,

 

Thanks for reply. Yes I also did an update on PF3 recently and your observation looks very logic.

And now as you said, I remember that I had the same situation, where for example approach said tower on 118.1, but F.O types 1118.5 instead. Obviously landing with lost communications is executed then 😊

I am sure Gerald and Dave will sort this out, just a question of time.

 

Viktor.

[d.tsakiris]

Ah...good catch. Guess one should hold off on updating PF3 this time until MCE is updated.

[FS++]

Guys.

Since integration with PF3 mostly involves fetching flight plan info, call-sign and  the hotkeys to send with FO monitoring "Clearance.log" to check last clearance and act accordingly (or ignore if intended for other traffic), I suggest you post "Clearance.log" for every flight you are having issues with. The log is where FO gets frequencies from

Be aware, for a hotkey to reach the simulator, there must not be some other add-on window stealing the focus from main simulator window.when MCE FO tries to send it

Just a reminder, unless things have changed, you need to have a "PF3_MCE.ini" (could have been reset by update) in main PF3 installation folder and deliberately set this option ON before "Clearance.log" is generated.

Active=1

Otherwise, FO won't be doing anything automatically with regards PF3. It would explain why he complies with requests to interact with ATC on ground when you ask him say "obtain taxi clearance" or "request takeoff clearance" and not doing anything when airborne.

Thanks

[BerndB]

hi Fellows, exactly this behavior by MCE i have already mentioned months ago. 

Indeed it´s related to updates of PF3 and/or MCE, for sure. But in my case all the mess started exactly at the time when pf3 and MCE where updated for MSFS compartibility. For me it seems, that the new MSFS capability messed up the functionality within p3d, as it is the case for other well working add-ons for P3D unless MSFS functionslity get´s added..

I would not blame MCE for the mess, because in my opinion it´s caused by changes of Pf3 for MSFS, where it seems the handling of the interface changed something unvovered yet. There are several other features lost since then, like that the FO reacts to traffic head-ups while in cruise. I have given up on hope this will be work again for P3D again as it was before MSFS. Since then i´am just live with the annoying constantly ignore the contact by PF3 atc on EVERY flight.

Gerald, i don´t think that lost focus is the cause, because for months now i allways refocus P3D by click into the window, before my FO transmit his request. This doesn´t help. But i´ve noticed, that sometimes, after the initial contact with atc has failed for 3-5 times and i have hit the zero key myself several times, that the FO-function of Pf3 itself get´s activated instead of MCE. But i have disabled this feature in PF3. After the PF3-FO established the contact with ATC, the voice used by the atc station has changed aswell. Very weird.

PS: I don´t have MSFS, nor it´s ever installed on my SIM yet.

Edited September 8, 2022 by BerndB

[Fighter Guy]

Gerald,

Prior to the update of PF3, the MCE would correctly enter the correct facility frequency when asked. For example when using the command "ground comm one" the copilot would dial in the correct frequency. However now that is not occurring.
I did a test from KSUS-KFNT. The frequencies listed by PF3 were GND - 121.7, CLNC - 133.1, TWR 124.75. MCE correctly inserted 121.7 for GND, however for TWR, he inserted 128.15, and for CLNC he dialed in 124.25. If I was on the wrong frequency and transmitted, PF3 would indicate being on the wrong frequency, and then the MCE copilot would dial in the correct frequency only if he has control of the radios.

This excerpt is from my clearance log:

Baron November 6 Tango Juliet loud and clear  
Baron November 6 Tango Juliet volume weak  
ComFreq: 124.25 <> ClearanceFreq: 133.1
Baron November 6 Tango Juliet cleared to Kilo Fox-Trot November Tango Climb and maintain 6 thousand expect Flight Level 250 ten minutes after departure. Squawk 7524 Departure 125.57   
Baron November 6 Tango Juliet Readback correct. Altimeter is 3001 Ground 121.7 for push and start  

The ComFreq 124.25 is what the MCE copilot dialed in when using the command "clearance delivery comm one" Interestingly also is that the frequencies that PF3 was using are the same ones that the aircraft database had 
(not always the case) but none of the frequencies that MCE used were indicated in the aircraft database with exception of the GRD freq 121.7. No changes were made to the PF3_MCE.ini file. Still showing Active=1

For me this issue is not a big deal as I use the MCE F/O more for checklist and flows, and use the PF3 VCP to handle the radios.  I just thought I'd bring what I noticed to your attention as one of the changes in PF3 was the location of where the  PF3_Freqs.dat file is created.

BTW, I'm running FSX.

 

Thanks for the support.

 

Tony J 

 

 

[FS++]

While waiting for the matter to be looked at, we advise anyone who switches back and forth between MSFS and Prepar3D to have PF3 update its databse to use "Legacy frequencies" and leave it at that even if PF3 prompts to update databse when it detects you are running MSFS.

There is an issue with the 8.33 khz spaced frequencies in MSFS aren't adjustable via the usual MSFS/Prepar3D/FSX SDK.

Right now, when you ask the Fo to dial a specific frequency that he is unable to dial directly, he'll set it the closest he can and asks you to fine tune the last digits.

11.8.700, 118.725, 118.750, 118.775 will be dialled without issues.

118.005 will be set to 118.000 and you'll have to use the plane button to increment it.

The exception is with PMDG 737, where he dials it the closest, then uses PMDG SDK to increment further, using the rotary swoitches on VHF1, VHF2

Edited September 10, 2022 by FS++
typo

[BerndB]

hi Gerald, unfortunetly it´s seem to be the same for P3D. I don´t have MSFS and it never was installed on my Sim, but my FO has big problems to get in contact with atc. It wouldn´t be a big issue so far, but it comes to be a real annoying issue if this happen when you was just advised to contact approach while decending with just 1000 ft left to reach the given step altitude. If it then takes up to 5 times of initial contact unless you get approach, you have already passed miles the point where pf3 would give final decent and rw instructions and will not give them anymore. This disrupt the whole approach into a mess. 

[BerndB]

On 9/10/2022 at 6:46 PM, FS++ said:

Right now, when you ask the Fo to dial a specific frequency that he is unable to dial directly, he'll set it the closest he can and asks you to fine tune the last digits.

Hi Gerald, imho the matter that the FO can´t dial the correct frequencies into PF3 since the latest update is an easy one to be solved. At least for Prepar3D.

As Fighter Guy mentioned and it´s written in the changelog of PF3, the location of the frequency.dat file of PF3 has changed. See below the extract of the changelog:

"CHANGED the location where the PF3_Freqs.dat file is created. This used to be in a folder named PF3_Display which was created inside the main FS folder. However, since the PF3 Display utility no longer requires WideFS when running on a client machine this file is no longer accessed directly. Subsequently, we now create this file in the main PF3\Data folder."

I have manually copied the .dat file from the new location in the DataFolder into the PFDisplay folder in the P3D main root folder, where MCE seems to exspect to find it, and this works. The FO is then able to dial all freq. in the correct way as usual if you say i. e. "going to tower" etc.

BUT this is just an additional little issue. It doesn´t help in the matter of the non-acceptance of the the initial contact by MCE FO even if the freq. is set as correct and this annoying issue still persists.

Sometimes it helps if i click into the active SIM wndow beforehand the FO transmit the request. But sometimes not. It´s hard though to confirm it´s just a matter of lost focus ONLY. But if this issue could be caused by a combination of more than one cause, is there may be a way that the focus would be forced somehow?! And why was this never an issue before MSFS has made all mad.

Edited September 14, 2022 by BerndB

[FS++]

3 hours ago, BerndB said:

Hi Gerald, imho the matter that the FO can´t dial the correct frequencies into PF3 since the latest update is an easy one to be solved. At least for Prepar3D.

As Fighter Guy mentioned and it´s written in the changelog of PF3, the location of the frequency.dat file of PF3 has changed. See below the extract of the changelog:

"CHANGED the location where the PF3_Freqs.dat file is created. This used to be in a folder named PF3_Display which was created inside the main FS folder. However, since the PF3 Display utility no longer requires WideFS when running on a client machine this file is no longer accessed directly. Subsequently, we now create this file in the main PF3\Data folder."

I have manually copied the .dat file from the new location in the DataFolder into the PFDisplay folder in the P3D main root folder, where MCE seems to exspect to find it, and this works. The FO is then able to dial all freq. in the correct way as usual if you say i. e. "going to tower" etc.

BUT this is just an additional little issue. It doesn´t help in the matter of the non-acceptance of the the initial contact by MCE FO even if the freq. is set as correct and this annoying issue still persists.

Sometimes it helps if i click into the active SIM wndow beforehand the FO transmit the request. But sometimes not. It´s hard though to confirm it´s just a matter of lost focus ONLY. But if this issue could be caused by a combination of more than one cause, is there may be a way that the focus would be forced somehow?! And why was this never an issue before MSFS has made all mad.

Thanks for feedback.

Will be looked at, but not before a couple of weeks as the schedule is packed with all other things that require attention in MSFS & X-Plane.

At the very least, the issue with setting focus to the sim will be no more in P3D & FSX at least. It will be automated in fsInside.dll and fsInsider64.dll to ensure the hotkeys always get delivered.

Should have been done a while ago tbh. It shows why feedback is important and gets things moving. 

 

 

[BerndB]

...so for all with the frequency dial in issue, it´s a workarround for the time waiting, to manually copy the freq.dat file from PF3/Data into the P3d mainfolder into PF3display folder!

This focus solving thing sounds really promising and will be welcome. Thank you!

[BerndB]

On 9/14/2022 at 3:16 PM, FS++ said:

Will be looked at, but not before a couple of weeks as the schedule is packed with all other things that require attention

Hi Gerald, in your last post you mentioned it (the issues with PF3 latest version and autofocus) will be looked at within a couple of weeks. Actually 2 complete weeks went by already, Her Majesty Elizabeth II was brought to her last rest, 😪 and King Charles III has taken over business already. What else now require your attention, other as to bright up our P3D days where everyone else treat us P3D users as we would be in the same condition as Elizabeth II.??? 

Do you have any news or even a patch for us already?? 🥺

[FS++]

4 hours ago, BerndB said:

Hi Gerald, in your last post you mentioned it (the issues with PF3 latest version and autofocus) will be looked at within a couple of weeks. Actually 2 complete weeks went by already, Her Majesty Elizabeth II was brought to her last rest, 😪 and King Charles III has taken over business already. What else now require your attention, other as to bright up our P3D days where everyone else treat us P3D users as we would be in the same condition as Elizabeth II.??? 

Do you have any news or even a patch for us already?? 🥺

Should have new files either tomorrow evening or Satuday at the latest.

It;s not the "fix focus" that takes long. This was already done last week.it's the fact MCE is an enordmous package now, and when you add a new potentially disruptive feature, you have some scaffolding put in place that sort of makes it temporarily "not recommended to release in that state.

I suggest you get in touch via e-mail and We'll send you a private link because we ddon't want to put a Beta out yet, for the upcoming feature.

Which aircraft are you using under Prepar3D?

Edited September 29, 2022 by FS++

[BerndB]

Hey Gerald, honestly it was more or less not serious meant, i would exspect you have everything done already. But, of course you are prepared as usual having somthing in the bag. I would appreciate to test a beta fix, especially for the "focus thing". I´ll sent oyu an e-mail later from my private account. 

Thank you for your support.