First impression bugs.

Sleepy81

Just got FSTraffic, and these are my observations
/bugs so far:

Sometimes (about 40-50% of callsigns) the callsigns are wrong. The flight number is missing, and ATC instead uses just the company callsign. This is confirmed for many airlines and airports, not just the ones I show in the pictures here.

Sometimes I get no traffic, and hitting regenerate traffic or remove and the regenerate does not bring any traffic either. Sometimes happens randomly, but seems to always happen if you change time in the sim, or if starting FSTraffic after starting AIGround and AIFlow mods from flightsim.to.
Lastly it takes a long time for traffic to start moving. Loading into KLAX at Friday morning should have a lot of flights landing and departing, but after about 10 min I had only one landing and 2 that started taxiing.

I think FSTraffic is very promising, but it needs som bug fixes and optimization (as far as starting traffic, not performance wise. Performance is very good, even with lots of traffic at big airports. )

Mark

Hi @Sleepy81, many thanks for the feedback. We're glad to hear the performance is very good on your machine! To answer each of your points:

The callsigns of departure aircraft at the moment we believe are a sim limitation with how traffic is assigned callsigns and flight numbers when at a gate. We are currently investigating a workaround for this and if we are able to improve this an improvement will be included in a future update.
If you are seeing no traffic generated in the simulator, our best advice would be to restart the simulator. If you suspect the aircraft may be generated but are invisible, this may be a situation where the MSFS maximum object count limit has been reached. The solution in this instance is to head to the Traffic Control Centre, then go to Aircraft Manager> Ground Services > Set No Ground Services > Save Changes. That will remove all ground services from the Ai aircraft, which should reduce the object count significantly.
The Ground Services options highlighted in point 2 will also affect how quickly Ai traffic starts pushing back from the gates. If you head to the Traffic Control Centre, then go to Aircraft Manager> Ground Services and select the "Set No Ground Services" or "Set For Fast Gate Turnaround" presets, then press Save Changes.

We hope that answers all of your points.

Mark - Just Flight

Sleepy81

@mark I'll test the fast turnaround and see if that speed things up. I did a propper flight this time, not just sightseeing. From London City to Paris (LFPG). Short flight, but that's all I had time for now. Results where like this:

At london city AI spawned, but did not taxi. I was on the ground for maybe 10 min though, and had not set fast turnaround.
Enroute I saw a total of 3 AI aircraft. (on TCAS and visual.) Did not hear ATC speak to any of them until I was within about 30NM from LFPG. Traffic density was set to 100%, and it was a thursday around 1000 local time takeoff, so should be plenty of traffic enroute.
Arriving at LFPG, I se lots of aircraft parked, but nobody is taxiing, and there is no radio com on ground or clearance channels. Almost like it has frozen up and AI is not moving.

Traffic options are 240Min on "Time before Departure" and 3min on "Time between cruise traffic spawn attempts" Alternate livery Traffic substitution.

Mookie2661

@mark Setting ground traffic to zero doesn't work for me to get traffic back. There is something wrong with the .dll or cache files in the packages folder.

lightflight10

@sleepy81 great post! I second everything you wrote.

Sleepy81

@mark I tried the fast turnaround options, and that does indeed speed up the start of the AI flights. At EGLL: Within a few minuets I had jets taxiing. :)

However two problems still remain:

This is the most important to me. Enroute traffic is almost non existent. Flying through Europe at FL290 should hav lots and lots of traffic, instead I see maybe 3-4 jets on TCAS or visually per hour of flight and almost no radio chatter. Enroute spawn timer is set to 3 min. Will I help lowering it maybe? Will there be a feature in the future to spawn AI based on distance and elevation differences from the player, instead of only between dep and arr airport on a timer? I think I would prefer that way.
Callsigns are missing numbers and spelled out phonetically. However this only happens to jets that are starting up and departing. Jets coming in to land have proper callsigns and flight numbers, and are pronounced correctly.

caffer

I did a few full flights, from CDG and back, and I also did not see any arriving traffic at the destination. There were planes parked but no radio communication either. I did see some enroute traffic but very little. But I really hope for some arriving traffic at the destination.

Mach 2

You can add Japan airlines to the list. It is pronounced as
"Japanair" instead of "Japan Air"

I knew exactly what the problem was and opened every aircraft model with a JAL ending and fixed the aircraft.cfg under...
atc_airline=JAPANAIR, I corrected to.
atc_airline=JAPAN AIR
It is now pronounced correctly.

Somebody who cares about this needs to go through all the aircraft.cfg's and fix all the typo errors. MSFS uses text to speech and reads these as written.
Actually I have done this in several Just Flight traffic programs over the years.

BPFonteyn

@mach-2 said

atc_airline=JAPANAIR, I corrected to.
atc_airline=JAPAN AIR
It is now pronounced correctly.

Could this be why I’m hearing call signs being spelled phonetically rather than properly pronounced?

I’ve noticed in the ATC text window that British Airways planes are spelled as Speedbird. When ATC calls them it says Sierra Papa Echo etc.

If the callsign was corrected to Speed Bird, I wonder if that would stop ATC phonetically speaking the call signs.

Derek

@bpfonteyn said in First impression bugs.:

@mach-2 said

atc_airline=JAPANAIR, I corrected to.
atc_airline=JAPAN AIR
It is now pronounced correctly.

Could this be why I’m hearing call signs being spelled phonetically rather than properly pronounced?

I’ve noticed in the ATC text window that British Airways planes are spelled as Speedbird. When ATC calls them it says Sierra Papa Echo etc.

If the callsign was corrected to Speed Bird, I wonder if that would stop ATC phonetically speaking the call signs.

Yes - as I say, we are looking to fix that bug.

Mach 2

@bpfonteyn said in First impression bugs.:

@mach-2 said

atc_airline=JAPANAIR, I corrected to.
atc_airline=JAPAN AIR
It is now pronounced correctly.

Could this be why I’m hearing call signs being spelled phonetically rather than properly pronounced?

I’ve noticed in the ATC text window that British Airways planes are spelled as Speedbird. When ATC calls them it says Sierra Papa Echo etc.

If the callsign was corrected to Speed Bird, I wonder if that would stop ATC phonetically speaking the call signs.

I went through the aircraft.cfg's and made some of the...
atc_airline=SPEEDBIRD to atc_airline=SPEED BIRD
and this seemed to work "Speed Bird" was pronounced.
The ones that I didn't space did as you said would say "Sierra Papa Echo etc."

Also noticed Air France was...
atc_airline=AIRFRANS, changed these to atc_airline=AIR FRANCE
just in case.

Mach 2

@derek said in First impression bugs.:

@bpfonteyn said in First impression bugs.:

@mach-2 said

atc_airline=JAPANAIR, I corrected to.
atc_airline=JAPAN AIR
It is now pronounced correctly.

Could this be why I’m hearing call signs being spelled phonetically rather than properly pronounced?

I’ve noticed in the ATC text window that British Airways planes are spelled as Speedbird. When ATC calls them it says Sierra Papa Echo etc.

If the callsign was corrected to Speed Bird, I wonder if that would stop ATC phonetically speaking the call signs.

Yes - as I say, we are looking to fix that bug.

THANKS Derek