NZFF

FSX AUTOGEN.

Wondering if anybody can help........I have inserted the extra lines which are recommended into the config. file, and have them set at 800 for trees and 1500 for buildings. Does this affect buildings and trees at airports as well? I would like to keep all the buildings/trees installed with add-ons such as RealNZ, but do not know if by setting the autogen figures to these low figures, if this will also affect airport buildings. Anybody know? Also, does anyone have experience about how big an effect on fps it has to set these at 1500 and 3000 (trees/buildings) instead?

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=800
TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=1500

Thanks in advance,
smooth landings.

The agns trees setting should not do much , the buildings mite ,,,i was testing out Robins scenery last week sometime ,i found i had nothing there in wellyX with everything set to low , i flick the slider up to "NORmal"settings and it all popped back up , kinda bugs me as this happens with my own scenery aswell ..
only way to make sure is to Test it out yourself as you can always go back and change it after if it has played up with scenery

Robin will be able to explain the reasons behind the way the spars to hign agn and building complex works with his scenery ..

The easiest way to test the effect on FPS is to experiment. Quick and dirty - turn on full Autogen and fly around an area taking note of FPS. Then turn off Autogen and do the same. Any tweaks you make to the amount of trees / buildings is going to fall somewhere in between

Deane

creator2003 wrote:

QUOTE (creator2003 @ Mar 2 2008, 10:06 AM) <{POST_SNAPBACK}>

Robin will be able to explain the reasons behind the way the spars to hign agn and building complex works with his scenery ..

There are two issues here, one the autogen density and the other the scenery complexity.
The autogen in my scenery is quite sparse compared to default. There are two reasons for this. First, I don't want to overpower the photo scenery, I like to let it show through as much as possible and just add enough autogen to give a 3D look when down low. Secondly, autogenning a photo scenery for FSX is a huge job, which takes months. If I autogenned every house and tree it would take years:)
The idea is that you should be able to use your normal autogen settings which work well with the default scenery, without having to adjust it for the photo scenery.
I doubt that the autogen tweaks would have any effect on my scenery, as much of the scenery would already be below the threshold which the tweaks impose.
Incidentally, the autogen and scenery complexity settings are completely unrelated, and have no affect on each other. However sometimes it may be tricky to figure out what is autogen and what are default buildings in a particular area.
The Scenery Complexity setting too works a bit differently from normal in my scenery. I figure that if someone went to the trouble of actually buying the scenery, then they want to see as much of it as possible most of the time. For this reason, there are normally (but not always) three different states:
With very low complexity, the entire airport may disappear, leaving only the runways and taxiways. This can be useful if, for example, you are flying online and need all the performance you can get without the complications of an addon airport.
With a lowish setting, ALL the airport buildings may appear, it just might thin-out the extra bits like cars, and remove fences etc. I normally sort objects into two sets, the first set is the real airport components, such as the buildings, and the other is eyecandy, which if we can't see it won't change the realism of the airport.
Then at normal or slightly higher, everything will display.
With 'default' scenery, or scenery made from default objects, it makes more sense to use all the different settings, but with photo-accurate buildings it makes more sense to see the 'real' airport.
These days, though, I tend to rely more on LODs to fine-tune the display complexity. LODs allow each object to have different model complexities, depending on their distance. So even though you might think you are looking at the entire complex airport from a distance, it is actually quite a bit lower in complexity due to LODs.

Thanks guys for the detailed replies!! I have already increased the settings on the texture for both trees and buildings, as I found that the computer could handle it. I am aiming at keeping the fps over about 20 on average, which is why I tried to initially set these texture settings lower.

So based on your answers then I will set the texture settings to high/very high and also increase the texture settings a bit further in the config. file.

Thanks again,

smooth landings.