11 hours ago, Happytfe said:

i think it was easier before. Now its like a surprise: will they be there when i arrive? 😊

Then you have not yet fully understand the new concept, I'm afraid. Read the documantation please.

27 minutes ago, kiek said:

Then you have not yet fully understand the new concept, I'm afraid. Read the documantation please.

Thanks for  your help. 
I suppose it maybe a good idea but I find that the effort you have made to prevent us from writing the destination airport on the psxt panel has been replaced by writing it in my_park_airports?. 
I will read the documentation. 
thank you 😊

11 minutes ago, Happytfe said:

I suppose it maybe a good idea but I find that the effort you have made to prevent us from writing the destination airport on the psxt panel has been replaced by writing it in my_park_airports?. 

No, you're wrong. And even if that was true, you have to do it now only once, while before 8.4 you had to do that for every flight to the same destination. 

11 minutes ago, Happytfe said:

I will read the documentation. 

That would be much better 😉 

Edited October 9, 20241 yr by kiek

It's been a while since I've flown in MSFS so I'm slowly catching up to the latest updates and releases. Something I thought of as part of the abandonment of destination airport parking fields:

When the destination airport feature fields were available, I would typically choose the destination and a specific parking gate where I would want to finish the simulation in (consider cases where an airline only has one assigned gate at an airport that serves as a hub for other airlines). I would set the destination gate to prevent an AI generated aircraft from spawning in that particular spot.

With the removal of the DestinationAirport fields, a couple of things got "harder subjectively:

1. We now have to manually open my_park_airports.txt and add the ICAO and gate that we would want to arrive at
2. When adding the parking spot, we now need to look into the corresponding XML file to make sure the parking spot is valid
3. Once the file is edited, a restart of PSXT is required

Wondering if it would be possible to restore the interface that would at least take help automate 1 and 2. Having an automated validation of the parking spot was super useful before. 

Looking forward to trying out the new features nevertheless!

For me the way it is set up now works perfectly because I fly smaller forms , but I can see usefulness of being able to put in destination and parking spot which software will put into my "my_park_airports.txt" file and updated it for now and future references.

If somebody doesn’t put in destination again and fly to the airport the previously assigned spot will be reserved , but it can be updated if you need it.

I can see usefulness of it.

Initially that’s what I envisioned.

Keeping the destination ability for detail assignment.

mike

9 hours ago, AeroMaster12 said:

With the removal of the DestinationAirport fields, a couple of things got "harder subjectively:

1. We now have to manually open my_park_airports.txt and add the ICAO and gate that we would want to arrive at
2. When adding the parking spot, we now need to look into the corresponding XML file to make sure the parking spot is valid
3. Once the file is edited, a restart of PSXT is required

@1 and @2  Note that if you start a flight at that destination at a gate, the gate will be stored automatically for when you return at that field. No need to look into the  airport file. Same when arriving at a destination the gate will be remembered.

@3 I could add a push button, that makes PSXT reload the my_park_airports file, after you have add something to the file manualy, so you do not need to restart PSXT. Will that help you?

7 hours ago, kiek said:

@3 I could add a push button, that makes PSXT reload the my_park_airports file, after you have add something to the file manualy, so you do not need to restart PSXT. Will that help you?

See 8.5.0

12 hours ago, kiek said:

@1 and @2  Note that if you start a flight at that destination at a gate, the gate will be stored automatically for when you return at that field. No need to look into the  airport file. Same when arriving at a destination the gate will be remembered.

Remembering the departure airport isn't too big of an issue, and actually helps prevent aircraft from spawning at the departure gate in the cases that I did a pushback just before PSXT updated aircraft.

Most of the time however, if I were to return to that same airport, I also won't necessarily be parking back at that same gate, so I'd still have to edit the file to change the gate assignment.

Thanks for the push button to reload the file! That makes easier

2 hours ago, AeroMaster12 said:

Thanks for the push button to reload the file! That makes easier

Yeah, and it also checks the stand id for correctness immediately.