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.

Quote from: tim arnot on September 05, 2020, 11:54:45 PM
Ok thanks. It looks like the Steam version stores things in a different place (nothing like consistency...)

Fortunately, you can set the path manually. In the Database Build Options dialog (click Build Navigation Database, then Settings...), at the bottom of the list of paths, you'll find one that's just called "Path". You can set this to the MSFS content folder:

- If you specified a content location when you installed the sim, that's the path you want.
- If you let it install the default settings then for Steam it's

C:\Users\[Your Name]\AppData\Local\Packages\Microsoft.FlightDashboard_8wekyb3d8bbwe\LocalCache\Packages\

and for MS Store it's

C:\Users\[Your Name]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\

(the Steam info comes from a third party site, as I don't have that version)

Note that AppData is a hidden folder, so you may need to select 'Hidden Items' in the Explorer View menu in order to see it.

The actual path for me (installed from Steam, default path) is:
C:\Users\[Your Name]\AppData\Roaming\Microsoft Flight Simulator\Packages