I hope I’m not reporting any known bugs. If so, I apologize.
Hello! Thank you for the feedback!
This has not been reported before, so thank you!
Unfortunately, it is very hard to reproduce this since you’re dealing with live data here. We have no idea what the data we get from VATSIM looked like at this point.
I will try to keep an eye out, but there is a high likelyhood that I will miss the next time that this situation shows up. If you manage to catch it again, please visit the following link:
Save the contents (Ctrl + S or copy-paste) and attach the resulting file to a post on this topic! This will be invaluable for us when attempting to fix the issue.
Kind Regards,
Malte
Perfect, thank you. I saved the link to download the data and will use it when I find a similar situation. It will be difficult because I imagine that cases like this can only be encountered in large events. If it can be useful as information, I also encountered the same problem of the undetected area on VATSpy, while it was correctly identified on vatsim-radar.
Sounds good! Yes it’ll probably be challenging, but there is definitely a better chance of you seeing it I think. Yeah, vatsim-radar has done a great job with this handling for sure!
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
vatsim-data.json (1.4 MB)
In reference to an old report of mine I send you the json file of vatsim data. in this case what was missing was AFRE_FSS (so an FSS not a CTR, but still a controller)
Thank you! I have noted your report.
Be aware: Vatsim Radar now also includes airspace from vatglasses, which we currently don’t have. So the coverage could be different due to this as well!
We shall investigate as soon as we have the resources to do so.
Kind Regards,
Malte
