Hello Kiek. Some suggestion:)

[kiek]

On 3/27/2025 at 10:11 PM, AbrahamGR said:

Hi Kiek. First of all, thank you for considering the new option you included in the update.

I have just ran a test, and unfortunately it didn't work.

Hi,

You must have misunderstood 10.8.0. The new algorithm is only about taxiing aircraft... So for instance aircraft waiting in line for take-off will remain more visisible.

Nothing has changed with push backs. In 10.8.1 I'll add the same mechanism for aircraft that have finished push_back (and are therefore in the push_backed state, waiting for data that triggers them to go for taxi.

Nico

Edited March 29 by kiek

[kiek]

8 hours ago, G-YMML1 said:

Nico, this new option does not work for me at least for now. I presume that if I remove hidden parameters from the *ini file, PSXT handling of taxiing plane would return back to 10.7?

The algorithm works for everyone 😉 

I can clearly see in my trace statistics that less aircraft disappear. Besides, it will not do any harm.

Removing the parameters from the parameters.xml file will not help, then the default values will be taken and you will see them written back into the parameters.xml file. The only thing you can do is to set the parameters at their lowest values, so dist 10 meters and max time 1 minute. But, again, there is no real reason for doing that.

Edited March 29 by kiek

[G-YMML1]

Well okey, I will give another shot. My problem is that arriving planes at KDEN and KPDX (I flew this route yesterday) freeze once approaching a gate and never park. They will disappear either in 20min or some other AI hit them. Yeah, it solves one issue, but brings another one.  

[G-YMML1]

BTW, how to decrease 20 min to 5 min. 

PS. The manual PDF link appears to be broken. The Release notes is fine. 

[kiek]

38 minutes ago, G-YMML1 said:

Yeah, it solves one issue, but brings another one.  

That can be repaired. It is two steps forward, one step back.

[kiek]

37 minutes ago, G-YMML1 said:

BTW, how to decrease 20 min to 5 min. 

PS. The manual PDF link appears to be broken. The Release notes is fine. 

You can always find the Manual in the \docs folder of your local PSXT implementation ...

RE-stored the Manual at my site too.

[kiek]

2 hours ago, G-YMML1 said:

My problem is that arriving planes at KDEN and KPDX (I flew this route yesterday) freeze once approaching a gate and never park. 

That's a sperarate  issue, sometimes the aircraft does not arrive close enough to the gate (maybe because the aircraft addon is not very accurate with its gates) . This has always been the case , although until 10.8.0 it would wait for 30 seconds and then disappear. Now I've to take care of that otherwise it will wait 20 minutes.  

Edited March 29 by kiek

[G-YMML1]

7 hours ago, kiek said:

That's a sperarate  issue, sometimes the aircraft does not arrive close enough to the gate (maybe because the aircraft addon is not very accurate with its gates) . This has always been the case , although until 10.8.0 it would wait for 30 seconds and then disappear. Now I've to take care of that otherwise it will wait 20 minutes.  

I "think" I haven't seen those parking issues prior to 10.8 

[AbrahamGR]

12 hours ago, kiek said:

You can always find the Manual in the \docs folder of your local PSXT implementation ...

RE-stored the Manual at my site too.

Hi, I don't know if I'm helping or hindering, but I'll share with you in a little more detail what happened on my next flight: LEMD - LEMG after the last update.

Upon arriving at LEMG, I noticed a plane stopped and taxiing out of the runway. It had just landed, but, logically, the RealTraffic signal was lost at that position, so PSXT did the logical thing: keep it visible until the plane reappeared. But it didn't, and the plane remained there for a while. And I was behind it.

On the other hand, an "airbaltic" plane performed a pushback with a gate change. And then it began taxiing. In this case, PSXT had it visible, but it suddenly disappeared after 7 minutes. On radar, the plane continued taxiing to the runway. Then PSXT injected it there for takeoff.

That is to say, although many aircraft visibility options are still very successful and enhance immersion, there are still many variables that cause planes to do strange things. The truth is, when it works, you say, "Thank you!" because the saddest thing is watching planes appear and disappear in front of you because the signal is intermittent.

As for the rest, I guess it's a matter of fine-tuning little by little without abusing your work, kiek.

Thank you very much again!!!

[kiek]

9 hours ago, G-YMML1 said:

I "think" I haven't seen those parking issues prior to 10.8 

Then you were lucky. I've seen plenty.

[kiek]

6 hours ago, AbrahamGR said:

Upon arriving at LEMG, I noticed a plane stopped and taxiing out of the runway. It had just landed, but, logically, the RealTraffic signal was lost at that position, so PSXT did the logical thing: keep it visible until the plane reappeared. But it didn't, and the plane remained there for a while. 

In the next version, I'll not use my new algorithm when a plane is in the landing_roll

6 hours ago, AbrahamGR said:

On the other hand, an "airbaltic" plane performed a pushback with a gate change. And then it began taxiing. In this case, PSXT had it visible, but it suddenly disappeared after 7 minutes. On radar, the plane continued taxiing to the runway. Then PSXT injected it there for takeoff.

Yes, there will always be strange things to see. Pls read the disclaimer in section 1.3 of the  Manual. 

PSXT is not perfect, but the excitement of seeing this real live traffic, and/or taxiing/flying in this real live environment, is its Unique Selling Point.

 

 

[AbrahamGR]

Hi. I've updated PSXT. It's getting better and better.

In this case, a Norwegian plane froze in the middle of the runway while still on the ground as it was about to take off. A minute later, another plane took off down the same runway, but the Norwegian plane hadn't disappeared.

Perhaps it would be interesting if planes taking off, if they lose signal at that moment, wouldn't disappear, but would ascend in a straight line until they found their next "signal insertion point."
This way, we wouldn't see it disappear during takeoff, and the next plane could take off without another one on the runway. In the worst case, they would dissappear in the sky, far from the airport, and it would be more discrete.

In fact, right now at LEMG, I'm seeing many planes frozen in their taxi-in or taxi-out positions because their signal disappears. They've been like that for 15 minutes. Perhaps it would be better if, except for those doing pushback, these planes stayed, not for 20 minutes, but for 3 or 4. Sometimes, those that have just landed, get frozen on a taxi runway, and then their next signal is already at the gate. But I wouldn't mind if they were brought to it slowly, visibly. It's preferable to them disappearing.

I know sometimes airports dont have signal from realtrtaffic, but PSXT can sometimes be a bit of an illusion and make us think everything is going well!

Thanks for the progress!

Edited March 30 by AbrahamGR

[kiek]

38 minutes ago, AbrahamGR said:

Perhaps it would be interesting if planes taking off, if they lose signal at that moment, wouldn't disappear, but would ascend in a straight line until they found their next "signal insertion point."

Too complicated.

38 minutes ago, AbrahamGR said:

In fact, right now at LEMG, I'm seeing many planes frozen in their taxi-in or taxi-out positions because their signal disappears. They've been like that for 15 minutes. Perhaps it would be better if, except for those doing pushback, these planes stayed, not for 20 minutes, but for 3 or 4. 

You can set 3 or 4 minutes your self in parameters.xml

38 minutes ago, AbrahamGR said:

Sometimes, those that have just landed, get frozen on a taxi runway, and then their next signal is already at the gate. But I wouldn't mind if they were brought to it slowly, visibly. It's preferable to them disappearing.

That's not possible. PSXT has no notion of runways and taxiways.  It only knows the parking positions ... On top of that it sometimes not even knows if the aircraft is arriving or departing. If it has just landed, I know it, but if an aircraft is just "thrown" on the airport I don't know. I cannot trust origin /  departure data either.

EDIT: If you want to see everything almost perfect, you must limit yourself to the well covered airports, LEBL and LFMN for instance.

Edited March 30 by kiek

[Robert_LH]

Kiek, 

I can‘t thank you enough for the improved taxiing behaviour. It adds so much to the realism by having „stable“ aircraft in line for take off, which do not disappear anymore.

Amazing work!

[Harrier77]

14 hours ago, Robert_LH said:

Kiek, 

I can‘t thank you enough for the improved taxiing behaviour. It adds so much to the realism by having „stable“ aircraft in line for take off, which do not disappear anymore.

Amazing work!

I can't agree more! Nico always listens to the users suggestions and implements timely changes if they are sensible and possible. Thank you.