NAV1 audio identifier bug?
-
There seems to be a problem with the NAV1 audio identifier. It answers to the frequency stored locally on the DME instead of NAV1.
In the example below NAV1 is tuned in to 108.80, but I get no sound when I try to listen in on it. Instead it plays the morse code for 115.30 when I tune the DME. It keeps beeping if I disconnect the DME on the circuit breaker.
-
There seems to be a problem with the NAV1 audio identifier. It answers to the frequency stored locally on the DME instead of NAV1.
In the example below NAV1 is tuned in to 108.80, but I get no sound when I try to listen in on it. Instead it plays the morse code for 115.30 when I tune the DME. It keeps beeping if I disconnect the DME on the circuit breaker.
@trussel Have you tested it with a default aircraft to verify that it's not a bug in MSFS? Also, have you tested it with a different VOR station?
-
There seems to be a problem with the NAV1 audio identifier. It answers to the frequency stored locally on the DME instead of NAV1.
In the example below NAV1 is tuned in to 108.80, but I get no sound when I try to listen in on it. Instead it plays the morse code for 115.30 when I tune the DME. It keeps beeping if I disconnect the DME on the circuit breaker.
@trussel Unless there has been a recent fix the problem with NAV1 audio ID has existed for a long time and is believed to be an issue within MSFS that is beyond control by 3rd party developers. Several others in the community have commented on this same issue. The Morse code ID for a VOR received on NAV 1 appears to actually correspond to the audio ID for a NAVAID received on whatever frequency that the DME is manually tuned to. Otherwise NAV1 responds correctly to the received NAVAID it is tuned to. That can be confirmed by crosschecking with NAV2 for which the audio ID is correct. Unless something has changed as I remember the problem exists with the JF Warrior and all of the Arrows. I could not hear the NAV1 audio ID on the stock aircraft I tested in the past so it was not possible to crosscheck with those other aircraft. I submitted a detailed ticket on this issue with Just Flight when the Arrow III first became available. Sadly your post testifies that it has apparently not been resolved. Since I have ignored this problem for some time I will make it a point to check it again ASAP.
-
@trussel Have you tested it with a default aircraft to verify that it's not a bug in MSFS? Also, have you tested it with a different VOR station?
@retiredman93231 said in NAV1 audio identifier bug?:
@trussel Have you tested it with a default aircraft to verify that it's not a bug in MSFS? Also, have you tested it with a different VOR station?
I did test it with different VOR stations, but not with other aircraft as it was working fine previously. It was not working on other aircraft either.
I've since reinstalled the game twice. First without deleting all the game files, which changed nothing. But when I reinstalled after having deleted all associated files, including the community folder, the morse code for NAV1 was audible again. I then tested again after reinstalling all 3rd party software except the PA-28 (mostly scenery, no aircraft) and it was working fine. I installed the PA-28 and jumped into the stock cessna 172, and I could still hear it. Only when attempted in the PA-28 did it stop working, at which point I had to restart the game for it to work in other aircraft. Having state saving enabled made the bug permanent and I had to uninstall the Warrior II to fix it.
-
@retiredman93231 said in NAV1 audio identifier bug?:
@trussel Have you tested it with a default aircraft to verify that it's not a bug in MSFS? Also, have you tested it with a different VOR station?
I did test it with different VOR stations, but not with other aircraft as it was working fine previously. It was not working on other aircraft either.
I've since reinstalled the game twice. First without deleting all the game files, which changed nothing. But when I reinstalled after having deleted all associated files, including the community folder, the morse code for NAV1 was audible again. I then tested again after reinstalling all 3rd party software except the PA-28 (mostly scenery, no aircraft) and it was working fine. I installed the PA-28 and jumped into the stock cessna 172, and I could still hear it. Only when attempted in the PA-28 did it stop working, at which point I had to restart the game for it to work in other aircraft. Having state saving enabled made the bug permanent and I had to uninstall the Warrior II to fix it.
@trussel There seem to be two issues being discussed. First is the ability to hear NAV1 audio ID Morse code and the second is whether it is the correct ID for the NAVAID being received on NAV1. Did you hear NAV1 audio ID on other aircraft and if so was it the correct ID?
I hear no NAV1 audio ID on any of the stock Cessnas prop aircraft or the Beechcraft G36. I do hear the correct NAV2 ID on each of them. However I have not yet tried removing the JF aircraft from my community folder to check NAV1 audio on these other aircraft. I will give that a try after placing the JF aircraft in my addon linker. This whole issue is so contorted! -
I've also seen this. For what it's worth, after reading this topic I double checked that I cannot hear anything on Nav 1 in the Warrior (I can't), but then I loaded up the stock C172 in the same place and confirmed I can't hear anything on Nav 1 in that, either.
