No traffic at destination. Again and again.
-
@art_p Thanks for the feedback. We are working on a fix for this dependency.
Yes that is one potential issue with the setting the wingspan to that option. We tried to optimise these to give the best balance of aircraft actually appearing at the gates of poorly optimised airports with the risk of some spawning at odd locations. For example at my local airport of EGNM all but 2 of the gates are too small for a 737!
You can always edit the wingspan= parameter in the flightmodel.cfg yourself to find a better balance for you specific preferred airports. I did float the idea of including some options in the Traffic Control Centre to set these yourself but that fell outside of the scope of what we wanted to do.
John - Just Flight.
-
On the wingspan issue where people say they have no problem is not wholly true as they are only using the default product.
Please try adding some 744, or 388 into your schedules and you will see that they will not appear.
I modify the wingspans in the .cfg file to correct the problem -
@hunterdouglas It depends on the airport. I chose not to reduce the widebody wingspans with compatibility mode because it resulted in too many showing up at gates that are far too small physically. One thing we could do in future is add a third option that reduces all of the widebodies. Any specific airports where you're not seeing them?
John - Just Flight
-
@jf-john YSSY was good with the compatibilty change, but YBBN still would not work, and OMDB, that ones a must as emirates have the most 380,s of any fleet I knocked the 744 and 388 down in the cfg file, sometimes those aircraft do show squeezed in, but it's a compromise that I'm happy to live with.
-
@hunterdouglas Thanks, I'll test some wingspans for YBBN and OMDB and we'll try to include a super-duper compatibility mode in the next Traffic Control Centre update.
John - Just Flight.
-
After getting a new module update from support and starting to use the compatibility mode as setting for wingspan I must say I am very pleased with the results of this new update. I am getting exactly the traffic I want both at departure and arrival airports and enroute.
I have been watching the traffic at Lyon LFLL for an hour now and it really works as clock work!
Thank you for all the help.
Best regards Jan
-
I've just flown two flights where I had no traffic at destination. I had changed nothing in my FS or JFT settings. The only difference between these two latest flights and my previous ones is that I took off from an airport that is not served by JFT (EGHF - Solent airport), but my arrival airports are served by JFT (Gatwick and Cardiff). Also, during these two flights I heard no radio chatter between AI and ATC either.
-
@bpfonteyn I have tried addilng unlisted airports to the database, and while they then show up in the Traffic Control Centre to schedule flights, they don't work in the sim. JF support informed me that there would be modifications to allow adding airports and also a bug fix to stop FS Traffic from crashing when these airports were involved.
-
@hunterdouglas The largest gate radius at YBBN is just under 60 feet which seems typical for AI generated airports. 110ft seems to be the sweet spot for the 747 so I'll use this as the third option for all aircraft 757-200 and bigger.
John - Just Flight.
-
What has actually helped - and I am not using the latest update of V 1.0.6 yet - is that I only input the destinatio via CONFIRM shortly before takeoff and also set my destination before in the MSFS „From/To“ menu. This has worked 100%. But agree not ideal…
-
Using 1.6 (official), I had another no-traffic-at-destination event yesterday.
I entered the ICAO in the field (FST window) but noticed during approach that while the destination airport was normally shown in the field during flight, it had vanished at some point in time, with the skies and airport then just being empty. Feels like something is crashing ... idk.Still an unreliable system unfortunately. Will keep trying though....
-
@disco79stu Hello,
Could you tell me what you departure and destination airport was? That way we can try to replicate.
John - Just Flight.
-
Hello,
destination traffic worked fine under version 1.0.5 before. I set the destination airport within the FS Traffic menu outside MSFS.
Unfortunately, with version 1.0.6 this option outside MSFS does not exist anymore.
So, I set the destination once when setting up the flight in MSFS (departure and destination airports) and then I set the destination again within MSFS using the in-build FS Traffic menu.
Unfortunately, there was no traffic at the destination. So, I de-installed version 1.0.6 and installed prior version 1.0.5 again and everything works well there.
For your reference, it was a flight from LSZH to EDDB. -
And again arrived at LIMJ from LFPO, with plenty of traffic on departure but practically none en route with zero at the destination. Destination filed correctly showed LMIJ.
Why is it even necessary to have this btw? Can't the system just spawn aircraft according to schedule by distance or something? Like every other traffic add on ever did? -
@disco79stu Hello, I just did that same flight to test. No problems here.
Traffic at the departure airport, traffic during the entire route (not too much, although I guess it depends on the day and time) and traffic at the destination airport. Little, but everything according to the Schedules Manager of the FS Traffic Control Center for the arrival time.
FS Traffic version 1.0.6.
I am attaching some sample screenshots from different moments of the flight.
