Pylon Air Racing and POI Creator Tool apps

Quote from Jugac64

...

One thing I could use your help on for the next small update (v0.1.2): the jetway cleanup. I'll keep the Jetway_footway_* objects, but before I hide the loose flexible-jetway parts I want to hide the right ones and nothing useful. Which names/prefixes are the "only-usable-in-TAP" loose parts — in particular, do the PBridge* / PBrucke* objects count as parts to hide, or are some worth keeping on their own? With that list I'll ship the filter (browse-list only — anything already placed keeps working).

Thanks!

At JETWAYS only the 20 horizontal elements "Jetway Footway" make sense:

By the way, it would be helpful if the length was already part of the name.

Moin Juan,

Thank you for the very rapid further development.

(1) Suggestion to the left column

Since we now get more selection groups in the left column, I suggest that we also fold in and out the XREF objects. Because at the moment "Point light (custom)" sticks in the bottom left corner:

(2) Suggestions for a better presentation of objects

There are some objects where, from my point of view, it makes sense to better present the required space on the bottom. For me, these include in particular:
- Antenna masts with tensions
- Building
- Airplanes

I'll show you the example of the 3 gliders:

• This is the representation in the ACT. Although this representation is not the right size for the individual gliders, it shows to some extent the space requirements:
  
  
  
• And this is what it looks like in the PCT. Here the size is generally better, But it is not possible, for example, to estimate how they can be parked more space-saving in each other:
  

For example, did the airplanes represent themselves like this?

Tschüss, Michael

Quote from Rodeo

This is my knowledge about xrefs and objects.

...

For the FS 2 there was a whole catalog of these XREF object views in the former Flight-Sim.org, which I also downloaded at the time.

Rodeo Do you remember who has the rights to this catalog or how it is today with the rights?

I ask this because on the one hand it has been published before (but I'm not sure who it was back then) and because it is still an ideal addition to the PCT today.

Hi Juan,

Great - and after the suggestion is before the suggestion (I now just continue to number):

(3) project.json - automatically when exporting POI

"Save" and "Save As ..." create a JSON file (text file) that can be read back into the PCT via "Open".

=> I suggest that the JSON file is also exported with the "Export POI...". Then you as a user have the possibility at any time to upload your POI back into the PCT and to revise it.

(4) "Open" - default on POI folder

"Open" always opens the 'Downloads' folder for me and I have to manually switch to the 'POI' folder.

I think it makes sense if the 'POI' folder is automatically activated with "Open", because that's where most users are most likely to store their projects.

@all

Using the example of PEOPLE, I will show which possibilities are now possible with the PCT.

I would like to be able to see the individual elements "live" in my developments of AIRPORTS and POI. For this purpose, I created heliports in my test area in mid-2025, which show the elements and their names. The elements themselves are in a TOC file and work as both AIRPORT and POI. Unfortunately, the display of the names as groundtext only works as AIRPORT.

For PEOPLE I tested whether and how I can upload it to the PCT. The solution is simple: a JSON file with the data must be created, which can then be opened in the PCT. In order to create the "ID" of the elements in the JSON file, I first created a JSON file with 23 elements in the PCT and then entered the data from my previous TOC file in this JSON file.

I provide the result here:

The ZIP file contains the AIRPORT folder, to which I attached the POI as an export from the PCT. The POI folder also contains the JSON file.

The two TOC files (AIRPORT: '000021.toc', POI: 'poi.toc') are identical.

The file '__xref_misc.tmi___PEOPLE.txt' describes the people in keywords.

Hi Juan,

one more suggestion:

(5) Include XREF folders in the user directory:

In FS 2 there were scenarios that contained XREF objects created by third parties and therefore stored here:

• '/Users/<USERNAME>/Library/Application Support/Aerofly FS 4/scenery/xref'

For additions by third parties, it would be good if PCT could also read this XREF folder.

What files would be needed for this? I only find 'xref_object_xyz.tmb' files

Quote from ApfelFlieger

For the FS 2 there was a whole catalog of these XREF object views in the former Flight-Sim.org, which I also downloaded at the time.

Rodeo Do you remember who has the rights to this catalog or how it is today with the rights?

I ask this because on the one hand it has been published before (but I'm not sure who it was back then) and because it is still an ideal addition to the PCT today.

Hi all,
you're progressing so fast, I hardly can follow up. Congratulations for your excellent work!

ApfelFlieger
This image is from IPACS directly. I have a few XREF libraries with associated images. I'll ask IPACS whether I can publish them.

Hi Claude (Hi Juan),

It continues with my tests.💪

To test the lights, I entered an existing POI of the approach lighting of the RW 30R from OBBI into the PCT.

There are 3 element groups:

• airport_lights
  => That works very well.
• Running light at the middle airport_lights
  => This still needs to be improved (see below). 🚧
• Localizer
  => This also needs to be improved (see below).🚧

With "Point light (custom)" essential input options are still missing:

• LON LAT
• FLASHING
• ORDER

I made these entries directly in the JSON file, which works and is not lost.

With the localizer, the map shows the orientation correctly, but the TOC does not take over this, but places the localizer in the north-south direction.

Jugac64

I have created screenshots of the people, please test whether they can be used in the PCT or what should be changed even better. There are a total of 8 ZIP files, spread over 2 posts.

Post 2