plane icon Welcome to Microsoft Flight Simulator’s SDK Q&A Platform!

Save the date ! On February the 9th, at 10:30am, we will be happy to meet you again for a live SDK Q&A ! You can already ask all your questions here on the forum.

You have questions regarding the SDK? DevMode Tools? SimConnect? You would like to submit an idea for future improvements, seek help or exchange knowledge? You’re in the right place.

Please take a moment to read the platform’s guidelines before you get started!


Idea

Flysimware avatar image
Flysimware suggested Flysimware commented

Nav morse code bug

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 
aircraftgauges
10 |10000

Up to 5 attachments (including images) can be used with a maximum of 4.8 MiB each and 23.8 MiB total.

1 Comment

· Write a Comment
EPellissier avatar image
EPellissier commented

We will look into this - in the future, may I suggest that you use a more specific title for your post on this platform? It will certainly ease the processing of your request and potentially speed up the resolution of your issue.

Best regards,

Eric / Asobo

3 comments
10 |10000

Up to 5 attachments (including images) can be used with a maximum of 4.8 MiB each and 23.8 MiB total.

I updated the title. Also yesterday i added a nav 3 entry to the Da62 sample project to confirm and it also failed to play the nav 1 morse code.
0 Likes 0 ·

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.

0 Likes 0 ·

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.

0 Likes 0 ·

Write a Comment

Up to 5 attachments (including images) can be used with a maximum of 4.8 MiB each and 23.8 MiB total.

Your Opinion Counts

Share your great idea, or help out by voting for other people's ideas.