No traffic at arrival airport
-
I do understand your frustration. I too rarely get any arrival traffic, nor enroute traffic.
I sometimes get both when flying into EGLC, with the latter, enroute traffic, only being heard as I approach London.
Really wanting to keep JF Traffic installed, but as each day passes without a fix it’s becoming harder not to uninstall it and write it off as a wasted purchase. Simple Traffic is by no means the best traffic software, but at least it had plenty of enroute traffic and traffic at destination airports (and no “ghost airports”). 😢
-
@bpfonteyn
We're almost there with the update. We had hoped to release today, but it wasn't to be. It should be available early next week though.
Here is the current changelog for the update:Module: Departures now using correct callsign callouts Module: Destination airport detection revisions Module: New system for handling departures Module: Additional cruise AI scenarios added, plus increased randomness Module: Additional airports added to database Module: SF3 added to aircraft database Module: Remove traffic/Regenerate traffic system improvements Module: Bug when switching to an airport with no scheduled arrivals - fixed TCC: VMR template exporting/importing bug TCC: Right clicking headers in the TCC would cause a crash - fixed TCC: Localisation issue fixed Misc: In-sim menu not showing ICAO code when reopened during flight - fixed Fleet: Added Cebu (CEB) Pacific A320, 320_SL and A320_NEO, A321_SL, A321 NEO, a330-300, ATR72 Fleet: Added Air China 747-400 Fleet: Added Air New Zealand 777-300ER Fleet: Added Asiana 747-400 Fleet: Added Aurigny E195,ATR72 Fleet: Added Iraqi 747-400 Fleet: Added REX 737-800 Fleet: Added Singapore 777-300ER Fleet: Added Smart wings 737-800 Fleet: Added missing A320NEO textures. AVA, QDA,SKU,LAN,IBE Fleet: Colour matched BA fleet Fleet: Rebuilt Aircraft.CFG's to correct some callsigns Fleet: Updated wheel anim code Fleet: Added bogie tilt to A330-200/A330-300/747-400/747-8/787-8/787-9Subject to change before release, of course.
Thanks
Rich -
please add cargo carriers! thanks!
-
@monkeypants Yus! :thumbs_up: I'd like to see more smaller aircraft.
I love the models but I find the implementation of FS Traffic limiting. I like to roam around (okay I get lost a lot!) and have traffic generated wherever I go and not have to worry about entering a destination which is why I currently prefer the FSLTL injector.
-
I think I've solved the problem. I've just done 7 flights with plenty of aircraft at destination.
It's the instructions that are wrong , they say to enter and confirm your destination AFTER you have loaded into a flight.
thats wrong, enter and confirm your destination BEFORE YOU PRESS the FLY BUTTON
In flight set up, i entered both departure and destination airport, then in FStraffic I entered and confirmed destination, then pressed FLY and it workedPlease could other people try this method and see if it works for them
-
No, you have not fixed the problem. I believe the manual gives two methods, of which one of them is your “fix”. Either that or a dev has already asked people try this method. I myself have already tried your suggestion without success.
If it was that simple don’t you think the devs would have fixed it by now?
Kudos, however, for your efforts 👍
-
@bpfonteyn
Sorry, but maybe you misunderstand what i did, attached is the two methods of the manual, both say click the fly button THEN type and confirm the destination,
what I'm saying is from the fstraffic control centre type in the destination and confirm BEFORE you hit the fly button.
I had been trying for weeks with know aircraft at destination, I tried this method and it works for me,here is what the the manual says,
Method 1 – setting the destination via the in-game menu:
- Load MSFS and go to the World Map.
- Select your departure airport and then click the FLY button.
- Once loaded into the flight, open the FS Traffic in-game menu.
- Type the four-letter ICAO code of your destination airport into the DESTINATION ICAO field (for example,
EGLL for London Heathrow, EHAM for Amsterdam etc.). - Press CONFIRM.
Method 2 – setting the destination via the MSFS main menu: - Load MSFS and go to the World Map.
- Select your departure and arrival airports and then click the FLY button.
- Once loaded into the flight, open the FS Traffic in-game menu.
- Confirm that the four-letter ICAO code of your destination airport is in the DESTINATION ICAO field.
-
@hunterdouglas i have done that. Sometimes it works, sometimes not.
-
That is the problem for the developers I think, I agree, same here: sometimes traffic and sometimes nothing, an empty destination airport. Last few flights were perfect, 6 flights in the weekend with 5 times a very active traffic at the destination airport and only at 1 (Frankfurt) I was alone…
-
@hunterdouglas I echo this
-
As I already wrote here: https://community.justflight.com/post/19995
Problem with missing traffic at destination is solved with v1.0.3 on my system!
I also have traffic at destination when I- fly slower than 250kts and lower than 5000ft - e.g. GA like Turbo Arrow!
- start in the air and choose destination later on in toolbar
So things are way better now (at least on my system)!
Thank you Justflight, FS Traffic is getting useful to me now ;-) -
Just had a flight from ENGM to EDDH. Plenty of parked and moving planes at ENGM. EDDH empty. It's getting really frustrating and it is ruining the experience. This time I forgot to enter EDDH in the in-game panel. But it was entered both in MSFS planning menu and in the FMC of the aircraft (Fenix A320). Shouldn't that be enough? It is way to easy to forget the in-game panel. Besides it will autofill when opened up anyway. So I really don't get it. I think the regime is too complex. I just want some planes at the airport. How hard can it be. I'm close to reintroduce Simple Traffic again. At least that is a set it and forget it piece of software... Better with ugly looking AI planes than nothing at all.
-
Yes, I too really dislike this requirement to have to enter the destination ICAO into the toolbar, even if it is just to open it for populating. By the fact that it automatically populates the field, it must be getting the info from our flight planner. Therefore why can’t this be done silently behind the scenes as it were? Why did we need to add this extra input?
Two days ago I flew from FMMI-EGLL, an eleven hour flight. When I arrived in EGLL, there were no AI at all. None on the ground and none arriving. I have a feeling this was due to the fact that I may have forgotten to open the JF toolbar window. I can’t remember doing it for certain. It’s a right pain in the neck having to open that wretched window field in the toolbar.
-
@bpfonteyn Agree! It's like we are doing some sort of workaround to get it to work. But this is the actual design. I think the concept is all wrong, and requires too much attention from the user. I'm having my hands full setting up flights and do the actual flying. Why not a pop-up window asking us to confirm the destination? Instead of having to open panels.
It's like I must have my own checklist just for FS Traffic?I am going back to simple traffic till this software are actually ready for the marked.
-
I’m not going to uninstall JFT as it has improved a lot since initial release. I just wish the devs could stop the requirement for us to have to do the ICAO confirmation.
-
To be honest, in my last flights I opened the in-game panel to add the destination, because I didn't enter a destination during flightplanning. I always had traffic at my destination.
So to me it seems you have to or should open the in-game panel.
The good thing though, with v1.0.3 you can do it during the cruise.But you are all right, it is a pain and shouldn't be necessary at all!!
-
I have the solution!...Just make the program work the way literally every FS9 and FSX traffic programmed worked before without having to jump through any hoops...It CAN be done because it HAS been done...I knew I was in trouble when I found out I had to do steps to make it work.
