I know that area and I know what the problem is

you are butting heads with a 'butthead' at Aces that designed the tree tiles.

Problem.. .there is no AG marked on those tiles.. instead the lazy sonofa... just told the sim to render the MAX trees on every single tile designed specifically for trees.. that means 4500 freakin trees per tile. If thee are 10 tiles with trees in your scenery radius that means 45 thousand trees with the system caching outside the SR.. before SP1 the system had hundreds of thousands of trees on the footprint. They switch to batch call for SP1/SP2 which helped a lot but the design problem is still there

idiot

All he had to do was make tiles that supported a few clearings and mark the clearings for no trees.. it adds up fast. If you were to remove just 15% of the trees per tile thats almost 7000 objects not being looked at by the CPU and video system on a 100% SR.

Ok, so dont try to go crazy making it work... drop the AG a notch and forget it. Until a complete redesign of the tree system can be made it will be an issue. We do have an idea how to fix this but the main problem is the IDIOT also gave us no way to tell the sim to switch trees to the 'exact' right type for the location the tile is playing if we assign tree locations manually

It will switch but your totally limited to choices that may not look right since the same tiles are used all over the world everywhere!

They made the tree system generic in a utterly lazy way


Sorry.. but this is one duckup I have absolutely no sympathy for and will call this one as I see it


In some places you can fix this with landclass.. if the LC removes the trees above the alpine line as it should you get the smooth perf back

I dont know of any LC that changes the are in question here.

you can try adding just the tree restriction line to the config.. set it for
TERRAIN

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=3800

I dont like adding that as it does throw off the priority system but give it a shot and see if it helps

SubZer0 wrote on Feb 25^th, 2009 at 5:15pm:



They added that hook to the DLLs becuse they knew what they ducked-up. As I said, I dont like using it and I would never use the building restriction line however if you are one that flys areas like that and need the relief it may be of benefit over the potential problem

I have not really tested what I posted so I dont know if it would work or not.. just doing the AG bandwidth math in my head gave me that number for the line. It may work fine and not be an issue elsewhere

In reality and knowing how much bandwidth the sim reserves for AG trees (20%) the real value for MAX per cell is about 3000 trees with 100% AG slider

Problem is I know that would probably cause more problems in other areas

You guys should test with a lower TBM and BP setting in this area and see what happens as well.. you may have set up for one type of flying but ducked yourself in trees

Try TBM 80, BP 70000000 frame lock 30 and MAX TREES PER CELL at 3300 on 100% AG and see what happens

It was better but still stutter/surges. At times it was very smooth but look in the wrong direction and bump bump bump. Frames were remained high durring the flight.

jwenham wrote on Feb 25^th, 2009 at 6:45pm:



ok, now bump TBM and BP back up and leave the trees restricted to 3300 and try again


The bottom line is those restriction lines really do mess up the priority system so its really best to just run without the tweaks in the config and just bump the AG slider down to compensate for the aces mess.

stevehookem wrote on Feb 25^th, 2009 at 7:00pm:


well... figure out whats going on... did you try working the scenery complexity, AG and AL/GA traffic and/or airport vehicles?.. all of those items are hard hitting in NYC

Cars, especially with UTX are killer. I dont ever let those go above 8 which is where they stay locked everywhere

If you are saying you have taken this same flight and it was smooth then something changed

there is no 1 size fits all with this sim... NYC is a hell of an area.. just becuse you get it working in Seattle does not mean NYC will run the same.

then just leave the tweak out of the config.. we may not be able to attack the tree problem till the first patch for GEX EU but we are going to try