FS Traffic

Thanks for reporting. We have this logged on our internal bug tracker and it will be investigated ahead of a future update. In the meantime, airports can be added to FS Traffic manually via the "Adding a new airport" method listed on Pages 26-28 of the FS Traffic manual: https://downloads.justflight.com/products/JFF003616/FSTraffic_MSFS_manual.pdf Mark - Just Flight

I've noticed the same problem and sort of know why it happens. First flight works fine and shows traffic. But If I do another flight at another location there is never ever any aircraft. What I do is shut down the PC and restart and traffic is there. So to me the problem is if I do a second flight at another location - No Traffic-

I had read somewhere in the MSFS forums that FS Hud now (mostly) works with FS Traffic, but unfortunately that turned out to be fake news. Still the same issues: a couple planes will land, but none of the planes spawned at the airport gates (which are about half of the usual amount) ever depart. So, unusable. I asked the team over at FS hud. They say: "There is still an issue of FS Traffic side that they have to fix. FS Traffic side doesn't update departure instructions for intercepted aircrafts - it was discussed with FS Traffic dev team and this fix is on their side." FS Hud has made great strides in development, and now that you can select active runways in the newest update, I might have to ditch FS Traffic entirely, which would be too bad. Wish my favorite ATC app and my favorite traffic app would just get along. I understand that there is always plenty to take care of for JustFlight, especially with Asobo putting out that mess of a beta version of MSFS 2024, but I wonder if the years of saying "it's on the to-do list" will ever result in anything, at least for the 2020 version?

I suspect this will have been intentional, as we don't have an Emirates A350 livery, so the VMR file is pointing to the closest match, which is the 77W. I'll raise this with our development team as something to check ahead of the next update. Mark - Just Flight

There were some lighting changes in the core simulator post-Sim Update 4, and our development team will be investigating what, if any, changes are required to the FS Traffic aircraft ahead of the next update to the product. Mark - Just Flight

Thank you. No, I had not thought to try that, and it does work in 2024. A very strange and unintuitive interface! Groetjes ! P.

Thanks as well - Still really looking forward to this one.

Thanks, @Mark.

There have been various improvements to this over the course of FS Traffic's updates; however, it's sadly not something that can be removed entirely without affecting the traffic generation at the destination airport. The small freeze is caused when the FS Traffic module detects that the player is within a certain radius of the destination airport, and starts to read the schedule files that are stored locally on your PC. Once it reads those schedule files, it'll start to generate the relevant traffic. The more schedules that exist at the destination airport, the longer it'll take for the FS Traffic module to read those; therefore, the size of the freeze is directly related to how busy the destination airport is. For example, if you approach a small to medium-sized airport like Manchester (EGCC), you may only notice a small stutter, but if you approach Chicago O'Hare (KORD) at rush hour, you will get a larger stutter. Mark - Just Flight

@dosendo said in Traffic settings: I only would like to know that about how those settings must be set that they are correct to use FS Traffic. Just Flight Support can help you with that. The forum is really only meant for users to chat about products.

Found where it is now, thanks.

FS Traffic traffic is spawning OK with GSX Pro uninstalled in Sim Update 4 Beta (1.6.23.0) for me as well as GSX Pro reinstalled with characters quantity set correctly.