Last reviewed 1 May 2026
Applies to
External mesh reduction workflow LOD asset preparation Performance-focused model cleanup
Difficulty Intermediate

Decimate objects in Maya/Blender for LODs

When an object is far away from the camera, players usually do not need to see the full high-detail version of that model. That is where LOD workflows become useful.

One common way to prepare LOD meshes is to create simplified versions of the original model in a 3D tool such as Blender or Maya. This process is often called decimation or mesh reduction.

For beginners, the idea is simple:

  • keep the best version for close viewing
  • use lighter versions at distance
  • reduce rendering cost where the detail is no longer noticeable
Recommended Setup

Plan lower-detail meshes before a VRChat world or Unity project becomes hard to change.

  1. Identify the expensive part of the scene before changing random settings.
  2. Make one change at a time, then test the result in Unity.
  3. For VRChat worlds, retest with realistic avatars, mirrors, lighting, and target platforms.
VRChat note

For VRChat worlds, Unity performance choices affect comfort, upload readiness, Quest or Android support, and how the world behaves with real players present.

What Decimation Means

Decimation means reducing mesh complexity while trying to preserve the overall shape well enough for the distance where it will be seen.

The goal is not to make the model look good in a close-up screenshot. The goal is to make the lower-detail version look acceptable at the distance where it will actually appear.

Why This Matters

If a detailed object remains fully detailed even when it is far away, the scene may waste performance drawing detail the player cannot meaningfully see.

Lower-detail versions help by:

  • reducing unnecessary geometry cost
  • making large scenes easier to render
  • supporting cleaner LOD workflows

When LOD Reduction Is Worth It

LOD preparation is most useful for:

  • repeated props
  • large environment pieces
  • detailed architectural assets
  • objects visible from many distances

It is less useful for:

  • tiny objects rarely seen at distance
  • assets already very low detail
  • objects the player only ever sees up close

A Good Beginner Mindset

Do not try to create perfect LODs for everything.

Instead ask:

  • Is this object detailed enough that a cheaper distant version would help?
  • Will players actually see this object from far away?
  • Is this object repeated enough that optimization would matter?

That helps you focus effort where it is useful.

Basic Workflow in Blender or Maya

The exact buttons differ by software, but the overall process is similar:

  1. Start with the original mesh
  2. Duplicate it
  3. Create a reduced version
  4. Check the silhouette and important forms
  5. Export the simplified mesh
  6. Bring it into Unity for LOD use

The reason you duplicate first is so the original high-detail model stays untouched.

What to Preserve When Simplifying

When reducing a model, the most important things to preserve are usually:

  • the overall silhouette
  • major shape readability
  • important visible features

What you can often simplify more aggressively:

  • tiny bevels
  • small hidden details
  • dense internal geometry
  • detail that disappears at distance anyway

This matters because a good LOD does not need to look identical. It only needs to look believable at the distance where it is used.

Be Careful With Aggressive Reduction

If the reduction is too strong, you may get:

  • broken silhouettes
  • obvious shape collapse
  • ugly shading
  • noticeable popping when the LOD changes

That is why beginners should compare the simplified model against the original from realistic viewing distances instead of just staring at both up close.

Naming LOD Meshes Clearly

Clear naming helps a lot later in Unity.

A simple pattern:

  • Building_A_LOD0
  • Building_A_LOD1
  • Building_A_LOD2

That makes it easier to understand which mesh belongs to which level of detail.

Exporting Reduced Meshes

After preparing the simplified versions:

  1. Export them in the format your project uses
  2. Keep the naming consistent
  3. Import them into Unity
  4. Check the scale and orientation

Once imported, those meshes can be assigned to a Unity LOD Group.

What to Check After Importing Into Unity

Once the reduced mesh is inside Unity, verify:

  • scale matches the original
  • pivot behaves correctly
  • shading still looks reasonable
  • the silhouette is acceptable in the scene

If the imported LOD looks wrong, the issue may be:

  • too much reduction
  • export settings
  • normals or shading problems

Common Beginner Mistakes

Reducing detail too aggressively

The object may become obviously broken when it switches.

Keeping too much detail in the reduced version

This defeats the purpose of the LOD.

Forgetting to compare from real gameplay distance

LOD quality should be judged where the mesh is actually seen, not only up close.

Poor naming

If meshes are not named clearly, LOD setup in Unity becomes more confusing.

Practical Advice

  • duplicate before reducing
  • preserve silhouette first
  • simplify hidden and minor detail aggressively
  • compare at gameplay distance
  • name LOD meshes clearly

Helpful follow-up pages

Final Advice

Decimation for LODs is not about destroying quality. It is about moving quality where it matters most. The close version keeps the detail. The distant versions stay readable but cheaper to render.

If you treat LOD reduction as a distance-based visual compromise instead of a close-up beauty test, your results will make much more sense.

Help! I do not know what to optimize first.

Start with the visible costs: geometry, materials, texture sizes, lighting, mirrors, effects, and anything active near spawn or busy social areas.

Help! The scene only slows down in VRChat.

Test with realistic avatars, platform targets, and active world systems. Editor-only testing can miss the costs that appear in real multiplayer use.

Related Navigation

References