What causes shadow rendering performance?

Shadows render the scene from each light's view, so high shadow resolution, many cascades, large shadow distance, and many casters make shadows a major GPU cost.

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 Shadow Rendering Performance Problems

Quick answer: Lower shadow resolution and distance, reduce cascade count, limit shadow-casting lights and objects, and cache static shadows where possible.

Shadow cost is resolution, distance, and caster count. Reducing them fixes it. Here is how.

How to fix it

1. Lower resolution and distance

Shadow map resolution and shadow distance directly drive cost. Lower them to the minimum that looks acceptable — distant shadows can be low resolution or fade out — to cut GPU time substantially.

2. Reduce cascades and casters

Fewer shadow cascades and fewer shadow-casting lights and objects mean less re-rendering of the scene for shadows. Disable shadow casting on small or distant objects that do not need it.

3. Cache static shadows

Shadows from static lights and geometry can be baked or cached rather than recomputed every frame. Caching the static shadow contribution leaves only dynamic shadows to render each frame.

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 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.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.