How to Fix HDR Tonemapping Washing Out Colors

Washed-out HDR is a tonemapper desaturating the highlights. Choosing an ACES or AgX curve and restoring contrast and saturation brings color back into the tone-mapped image.

How to fix it

1. Choose a better tonemap curve

Replace a plain Reinhard or neutral tonemapper with ACES or AgX, which keep more saturation and contrast in the highlights instead of fading them to white.

2. Tune contrast and post-saturation

After tonemapping, nudge contrast and saturation back up in color grading to compensate for the curve's natural flattening of the midtones.

3. Check the white point

Set the tonemapper's white point so very bright values clip cleanly instead of desaturating a wide range of highlights into a gray smear.

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.