2 minutes ago, vgbaron said:

ok - understood. When you first run the new version, they are added by default.  The first entry TrafficLimit being set to 0 disabled. Set it to 100 and leave the other settings alone and see how you like it for the areas in which you fly. I have mine set at 70,20,70 respectively but it's a personal call.

You will need to adjust the settings manually in the ini file after the first run.

HTH,

Vic

Thank you Vic, you have been a very great help to me today, I appreciate it!

You're welcome!  Enjoy!

 

Vic

2 hours ago, Jack_Sawyer said:

You will need to adjust the settings manually in the ini file after the first run.

Hi Vic, just re-read this.  So I will have to manually edit the ini?  Why is this?  And what do I set the numbers too?

And what is first run?  Is that first run of P3D?  I'v been using the registered version for a while now.

Thanks again.

Then the entry is there. Look at the numbers, other than setting the TrafficLimit to 100, which ENABLES the limiter, leave the others alone.

Fly - then change the three other numbers and see what you like. There is no "right" setting. AS I said, I like 70,20,70 but YMMV.

 

Vic

I see, thanks again Vic!

Vic, one last couple of questions.

I have P3D 3.4, registered FSUIPC, and I just installed for traffic Orbx's N/A AI Traffic freeware.  So I made several flights to test it out, modified the ini per your settings and have a smattering of traffic.

My question is this, what should I set the Traffic to inside P3D?

Thanks for helping me and because of you I now have AI GA traffic again!

10 hours ago, Jack_Sawyer said:

So I will have to manually edit the ini?

you can alter the value in the sim, FSuipc4 addon... miscellaneous tab...AI traffic Limit..

bob

8 hours ago, onebob said:

you can alter the value in the sim, FSuipc4 addon... miscellaneous tab...AI traffic Limit..

bob

That only sets the overall percentage. You still can fine tune it by setting the individual amounts in the ini file.

 

Vic

Since the original post in this thread is seriously out of date, I revised the information based on the most recent FSUIPC4 Users Guide. I strongly suggest to use what follows only as a quick reference and to consult the Users Guide for detailed information.

The Traffic Limiter’s behavior is controlled by these settings in the FSUIPC4.INI file. There will be a new section, probably added at the end of the file, containing, by default: 
[Traffic Limiter]
TrafficLimit=0 
GroundPreference=50 
PlannedAirportsPreference=50 
AirportPreference=50 
NearerPreference=50 
TargetFrameRate=0 

The limit set to 0 switches the facility off. The other parameters determine how to decide which ones to delete when 
the limit is breached.

GroundPreference: This is the % probability of nearby (up to 20nm with slight bia to > 0.5nm) ground traffic being deleted provided 
they do not already have clearance, or are shutting down after arrival. GroundPreference value determines the probability of excess 
aircraft being deleted from any airports within FS's "reality bubble" EXCEPT your departure and arrival airports. 

PlannedAirportsPreference: This allows you to set a separate % probability for deleting excess traffic at your planned airports 
of Departure and Arrival. For this to operate fully you need to have a plan loaded in FSX/P3D.

AirportPreference: The gives the % probability of aircraft destined for one of the six nearest airports (including the one you may be on) 
being deleted if it is a candidate (i.e. furthest, or as determined by the other parameters.

NearerPreference: This is the probability of deleting aircraft which are not necessarily the furthest away. With it set to 
anything above 0 the aircraft chosen for deletion might be anything from 20nm away. The idea of this is to give newly added 
aircraft in flight, spawned as usual at the far reaches of that “reality bubble”, a chance to follow their plans.

If they are all set to 0 (the original defaults in a pre-release) then the only criteria used when deciding which to 
delete is the distance – furthest only, every time.  

TargetFrameRate: This facility, which defaults off (= 0) makes the limiter ignore the Traffic Limit value altogether, 
so not deleting any traffic, when the frame rate is greater or equal to the value given here (excepting when this is 0 
which turns this facility off). 

 

What is your recommendation for the % setting to be used within P3D v4 (airliners and general aviation)? Thanks.

 

There really are no "recommended  settings" since altering each of the 6 settings that control the traffic limiter give slightly  different  results. I generally use traffic limit=100 and targetframerate=30. That seems to give the best performance  and reasonable  numbers of AI aircraft for my setup. Your results will depend on the add-ons installed, the AI package being used, your hardware capabilities and the two traffic slider values in the sim.

1 hour ago, jabloomf1230 said:

There really are no "recommended  settings" since altering each of the 6 settings that control the traffic limiter give slightly  different  results. I generally use traffic limit=100 and targetframerate=30. That seems to give the best performance  and reasonable  numbers of AI aircraft for my setup. Your results will depend on the add-ons installed, the AI package being used, your hardware capabilities and the two traffic slider values in the sim.

But, if you set the target rate to 30, doesn't it ignore the traffic limit that you set?  So, if you can get 30 FPS with 300 planes at one airport but only with 75 at another, it will handle it that way?

If your system can maintain 30 FPS then the traffic limiter  is disabled. Once the frame  rate drops below 30 then the limiter kicks in. Generally, densely populated areas are the issue with higher numbers of AI aircraft. It's a problem when the sim has to keep track of many AI aircraft and also simulate large amounts of road traffic and building autogen. Using the frame rate feature also allows for a user to pilot both complex and simple aircraft without fiddling with the limiter's options for each individual  scenario.

As I stated in my response, there are no recommended settings and YMMV.

Revisiting this thread. Does UT2 / UTLive traffic work with this or does UT (as mentioned in this thread) just keep re-injecting the traffic after FSUIPC deletes it?

 

The UT series apps have their own built-in traffic limiter which is based on maintaining a target frame rate.