Hi Nico! I have several questions about the new version.
So far I have been using my own, modified files in the my_thirdparty folder. These files contain all the parking spaces of the given airport, I have also modified the coordinates to match the real values, so my successful parkings are much better and the planes are actually parked in the parking spaces where they are in reality.
After RESET, new files are created in the my_thirdparty folder. The number of parking spaces in these files is often significantly less than the ones I modified. The coordinates do not match the real data either, so the program often modifies the parking position of the approaching aircraft (it moves the aircraft away).
1. Can I continue to use my modified files? (currently the program allows it, but the parkings are always unsuccessful)
2. Is it enough to add the type values to my previous files?
3. The parking space ID codes have changed. If I want to record the missing parking spaces (e.g. secondary, tertiary parking spaces: 36L, 36R), does the ID name matter for them?
4. Overall, how can I make the modifications that I have been able to make so far?

Suggestion: It would be nice to have an accessible database where I can download the basic files if I want to modify the coordinates and parking spaces.

Hi vonSzuli!

I'm confused and surprised about the things you are doing...

40 minutes ago, vonSzuli said:

So far I have been using my own, modified files in the my_thirdparty folder.

These "files" are not for modification. Normally these are shortcuts to the file in the archive. Only when there is no file in the archive (for your version) an .xml file is being generated and copied to tblo. The file in my_thirdparty is for temporary use till I've added it to the archive, and will be replaced by a .txt at the next airports scan. 

40 minutes ago, vonSzuli said:

After RESET, new files are created in the my_thirdparty folder.

No, after each Airports scan...

40 minutes ago, vonSzuli said:

1. Can I continue to use my modified files? (currently the program allows it, but the parkings are always unsuccessful)

You can continue your "illegal" work 😉 

40 minutes ago, vonSzuli said:

2. Is it enough to add the type values to my previous files?

 Yes, I would think so.

40 minutes ago, vonSzuli said:

3. The parking space ID codes have changed. If I want to record the missing parking spaces (e.g. secondary, tertiary parking spaces: 36L, 36R), does the ID name matter for them?

No. 

40 minutes ago, vonSzuli said:

4. Overall, how can I make the modifications that I have been able to make so far?

The 'royal route' is to create a handmade learned file, see the Manual 8.18.1.  Don;'t mess around with files in my_thirdparty. Maybe I'll change my program such that the .xml file does not stay ...
 

40 minutes ago, vonSzuli said:

Suggestion: It would be nice to have an accessible database where I can download the basic files if I want to modify the coordinates and parking spaces.

I can imagine, but that will not happen. That knowledge is and stays propriatary. There are more traffic programs these days, you know.

Edited February 21Feb 21 by kiek

Thank you. Fixing the type values solved the problem, now the program works fine. 
According to what you wrote, the solution for me in the future may be sub-point c) of point 8.18.1 of the PSXT manual. Here it is written: "PSXT will then take your file (only) if Learn Real and/or Learn Soft is true, and add learned options." Where exactly should the Learn Real and/or Learn Soft parameter be set to true?

12 hours ago, vonSzuli said:

Thank you. Fixing the type values solved the problem, now the program works fine. 
According to what you wrote, the solution for me in the future may be sub-point c) of point 8.18.1 of the PSXT manual. Here it is written: "PSXT will then take your file (only) if Learn Real and/or Learn Soft is true, and add learned options." Where exactly should the Learn Real and/or Learn Soft parameter be set to true?

Oh, I'm sorry. The Manual is not up to date. That sentence is somethim of the past, it must be deleted. 
Your handmade file will always be read and "overwrite the airport file from the archive.

Thx for pointing at it.

The following lines are now in the airport file header (not all data has been updated yet):

 

<?xml version="1.0"?>

<meta>

<info name="author" value="PSXT" />

<info name="version" value="5.5.1" />

<info name="date" value="Sept 26, 2025" />

<info name="copyright" value="(c) 2025 vonSzuli, Hungary, All Rights reserved" />

<info name="MSFS" value="2020" />

</meta>

<parameters>

<parameter name="airport_name" value="Ferihegy" />

<parameter name="publisher" value="LHSimulations" />

<parameter name="altitude" value="448" />

<parameter name="num_parkpos" value="75" />

<parameter name="Qf_real" value="56" />

<parameter name="Qf_soft" value="0" />

<parameter name="RT_traffic_week" value="Jan22 - Jan28" />

</parameters>

 

Where exactly and how does the handmade="true" parameter go?

Should I leave all the data in it, or just the airport_name and publisher parameters as described in the Manual?

1 hour ago, vonSzuli said:

Where exactly and how does the handmade="true" parameter go?

In the parameters block, does not matter where exactly.

1 hour ago, vonSzuli said:

Should I leave all the data in it, or just the airport_name and publisher parameters as described in the Manual?

Leave it in except Qf.
QF is no longer relevant, will probably be calculated when the file is loaded and only kept in the UI.

For traffic week, fill in a number 1 .. 52  (does not have to be accurate, but an integer is expected)