Reference

errorThresholdPixels, shadowErrorMultiplier, shadowMinLodLevel, castShadows and forceFallback can be changed at runtime. isRenderedByNanoGeo tells you whether NanoGeo draws the object, fallbackReason tells you why not.

enabled

Turns NanoGeo on or off for the whole game.

current

The running instance, or null. current.stats has the statistics shown in the NanoGeo window.

registered

Lists all NanoGeoMesh components.

failureReason

Explains why NanoGeo is not running.

ResetAll()

Restarts NanoGeo.

SetMode(mode) changes the visualization, freezeCulling freezes culling, available is true in the Editor and Development builds.

Both have enabled and SetEnabled(camera, value).

Set recording to true, then read GpuMilliseconds(pass) or TotalGpuMilliseconds. Editor and Development builds only.

Enable NanoGeo, Disable NanoGeo

Turn NanoGeo on or off in the Editor.

Rebake All In Open Scenes, Delete Unused Baked Data

See Baked data.

Regenerate Shaders

Makes the NanoGeo shaders again, for example after updating HDRP or URP.

Validate Shaders

Checks the NanoGeo shaders for Direct3D, Vulkan and Metal.

Repair Runtime Resources

Recreates the settings asset if it went missing.

Restore Project Render Pipeline

Switches back to your own pipeline after a demo scene.

Export Package

Saves NanoGeo as a .unitypackage without the Generated folder, for use in another project.

Samples

Rebuilds the demo scenes.

Benchmarks

See Benchmark.

Add NanoGeo Mesh Prefab and Remove NanoGeo Mesh Prefab work on the selected prefabs and folders. They are also in the right click menu of the Project window.

Select it and read the message in the NanoGeoMesh Inspector, or look at the list in the NanoGeo window. Common reasons are Read/Write turned off on the mesh, a transparent material, a material that is not HDRP Lit, URP Lit or an HDRP Shader Graph, and baked lightmaps.

If the Inspector says NanoGeo is turned off, run Tools > NanoGeo > Enable NanoGeo.

That is expected. The LOD0 NanoGeoMesh draws it at every distance.

After you add NanoGeoMesh or change its material, a new shader variant is compiling. The object appears when it is done.

The copies that were already in the scene use baked lightmaps. Set Receive Global Illumination to Light Probes, see Baked lightmaps.

Turn it off in Project Settings > Graphics > Render Graph. NanoGeo keeps drawing either way, but occlusion culling, the software rasterizer and the visualization modes need Render Graph.

BatchRendererGroup Variants is not set to Keep All, see Installing.

Run Tools > NanoGeo > Regenerate Shaders, usually needed after updating HDRP or URP.

Run Tools > NanoGeo > Regenerate Shaders.

Check that Custom Pass is enabled in the HDRP asset and in the camera frame settings.

The Generated folder was copied from a newer Unity. Delete the Generated folder; NanoGeo creates everything again. To share NanoGeo, use Tools > NanoGeo > Export Package.

Lower the buffer sizes or set a streaming budget, see Making it faster.

Increase the shadow bias on the light, or lower Shadow Error Multiplier.

Baking runs only in the Windows Editor. Streaming saves video memory only. Ordinary MeshRenderers do not hide NanoGeo objects. Shadows always use the normal GPU rasterizer. URP Shader Graphs are not converted yet.

The full test suite passes on Unity 6000.0 (HDRP and URP 17.0), 6000.5 (HDRP and URP 17.5) and 6000.6 (HDRP and URP 17.6), on Direct3D 11 and Direct3D 12, on Windows with an NVIDIA RTX 5070. Unity 6000.1 to 6000.4 were not run; the code was checked against their scripting API. Vulkan and Metal shaders compile but were not run on a device, and Linux and macOS were not tested.

1. Run Tools > NanoGeo > Benchmarks > Generate Benchmark Scene (HDRP). It creates a rock with 1.3 million triangles, comparison LODs and scenes in Generated/Benchmark. This data is large and can be deleted at any time.
2. Run Tools > NanoGeo > Benchmarks > Build Benchmark Players (Development). The players are written to Builds/NanoGeo next to the project.
3. Start each NanoGeoBenchmark.exe. It flies through 1 to 500 million triangles at 1080p and 1440p, writes NanoGeoBenchmark.csv and quits.

On an RTX 5070 at 1080p with shadows, 500 million source triangles took 1.73 ms of GPU time per frame with NanoGeo, 3.72 ms with GPU Resident Drawer and LOD Groups, and 161.5 ms with plain MeshRenderers. With one rock of 1.3 million triangles the difference was small (1.57 ms against 1.93 ms). The measured numbers are in Samples/Benchmark/Results.

Expect a large gain in scenes with many millions of triangles and a small one in scenes that already have good LODs.