Try this:[JOBSCHEDULER]AffinityMask=15[bufferpools]poolsize=50000TEXTURE_BANDWIDTH_MULT=80UPPER_FRAMERATE_LIMIT=60FIBER_FRAME_TIME_FRACTION=0.02I know my fiber and poolsize are very low, but I was getting lockups and now is is smooth with more 10 FPS, give it a try.Worked in my system, i5, GFX 275, but each system is different for FSX.I hope this helps,Ulisses

Terrain imagery loaded in at 9NM with no pause. At about 8NM Trees were rendered with a slight pause. Static AI rendered at 7NM with a very short pause

Photoreal ground scenery is NOT handled by the Addon Manager at all. It's a normal BGL which means, anything regarding its loading strategy, is not due because of the Addon Manager, it's not influenced by it, and it's exactly as any other scenery around. Which also means, the Antipop up doesn't do anything to it.The fact that it didn't pause, it's because the ground scenery is just a bunch of polygons, less than 50 in total, probably, which can't just be compared to the complexity of a scenery object, that is usually measured in thousands of polygons, like the group of C17s.

At 4-5NM the main aerodrome buildings with terminals rendered with a fairly significant pause. I'm attempting to seek clarification on your statement that setting "[AntiPopUp=30] WILL force EVERYTHING to be loaded at the maximum scenery range."

All the objects handled by the Addon Manager, yes.However, you are right with the buildings because, they are handled differently, they don't have a "dynamic" range, like small objects, so they don't get effected by the Anti-popup setting, and they were set at 6 nm, which is a little bit too short.

Does that imply that all scenery objects would be simultaneously loaded? Understanding that each scenery product has differing loading ranges, what is the range of PHNL in particular?

PHNL had a 10 nm range in the release version, but buildings were set at 6.Yes, this was an oversight, the buildings range and the main scenery range should be usually set at the same value, and they usually are.If you download the Stand-Alone Addon Manager now, you will get the updated version, that put both the global scenery range and the buildings range for PHNL at 8 nm:http://www.virtualisoftware.com/binaries/s...donmanagerX.exe

I understand the need for flexibility given the wide array of hardware capabilities within our community.

It's important to understand this flexibility, which is a bonus, and it's only obtained by the means of the Addon Manager. As you can see, we can both give the user a setting to play with, and we can fix things very easily, without touching the scenery, by simply distributing updated Addon Manager files.If we didn't use it, we would have been forced to hardcode loading ranges in the scenery, and making a decision ourselves of smoothness vs frame rate, that is not said would have worked across all systems, and tweaking it would have required to recompile and redistribute the whole scenery.Instead, we can keep the scenery in sync with new hardware developements: if we released the Addon Manager with the ability to increase object ranges 30x in 2006, when we released our first FSX scenery and FSX was still at RTM running with Intel Dual Core at *best*, nobody would have been able to use it.

Umberto,When try different settings on the antipop up slider, there are actually more pauses. The best setting on my system is O.My setting only goes up to 10. I'm downloading the new manager today. I'll check in with my test results."Since some users wanted to try higher values, and suggested to "load everything at once", we put a new version online today, that allows to set the slider up to 30x"Can you provide a link, please.Thanks.

When try different settings on the antipop up slider, there are actually more pauses. The best setting on my system is O.

I doubt it, since it's not possible to set it to 0 in the first place and, even if you set it manually in the FSX.CFG, it wouldn't be used as 0 because, if it was, it would multiply every range by 0, which means the whole scenery would just disappear so, if you see the scenery, you can be sure it's not 0.In any case, it's plain impossible you get more pauses at low settings compared to high settings, and if you followed the explanation so far, it would be apparent why.However, if your system can't really cope with the added load of increasing the object's ranges, you might get generally worse performances, and pauses might have instead NOT caused by the distance culling, but simply by the sheer complexity of the scenery, which includes both polygons and textures, and it wouldn't make any difference in this case if it was handled by the Addon Manager or not. THAT'S why there's a setting. If there was such thing as a "universally correct" value, we wouldn't make it user settable but, instead, it would have been a fixed harcoded value in the scenery, the same for everyone.

Can you provide a link, please.

The link was in my previous message. And of course, it's on each and every Info page of every product on our website.

My apologies for using a 0 number. I thought it was 0. The slider is all the way to the left.I downloaded the new manager and set it to 30. It didn't help. However, I did find the solution. This answers why when I ran the demo it ran perfectly without minor pauses.The answer is in the AG setting. A setting of Dense, which is where I always keep it when flying in the Orbx world works perfectly with no pauses.A setting of 30 does keep the scenery in place with no pop ups, but as you explained there's a significant fps drop.Thanks for your thorough explanation.

None of this makes any sense. I can hover over parking lots at 20 feet away and watch the traffic pop in. I'm not talking nautical miles distance, I'm talking about things like boxes and cars in lots, trees, etc popping in when I am literally 20 feet away. What fixes that? I get pauses from those things. How can I load all of that stuff at the beginning and keep it loaded. I've always hated that I can be literally right overhead in my chopper and half the scenery is missing in these airports...

None of this makes any sense.

It obviously does, unless you decided to skip all the explanation.

I can hover over parking lots at 20 feet away and watch the traffic pop in. I'm not talking nautical miles distance, I'm talking about things like boxes and cars in lots, trees, etc popping in when I am literally 20 feet away.

Which, as I've said:

This act as multiplier of loading ranges for ALL the objects handled by the Addon Manager. Normally, on a scenery like KFLL or KFJK, the smallest loading ranges are assigned to objects like airport ground clutter, carts, small signs, and this is usually set around 0.3/0.4 nautical miles.

So, the DEFAULT for this kind of objects, with the Antipop slider to 1.0, is 0.3 nm (which is quite a lot more than "20 feets"), but by using the slider, with the old version, you could have set it to 10, making the loading distance for these objects to 3 nm.With the new version, the loading distance can be multiplied up to 30x, which makes for 9 nm for the things that have the shortest range possible.

What fixes that?

The Antipop slider.

I get pauses from those things.

You will not, if you use the slider.

How can I load all of that stuff at the beginning and keep it loaded. I've always hated that I can be literally right overhead in my chopper and half the scenery is missing in these airports...

Which is why we have that setting. By using the newest Addon Manager and set it to the maximum value, those objects will be loaded only once when entering the scenery area (about 9-10 nm), and never discarded again.Which is confirmed by this user in the previous post:

A setting of 30 does keep the scenery in place with no pop ups, but as you explained there's a significant fps drop.

NOTE that, as already explained, objects STILL have their LODs. And this is not handled by the Addon Manager but by FSX, entirely on its own.This means you will still see some object pop-ups, because in that case, you are not seeing the Addon Manager loading/unloading the objects, instead, you are seeing the switch between high, mid and low LOD levels made by FSX.LOD level switching does not cause loading pauses when its happening, because the object has already been loaded with all its LODs when it entered in viewing range. There's no loading involved when the LOD is switching. If there was, you would had constant pauses caused by AI airplanes as well, since they also use several LOD levels (at least those programmed as they should).