Clever boy Tim :)

Old log snippet

20:10:54.7 LocPak in D:\msfs2020_pf\Official\OneStore\fs-base\en-US.locPak
20:10:55.1 Generating new Names Lookup database.
20:10:57.5 0 names found. Patching...
That file is still present. There are lots of these files but I found one in fs-base-genericairports. New log snippet

10:09:55.6 LocPak in D:\msfs2020_pf\Official\OneStore\fs-base-genericairports\en-US.locPak
10:09:55.8 Generating new Names Lookup database.
10:10:01.6 128996 names found. Patching...
I have my friendly names back :)

Thanks Tim

Thanks Tim. Is there anything in a log PlanG makes that might be helpful to you?

Sadly that didn't work and I'm wondering if the problem is the 2020 beta. I've tried a competing product and that also failed to display friendly names!

But I don't have any Khorixas Airports, mine for example is "TT:AIRPORTSZ.KYKX.name"

Just built my MSFS database and now all airport names are of the same format

TT:AIRPORTSZ.UKKK.name

The only bit that changes between each one is the ICAO code, e.g. UKKK -> UKKM for instance.

I am running the 40th Anniversary Beta v1.29.25.0

Windows 10, 32GB. Any idea what's gone wrong?

Darn it, working for me today to! Don't understand.

If you want a 'laugh' try and create this plan in the game itself. When I add the 3rd en-route airfield it makes it the second in the plan  :o However add it as the first en-route field and then add the rest in order and it works! Boy does MFSF still have problems.

Thanks for looking Tim :)

Created a flight plan in my usual way. Right click the airfields and add to plan. Then exported the plan as a Microsoft 2020. When I load the pln file in to 2020 the flight starts over the airfield at around 300 ft rather than on the runway. I've attached the flight plan for giggles ;)

This may not be a Plan-G problem as I flew part of the route and landed full stop at the first intermediate airfield, taxied to the fuel pumps and save it as a FLT. When I load that FLT again I'm started 300ft over the airfield!

Has anyone done a flight plan for the mach loop used by the RAF for training?

TIA

Fingers crossed but we may have got this sorted. Les couldn't reinstall PlanG due to an error I'd never come across before. "The advertised application will not be installed because it might be unsafe" followed by something about getting an installer made that would run in Basic mode.

Googling the first bit of the error threw up a MSDN item on this. The trick to getting it reinstalled was to execute the following command in a command prompt in the folder where the installer was

msiexec /qb /i Setup.msi

Les has now built the database and can see the air space, airfield data etc in his Plan G :)

Result  :afro:

FSInn can cause a crash on exit, you need to disable the tuner to stop that. From Addons->Copilot->Settings find the Tuner line and double click so the Enabled becomes Disabled. FSX will still crash on the next exit but after shouldn't. Sadly mine still does but only rarely now.

Oh how strange is that, thanks for the update :)

And yes mine is on the left too.

Completely wild thought here, your min/max/close icons are different to the ones used by MS in office which does work on my PC where Plan-G fails. Are there multiple ways to create the title bar (or whatever it's technically called?)

PS. Plan-G is front window with focus, Word is the rear window

I've now deleted the 3 WinSXS folders and just installed the RTM SimConnect.msi. My SimConnect debug log still says I'm running a later version so I assume FSX itself is not running a version in the WinSxs as there is only the RTM version there now  ??? However what ever state it is in now Plan-G is talking to FSX :)

Any idea what breaks the installation/registry entries for this Tim?

I've also got an XP SP3 PC that fails to load simconnect 60905 even though it exists within my WinSxS structure. One thing I noticed it that my registry thinks the PublicKeyToken for 60905 is 67c7c14424d61b5b where as the error Plan-G generates says the PublicKeyToken is 31bf3856ad364e35

I expect I'm taking rubbish but I'm loath to simply delete the WinSxS folders as there are numerous entries in the Registry associated with these various versions.

Well you know about me and that globe ;)

I've updated the nVidia drivers on my XP work box, no different. Works on primary display not the secondary still.

Just tried it on my Win7 RC laptop and the Globe button wasn't working at all :( Are you interested in problem reports for the Win7 release candidate?