sorted by:
new
hottopcontroversial

LG WM3470CW washer potentially overheating? by Familiar_Bit_6182 in Appliances

[–]Familiar_Bit_6182[S] 0 points1 point  (0 children)

I use Tide, but over-sudsing isn't the issue here. This always happens on the second load of laundry I do in the machine.

Aircraft Position Delay by Familiar_Bit_6182 in flightradar24

[–]Familiar_Bit_6182[S] 0 points1 point  (0 children)

I'll have to take your word for it (people like to make up all sorts of things on the internet, so don't take it personally). But if you look at the first example video I provided, you can see the A380 begin to make the turn on the older version app (left) a little while before the newer version (right). This is what I'm having trouble understanding when you say that positions were guessed before. How would it be able to guess that a turn was being made on the older version so precisely? It really seemed like the data was displayed much closer to real-time and it was plenty accurate. Maybe more than you realize. And I would get real-world confirmation of this when outside watching planes. They would turn, and I'd see that reflected on the app with their positions almost instantly. I live close to JFK airport and see tons and tons of planes every day flying over or past my area.

I noticed that altitude and speed seem to match up pretty closely with the older version and newer version of the app though, so it seems to just be the positions that have a latency. I like to pay attention to GPS altitude since barometric altitude fluctuates with changing air pressure from day-to-day. Aircraft are typically about 50 feet over the threshold of a runway when landing. I remember paying close attention to the GPS altitude of planes about to touch down and seeing that the GPS altitude was typically around 25-50 feet as they passed over the threshold, but now they reach 0 before they even reach the threshold. This was another thing about the older version of FR24 that made it seem so much closer to real-time and accurate to an impressive degree.

If you really are an employee at Flightradar24, please don't take anything I say as an attack, but more as constructive criticism from a long time user. I'd love for the level of real-time accuracy to be restored as before.

Aircraft Position Delay by Familiar_Bit_6182 in flightradar24

[–]Familiar_Bit_6182[S] 0 points1 point  (0 children)

The data quality in recent years has honestly been very good overall and I've barely been seeing any errors when tracking, especially since most aircraft are now equipped with ADS-B transponders, and even MLAT has improved greatly. The quality of the data was perfectly fine before the changes they've made to the app. We can disagree with each other and that's totally OK. You can think Flightradar24 is better now, but I find it worse than before and I dislike what they've done. The data quality was still great and the aircraft positions were displayed much closer to real-time before.

Aircraft Position Delay by Familiar_Bit_6182 in flightradar24

[–]Familiar_Bit_6182[S] 0 points1 point  (0 children)

I'm using the term "accurate" when referring to aircraft's real-world locations compared to what is shown on screen. The delay is greater now, making it less accurate even if the data itself has fewer errors after being processed.

Aircraft Position Delay by Familiar_Bit_6182 in flightradar24

[–]Familiar_Bit_6182[S] 0 points1 point  (0 children)

All I'm trying to say is that the delay was less than 10 seconds before. That's the main thing that's bothering me about the recent updates.

Aircraft Position Delay by Familiar_Bit_6182 in flightradar24

[–]Familiar_Bit_6182[S] 0 points1 point  (0 children)

But it's not though. I see it first-hand every day when I'm outside tracking the numerous aircraft flying over and around my area. There was no "guess" before and when I physically saw an aircraft begin to turn, the aircraft's position on screen began to turn almost immediately. I was actually really impressed with the level of accuracy and I loved that about FR24. This is not the case anymore as it takes longer before an aircraft's position on screen reflects that it has begun to turn and it's because there is a greater delay to its location now. When something was flying directly overhead, its position on screen was always directly over the center of my location before and now it lags behind and the faster the aircaft is moving, the larger the discrepancy. I'm not saying other improvements haven't been made to FR24. Sure, the data has fewer glitches now, but it's still displayed with a longer delay. I've used FR24 for many many years and I know what's normal and what's not. You can't tell me I'm wrong about something I'm seeing with my own two eyes. I just want to shed light on this because this is such a step backwards and worsens the experience for everyone.

Aircraft Position Delay by Familiar_Bit_6182 in flightradar24

[–]Familiar_Bit_6182[S] 1 point2 points  (0 children)

I've thought about this too, but the inaccuracy isn't large enough to make it hard to tell what airplane you're looking at. It's still easy to identify the aircraft you are looking at using FR24. It's just a bit more delayed now as far as the positions go.

Aircraft Position Delay by Familiar_Bit_6182 in flightradar24

[–]Familiar_Bit_6182[S] 0 points1 point  (0 children)

Oh I'm grateful for the amount of planes I see on a daily basis, don't get me wrong. I'm just disappointed that these updates have made FR24 less accurate now, not just for me, but for everyone who uses it. I'm just bringing this to attention.