LOD & Nanite Studio

LOD & Nanite Studio

Module: Modeling · Category: LOD · Tool ID: LODNaniteStudio

A five-tab studio covering the full LOD-and-Nanite pipeline. LOD Analysis audits LOD chain quality. Nanite Mesh Validator flags meshes that should/shouldn’t have Nanite enabled. Nanite Readiness checks for material compatibility. Mobile Proxy estimates proxy requirements per platform profile. LOD Generator creates LODs in single or batch mode and generates HLOD configs.

---

When to use it

• Performance pass — find every high-poly mesh that’s missing LODs or missing Nanite, all in one place
• Multi-platform shipping — get an objective view of what your assets cost on Mobile / Quest / Console targets
• Pre-cook validation — meshes with Nanite enabled but using translucent / masked / WPO materials silently fall back to fallback meshes
• New project setup — generate LOD chains in batch instead of asset-by-asset in the Static Mesh editor

When not to use it

• Don’t use this for skeletal mesh LODs — focus is Static Meshes
• Don’t expect this to replace per-mesh hand-tuned LODs — the LOD Generator is good for batch first-passes, not for hero assets

---

Opening the tool

1. Open the EQLabs Hub and search for LOD (or browse to Modeling → LOD)
2. Click the tool card
3. Use the tab bar to pick the analysis or operation you need

---

Tab 1 — LOD Complexity Analyzer

Project-wide audit of every static mesh’s LOD chain.

Interface

Section	What it does
Search box	Filter by mesh name
Problems Only checkbox	Hide healthy entries
Min Triangles Threshold	Don’t audit meshes below this triangle count (small meshes don’t need LODs)
Scan	Walks every Static Mesh and computes per-LOD reduction and screen size
Copy	Plain-text dump
Summary	Total meshes / no-LOD count / Nanite count
Results list	Per-mesh row, severity-coded

Per-mesh data

For each mesh: LOD count, LOD0 triangles, Nanite enabled flag, auto-LOD setting, full LOD chain with reduction percent and screen size per level.

Severity coding

Severity	Meaning
Good	LOD chain in good shape (or Nanite enabled and high-poly)
Warning	High-tri mesh with no LODs, or LODs with poor reduction ratios (<30% reduction between consecutive LODs)
Critical	Severe issues — no LODs on a very high-poly mesh that isn’t Nanite-eligible

---

Tab 2 — Nanite Mesh Validator

Per-mesh Nanite recommendation engine.

Interface

Section	What it does	Default
Scan Path	Folder to scan	/Game
High-Poly Threshold	Tri count above which Nanite is recommended	10000
Low-Poly Threshold	Tri count below which Nanite is not worth the overhead	500
Scan	Walks meshes and classifies each
Batch Enable Nanite	Enables Nanite on all selected meshes flagged “Should Enable”
Batch Disable Nanite	Disables Nanite on all selected meshes flagged “Should Disable”
Copy	Plain-text dump
Summary	Total / Nanite-enabled / Should-enable / Should-disable

Recommendations

Status	Meaning
OK	Nanite setting matches mesh complexity
Enable Nanite	High-poly mesh that would benefit from Nanite
Disable Nanite	Very low-poly mesh — Nanite overhead exceeds the gain

Workflow

1. Pick a scan path, click Scan
2. Review the recommendations; select rows you trust to be batch-fixed
3. Click Batch Enable Nanite or Batch Disable Nanite as appropriate
4. Save All to persist

---

Tab 3 — Nanite Readiness Checker

Material-side compatibility check. Nanite has hard requirements — translucent, masked, or WPO-using materials force fallback.

Interface

Section	What it does	Default
Scan Path	Folder to scan	/Game
High-Poly Threshold	Tri count for “should use Nanite” classification	10000
Low-Poly Threshold	Tri count below which Nanite isn’t worth it	1000
Scan	Walks meshes and inspects assigned materials
Copy	Plain-text dump
Summary	Ready / Needs Attention / Incompatible / Recommended counts

Readiness states

State	Meaning
Ready	Nanite enabled and materials are all compatible
Needs Attention	Nanite enabled but at least one material has WPO / translucency / masked usage
Incompatible	Mesh would benefit from Nanite but materials make it incompatible
Recommended	High-poly mesh, materials are compatible — recommend enabling

What flags a material

• WPO — World Position Offset usage in a material disables Nanite for that mesh
• Translucency — translucent materials are not Nanite-eligible
• Masked — masked materials work but with caveats; flagged for review

---

Tab 4 — Nanite Mobile Proxy Generator

Cross-platform proxy analysis. Pick a platform profile, see which meshes need proxies.

Interface

Section	What it does
Scan Path	Folder to scan
Platform Profile combo	Pick the target — Mobile Low / Mobile High / Quest VR / Console
Scan	Analyzes Nanite meshes against the selected profile
Copy	Plain-text dump
Summary	Total Nanite meshes / proxies needed / tri budget used / over-material-limit
Results list	Per-mesh row with target tri count, base LOD recommendation, status

Platform profiles

Profile	Max Triangles	Max Material Slots	Vertex Colors Required
Mobile Low	5,000	(configured)	(configured)
Mobile High	15,000	(configured)	(configured)
Quest VR	10,000	(configured)	(configured)
Console	50,000	(configured)	(configured)

Proxy status

Status	Meaning
Good	Source already fits within the platform’s budget
Warning	Needs a proxy; reduction is achievable
Critical	Source exceeds material slot limit, or vertex colors need baking

The tab tells you which existing LOD level would best serve as a base for the proxy and whether vertex colors need to be baked separately.

---

Tab 5 — LOD Generator

Generates LOD chains for single meshes or in batch. Includes an HLOD configuration section.

Single-mesh generation

Field	What it does	Default
Source Mesh	Static Mesh to generate LODs for	(empty)
Reduction Percents	LOD reduction targets, in order	[50%, 25%, 12.5%]
Screen Sizes	Screen size thresholds per LOD	[1.0, 0.5, 0.25, 0.125]
Generate LODs button	Builds the LOD chain on the source mesh

The Proposed Levels list previews predicted tri counts before commit.

Batch generation

Field	What it does	Default
Batch Scan Path	Folder to operate on	/Game
Min Triangles	Skip meshes below this tri count	1000
Skip Nanite	Skip meshes that already have Nanite enabled	true
Skip Existing LODs	Skip meshes that already have LODs	true
Batch Generate LODs button	Walks the path, generates LODs on every eligible mesh

HLOD configuration

Field	What it does	Default
Enable HLOD	Toggle HLOD config generation	false
Cluster Radius	World-space radius for HLOD clustering	5000 cm
Min Cluster Size	Minimum actor count to form a cluster	5
Generate HLOD Config button	Builds an HLOD setup based on these params

Workflow

Single-mesh

1. Drop a Static Mesh into the Source field
2. Tweak Reduction Percents and Screen Sizes if needed (defaults are sensible)
3. Confirm the Proposed Levels preview looks reasonable
4. Click Generate LODs

Batch

1. Set the Batch Scan Path
2. Adjust Min Triangles to control which meshes are touched
3. Leave Skip Nanite and Skip Existing LODs on unless you have a specific reason
4. Click Batch Generate LODs — a progress dialog tracks the run
5. Save All afterward

---

Settings reference

LOD Analysis

Field	Default
Min Triangles Threshold	5000
Problems Only	false

Nanite Mesh Validator

Field	Default
High-Poly Threshold	10000
Low-Poly Threshold	500

Nanite Readiness

Field	Default
High-Poly Threshold	10000
Low-Poly Threshold	1000

LOD Generator

Field	Default
Reduction Percents	[50, 25, 12.5]
Screen Sizes	[1.0, 0.5, 0.25, 0.125]
Batch Min Triangles	1000
Skip Nanite	true
Skip Existing LODs	true

HLOD

Field	Default
Enable HLOD	false
Cluster Radius	5000 cm
Min Cluster Size	5

Settings are persisted to [Project]/Saved/EQLabs/Settings/LODNaniteStudio.json.

---

Output

• In-place modifications — Batch Enable/Disable Nanite, single-mesh and batch LOD generation modify Static Mesh assets directly. Marked dirty until Save All.
• Undo — Nanite toggles and LOD generation are wrapped in ScopedTransaction. Ctrl+Z reverts. Batch operations are a single undo step.
• Clipboard — every tab has a Copy button
• HLOD config — generated configuration is applied to the level’s HLOD setup

---

Tips & gotchas

• Nanite recommendation thresholds are heuristics — the defaults work for typical games. Tighten the High-Poly Threshold for mobile-first projects, loosen for film-quality archviz.
• WPO disables Nanite silently — a Nanite mesh whose material uses WPO falls back at runtime with no warning. The Readiness Checker is the only signal you’ll get.
• Batch LOD generation respects the safety toggles — Skip Nanite and Skip Existing LODs are on by default for a reason; only turn them off if you understand the implications.
• HLOD config generation is a starting point, not a finished setup — you’ll typically need to tune cluster radius and inclusion rules in the World Settings afterward.
• Mobile Proxy Generator is analysis-only — it tells you what proxies you’d need; actually generating them is the LOD Generator’s job (with low Reduction Percents) or a manual export.
• Single-click pings the asset in the Content Browser; double-click opens the Static Mesh editor.

---

Related tools

• Mesh Intelligence Dashboard — find the high-tri meshes that drive the LOD/Nanite conversation
• Scan Cleanup & Remesh Utility — clean dense scans before generating LODs
• Physics & Collision Studio — Nanite meshes still need traditional collision; check both
• Project Doctor Suite (Tech module) — broader project-health audit

---