Build 223

[tim arnot]

Thanks. In that case, can I trouble you to send me a copy of the file, in case there's something different about the Steam version of it?

[mcellini]

Attaching the en-US.locPak file.  First attempt failed with an invalid attachment error.  Had to rename it with .txt extension.  Appreciate the help Tim.

[tim arnot]

Ok thanks. That's confirmed my suspicions that it's the wrong one. Could you check another location for me? There should also be an en-US.locPak at

C:\Users\mcell\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam\fs-base\

If it's there, I can have a test build ready to try very shortly.

Just one other question: did you set the content path manually, or did you let Plan-G find it?

[mcellini]

Confirmed en-US.locPak file exists at path C:\Users\mcell\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam\fs-base\
I believe I had set the content path manually but I'm not 100% sure.

[tim arnot]

Issue really was whether "Packages" was part of the given path. Still, this should catch it either way:

https://1drv.ms/u/s!AkfXrd8YzuWw7Aw8AVbvsg9ihw0O?e=WGuv9M

Let me know how it goes.

[mcellini]

That did the trick.  Airport names are back.  Thanks again Tim.  Best customer service I ever ever seen.  Sending a donation as we speak.  Take care.

[mightykong]

You're the developer and it's your software, but is removing a 64-bit option really a good thing?

Just curious as to why going back to 32 bit is better?

[marcc]

I have the same problem: Database is fine but no airport names (except for EDDS which I added as a community addon). I have also the steam version. Tried 223 and 224.
There is no C:\Users\USERNAME\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam\fs-base\ folder for me. The path exists up to "Steam", but this folder is empty. My en-US.locPak is located where I let the game-internal downloader/installer put the content: PATH_I_CHOSE\Microsoft Flight Simulator\Official\Steam\fs-base (so no "Packages" here).
But names do not show up even if I set this path when generating the database (same result than when setting no path at all).

[jacf182]

No airport names for me either.

I do have the en-US.locPak file in the default install location (Steam version): C:\Users\USERNAME\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam\fs-base\
I've set my Steam library directory. C:\SteamLibrary (or should it be C:\SteamLibrary\steamapps ?)

Plan G automatically recognized FS2020 path when building the database (I didn't manually set a path) but still, the airports have no names. I even deleted the Plang G Files folder and rebuilt the database but no dice.

By the way, I've also lost all VORs and NDBs. They showed up just fine in build 220.

EDIT: Just to confirm, if I build the database with build 220, VORs, NDBs, airways, airspace, etc show up just fine.

[mutley]

MSFS 2020

Plan G 64Bit 221 worked ok for me, connected no problem

Plan G 223...this version wont connect to the sim


Also tried Build 221  32 Bit as suggested....No Connection

I should clarify.....when i connect....the normal sound doesn't trigger saying that Plan G has connected....Plan G appears to connect and the disconnect button becomes available but my position isn't shown on the map
so i assume that it in fact hasn't connected...this is the same for 221 and 223 32 Bit

these were tried with Firewall Off

Hi have you tried setting the FS connection to P3D (rather than FSX/2020) I had the same problem as you but it appears to have solved it.