No traffic at arrival airport
-
@cadum
Well, tried with just FSLTL, works better but FPS was lower.Then tried AI Air Traffic setting, using non generic AI aircraft setting.
Got much better traffic and only one Osobo Generic upon arrival at KDCA.
I could be happy just flying with AI Traffic on....if I could determine how to eliminate all the Osobo pointed nose airliners?
Is it possible to just move those out of their directory....into a temp directory....and I wonder if I did that would the sim then just select the next available models....for example Just Flight FS Traffic and/or FSLTL Models?
-
Same issue with me, Since the update I cannot see traffic at the arrival airports.
I'm at a complete loss on what to do next -
Sorry to say that I have the same issue, no traffic upon arrival. I have a lot of 3rd party airports bought at the Marketplace. Could that be an issue?
-
as a step by step guide on what i'm doing and not seeing any traffic at arrival
- using GSX pro , in traffic control/aircraft manager/ground services/ all turned off, ie unchecked
- created flight plan through simbrief EDDF to EGLL, imported it to FS
- started FS and loaded flight plan EDDF to EGLL
- Aircraft was std A320
- set myself at gate at EDDF plenty of Aircraft showing nicely, also taxing and Landing
- I selected FS tool and ICAO on start did not show ICAO for EGLL, but after about 20 secs up it popped, and i pressed the confirm button.
Traffic was showing 100% so it was active
Note here - when I select FS tool another time, EGLL does not immediately come up, I needed to wait a couple of secs.
Took off and flew and landed,
no traffic at EGLL nothing
I did enter EGLL in destination and pressed confirm,
-
Same here. Nothing. Did short 15 min flight from KSRQ to KTPA. Ok traffic at departure and nothing at arrival. Put in KTPA and tapped confirm at FS Traffic in panel. This obviously is a very wide problem with multiple users over a wide range of airports.
-
@lightflight10 said in No traffic at arrival airport:
Sorry to say that I have the same issue, no traffic upon arrival. I have a lot of 3rd party airports bought at the Marketplace. Could that be an issue?
Have you tried going to airports that are not third-party? That would have given you the answer to that one.
-
Just did the following flight:
EGLL-ESSB
Time Before Departure value (TBDv): 120 minutes
Flight Planning Method: Native MSFS planner using High Altitude Airways
Flight Time: 3hrs 3 minsPlenty of departures and arrivals at EGLL.
No ATC chatter/AI aircraft enroute
ESSB empty upon landing.
Looking at the JF Traffic Control Centre ESSB is in the database and has plenty of incoming/outgoing flights on a Sunday
Again, I find myself wondering if the empty airports on arrival is linked to the TBDv. As I said, mine is set to 120 minutes. I know that when I spawn into my departure airport all the aircraft due to depart in the next 120 minutes spawn in with me. I also know, from the manual, that once those aircraft have departed, no more will spawn in. So, if I hung around at my departure airport for more than two hours, I'd eventually see the airport empty, at least of due to depart aircraft.
I wonder if the arrival airport's aircraft spawn in at the same time as my departure airport's aircraft spawn in. Obviously not physically, as it were, but in the programme's memory. But because my flight time was 3 hours, one hour over the 120 minute TBDv, have all those aircraft departed from my destination airport before I arrive?
Could that account for the empty arrival airports? I am going to test this by flying the same flight plan, but extending my TBDv to 240 minutes.
-
@jvortiz56 said in No traffic at arrival airport:
...all showing flight plans of EGSS-LEVC.
From what I have seen mentioned elsewhere, these flights show up around you know matter where you are in the world. Apparently there are placeholder flights. I am not quite sure what that means though. :beaming_face_with_smiling_eyes:
-
Just download FSLTL latest installer....which now gives you the option to have FS Traffic models take priority...I also set it up to eliminate generics and blank liveries.
On my test flight from KIAD to Regan National, I got plenty of traffic on ground and airborne with aircraft on arrival, on ground, landing and taking off.
Using the 4k Models for FS Traffic....I got close to 30 FPS the whole time.
Not bad.....and at least an effective temporary solution to the Osobo technique of On line traffic....admit that Generic Osobo gives higher frame rates.
Advantage of using FSLTL injector is that it removes all the Osobo pointy aircraft....for AI controlled real time flight.
-
@cadum
Also, redid the same flight, but this time I removed the base models from FSLTL from my community folder.Noticed...a gain in FPS overall about 10 FPS during the flight.
So...right now for me....disabling FS Traffic but using its models with FSLTL seems to be the best option for a fine on line AI injected experience, with lots of traffic, and arrival and departures from the destination airport.
-
I did two flights this weekend (1,5 hours and 3 hours), and on both flights there was no traffic at the arrival airports. In both cases I have entered and confirmed the arrival ICAO at the in game FsTraffic window.
While cruising I have observed several aircraft (contrails). But there was no communication on ATC.
I hope this problem will be fixed in the future.
Patric
-
I’m approaching EGLL from ESSB.
I had one aircraft at my departure airport. No aircraft seen nor heard over ATC during the flight.
I have the feeling that EGLL is going to be empty, as I’m over London and my frame rates are far too high for this area. 🤔
-
Well, I have to say I was very surprised to see traffic on the ground at EGLL on my arrival.
I normally get fps of about 26-30 on the ground at EGLL, and somewhere in the region of 40 fps as I fly over London (when I used Simple Traffic or FS default AI traffic). So when I approached London and was getting fps of 70 I assumed this was because there were no JF Traffic aircraft generated in the area, or at EGLL.
However, my hopes rose as I heard ATC speaking to a British Airways plane on its final to EGLL. The Speedbird call sign was read properly. (I have noticed that callsigns for incoming aircraft are always said properly, whereas outbound aircraft always have their callsigns uttered phonetically JF: if you are reading this and have not seen my post on my discovery you can read it HERE.
As I approached EGLL, there was a BA AI aircraft landing next to me. As I landed at EGLL I saw lots of traffic on the ground. My fps was a more normal 30-35 on the ground there. I guess the good 70+fps earlier were due to the fact that JF Traffic does not spawn in flights passing by from other airports, only those that follow your own flight plan, in my case ESSB-EGLL.
So, a semi-successful flight where JF Traffic traffic spawning is concerned. Semi-successful as there was only one aircraft at my departure airport, and absolutely nothing enroute.
-
So - I don’t usually complain about software - I am a software developer and I know only too well how things can be rushed and testing cut in order to meet a deadline release date. But - this software doesn’t work with GSX, doesn’t show any traffic ever at a destination airport, sometimes shows traffic at origin and sometimes it doesn’t. It certainly seems to me that at this point i have to write off the 30 bucks and uninstall it. Others seem to fare better with it than me, but at least for me - I’m done.
I hope that one day it will deliver on what it’s promised to be. It has a lot of great potential. But right now, frankly, I am better off uninstalling it and going back to no traffic or FSLTL (not that it’s perfect either, but it’s free and seems to work better overall). Sorry.
-
Reading all this is a strong stuff, people accusing the developers of lying and releasing a product without any extensive testing etc. It's really true that the flight sim community can be very toxic.
I have just finished a long flight from Canberra YSCB to Perth YPPH and FS Traffic was doing its thing just perfectly. Perth YPPH was populated with aircraft at gates and there was also one aircraft approaching when I was taxiing to my gate.
I also use GSX and both things work together. However, I have taken some precautions because of the MSFS objects limit (I'm not saying that's the reason of your problems with no traffic at the destination airport, it's just a suggestion):
- I disabled all ground services in the FS Traffic Control Centre for all models (to be sure I switched it on and off after the latest update)
- I disabled Extra Ground Clutter on the GSX config page
- I excluded airport services for all my addon airports
And this is what I do with all my flights:
- I import and load my flight plan from Simbrief in the sim planner, set all other things (gate, callsign, flight number etc.) and get to the flight
- Any time during my preflight preparations I open the FS Traffic in-game menu and wait a couple of seconds till it enters ICAO of my destination airport itself. I don't click on Confirm and I just close the window
And that's it. It has been working fine since the release day for me and I'm pretty sure Just Flight will fix most of the issues some people have.
-
@mhron said in No traffic at arrival airport:
Reading all this is a strong stuff, people accusing the developers of lying and releasing a product without any extensive testing etc. It's really true that the flight sim community can be very toxic.
People being disappointed in a piece of software that does not appear to work for all and making complaints about it is not toxic!! People have the right to complain if they are disappointed in a product because it appears not to work properly.
Yes, being disrespectful could be classed as toxic, but certainly not exercising their right to complain.
The thing that is frustrating those complaining is that within, say, half hour or an hour of playing, people, who have paid for this product, are noticing almost game-breaking bugs. It is understandable that people are asking questions such as Why is it that we are picking up bugs almost straight away that the devs and their beta-testers missed with weeks of testing? or Did the beta-testers really test or did they just say they would for a free copy of the game? Questions I have seen being asked.
I myself am very disappointed in this piece of software. I have used previous incarnations of JF's Traffic series and have always been impressed. But unfortunately my experience with this latest Traffic programme from JF has really knocked my confidence in them.
If people did not complain then JF would not know of these bugs, and, of course, a barrage of complaints will encourage any developer to work harder to fix the issues.
Some people might also be frustrated by a perceived lack of information from the, or any, developer when there are a large volume of complaints, and people would like to know exactly what the devs are doing. Perhaps a thread by the devs showing what bugs have been reported and what they are doing about it would be helpful. At least it might show transparency. MS/Asobo have a similar thing where you can see lists of bugs that the developers are working on.
We now just have to wait for JF to fix these issues, which I am sure they are working on.
But, please, do not throw the word toxic around just because people are exercising their right to complain. So long as it's done respectfully of course.