Welcome to
Microsoft Flight Simulator’s SDK Q&A Platform!
Please take a moment to read the platform’s guidelines before you get started!
Adding Nav.3 to the [RADIOS] section causes the morse code for NAV 1 to stop working for all planes until you restart the sim. The CJ4 the 747 and A320 all have 4 navs entry's but they use a HTML FMC code and not Lvars. So they can get away with it. So we need to fix this as you can have up to 4 nav entry's according to the SDK.
Nav.3 = 1, 1, 1
Oh hi Eric it's Momo from the FS Think Tank. Anyways i also found if you only have 2 nav entry's you can also break the nav 1 morse code by using variables that include the index 3. So for example this is in my xml gauge (A:NAV ACTIVE FREQUENCY:3, MHZ) or using events as well. I had this in a Asobo update template (>K:NAV3_RADIO_SET). Hope this also helps as it seems as soon as index 3 get called or tries to set this kills nav 1.
I have made a new discovery. When you add a new entry nav 3 the morse code for nav 1 is reading the nav 3 index. So that is what is wrong. it's not like it stopped working but just updates to look for nav 3. But the odd thing is all the other planes with only 2 nav entry's now fail on nav 1 until you restart.
Does this fix, I assume of the nav Audio not working at all, also include a boost to the very low level that that audio is at Max Nav AUdio volume.
I can understand Historically a default low level, in FSX wirth no Nav Volume control, but now in MSFS, it should be possible to set its Max volume level to that of the Coms audio. ?
Just to be clear if you add a nav3 or nav 4 entry the nav1 will not play a morse code.
I am now totally confused by this whole thread.
My Understanding is
(1) After release, the Nav 1 & Nav 2 audio worked, but there were many comments that it was far too low in volume.
(2) In Su9, (or there abouts) support for Nav 3 & Nav 4 was added, ?
(3) In SU10 Beta, Both nav1 & Nav2 audio stopped working, in a plane , even if that plane did not have a Nav3 or Nav 4
We now hear from Asobo:
This issue has been fixed on our side and the fix will come with the next SU10 flighting update.
Let us know if you encounter any issue with it when it's released.
(a) What is a "next Su10 flighting update ?
(1) A Beta 2 Update
(2) The final SU10 update in August
(b) What has been fixed ?
Nav 1 & Nav 2 Not producing audio
and / or Nav Audio way to low at max volume
Also, has the "fix" resulted in any update/correction to the SDK in this area ?
My hope BOTH of these issue have been fixed, and there will be another SU10 Beta 2, before release, so we can confirm that the issues have been fixed, or else we are waiting another 1-2 Months for any chance of a permanent fix.
During the flighting, the game will be updated several times so we include fixes on issues you reported, until the end of the flighting where the final build of SU10 will be released.
So the issue that will be fixed in the next beta version is the NAV1 & 2 audio no longer working.
The problem with sounds being too low has been reported as well and a fix is planned but I can't tell when it will be available yet.
I hope that answers your questions.
Regards,
Sylvain
1 Person is following this idea.
