It appears to be something about the RXP GTN 750 gauge. Removing the legacy radios had no effect.

Hi jabloomf1230

Don't know if it makes any difference but i'm using the Flight1 GTN 750.

2 hours ago, GAJ52 said:

Hi jabloomf1230

Don't know if it makes any difference but i'm using the Flight1 GTN 750.

I have  the F1 version installed in the stock Piper Cub for testing. Let me check on that

The plot thickens...

 

@GAJ52 are you using fsaerodata and/or the level D navigraph data with vox?

11 hours ago, jabloomf1230 said:

I have  the F1 version installed in the stock Piper Cub for testing. Let me check on that

Do you get the same issue with both versions then Jay? I only have the F1...

Edited July 18, 20205 yr by kevinfirth

Kevin, for some reason I can't get the most recent F1 (2.30) version to work at all. You'll have to check it.

I'm not at home at present, dealing with a family emergency, so will have to stay on hold for a while until I'm back. I haven't tried the latest F1GTN yet either this will be my first outing with it!

According to Navigraph, they did not update the tower frequency at EGKA with the real world value (125.405) because the stock p3d5 airport uses 125.400 (probably obtained from one of those inaccurate online flightsim-related navigation data websites). There seems to be no way out of this loop unless LM changes the stock airport, which I suspect that they won't do because there may be other frequencies in the UK that also don't match the real world values.😕

I know that VOXATC has a folder of mostly UK corrections located at:

C:\Users\Jay Bloomfield\AppData\Roaming\Internal Workings\VoxATC P3D 5\apdata

and the entry for EGKA does  affect the tower:

<?xml version="1.0" encoding="utf-8" ?> 
<Airport Airspace="ukatz">
	<ATSUTower Name="Shoreham" Frequency="123.15" />
	<ATSUTower Name="Shoreham" Frequency="125.4" />
	<ATIS Name="Shoreham" Frequency="130.975" />
</Airport>

So I'm guessing that it must be VOXATC changing the frequency back. But why there's no response, I have no idea. Let me disable that folder and see if the RXP gauge works correctly.

would this not be fixed by using fsaerodata then, which should update Comms freqs?

Just now, kevinfirth said:

would this not be fixed by using fsaerodata then, which should update Comms freqs?

No, actually that apdata folder overrides the sim's navigation db. And further, according to Tegwyn West any SIDs and STARs data provided by fsaerodata are also ignored, as VOXATC solely relies on the LevelD folder for SIDs and STARs data.  I thought at one point we tested whether VOXATC used fsaerodata SIDs and STARs and I could swear that we concluded that it did. I'm getting dizzy thinking about all this. 😓

Therefore updating or deleting the entry(ies) in that folder should cause it to work.  We should suggest to Tegwyn that a simple tab is included in the options app to allow that data to be edited if necessary?

There still may something amiss with the RXP gauge when combined with some aircraft. It may be that some code in the aircraft may be affecting the display of 8.33 KHz frequencies.

Edited July 18, 20205 yr by jabloomf1230

ok I'll test with the F1 GTN as soon as I can to eliminate that.

I thought that I'd test various P3d5 "compatible"aircraft with the RXP GTN to see if I could figure out what was going on. Here's what I found. The behavior of the GTN is is the same (125.405 is displayed as 125.400) in all the A2A aircraft that are designed for P3d5 (I asked A2A about this, but they haven't responded yet). There are no Milviz aircraft that are compatible with P3d5.  When installed as a popup gauge in the default P3d5 Piper Cub, the behavior is the same as the A2A aircraft. When installed in the default P3d5 C-130, if the native comm radio is used to tune the frequency to 125.405, it stays at that frequency in the GTN. But if the GTN is used to tune to 125.405, it switches back to 125.400. BTW, VOXATC works perfectly with the P3d5 C-130 at EGKA. I suggested to RXP that they start with the P3d5 C-130 to test the 8.33 KHz spacing with the GTN. Let me know how the F1 GTN tests go.

In any case, this issue is on hold until we can get some resolution from the GTN gauge vendors as to whether they work or not with 8.33 KHz spacing.