Recently, I experience undesired jumps / set backs when wanting to dial in certain frequencies. Lets say I want to dial in 122.80, then when reaching 122.70 or so it suddenly jumps back to 122.10 (for instance) and I have to dial up from that again. This sometimes repeats for several times. What I suspect to be the problem is a strange error I recently I encounter: When P2ATC is connected to the Sim (MSFS2020) via WideFS it does not receive the "empty" frequencies and just displays ".00", regardless of whether it is in STBY (see screenshot 1) or COM1 (see screenshot 2). Only when a frequency is covered, it shows up in the P2ATC panel (see also screenshot 3). It seems that this leads to these undesired jump backs when dialing in certain frequencies, because whenever a covered frequency is "dialed over", P2ATC recognizes it for a moment while I am already dialing further, but this short recognition sets back my frequency to that recognized and thus sets it back. Any idea how to solve this issue?

Edited January 7, 20233 yr by Svener
I inserted links to images for screenshots

When you change the frequency in the SIM or using a hardware device connected to the SIM, P2A is only reading the frequency and does not affect the setting of the frequency.

If using a hardware device it could be something between the Hardware and MSFS, or more likely, it is one of the ATC settings in MSFS is not turned off.

Options -> Assistance->Piloting->AI Radio Communications (ATC) - OFF
Options -> Assistance->Navigation Aids->Route & Waypoints - OFF
Options -> Assistance->Navigation Aids->Taxi Ribbon = OFF
Options -> Assistance->Navigation Aids->Landing Path - OFF
Options -> Assistance->User Experience->ATC UI Panel Open at Start - OFF
Options -> Assistance->User Experience->Show Message Log in ATC Menu- OFF
Options -> Assistance->User Experience->ATC Voices - OFF
 

Dave

 

Dear Dave,

thank you so much for taking the time to reply. All these settings are set to OFF in my case. I understand that P2A only reads out the frequencies from the sim. But the issue that P2A only reads frequencies that are "covered" and when they are empty ".00" is stated (see screenshots in my previous post), is actually not normal right? P2A should also display the empty frequencies as they are dialed over right? Also, P2A still displays a covered frequency when already dialed plus 0.015 further: the dialed standby frequency in the aircraft reads 121.985, the displayed frequency in P2A reads 121.97 (see screenshot). I think all these strange issues might be related to the jumpbacks, because most importantly, they only occur when P2A is running. I have no clue where to look at for a sollution. I already deactivated all addons to rule out interactions with P2A, but no effect.

P2A displays the ".00" frequency when it doesn't find a valid 25 kHz spaced frequency within range.  If using a "rotating" dial as you seem to be doing, P2A is checking for a frequency change every 1/2 second, so you may skip a lot of frequencies between checks, and not all of the frequencies you dial through will show, unless you dial very slowly.

121.985 is not a valid frequency for 25kHz spacing, so P2A will not display that frequency.

You need to get the desired frequency for a controller from P2A's Frequency window or from the P2A Info window for an airport.  Many published frequencies follow the 8.33kHz spacing rules and are not in P2A's data, therefore rendering them invalid.  

Dave

Dear Dave,

thanks so much for your reply again. I understand the 25 kHz spacing and that due to that some frequencies might not be displayed. But I think in my case the issue goes beyond that. To better visualise I replicated a certain state within a tutorial video I used earlier. In that particular case COM1 is set to 124.86 and STBY to 124.85 and it is shown in P2A in the tutorial video (see screenshot). In my case both, COM1 and STBY show ".00" (see screenshot). So something is odd right?

Looking at the screenshots from your first post, I noticed you are on version 2.6.4.1.  I was assuming you were on the latest version.

Try using the latest Beta 2.6.4.2 Beta 3.  I believe this issue should be fixed.  Sorry I didn't notice that earlier.

Dave

I did make the P2A update to the most recent version (2.6.4.2 Beta 4). Unfortunately, the issue remains exactly the same (screenshot).

OK.  I finally got it.  Thanks for being persistent and patient.

Beta 4a fixes the frequency display problem when the frequency is not a controller in range.  The frequency will show, but the controller name will be - - - - .

Dave

Dear Dave,

first of all, I have to thank you for responding so instantly and persistantly! It is really appriciated. However, speaking of persistance, while the display issues are fixed (thanks to your update), the jumpback issues with the frequencies are still there. And this only occurs when P2A is open and connected. So there must be some kind of "triggering communications" between P2A and the sim. The issue appears also when only the minimal setup is loaded: All addons deactivated, a default Asobo aircraft is loaded (e.g., A320), FSUIPC is running and P2A is running and connected. I dial through the frequencies in the aircraft (not with an external devise) and they frequently jump back to a frequency that was already dialed over, but was in a controller range. When closing P2A without changing anything else, the jump backs stop to occur. Is there a possibility to check or generate some kind of a log file to see what is going on between the sim and P2A?

P2A Log files are located in: C:\Users\<UserName>\AppData\Roaming\P2A_200\Logs where <UserName> is your PC user name. 
Portions of the path may be hidden by default, so be sure Windows Explorer has Show Hidden Items checked in the View tab.
A new one is created each time you start Pilot2ATC, and is closed when you shut it down. So if you take the most recent one after you have the error and after you shut down P2A, you should have the correct one.  

Email the most recent log file after you shutdown to me at [email protected] and I'll have a look. 

Please do not paste the log file here as it makes the thread unreadable.  If you want it here, you can use the Page feature to put it on another page, if you can figure out how to do that.

Dave
 

Just sent out the log!