I have an issue with recent versions of PSXT with respect to static parking.

For context, I am developing (VERY slowly) custom airport parking (specifically at the moment for KABQ) and PSXT has historically been great for testing that the realigned taxiways and parking are working correctly. The resulting custom airport file obviously only exists on my local machine and is unpublished, at least for the time being...

With earlier versions of PSXT, this was no problem. Many parking spots filled up with appropriate aircraft in addition to live traffic taxiing and parking correctly, the revised taxiways working much better than the out-of-date default airport. Recently however, I'm not seeing any static aircraft parking, only live traffic, I assume due to the TBLO feature. For example, if I delete KABQ.xml from the PSXT\airports\my_thirdparty, I get static aircraft parking, but in the default locations, as you would expect. If I check "scan for addon airports", a KABQ.xml file is generated, which correctly includes 109 parking spots and refers to the correct .bgl file for my custom airport. However on loading FS2024, there are now no static aircraft parked. If I look in the PSXT Log.txt file, I see the following entries:

The park airport is KABQ (ABQ)
airports\my_thirdparty\KABQ.xml
learned does not exist
          parking_percentage      : 30%
Airport file read from 'airports\my_thirdparty\KABQ.xml' for 
          publisher               : 
          altitude                : 5319 ft
          num_parkpos             : 109
          quality factor          :  0/ 0
          RT traffic week         : 0

21:54:29 (utc) It is day 3 (Wed), 21.0 hours
0 parking positions from PT
no parking positions found

I'm guessing the final two entries here are key. Do I need to configure something to allow for a local only airport (unpublished) airport file? Is there a way to revert to the old behavior for unpublished airports? Or am I missing something altogether (quite possible!)

Thanks.,

Paul

20 hours ago, PaulH2 said:

I have an issue with recent versions of PSXT with respect to static parking.

For context, I am developing (VERY slowly) custom airport parking (specifically at the moment for KABQ) and PSXT has historically been great for testing that the realigned taxiways and parking are working correctly. The resulting custom airport file obviously only exists on my local machine and is unpublished, at least for the time being...

With earlier versions of PSXT, this was no problem. Many parking spots filled up with appropriate aircraft in addition to live traffic taxiing and parking correctly, the revised taxiways working much better than the out-of-date default airport. Recently however, I'm not seeing any static aircraft parking, only live traffic, I assume due to the TBLO feature. For example, if I delete KABQ.xml from the PSXT\airports\my_thirdparty, I get static aircraft parking, but in the default locations, as you would expect. If I check "scan for addon airports", a KABQ.xml file is generated, which correctly includes 109 parking spots and refers to the correct .bgl file for my custom airport. However on loading FS2024, there are now no static aircraft parked. If I look in the PSXT Log.txt file, I see the following entries:

The park airport is KABQ (ABQ)
airports\my_thirdparty\KABQ.xml
learned does not exist
          parking_percentage      : 30%
Airport file read from 'airports\my_thirdparty\KABQ.xml' for 
          publisher               : 
          altitude                : 5319 ft
          num_parkpos             : 109
          quality factor          :  0/ 0
          RT traffic week         : 0

21:54:29 (utc) It is day 3 (Wed), 21.0 hours
0 parking positions from PT
no parking positions found

I'm guessing the final two entries here are key. Do I need to configure something to allow for a local only airport (unpublished) airport file? Is there a way to revert to the old behavior for unpublished airports? Or am I missing something altogether (quite possible!)

Thanks.,

Paul

The TBLO feature has not changed, it has always been there.

What has changed however, and already for at least a year, is that offline learned airport files are always on line in the archive, and no longer local.

If you want to use your manually aligned airport you must give it a publisher name, either in the Manufacturer or the Creator field of the manifest.json file. At the moment these fields are probably empty ( or filled with strong shorter than 4 characters), and that's why your clean KABQ.xml file stays in my_thirdparty instead of zipped in TBLO.zip for offline learning by me.

So act as any airport creater and put your name or company in the manifest.json file. Then run an airports scan.

 

Edited October 6, 2025Oct 6 by kiek