What causes foliage performance problems?

Huge instance counts, expensive foliage materials, no LOD, and poor culling make rendering grass and trees a major cost, especially across an open world.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Foliage Performance Problems in Unreal Engine

Quick answer: Use hierarchical instanced foliage with LODs, enable culling distances, simplify foliage materials, and reduce density where it is not noticeable.

Foliage that kills frame rate needs LODs, culling, and density tuning. Here is how to optimize it.

How to fix it

1. Use instanced foliage with LODs

Render foliage as hierarchical instanced static meshes with proper LODs so distant grass and trees use cheap versions. Unique meshes or no LOD makes foliage one of the heaviest costs.

2. Cull aggressively

Set culling distances so foliage stops rendering when far away or small on screen. Drawing every blade of grass to the horizon is wasted work nobody sees.

3. Simplify materials and density

Foliage materials with translucency and complex shading are expensive across millions of instances. Simplify them, and reduce density where the player will not notice fewer instances.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unreal Engine error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.