I thought I would put this issue here as it relates to communication on Vpilot.
Here was the issue I faced. I was inbound to EDDS with the tower being on 118.805.
I use Prosim and P3D V5 on a full-size sim, so when I tried to select 118.805 in the comms radio it would automatically revert to 118.800. I don’t know if this is a P3D issue or a Prosim issue (have raised a post on Prosim forums), either way, I was unable to communicate with the tower controller.
I seem to have issues with any xxx.x05 type frequency for some reason 118.305 also is an issue.
Can anyone shed any light on this? It makes it difficult to communicate if I am unable to select the frequency.
There should be no difference between .800 and .805. On an 8.33 kHz radio, .805 is a channel and the actual frequency it tunes is .800.
There were some issues with FlighFactor aircraft flying on another network as the aircraft correctly tunes to (for example) .800 when .805 is entered. However that network treated .805 as a unique frequency.
You are quite correct, but unfortunately, AfV doesn’t simulate this. Broadly speaking, each .001 MHz (and iirc, AfV could be even more granular) is a completely separate thing, there is no overlap.
But even if there were an overlap, 25kHz radios/the 25kHz channels shouldn’t be used to tune to 8.33kHz channels as that might result in an overlap with adjacent 8.33kHz channels.
I can see that you already got some suggestion on the Prosim forum. If the checking on the prosim ios doesn’t work, then it could be the radio hardware, which needs updating or a failure in prosim not allowing the setting of 118.805 for some reason. My old version 2.41 isn’t fully compatible with 8.33kHz so I can’t tune 123.130 and according to Humberto it’s because of the old version. If you’re using a new version and it still is a problem, the I would raise a ticket with prosim.
The problem here is going to be that there are several aircraft (at least in X-Plane) that tune the correct frequencies for the 8.33 kHz channels. It’s not that they don’t support 8.33 (they do), the problem is they support it with real world accuracy.
Ok, I have it figured out. It was a setting in Prosim V3. I have switched it over to 8.33kHz and have tested it in Vatsim. At least can enter 118.805 in the com.
Looks like I will have to get a new RT module as the current one is only 5 digits. However, I can still use the CDU to enter com frequencies in the meantime.
Thanks for the help.
A couple of hardware com panel users in the VATGER community have reported that they were able to work around that issue by using spad.next or similar to drop the initial 1 (so, in the case of Stuttgart Tower, they would simply see “18.805”) on their panel. Might be a good compromise for you as well? Not sure if prosim/your hardware/etc. let’s you do that, of course.
Another point about channel spacing is more important for busy pilots: It would be a great help if the pilot could select the active frequency of COM1 and COM2 from the frequency list using the mouse menu.
I tried contacting Ross Carlson (developer) but had no success.