Quick answer: Enable specular/normal-map anti-aliasing (roughness widening with mip level), bake roughness into mips correctly, and add TAA to temporally stabilize the highlights.
Specular shimmer is undersampled highlights. Increasing effective roughness in the distance and stabilizing with TAA removes the sparkle on far metal and glossy surfaces.
How to fix it
1. Enable specular AA
Turn on specular anti-aliasing (geometric/normal-variance to roughness) so smooth distant surfaces get effectively rougher at mip distance and stop sub-pixel sparkling.
2. Bake roughness into mips
Ensure normal and roughness maps mip correctly together (Toksvig or variance-based) so far mips widen the highlight instead of preserving sharp aliasing-prone detail.
3. Add temporal AA
TAA accumulates the highlight across frames, which damps the crawling shimmer that a single-frame technique cannot resolve on tiny specular hot spots.
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.
The bug you can't reproduce isn't gone — it's just invisible until you capture it from the player's device.