FS Traffic

@nick yeah looks like for me - changing times messed it up. I saw no traffic enroute - I'm 60 miles out now and it has spawn 7 planes in the air destined to the same airport I'm going to but nothing on the ground so far. I'll reload after this and continue on testing - pretty sure it shouldn't work like this, however it was my fault I believe for letting it happen.

@andybrwn7 Check out the V1.0.2 update. It should address those compatibility issues with other addons. We've also included a way of disabling the in game panel entirely, allowing you to set the destination in the Traffic Control Centre instead. John - Just Flight

@dommel This is very likely a scenery issue. What payware addon are you using? John - Just Flight

@balzbac I'm not sure that your reply adds anything valid to my post. Not sure if you're trying to invalidate my disappointment by sprinkling on some positivity. As a paying customer, I expected more. I'm not picking a fight, I just don't see why you had to reply in those terms.

@b3_burner Thanks for making this clear, I was actually already suspecting this, as I saw no traffic change when changing the time-slider Good enough for me, I'm happy with setting the correct time and then having realistic traffic for that time (as I usually only find time very late in the day, where "live" traffic isn't that prominent). Cheers

@voice-of-reason @Derek When I wrote my initial post, I did not understand how many issues the system (MSFS or FS Traffic) had with the traffic itself. I'll buy the package according to the first 'encouragement'. But a nice traffic package for my part, aside from the model library, would be 'something that lives its own life'. I would not like to specify where I'm headed or restart the simulator for every flight, and would expect proper en-route traffic at correct flight levels during a flight, and a proper traffic pattern where ever I would land. Hope there is direct dialog with MSFS/Asobo to improve the system? Another issue with the simulator itself, that adds a lot of stress for the end user, is the lack of a 'static aircraft' switch in the options menu. If one wants to fly without traffic, the 'static aircraft' that many developers add make the airports look great and feel live enough and add atmosphere. Ideally I would just like a switch to turn on and off traffic, and not needing to think more about it. Hence pay Just Flight a decent amount for the traffic product, and spend my time flying in the simulator. Just some thoughts from an end user.

@baxterchico said in My experience with FS Traffic: My experience with FS Traffic. I bought the product with great anticipation. As I find AIG very complicated to install. FSLTL is very simple, but it just eats up too much performance for me, so I'm happy to have FS Traffic. Where I notice noticeable performance improvement. On average this is 5-8 FPS. I stream on Twitch and have also presented your product, but I also had to explain the negative points of your product to my viewers, and they were unfortunately very clear on the day of the presentation. Let's start with the negative points that I noticed. I had to restart the simulator several times to see the traffic again. after each flight I have to go to the \AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages folder and remove your Justflight Moule, otherwise I won't have any traffic at the next start. This is a workaround I found out myself. After deleting the module, everything is ok again at the next start. Something like this should not happen, that the player has to leave the game after every flight to fix this. Thanks very much for your feedback. Neither of those issues you mention should be happening and although your workaround obviously 'works' it's not what was designed Very interesting to read your experiences with GSX. There are reports online of FSTL and AIG having issues with the maximum object limit - but other users in the forum are saying they have never had a problem with object limits with other traffic programs - only FS Traffic. I am inclined to think the location may be the main reason for this (hence the variety of experiences), but it's not my area of expertise and it is something we are looking into. As I've mentioned elsewhere, we even created a tool to help with the object limit - but other users are saying that is no help.

@twentyfivehundred said i If you have no ground objects how does FS Traffic push back planes? I have noticed with FS2020, even with no traffic add-ons, that sometimes when an AI plane calls for a pushback, and ATC tells them there is no pushback tug available, the AI aircraft still gets pushed back, even though there is no tug there.

@pscharff I agree as well as supporting MSFS. Gotta have traffic first.

@derek said in First impression bugs.: @bpfonteyn said in First impression bugs.: @mach-2 said atc_airline=JAPANAIR, I corrected to. atc_airline=JAPAN AIR It is now pronounced correctly. Could this be why I’m hearing call signs being spelled phonetically rather than properly pronounced? I’ve noticed in the ATC text window that British Airways planes are spelled as Speedbird. When ATC calls them it says Sierra Papa Echo etc. If the callsign was corrected to Speed Bird, I wonder if that would stop ATC phonetically speaking the call signs. Yes - as I say, we are looking to fix that bug. THANKS Derek

@2thfixer name one addon that has been released that has no issues on first release

@disc79stu said in No Traffic at larger Airports with and without Couatl (GSX) running.: Same issues for me with larger airports like EDDM and LEBL etc... This is ridiculous. Wothan's workaround didn't fix it for me unfortunately. If you have no traffic at a large airport then the software isn't working as it should. Please get in touch with Support and we can look into it. We can go through all the usual steps from the FAQs and if that doesn't work then we can try to find out what specifically is causing the issue.

@nd23rin said in KSEA is like a circus: Wow, I apologize for piling on but come on guys. I just loaded into default KSEA and it is actually hilarious how bad this is. Planes are landing constantly and 50% of them are hitting the runway and making immediate hard lefts at full landing speed driving across the grass right past the gates onto the highway. The other 50% are about 100 feet behind doing Top Gun style go arounds at what looks like 100 ft over the tower in a bank. I haven't seen one plane actually takeoff, and ATC is randomly requesting pushback from a few aircraft yet nothing ever happens. I have GSX turned off, so couatl isn't even running. I'm sure alot of this boils down to MSFS just not being fully ready to do traffic correctly, but patience and a little (alot) more testing may be in order here. Tried KPHL and basically just saw nothing in the air just some aircraft on the ground. Probably gonna give this another day or two and then refund as well. If you raise a support ticket we can take a look at Seattle and see if we can replicate what you are seeing. making immediate hard lefts at full landing speed driving across the grass right past the gates onto the highway. That sounds bizarre. Not sure we have seen that reported and I would think there is a pretty straightforward explanation/fix.

didnt think the sounds would be that loud in the cockpit any way

@tigergoogs said in CTD with Traffic: removing flightcontrolreplay-ingamepanels-custom wow, this makes me hate flight control replay even more! removing flightcontrolreplay-ingamepanels-custom worked for me too after multiple attempts! thank you.

@qqwertzde Canadian North and First Air merged now they use Arctic for their callsign and code AKT. Empress was the callsign of the original Canadian North airline.

@sinanajibi said in Quick Fix for No Traffic: @derek Thanks for the reply! However, in your example, mookie261's suggestion cannot be considered as a fix as it is a workaround.. Agreed, but if a clever person wrote a script to do that and sent it out as a fix there would be some disappointment It is definitely not a soution, but it does point to either a different problem between the two users (despite similar symptoms) or (more likely) a difference between their setups which is why we wanted to direct everyone to Support.

@jf-john ok thanks for update