Hi,
for the last few days I’ve noticed that aircraft disappear visually immediately during/after takeoff. In most of the cases they are already gone before reaching mid-runway, so I can’t even see the rotation phase anymore.

I just wanted to report it because it feels quite unrealistic compared to before. I’m not sure if this depends on a new version of PSXT or if it is related to the SU5 update.

8 hours ago, fra147 said:

 

Hi,
for the last few days I’ve noticed that aircraft disappear visually immediately during/after takeoff. In most of the cases they are already gone before reaching mid-runway, so I can’t even see the rotation phase anymore.

I just wanted to report it because it feels quite unrealistic compared to before. I’m not sure if this depends on a new version of PSXT or if it is related to the SU5 update.

No it cannot be related to SU5.

Most likely it is an RT issue for that field at that moment in time.

Did not see that here.

Will wait for more users to report this.

EDIT: check: if using the RT App, make sure you have Show All set.

 

Edited May 11May 11 by kiek

Hi Nico,

This is not exactly what the OP reported, but over the last few weeks, I have noticed a deterioration in the quality of the PSXT live traffic. These observations have been noticed at many UK airports, but not exclusively in the UK. The airports where I have seen this behaviour have good RT coverage.

This is what I have observed:

1. Many live taxiing aircraft 'cut corners'. i.e., they do not follow the airport taxiways. I know PSXT does not know the airport layout, except the parking positions, but up until recently, live taxiing aircraft would largely follow the routes expected, but this happens less often now.

2. Many live aircraft now 'freeze' during taxi out, and in particular on the runway, and therefore do not take off. These frozen aircraft eventually get removed by PSXT or by another live aircraft moving over their position.

3. The incidence of live aircraft failing to park on stands properly has increased (i.e., they do not transition to live parked status).  Live aircraft not parking properly is seen as either not stopping in the correct position and then being removed, or they end up in the correct area but start to rotate in a position and then get removed.

I appreciate that a lot of this depends on the quality of the RT data, but the change in what PSXT is showing now compared to what I have seen previously is very noticeable.

Peter

Hi Peter,

You wrote  "over the last few weeks".

Dit you notice this already before 15.0 was released at April 28th?

Did you noticed it as a beta tester?

Nico

No, this is since v 15.0 was released. I did not see this behaviour during the beta test period.

6 minutes ago, Harrier77 said:

No, this is since v 15.0 was released. I did not see this behaviour during the beta test period.

Ah good to know. Then it is more likely a PSXT issue, that can be solved.

4 hours ago, kiek said:

Ah good to know. Then it is more likely a PSXT issue, that can be solved.

Although, I've tested yesterday at KSFO for many hours and I did not see any problems. About 15 aircraft lining up for take-off. Arriving JAL nicely parked at a stand.
That was with (beta) 15.1.1. You @Harrier77have that version too, what is your opinion?

2 hours ago, kiek said:

That was with (beta) 15.1.1. You @Harrier77have that version too, what is your opinion?

I do have that version. I have tested at EGCC, EGPH, EGBB, and EBBR. At all these airports, I have seen many aircraft cut corners and freeze, particularly when moving onto the runway for departure. This morning at EGBB, for almost every second departure, the aircraft froze on the runway. Also, many aircraft cut corners and moved over the grass areas. The issue is definately there at some airports.

I  have this beta as well. While it shined at YSSY yesterday, where I had multiple issues before, EDDF had exactly the same situation as Harrier77 described.

And yes, everything worked perfectly with 14.XX, the best PSXT package I have ever had. Maybe, it's worth to pause with experiment and new additions while it's summer time 🙂 

And I also agree that it's airport-dependent.

Edited May 12May 12 by G-YMML1

I've also seen the freezing aircraft. sometimes on taxiways, and other times on runways - after lining up for takeoff, and also after landing rollout.

1 hour ago, G-YMML1 said:

I  have this beta as well. While it shined at YSSY yesterday, where I had multiple issues before, EDDF had exactly the same situation as Harrier77 described.

Then it points in the direction of RT ...
I'm at EHAM and KSFO the whole day, and no problems at all. Aircraft diappearing  during takeoff I do not see. I remeber these things to happen at EGLL often, even before 14.0

 

Edited May 12May 12 by kiek

I’ve seen this too. I was at CYOW on the ramp just watching AI for a bit.  An ACA flight lined up on 25. It never took off in the sim, but the “blip” in RT was already moving. The ACA flight just sat there for 5 minutes doing nothing, meanwhile the ACA blip on RT was already about 30-40nm out.  Landing traffic just kept coming in over the ghost plane. Littlenav map also showed the ghost ACA plane just sitting there. There was no 2nd ACA plane injected for the actual blip shown by the RT app.

I also see ground traffic disappear or cut corners too even though they are smooth on the RT map.

I just attributed this as a glitch, but it happened again last night with a Porter Airlines jet. I’ll keep an eye out for it again and send logs if I see it.

Edited May 12May 12 by netshadoe

14 hours ago, netshadoe said:

  meanwhile the ACA blip on RT was already about 30-40nm out. 

I've written many times that the RT App and PSXT are two different programs. The fact that you can see something on the RT radar screen does not necessarily mean it will also be visible in PSXT. One is a 2D radar display, while the other is a 3D simulation environment. In addition, several PSXT parameters can influence what you see, and there are many other factors involved.

I've discussed this with Balt. I will implement a continuous RT data quality measurement, mainly by counting irregularities in the RT data stream, and display that figure in the main window. Hopefully that will provide more insight into the quality of the incoming data.

 

Thanks Kiek. I checked RT and everything is set as you suggested, including “Show All”. I can confirm, regarding the reports from others, that I noticed this behavior especially at EGLL (rwy 09R)

I’ll need to do some more testing to verify whether this is a consistent pattern everywhere or if it only happens at certain airports. I was simply reporting what I observed at Heathrow, which is different from what I experienced with previous PSXT builds at the same airport.

In any case, it’s not a major issue and hopefully it can be improved over time. Thanks again, as always, for all your work and support.

Francesco

9 hours ago, kiek said:

I've written many times that the RT App and PSXT are two different programs. The fact that you can see something on the RT radar screen does not necessarily mean it will also be visible in PSXT. One is a 2D radar display, while the other is a 3D simulation environment. In addition, several PSXT parameters can influence what you see, and there are many other factors involved.

I've discussed this with Balt. I will implement a continuous RT data quality measurement, mainly by counting irregularities in the RT data stream, and display that figure in the main window. Hopefully that will provide more insight into the quality of the incoming data.

 

So I am clear on this then....

You're saying that the Air Canada 737 I watched PSXT taxi from the terminal to runway 25, using the target data that RT was feeding to PSXT (RT=RealTraffic, the app that PSXT draws data from so we are clear) that I watched on the RT map screen in real time, side-by-side on the same computer....it then taxis out on the runway just like the RT app...then the 737 just sits there on the threshold for five minutes.  Meanwhile, the same target on the same RT app that is feeding PSXT does the takeoff and is nearly 40 miles away when the forgotten Air Canada 737 on the threshold is deleted (5 minutes or so).

So, what I'm trying to wrap my head around is why would PSXT stop using the data from the same target that remained on the map in RT - it was there - it didn't change or glitch out - it flew for 40 miles from takeoff until the 737 was deleted.

It's hard to convey in words what I'm seeing. But, are you saying that the data in RealTraffic is ignored by PSXT when certain parameters and factors are involved?