• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Insert Model Problem

Messages
1,269
Country
us-northcarolina
Insert Model Problem/ Traffic Scalar

When I try to insert a model into ADE, the model shows up, but it is the wrong size and place...

the yellow rectangles are hangars that I made but when I go into FSX they are way largers and extending out into the apron...


klhzmodel.jpg




PS--- What is the 'traffic scalar'?
 
Last edited:
there are two things you can try:

1. double click to open it, then simply change the size
in the "Scale" from 1.00 to 0.80 or whatever you need to get it right

2. from the ADE menu, open up tools/library object manager
find your object from the library then change the size with X and Y
not forgetting to save when you close
then each time you select this object it will be that size
 
PS--- What is the 'traffic scalar'?

Adding to Doug's post

The traffic scaler is part of a throttle value for Flightplans that are built with the Traffic Database Compiler.

We leave it at the FSX default value of .7 and there is no change in Flightplans if you set it differently. In FS9 the scaler was hidden from view but FSX exposed it.
 
Last edited:
Adding to Doug's post

The traffic scaler is part of a throttle value for Flightplans that are built with the Traffic Database Compiler.

We leave it at the FSX default value of .7 and there is no change in Flightplans if you set it differently. In FS9 the scaler was hidden from view but FSX exposed it.

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.
 
when you put the traffic all the way up on the sliders, why do you still not have that much traffic?
 
when you put the traffic all the way up on the sliders, why do you still not have that much traffic?

Michael...

It used much like a safety valve, that is the traffic scaler, and each airport has one... ex. your computer has a sound card and has a master volume (the slider) and the wav files and/or line in has a separate volume controls (traffic scaler).
 
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.
 
Jim-

Is there a way to change the traffic scaler in FS9?

ex..

In AFCAD I added an extra runway to KRDU solely for takeoff, and DRAMATICALLY increased traffic there. (Probably ~50 planes in line to take off) When I go there though, all of the planes get the same runway assigned to takeoff instead of assigning half to 5C and half to 5R (designators changed of course from regular) all try to take off 5C and there is just a long line from both terminals...

is there a way to change this?

Doug-

No i wasnt talking about the traffic scaler, I was talking about the sliders in FS itself under 'settings -> world -> traffic' etc
 
Last edited:
Jim-

Is there a way to change the traffic scaler in FS9?

ex..

In AFCAD I added an extra runway to KRDU solely for takeoff, and DRAMATICALLY increased traffic there. (Probably ~50 planes in line to take off) When I go there though, all of the planes get the same runway assigned to takeoff instead of assigning half to 5C and half to 5R (designators changed of course from regular) all try to take off 5C and there is just a long line from both terminals...

is there a way to change this?

Doug-

No i wasnt talking about the traffic scaler, I was talking about the sliders in FS itself under 'settings -> world -> traffic' etc

mdm248111

There is no way to change the Traffic Scaler in FS9. If your Flight Plans are TTool Compile type FP's then changing the Traffic scaler does nothing.

The only way to see why your KRDU is working the way you say is to attach the bgl so I can look at it.
 
I will do that but it is at my Grandma's house and she only has dial-up so i will go over there and put in on my flash drive then will upload it. It might be a couple days because I only go over there about twice a week.

I don't know if mine is TTool compile because I created the plans using yRoute then just recently changed over to AI Flight Planner.
 
Michael

I've just dug out the KRDU file i was working on a couple of mths ago, and everything at terminal 2, the GA on that side and the cargo area went from rwy 5L,
all traffic at terminal 1 and the GA area parallel to it went from rwy 5R, this is in FSX......
Not sure why you changed 5L to 5C as that is not how it is in real life,
i know there were plans for a 4th rwy but that was put on hold according to their website and the latest chart doesn't show it either........
 
i know (I live 30 mins away) but I was just getting creative, not really caring about what was actually there, I was trying to get a lot of traffic going.

I know that they have plans to build a third runway like you said but haven't---yet.

I just wanted to 'get ahead' and was just plain being creative...(you should have seen my first one before I realized it was too much)
 
Jim: I'm curious to find out which FSX airports (especially outside of Russia) are effected by the use of the scalar. My testing of the scalar using many airports in Europe and the US with flight plans compiled using the TDBB and a range of values for the scalar has not resulted in any change from the default value of 0.7. I was under the impression that the scalar was not working with the TDBBx due to a bug. I have not tested the scalar on Russian airports. Are you aware of a list of airports outside of Russia that the scalar will work?
 
Jim: I'm curious to find out which FSX airports (especially outside of Russia) are effected by the use of the scalar. My testing of the scalar using many airports in Europe and the US with flight plans compiled using the TDBB and a range of values for the scalar has not resulted in any change from the default value of 0.7. I was under the impression that the scalar was not working with the TDBBx due to a bug. I have not tested the scalar on Russian airports. Are you aware of a list of airports outside of Russia that the scalar will work?

I do not work with TDBB type FP's. The FP's have a percent value where we can scale back Airline and GA density traffic. The problem when doing this is, it effects all airports. If we set the Airline Traffic Density to 100 percent then all AI Planes on FP's should show in the Traffic ToolBox utility.

The Scaler is on a per airport basis. If the scaler is set to .5 for any one airport it should stop 50 percent of the Airlines from showing up at that airport. At least that is what ACES claims happens.

Since the Scaler is now part of the Airport Header XML I was going to test it by using all the default FSX FP's and set the scaler to 0.1 for a test airport. If the Airline Traffic Density is set to 100 and the Traffic scaler is set to 0.1 for any given airport then all airports should get 100 percent traffic except the airport that I set the scaler to 0.1

Several airports come to mind that the scaler could be affective. KSAN (rwy 27), KBHM (rwy 06) and KDAB (rwy 07) all have long Taxiways out to the end of a runway. It is easy to get Head to Head AI planes when one is taxing out to the runway and one has landed.

I saw some odd taxi behavior when I was testing my KBHM with the default FSX TDBB FP's at KBHM for runway 6. By default FSX set the Traffic Scaler to .7 (at all airports that I have worked with) out of a possible 1.0.

What ACES did not explain was why the Scaler is compiled in 2 different bgl's. The TDBB has a varible scaler value from .01 to 1.0 in the Airport Entry Description of the FP and then a scaler value in the Airport Header that we see with ADE. It's unclear why both have to be exposed and leaves unanswered questions.

We can see the scaler value of .7 in the airport header but we can not see what the TDBB compiled in the airport description header for all the default FSX FP's. ACES says it works but what value goes into what header for it to work properly.
 
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.

Ahh! I get it now... so it actually speeds up the AI Planes up while taxiing in or out! very neat!

Thanks Jim
 
I do not work with TDBB type FP's. The FP's have a percent value where we can scale back Airline and GA density traffic. The problem when doing this is, it effects all airports. If we set the Airline Traffic Density to 100 percent then all AI Planes on FP's should show in the Traffic ToolBox utility.

The Scaler is on a per airport basis. If the scaler is set to .5 for any one airport it should stop 50 percent of the Airlines from showing up at that airport. At least that is what ACES claims happens.

Since the Scaler is now part of the Airport Header XML I was going to test it by using all the default FSX FP's and set the scaler to 0.1 for a test airport. If the Airline Traffic Density is set to 100 and the Traffic scaler is set to 0.1 for any given airport then all airports should get 100 percent traffic except the airport that I set the scaler to 0.1

Several airports come to mind that the scaler could be affective. KSAN (rwy 27), KBHM (rwy 06) and KDAB (rwy 07) all have long Taxiways out to the end of a runway. It is easy to get Head to Head AI planes when one is taxing out to the runway and one has landed.

I saw some odd taxi behavior when I was testing my KBHM with the default FSX TDBB FP's at KBHM for runway 6. By default FSX set the Traffic Scaler to .7 (at all airports that I have worked with) out of a possible 1.0.

What ACES did not explain was why the Scaler is compiled in 2 different bgl's. The TDBB has a varible scaler value from .01 to 1.0 in the Airport Entry Description of the FP and then a scaler value in the Airport Header that we see with ADE. It's unclear why both have to be exposed and leaves unanswered questions.

We can see the scaler value of .7 in the airport header but we can not see what the TDBB compiled in the airport description header for all the default FSX FP's. ACES says it works but what value goes into what header for it to work properly.

Ooops ... I guess I misread the original post with ACES explanation... no problem.
 
Back
Top