Jim,...
If I understand correctly,... leaving it at .70 the flightplan will not change? and if set differently will change? I have noticed when it is changed also there is more ground movement... miscellaneous vehicles.
In order for the Traffic Scaler to have any effect on the flightplan we would have to use the Traffic Database Builder Utility that shipped with the FSX SDK's.
Many years ago when FS2002 (FS8) was released (started using AI Planes) the FP's ACES introduced used the TDBB Utility that the default FS AI planes work from. This Utility has many FP restrictions and Lee Swordy decided to develope a FP utility called TTools that does not have restrictions.
The traffic Scaler is embedded into the TDBB Flightplan prior to a compile
Airport entry Description
KSEA,
47.448999994,
-122.309305519,
132.0,
B,
10,
1.00, <<<<<<<<<<<<<============= Traffic Scaler
United States
{
RUNWAY,11894,150,HARD
RUNWAY,9421,150,HARD
PARKING,18.0,GATE
PARKING,36.0,GATE
}
The ICAO code identifies SeaTac airport, followed by:
Latitude = airport latitude in decimal degrees
Longitude = airport longitude in decimal degrees
Altitude = airport altitude in meters above mean sea level
AirspaceClass = airport's ICAO airspace class: B, C, D, or G
NumApproachFreqs = number of ATC approach control frequencies
Traffic scalar factor = number in range from 0.01 to 1.00 that determines busyness of airport.
The purpose of the Traffic Scaler percent value is for airports that have a single long taxiway going out to the end of a runway. ACES uses the Country of Russia as the example for these type taxiways and the Traffic Scaler scales down the number of head to head confrontations AI Planes can have on a long taxiway that is used both ways (Takeoff and Landing).
There should be no difference in the percent of airport vehicle traffic from parking spot to parking spot since this is controlled by a Parking Spot.
Airport vehicles that travel to a plane is a recorded track per autogenerated airport vehicles. The amount of vehicles seen at a airport is controlled by how many GATES and CARGO parking the airport has and the Airport Vehicle Density slider.
In all my testing the Traffic Scaler of .7 vs 1.0 has no affect on how many autogenerated airport vehicles randomly spawn. The only place we see its value embedded is in the TDBB Flight Plan Utility.
However that is a tested assumption on my part and I have been known to be wrong in the past.
The following is the exact quote when I asked ACES to explain the traffic scaler.
Up to FS9 we used a hardcoded ratio of parking spots to AI traffic. For FSX we exposed a scalar to allow throttling AI traffic at certain airports. There were some airports, in Russia notably, but also elsewhere, that the combination of many parking spots and a minimal taxiway infrastructure (or choke points) resulted in gridlock. The TrafficScalar allows us to help eliminate this problem.