Callsign , Tail Number , and Flight Number gets capatilized

:wave: 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

Brief description of the issue:

When I type in a Callsign, Tail Number, or Flight Number, everything gets capitalized and “pushed” together. For example, if I type in SkyWest, it changes to SKYWEST. In some cases, when capitalized, it will spell out the word, like S-K-Y-W-E-S-T.

This happens normally when the game is started and I enter it in.

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

N.A

Detailed steps to reproduce the issue encountered:

  1. Restart Flight Simulator
  1. Open “Customization” in the Aircraft Menu
  2. Enter Callsign (i.e. SkyWest)

PC specs and/or peripheral set up if relevant:

N/A

Build Version # when you first started experiencing this issue:

Sim Update 6


:loudspeaker: 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:

@HamMan2118 - I agree with you that these are not the easiest data fields to edit, but the information you enter will be used elsewhere in the sim, so formatting is likely quite important. I would like to see the text as selectable by either double-clicking or click and drag so it is easier to change, but these are relatively minor issues when compared to much more important fixes being focused on at this time.

But, a good idea, so it gets my vote.

1 Like

This behaviour has been around since launch. So it doesn’t look like a bug, per se… But more of a bad UI/UX design of the flight customisation menu, in my opinion. In PC, we workaround this by keeping the field empty on the flight customisation menu, but instead, add the callsign to the livery’s Aircraft.cfg file. This way, the sim will always use the callsign from that file, and it can work with lower cases and spaces. And the positive side here as well is that when I switch to different livery of different aircraft, the sim will automatically read a different aircraft.cfg file which will automatically read their respective callsign, without me having to manually change it.

But I understand that Xbox doesn’t have this luxury, so I’m still voting for it, but I disagree that this is a bug, so instead I would vote for a UI/UX redesign wishlist to have this changed to accept lower cases and spaces so Xbox users can enjoy proper callsign as well.

1 Like