I agree with both of you, Nico and vonSzuli. I don't often edit airport files but I have and would probably do so in the future on rare occasions. Nico has spent endless hours building and improving PSXT and I think it makes sense to limit adding future feature requests...say maybe once every three months or six months in addition to dealing with bug fixes as needed. I have to admit a bit of fatigue in constantly updating PSXT - it would be nice to be able to run the same version for months at a time unless bug fixes are needed. NO program will or can be everything for everybody and we shouldn't expect it. I would go so far as to say if one wants a feature request added to PSXT, if it is important to that person, then let a bit of money do your talking - I'm sure Nico would appreciate it.

PSXT/RT gives us the only true live traffic for MSFS, and while not perfect (which no traffic product will ever be perfect) it is the best available and darned good at that.

I agree, this is an incredibly good program that multiplies the basic MSFS experience. I only have one thing to complain about, which is to keep the freedom of modification (instead of the current much more limited form). 

Until now, the files could be modified without restrictions, it was just my decision to share them with the community so that everyone could enjoy the more accurate and detailed parking spaces. 

Money can certainly lead to results, that's for Nico to decide. In any case, I'm grateful that he listened to me and included the sent files.

 

I solved the Marketplace problem.
Currently, airports purchased on the marketplace are not showing up in the PSXT/airports/my_thirdparty (or my_thirdparty2024) folder. But if I create a txt file here with the following text, it will load the specified thirdparty file instead of the stock file. E.g.: archive/thirdparty/LHSimulations/LHBP.xml

8 hours ago, vonSzuli said:

I solved the Marketplace problem.
Currently, airports purchased on the marketplace are not showing up in the PSXT/airports/my_thirdparty (or my_thirdparty2024) folder. But if I create a txt file here with the following text, it will load the specified thirdparty file instead of the stock file. E.g.: archive/thirdparty/LHSimulations/LHBP.xml

Very interesting. I think I have only one or two market place airports but I'll definitely give this a try...if I can remember which ones I bought.

13 hours ago, vonSzuli said:

I solved the Marketplace problem.
Currently, airports purchased on the marketplace are not showing up in the PSXT/airports/my_thirdparty (or my_thirdparty2024) folder. But if I create a txt file here with the following text, it will load the specified thirdparty file instead of the stock file. E.g.: archive/thirdparty/LHSimulations/LHBP.xml

@vonSzuliGood thinking! Although you have to repeat this after each airports scan, like you had to do that for each archive update in the past. (automation may help). EDIT: I've updated FAQ #37 to reflect this.

And btw I was wrong with my (quick) answer to your second question:

"@2 You're right, therefore you have to send the file to me, and I'll put it in the on-line archive, and then you can test it. Takes a little bit more time indeed, but it still can work. I am almost "always on" you know, being a pensionado."

It is way easier that that. Suppose you are updating KSFO, then remove \airports\my_thirdparty\KSFO.txt and put your KSFO.xml in the \airports\my_thirdparty folder.

PSXT will load your local file.  \airports\park_airport.xml is not updated, that only takes place with files loaded from on-line.

This works till you do an airports scan (so don't do that during testing/updating)

Edited January 13, 20251 yr by kiek

14 hours ago, somiller said:

.I have to admit a bit of fatigue in constantly updating PSXT - it would be nice to be able to run the same version for months at a time unless bug fixes are needed.

It was the introduction of MSFS 2024 that forced me to make updates, and before that the introduction of the RT API. However, PSXT and RT are pretty stable at the moment,  hence I predict a few quiet months to come 😉 

Edited January 13, 20251 yr by kiek

We’ll solve this problem somehow!

With these solutions, I can already see that modification/testing will work again. 😉

Hi All

Some advice please. I have this problem with a number of airports that I have purchased on Marketplace (I have an XBOX at a holiday home so use to avoid buying twice). Is there an easy way to know if you are using the right text in the new line to be added? For example I have MKStudios Keflavik which shows in the OneStore folder as mkstudios-airport-bikf-keflavik, so would the correct text file be: archive/thirdparty/ mkstudios-airport-bikf-keflavik/BIKF.xml?

Ian

Put in \airports\my_thirdparty

a text file with the name BIKF.txt

containing this line:

archive/thirdparty/MKStudios/BIKF.xml

Edited January 22, 20251 yr by kiek

Hi Nico

Many thanks

Ian

1 hour ago, icrookham said:

Hi Nico

Many thanks

Ian

@icrookham   Sorry, it must be MK-Studios, so 

archive/thirdparty/MK-Studios/BIKF.xml