Skip to content
Amir Ebrahimi edited this page Mar 7, 2018 · 6 revisions

AutoLOD

Addendum (from blogpost)

  1. HLOD implementation
  2. Details about dynamic time costs

Settings / Preferences

These preferences are located under Edit->Preferences...

Max execution time

One of the features of AutoLOD is to keep the editor running responsively, so it’s possible to set the max execution time for coroutines that run. AutLOD will spawn LOD generators on separate threads, however, some generators may require main thread usage for accessing non thread-safe Unity data structures and classes.

Default Mesh Simplifier / Batcher

All simplifiers (IMeshSimplifier) and batchers (IBatcher) are enumerated and provided here for selection. By allowing for multiple implementations, different approaches can be compared.

The default mesh simplifier is used to generate LODs on import and when explicitly called. The default batcher is used in HLOD generation when combining objects that are located within the same LODVolume.

Maximum LOD Generated

Controls the depth of the generated LOD chain.

Initial LOD Max Poly Count

In the case where non realtime-ready assets are brought into Unity these would normally perform poorly. Being able to set a max poly count for LOD0 allows even the largest of meshes to import with performance-minded defaults.

Generate on Import

Controls whether automatic LOD generation will happen on import. Even if this option is disabled it is still possible to generate LOD chains individually on individual files.

SceneLOD

Enable Hierarchical LOD (HLOD) support for scenes, which will automatically generate and stay updated in the background.

Show Volume Bounds (for SceneLOD)

This will display the bounds visually of the bounding volume hierarchy (currently an Octree)

Clone this wiki locally
You can’t perform that action at this time.