Flight Plan from World Map generates incorrect locations on Flight Plan

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

Are you using Developer Mode or made changes in it?
No

Brief description of the issue:
When creating a flight plan from the World Map with at least a Departure and Destination, the flight plan loaded in the flight management system shows the correct locations on the map but the starting distance of the plane to the first point on the flight plan is 1000’s of nm away whereas it should be 0nm (at the same location).

Provide Screenshot(s)/video(s) of the issue encountered:
Incorrect Flight Plan generated from World Map
image
LCPH-LCLK direct flight selected on World Map with Cessna 172 (G1000). Distance is 106 km (= 57nm)

Screenshots are taken from LCPH runway before take-off.
image
Flight Planner in plane shows incorrect distance and direction on left, but correct map on right.
image

Distance of leg shows 2766, but should be 57nm. Bearing shows 224 but should be 80.
image
Incorrect CRS heading flying from GPS. Once flying, Autopilot will head 356 on Nav mode instead of 80 of first leg.

image
Map correct

image
Map correct, but incorrect DTK

image
image
Nearest Airport info has correct distance and direction.
image
Navlog has incorrect data with distance = 0nm and heading incorrect.

NB

  1. If flight plan is created from FMS (flight management system) on plane and not World Map, the distances and directions are correct.
  2. This problem occurs on all planes with an FMS.

Detail steps to reproduce the issue encountered:
Create Flight plan with direct flight and Cessna C172 G1000 from world map.
Ensure CDI set to GPS mode.
Observe Distance and Bearings

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

I have just figured out what the problem is. I had followed a suggestion in the forum to correct unicode text by changing the setting in the Windows Control Panel for “Beta: Use Unicode UTF-8 for worldwide language support” to checked (enabled). This caused a problem in the customflight.pln file by replacing the degrees symbol with a strange character, which messed up everything. After reinstalling completely twice and not being able to fly from the planner for 2 weeks I finally figured it out.
Lesson learnt: DON’T enable this Regional setting, and DON’T blindly follow recommendations given in the forum. Write down your changes (with a date) so that you can retrace your steps if it doesn’t work.
Apologies to Asobo for being frustrated with the product whereas it was just a bad (and untested) user recommendation.