Certainly once I get some dev docs out there will be guidelines to make sure OSX objects hit the fast path.

As a hack, I downloaded that downtown LAX conversion – it’s heavy for my Mac, but went from 12 to 14.5 fps when I replaced the ATTRibutes used with their optimized v10 equivalents…that’s a 20% fps boost for a little bit of search and replace.

Another potential big win would be in OpenSceneryX, but currently not with facades – there are only two of them in the library (well done Jonathan! 😉 but even these don’t make use of either of the optimised features mentioned above. I’ll keep an eye open here for any new optimisation options being implemented for objects, lines, polygons or forests, in case there are opportunities for tweaking OSX objects.

Not to stray off topic, but was wondering when we might start seeing at least some building at airports other than the “demo” area?

Yes, all this work is worth it so us 3rd parties can build efficient facades etc. can’t wait to find out how to customize the autogen for local areas too, so we can mix up those lovely residential and commercial buildings.

Well, first, any optimization to common art assets affects everyone. So optimizations that apply to the autogen, base terrain textures, roads and airport lib will apply outside the demo area. (The KSEA demo area’s parking garage, for example, is the default library one.) And some optimizations will be engine wide. But you are right; some optimizations don’t have kick until third parties adopt them.

That’s good….I think! I’ll do some digging and see if I can duplicate the difference. If I find something, I’ll file a bug report. Thanks!

Textures are hard as well, the gap between high and very high seems like a gulf, even if you pull every other render setting back to zero it doesn’t have virtually no effect, high is very jaggy, very high is perfect but unusable, even something in between would be acceptable, extreme textures just crashes the system, so why have it?

I could always find a level base to which i could adjust settings in XP9, but in XP10 I seem to be always on shifting sands and have nothing i really am happy with what i am looking at, and yet at times it comes into perfect focus and with the right frame rate….

No, it will be global objects, I think. The long-term goal is:
– Objects: affects density of all kinds of modeled 3-d
– World level of detail: affects how far out all 3-d goes
– Forests: affects density of forests
– Roads: affects detail of roads
– Airports: affects detail of the airport _ground_ markings and pavement.
That’s the theory at least. Airports can be set up so that at low object density only the _essential_ elements are in place, then in priority order more 3-d comes in. The big divide is between instancing-capable cards (DX11 + some ATI) and not; the instancing-capable hardware has a much higher OBJ density; often you can max them out. Without instancing, you have to dial back objs and/or 3-d distance.

I’m guessing (or at least hoping) that this is going to be tied to the Airport Complexity setting and not the Global Objects density setting?