No traffic at destination. Again and again.
-
@jf-john Thanks again. I have been in contact with Support about these issues for almost a week now but never been asked these questions. Today I got a reply from Mark at Support and he said they are investigating the issue using Winter 22/23 schedules, but I am using the Summer 22, so that seems strange.
I will see if Support asks for departure and arrival airports later on. They haven't asked for any logs either.
Best regards Jan
-
Hi Derek, I love this product and really want it to work, but sometimes it does, and other times it does not, especially on arrival.
Also the wingspans is still not sorted, and if you add 744,s they will not appear at most major airports.
Most of the confusion comes from justflight not explaining what the product should actually do.
If I could give you a question, could you explain what the product should do
I have scheduled departures and arrivals set at 6 min intervals, my time before departure options is set to 60
so in my mind i should see 10 aircraft parked at the departure gates and 10 at the arrival gates. with aircraft taking off and landing every 6 mins
Is this correctHere is where I think it's going wrong, it only shows scheduled aircraft at arrive but does not spawn extra.
ie When we start at departure, we see nearly every gat full, ie the program has spawned in the aircraft. Then we see the aircraft taking off from the schedule,.
But on arrival we do not see any spawned aircraft at the gates, only the scheduled aircraft. so if you have your setting at 60 if an aircraft landing every 10 mins ,then you will only see 6 aircraft@hunterdouglas said in No traffic at destination. Again and again.:
If I could give you a question, could you explain what the product should do
I have scheduled departures and arrivals set at 6 min intervals, my time before departure options is set to 60
so in my mind i should see 10 aircraft parked at the departure gates and 10 at the arrival gates. with aircraft taking off and landing every 6 mins
Is this correctHi,
Just to explain this a bit. The time before departures value controls how far into the future flights are loaded and monitored. So, setting it to 60mins will load the traffic for the next hour of airport operations (and therefore will generate less traffic than the default value of 90mins).
The other value is "Time between cruise traffic spawning" and doesn't have any effect on the arrivals. This value determines the amount of traffic that will be generated during the flight. -
@jf-john Thanks again. I have been in contact with Support about these issues for almost a week now but never been asked these questions. Today I got a reply from Mark at Support and he said they are investigating the issue using Winter 22/23 schedules, but I am using the Summer 22, so that seems strange.
I will see if Support asks for departure and arrival airports later on. They haven't asked for any logs either.
Best regards Jan
@janjoensson said in No traffic at destination. Again and again.:
Thanks again. I have been in contact with Support about these issues for almost a week now but never been asked these questions. Today I got a reply from Mark at Support and he said they are investigating the issue using Winter 22/23 schedules, but I am using the Summer 22, so that seems strange.
On investigation I found that the problem occurred with either set of flight plans. This bug has been identified and addressed and will be included in the forthcoming v1.0.6 release.
We've also now received some console logs showing the conditions present when traffic is refusing to generate at the destination. I think I know the cause and we're currently circulating some potential fixes. Hopefully a solution will be confirmed soon and we can add it to the next release build.
-
@dmullert said in No traffic at destination. Again and again.:
For me, FSTraffic has turned into just a provider of models and repaints lacking in FSLTL - period. The program turned me off when I discovered the issue with aircraft radiuses where the AI traffic does not show up in airports which is an issue that AIG nor FSLTL suffer from. I got tired of fiddling with it and reverted to FSLTL, using it along with FSTraffic models and paints and working very well.
Hi,
Could you explain what you mean by the issue with aircraft radiuses? Are referring to wingspans?
Thank you
John - JF
-
I received information from Justflight about one possible cause of no traffic at destination being that the user does not have the Asobo Pitts special installed in the sim. This aircraft is used by FS Traffic as a dummy for calculations and it's absence will cause this problem as I found out in my case. All is now good.
As far as using compatibility mode in lieu of wingspan for parking, I'm seeing a lot of aircraft parked in improper locations when using it.
-
I received information from Justflight about one possible cause of no traffic at destination being that the user does not have the Asobo Pitts special installed in the sim. This aircraft is used by FS Traffic as a dummy for calculations and it's absence will cause this problem as I found out in my case. All is now good.
As far as using compatibility mode in lieu of wingspan for parking, I'm seeing a lot of aircraft parked in improper locations when using it.
@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.
-
@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 -
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
-
@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.
-
@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.
-
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.
-
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.
-
@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.
-
@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 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.
-
@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.
@jf-john That sounds perfect, thank you
-
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…
