What causes an inverted normal map?

The normal map's green (Y) channel uses the opposite convention from your engine (DirectX versus OpenGL style), so surface detail appears inverted — bumps look like dents under lighting.

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 an Inverted Normal Map (Wrong Lighting Direction)

Quick answer: Flip the normal map's green channel to match your engine's convention, set the texture's import setting accordingly, or flip it in the shader.

A normal map that lights inside-out is a green-channel convention mismatch. Flipping Y fixes it. Here is how.

How to fix it

1. Identify the Y convention

Engines expect either OpenGL (Y+) or DirectX (Y-) normal maps. If detail looks inverted under a moving light, the green channel is in the wrong convention for your engine.

2. Flip the green channel

Flip the normal map's green channel — in the import settings, a texture tool, or by inverting Y in the shader. This switches the convention so bumps read as raised, not recessed.

3. Standardize your pipeline

Decide on one convention for the whole project and author or convert all normal maps to it, so you do not chase this per-asset. Document it so new maps come in correct.

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.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.