Darkstar crashes the game when entering a leading 0 in the transponder

[IDNeon]

Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons?

No

Brief description of the issue:

In the XPNDR if you select 0 first, it crashes the game. But if you select any other valid number it will accept the 0 just fine. After some period of time, 8 and 9 become available on the XPNDR configuration window, and if you select 8 or 9 it will also crash the game.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

Open the XPNDR dialog menu to configure XPNDR. You will see num pad but with 1-7 and a 0. If you press the 0 first it crashes, but if you enter 1072 as a SQAWK it works fine. After some time 8 and 9 reappear in this window and will also crash.
Also, uninstalling and reinstalling the content hasn’t worked. I’m trying uninstalling content, removing the plane from being selected in the hangar, signing out, and then reinstalling.

PC specs and/or peripheral set up if relevant:

Not relevant

Build Version # when you first started experiencing this issue:

1.29.30.0

---

For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

[MikeB54331]

Transponders don’t have the 8 or 9 digits. They only use digits 0 - 7

[IDNeon]

Im so stupid! I forgot that. My friend even said it today about that haha.

Im still pretty sure the game will crash if I press 0 on the XPNDR. Will test now.

Also I was able to get an 8 or 9 to load on the XPNDR menu. So it does have some kind of buggyness.

[IDNeon]

Well it still glitches out when pressing 0 first.

Im just going to chock it up to being a VFR-only aircraft that it just uses default 1200 and leave it at that.

0 works if you use any other button first.

Theres definitely a coding issue.

Then 8 and 9 load and that will cause a crash as invalid input.

Seem to work otherwise

[PowerNow1485]

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

I conform this, entering leading 0 in the transponder freezes the simulation.