Customizing parking with 3.5

[Dave_YVR 926]

Hi Nico,

 Any suggestions on how the best maintain my customized parking while working with 3.5?   As we all know most airports especially payware airports don't have anywhere near enough ga/bizjet parking. I have been manually adding spots to help fill the fbo ramps with biz jets etc but am unsure how to best go about continuing this with the new version.

[kiek 1,135]

On 9/26/2023 at 9:13 PM, Dave_YVR said:

Hi Nico,

 Any suggestions on how the best maintain my customized parking while working with 3.5?   As we all know most airports especially payware airports don't have anywhere near enough ga/bizjet parking. I have been manually adding spots to help fill the fbo ramps with biz jets etc but am unsure how to best go about continuing this with the new version.

Good point, a definition oversight. I did not realise that manualy created gates would not synchronise with the gates in the archived airport file... Only new options from gates in the archive file will be added.

Hense I suggest this solution:

If you add a new keyword  manual="true" to your new gates (at any place in the same line), everything will run fine.

Suppose it is KDTW.xml  from published PUB

Place your file here airports\learned\thirdparty\PUB\KDTW.xml

 

 

Edited September 30 by kiek

[Dave_YVR 926]

 Thanks Nico. I'll try it out and see what results I get.

In previous versions, I have added about 30-50 spots to various airports and psxt near instantly has parking assignments for them, so they just get better and better.

Edited September 27 by Dave_YVR

[kiek 1,135]

3 hours ago, Dave_YVR said:

 Thanks Nico. I'll try it out and see what results I get.

 

It is not yet released. Maybe tomorrow in 3.5.1.

But you can prepare your files already ofcourse.

[Dave_YVR 926]

So just to clarify as an example

    <parkpos id="r34" latitude="32.8423691" longitude="-96.8436203" heading="315.299988" radius="15" cargo="false" ramp="true" manual=”true” /> for any custom  spots. I'm curious as to why we would even need to add a new entry for every custom parking spot as it worked great before without having to specify anything different.

 So with doing that I'll need to keep backups as every update to PSXT will overwrite my custom files when I put them in the airports\archive\thirdparty\devname folder? That was the best part of having the updated folder in previous versions, as we didn't have to worry about custom files getting wiped out with new versions. 

 

Edited September 29 by Dave_YVR

[mmcmah 149]

11 hours ago, Dave_YVR said:

So just to clarify as an example

    <parkpos id="r34" latitude="32.8423691" longitude="-96.8436203" heading="315.299988" radius="15" cargo="false" ramp="true" manual=”true” /> for any custom  spots. I'm curious as to why we would even need to add a new entry for every custom parking spot as it worked great before without having to specify anything different.

 So with doing that I'll need to keep backups as every update to PSXT will overwrite my custom files when I put them in the airports\archive\thirdparty\devname folder? That was the best part of having the updated folder in previous versions, as we didn't have to worry about custom files getting wiped out with new versions. 

 

You wouldn't have them overwritten because you would put them in the Learned folder and folder structure rather than in the archive. Look at Nico's response again:

On 9/27/2023 at 7:22 AM, kiek said:

If you add a new keyword  manual="true" to your new gates (at any place in the same line), everything will run fine.

Suppose it is KDTW.xml  from published PUB

Place your file here airports\learned\thirdparty\PUB\KDTW.xml

 

 

 

Edited September 30 by kiek

[Dave_YVR 926]

31 minutes ago, mmcmah said:

You wouldn't have them overwritten because you would put them in the Learned folder and folder structure rather than in the archive. Look at Nico's response again:

Ah gotcha... Ok, I'll try that. Thanks for the point out!

[kiek 1,135]

11 hours ago, Dave_YVR said:

 So with doing that I'll need to keep backups as every update to PSXT will overwrite my custom files when I put them in the airports\archive\thirdparty\devname folder? That was the best part of having the updated folder in previous versions, as we didn't have to worry about custom files getting wiped out with new versions. 

mmcmah has given you the right answer already.

Remember, In the new way of doing things you have the best of both worlds, in the old way you were "on your own" in \updated_airports

Edited September 30 by kiek

[kiek 1,135]

22 hours ago, Dave_YVR said:

    <parkpos id="r34" latitude="32.8423691" longitude="-96.8436203" heading="315.299988" radius="15" cargo="false" ramp="true" manual=”true” /> for any custom  spots. I'm curious as to why we would even need to add a new entry for every custom parking spot as it worked great before without having to specify anything different.

You need that because PSXTraffic now works with two files, always with the ofline generated file in the archive, and (optional) an on-line learned options file in the Learned folders. PSXTraffic adds the learned options based on the id of the parking position. It checks these names for synchronisation, hence if you add a new name (position) you have to specify that with attribute manual, otherwise PSXTraffic would ignore it (unknown id..). 

Edited September 30 by kiek

[Dave_YVR 926]

Ok, thanks. I'll see how it goes. I'm sure I'll have more questions down the road. 

[Dave_YVR 926]

Ah.. This didn't take long at all. So I add one of my custom airport files to the airports\learned\thirdparty\devname folder and start the sim and PSXT.  As soon as the very first update occurs, the airport file that I just put in there changes to something very different. Where does the airport file with all of the custom parking coordinates go?

 As custom airport files are generally a continual work in progress, if I now go and make more changes to my backup copy and put it in with the recently updated one, it will overwrite any of the newer updates. 

[kiek 1,135]

1 hour ago, Dave_YVR said:

 As soon as the very first update occurs, the airport file that I just put in there changes to something very different.

NO, it does not. The aiports\learned\... hierarchy is local, only at your end. It is not part of an update. Only the airports\archive\... hierachy is being updated each week.

Edited October 1 by kiek

[Dave_YVR 926]

So when I make more changes to any airport file and drop it in overtop of what has been learned locally, I lose whatever has been learned before that. Where does the data for the custom parking spots go?

[kiek 1,135]

4 hours ago, Dave_YVR said:

So when I make more changes to any airport file and drop it in overtop of what has been learned locally, I lose whatever has been learned before that. Where does the data for the custom parking spots go?

No, you do not change the archived file, but add the new gate(-s)  to the already existing locally learned file. Nothing gets lost.

[Dave_YVR 926]

39 minutes ago, kiek said:

No, you do not change the archived file, but add the new gate(-s)  to the already existing locally learned file. Nothing gets lost.

 But where has the parking data that I have added gone? I'm pretty unsure about how much I like this. With the updated airports folder, I could just work from those files knowing what parking exists on the airport as well as the updated assignments.