I use mostly Navigraph in combination with Pilot2ATC. Else with MSFS 2024, the question is, how much i need a subscription. But that is another topic!
I upgraded from Pilot2ATC v2 to v3.0.0 and while flying Pilot2ATC I have issues. The Pilot2ATC owner wrote this:
The issue with Navigraph is that they have not updated the P2A data to include 8.33kHz spaced frequencies. When P2A was started, over 10 years ago, the 8.33kHz spacing was not common in the real world and none of the SIMs supported it, so the database was modified to round frequencies to the nearest 25kHz spaced number.
Could you guys provide an update for the 8.33KHz for Pilot2ATC V3? Could this be possible, if no then tell me guys.
According to your request, removing the rounding workaround in the code is straightforward, but the unanswered question was, what happens with non-V3 users? V3 is the SQLite version of V2, so when I remove this in the primary source (V2), V3 is good, but with V2, the frequencies don´t work anymore.
So, I assume we need an internal discussion on how to handle this change first. Again, from the coding side, it´s a few minutes, and that’s it, because we have all these frequencies in this spacing available. For me, it´s a developer decision to ignore V2 users here or not—that´s not what we can decide.