Quick answer: Take the rotator from FindLookAtRotation, zero its Roll component, and clamp pitch short of straight vertical so the up vector never becomes ambiguous.
If your Unreal aiming camera tilts sideways near the poles, the look-at up vector is degenerating. Zeroing roll and clamping pitch fixes it. Here is how.
How to fix it
1. Zero the Roll component
After FindLookAtRotation(eye, target), set the resulting rotator's Roll to 0 before applying it so accumulated tilt is discarded each frame.
2. Clamp pitch away from vertical
Limit pitch to roughly +/-89 degrees. Exactly straight up or down makes the yaw/up basis ambiguous, which is where the roll drift appears.
3. Interpolate rotation smoothly
Use RInterpTo toward the cleaned rotator rather than setting it directly, so corrections blend in without a visible snap.
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.
Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.