When I position at Flightbeam KPDX, PSXT uses stock KPDX. Flightbeam KPDX is active in Community folder and was purchased from Flightbeam - not from the MSFS market place.

20 hours ago, somiller said:

When I position at Flightbeam KPDX, PSXT uses stock KPDX. Flightbeam KPDX is active in Community folder and was purchased from Flightbeam - not from the MSFS market place.

Did you scan your airports lately? At least after you have installed FlightBeam's KPDX ...

FYI: you can check your scanned airports in /PSXT/airports/my_thirdparty

Edited October 2, 20241 yr by kiek

23 hours ago, somiller said:

When I position at Flightbeam KPDX, PSXT uses stock KPDX. Flightbeam KPDX is active in Community folder and was purchased from Flightbeam - not from the MSFS market place.

Have you installed static planes removal patch from flightsim.to? It might cause troubles with PSXT, and I was a victim 🙂

4 minutes ago, G-YMML1 said:

Have you installed static planes removal patch from flightsim.to? It might cause troubles with PSXT

I have the static aircraft removed and PSXT works fine at PDX. Just be sure to tell PSXT what airport file you want it to use.

 

 Go into your PSXT\airports\my_thirdparty folder and search for KPDX. Open it and point it to the Flightbeam KPDX file.

airports\archive\thirdparty\Flightbeam\KPDX.xml  

IF you DON'T have a KPDX file your  PSXT\airports\my_thirdparty then make a copy of one that you do have and rename it KPDX and again tell it to use the one from the archive\thirdparty\Flightbeam folder.

 

 

1 hour ago, Dave_YVR said:

I have the static aircraft removed and PSXT works fine at PDX. Just be sure to tell PSXT what airport file you want it to use.

 

 Go into your PSXT\airports\my_thirdparty folder and search for KPDX. Open it and point it to the Flightbeam KPDX file.

airports\archive\thirdparty\Flightbeam\KPDX.xml  

IF you DON'T have a KPDX file your  PSXT\airports\my_thirdparty then make a copy of one that you do have and rename it KPDX and again tell it to use the one from the archive\thirdparty\Flightbeam folder.

 

 

As you indicated in your first post I hadn't MANUALLY set PSXT to scan liveries or airports - I had missed this in the 8.1.0 release notes:

"Added two checkboxes to control the scanning of Liveries and Addon airports. No scanning after 3 hours 'unuse' of PSXT anymore. In most situations this is redundant and an annoying waste of time at start up."

I usually don't start PSXT until after MSFS is running, and as soon as the PSXT window comes up I select the MSFS window, so I didn't realize that PSXT was NEVER scanning, even on first start of the day.

14 hours ago, somiller said:

I had missed this in the 8.1.0 release notes:

Always read the Release Notes 😉