IFR Flightplan broken. Next GPS Marker thousands of miles away too the north

[Princeps]

Do you have any add-ons in your Community folder? If yes, please remove and retest before posting.

No.

Are you using Developer Mode or made changes in it?

No

Brief description of the issue:

Whenever I create a flightplan (in the main menu) and load it with any plane, the flightplan is broken.

• Bogus Waypoints (D0,D1) are inserted thousands of miles away (see screenshot 1)
• The GPS thinks it needs to fly heading 355 to reach them (see screenshot 1)
• After deleting them through the “Active Flight Plan” menu they disappear from the map (see screnshot 2)
• The distance to my “real” waypoints and the direction is still broken (see screenshot 2)
• For each leg the distance is calculated as 0Nm and the direction 6° (see screnshot 2)

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

Detail steps to reproduce the issue encountered:

Create an IFR flight plan from the world map. Select runway, departure, approach, and arrival.

PC specs for those who want to assist (if not entered in your profile)

Don’t think those are relevant. The only think that might be interesting is that I’m using English as my system language but a German keyboard layout.

Build Version # when you first started experiencing this issue:

1.17.3.0

Are you on the Steam or Microsoft Store version?

MS Store

Did you submit this to Zendesk? If so, what is your ticket #?

No, but I will if this isn’t just a stupid mistake by me.

[Raynen]

Sounds like UTF-8 strikes again, see if this fixes it;

In Windows 10 Control Panel → Region → Administrative Tab-> Change System Locale…
Turn off: “Beta: Use Unicode UTF-8 for worldwide language support ”
Reboot PC

[Princeps]

That fixed it. Thank you very much.

For future readers:

The setting is in the “Language” section of the windows settings. On the right side you’ll finde “Administrative language settings”

I guess Asobo follows the aviation industries decision of being veeeery conservative when it comes to adopting technological changes

It’s 2021 UTF-8 should be the default..

Fun fact: I distinctly remember turning on that setting for some Windows development / programming tests.

[MudMoverGSH]

Too bad, maybe the UTF-8 issue will never be solved. Not everyone is using an EN OS, non-unicode setting has to be set as other languages in order to use other daily software. Restarting to change it for every MSFS2020 flight is just a pain. After WU4, even loading a flight is something that cannot be accomplished with bing data on if the system locale is not EN(**). I guess the only way for me to go is to build a PC that is dedicated to run MSFS2020.