No traffic at destination bug reports
-
@art_p Thanks for relaying this to us. We discovered this potential issue not long after I posted this thread. Hopefully a small change will fix the issue for those still having it.
Out of interest had you intentionally uninstalled this aircraft or was it some MSFS quirk?
John - Just flight
-
@jf-john As I explained to Simon, the Pitts Special was uninstalled by me a long time ago when it was showing up too much as AI traffic.
-
Departure airport: LFKF
Departure time: 16:37
Arrival airport: LIEE
Arrival time: 17:42
Any third party airport scenery: No
If GSX is installed: NoThis is just one example but I have only seen two AI aircraft flying high on any of my recent flights. I am not sure what is going on but it is very lonely out there and I would like to see more AI going about their business.
I have multiple AI packages installed (FSLTL, AIG and FSTraffic) as well as edited flightplans to show more AI models and liveries but wo is me, they don't want to show themselves..
Please help JF, you're my only hope..
NO AI seen at airports in any of these flights..
-
Check that you have the Wingspan Options in the Traffic Control Centre set to "Compatibility Mode" This will allow aircraft to spawn at airports where the gate sizes are not correct and solve the issue for most users
For anyone who is still having cases of traffic not spawning at the destination please use this thread to give us the following minimum information about your flight.
- Departure airport
- Departure time
- Arrival airport
- Arrival time
- Any third party airport scenery
- If GSX is installed
Thank you
John - Just Flight
@jf-john TNCM
1500
TNCM
1530
tncm by airworthy designs
No GSX installed.
Have tried wingspan option makes no difference nothing shows at this airport. I know FS traffic is working as it has planes at other airports in europe. -
@jf-john TNCM
1500
TNCM
1530
tncm by airworthy designs
No GSX installed.
Have tried wingspan option makes no difference nothing shows at this airport. I know FS traffic is working as it has planes at other airports in europe.Ok i fixed this myself. Seems to be a problem with the TNCM scenery by airworthy designs. When i went back to default msfs it works fine.
-
Ok i fixed this myself. Seems to be a problem with the TNCM scenery by airworthy designs. When i went back to default msfs it works fine.
-
@captainlovepony Hello,
With these things its always worth checking if the airport works with the default AI too as the problem of that nature will affect both. Have you also got the handcrafted default TNCM installed?@jf-john No i removed it and went back to default, Traffic fine now.
-
Problem at SABE and SAEZ airports.
Ultimately, when I chose them as departure airports, no traffic is shown at all. I didnt try with other airports at the region .
Strangely, if I set a flight from KEWR, (at which FSTraffic works OK), get out and set a flight from any of both SABE and SAEZ, then the traffic appears. -
Departure airport: LOWI
Departure time: 17:30 UTC
Arrival airport: EHAM
Arrival time: 18:40 UTC
Any third party airport scenery: NO
If GSX is installed: YESEHAM was completely empty. No traffic at all, nothing, nada. I have removed all cluter. Wingspan to compability. Sometimes it works, sometimes it does not work.
All i want is traffic so...can i use the FStraffic models with the standard MSFS AI generation model?
-
Is there now a solution to display aircraft at the destination airport? I now find it a shame to leave a product half-finished for so long!
-
a product that has never worked, without updates for a year now, now unusable.... all money wasted, I want a refund!!!!!
-
The only solution that works 100%:
Before every flight and before opening MSFS:
Navigate to C:\Users<YourUserName>\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages
Then delete everything in the "justflight-fstraffic-module" folder.
Start MSFS and it will rebuild those files and should work properly.
I am using FS Traffic daily and had 1/10 times no arrival traffic as the module stopped working after takeoff. The above solves it.
