No traffic at destination. Again and again.
-
@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 correct
Here 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 aircraftI think the above is excatly the sort of thing to ask Just Flight support. They should be able to answer questions like that by asking the dev team.
-
@derek Hahaha yes that is probably true!
However, looking through different forums and also comments on YouTube videos reporting on the new update 1.0.5 there actually seem to be many users describing the same issue, that is: Lots of aircrafts at departure, less and less traffic enroute, and very few aircrafts on arrival.
I have watched how the traffic behaves and as many describe the problem it seems when on the departure airport lots of traffic is spawned because they are prepared for departure depending on the spawn before departure time set. But then on arrival it seems as the amount of aircrafts parked when you arrive depend on how many aircrafts have actually managed to land. Now from what I can see lots of aircrafts go around for some reason, even if no other aircrafts block the runway. This cause the aircrafts to fly around for a long time. Occasionally they manage to land but the influx of aircrafts is much too small to fill the airport, as it would have been if more of these aircrafts managed to land or were spawned directly as parked instead.
I can see in the forums and comments that many users have switched to using FSLTL injector instead. That injector manages go arounds with after a few minutes parking the aircraft on the airport instead of having it flying around on low altitude for a long time. That is probably why when you come in on approach using FSLTL the airport is already filled with parked aircrafts.
Best regards Jan
-
@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
-
@janjoensson said in No traffic at destination. Again and again.:
@derek Do you know if support is working on this issue? I got a message after contacting support, but the requests in that reply, with testing different airports would take me so much time, time I simply don't have... To be able to know if for example the wingspan compatibility mode works for a certain airport, I would have to fly a complete route to that airport several times. But I can't do that kind of testing, then all my "play" time will go to testing. And I mean, support seems to reply only one time a day (at best, seems more like a few times a week), and the waiting also gets very time consuming for me.
At the moment I use FSLTL injector instead (but I actually liked the time table of FS Traffic better so I would rather use that) with the FS Traffic models. Using FSLTL also means I get more traffic enoute. It works to do like this of course, but I hope Just Flight sorts these issues out as it was supposed to in the new 1.0.5 update. So far the improvements to the core product is not working as stated in the change log, at least not for me...
Best regards
Jan
Hi,
Without more info as to why you're having the issues its extremely difficult for us to find the cause. In testing V1.0.5 was more stable than ever. There are two possibilities for you not seeing aircraft at the destination.
-
Gate size too small: Turn wingspans to compatibility. I now use this setting by default as most MSFS generated airports gates can't actually fit the aircraft. No need to do a whole flight to test this as it would also affect the same airport when used as a departure.
-
If the above doesn't fix the issue then it suggests the module may be crashing for unknown reasons. We absolutely need you to send those e logs that support will ask you for. Without that we are unfortunately stuck.
Thank you
John - JF
-
-
@janjoensson said in No traffic at destination. Again and again.:
@derek Well I am Stockholm based so it is only one hour time difference. That can't be the reason for slow replies... It's strange if it can't be replicated since I mean there are quite a few users here reporting the same issue. I can do some tests but if you want me to do several hours and weeks of testing, then I need to get paid as a consultant.
Hello,
It does appear that these issues are affecting a minority, for those where everything is working they don't tend to post about it in the forums. We do still want to help the customers who are having issues though.
Ideally we need you to contact support so that they can help you provide the correct information that we need to track any bugs down.
Unfortunately reporting you have no traffic at destination without telling us what that destination is gives us very little info to replicate the problems. As a minimum I'd suggest posting the following.
-
Departure airport
-
Departure time
-
Arrival airport
-
Arrival time
-
Any third party airport scenery
-
If GSX is installed
Thank you
John - Just Flight
-
-
@jf-john said in No traffic at destination. Again and again.:
@janjoensson said in No traffic at destination. Again and again.:
@derek Do you know if support is working on this issue? I got a message after contacting support, but the requests in that reply, with testing different airports would take me so much time, time I simply don't have... To be able to know if for example the wingspan compatibility mode works for a certain airport, I would have to fly a complete route to that airport several times. But I can't do that kind of testing, then all my "play" time will go to testing. And I mean, support seems to reply only one time a day (at best, seems more like a few times a week), and the waiting also gets very time consuming for me.
At the moment I use FSLTL injector instead (but I actually liked the time table of FS Traffic better so I would rather use that) with the FS Traffic models. Using FSLTL also means I get more traffic enoute. It works to do like this of course, but I hope Just Flight sorts these issues out as it was supposed to in the new 1.0.5 update. So far the improvements to the core product is not working as stated in the change log, at least not for me...
Best regards
Jan
Hi,
Without more info as to why you're having the issues its extremely difficult for us to find the cause. In testing V1.0.5 was more stable than ever. There are two possibilities for you not seeing aircraft at the destination.
-
Gate size too small: Turn wingspans to compatibility. I now use this setting by default as most MSFS generated airports gates can't actually fit the aircraft. No need to do a whole flight to test this as it would also affect the same airport when used as a departure.
-
If the above doesn't fix the issue then it suggests the module may be crashing for unknown reasons. We absolutely need you to send those e logs that support will ask you for. Without that we are unfortunately stuck.
Thank you
John - JF
@JF-John Hi and thank you for your reply.
-
I will try the Compatibility mode although that contradicts what the manual says. I only fly to and from airports bought through Aerosoft and Orbx, no MSFS generated airports. When I go to these airports (ESSA, ESSB, LPPT, LPFR, LIPE for example) I always 100% of the time have plenty of traffic when departing. Isn't that strange if it has to do with wingspan? But on arrival they are almost always empty.
-
Maybe it's crashing because I have noticed that if I try to open the FS Traffic app after arrival parking again at the gate MSFS sometimes crash to desktop. There are a few aircrafts circuling though.
-
In the three emails I got from Support so far never been asked to send in any logs. I now replied to Mark at Support if they want me to send logs and how to do it.
Best regards Jan
-
-
@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 Thank you
I'll give support a heads up about your reply. It sounds like those winter schedule issues are separate from your problem. They should give you a form to fill in.
Thank you
John - Just Flight
-
@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. -
@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.
-
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.
-
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
