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 Nausea From a Missing Stable Horizon in a VR Cockpit in Unity

Q: What causes nausea from a missing stable horizon in a VR cockpit in Unity?

The player sees only the moving world with no stationary reference frame, so vection conflict from acceleration triggers motion sickness.

Quick answer: Give the player a static cockpit or reference frame that moves with them, plus a stable horizon element, so the inner ear conflict is reduced.

Sickness in VR vehicles comes from seeing motion your body does not feel. A stationary visual reference, like a cockpit or a nose cone fixed to the player's view, gives the brain a stable frame and dramatically reduces nausea during acceleration and turns.

How to fix it

1. Add a static cockpit

Parent a cockpit or vehicle interior to the player's rig so part of the view stays still relative to the head even as the world moves.

2. Keep a stable horizon

Avoid roll on the camera during maneuvers, or provide a fixed artificial horizon, since rotating the horizon is a strong nausea trigger.

3. Add comfort options

Offer a vignette during acceleration and let players reduce or lock roll, so sensitive users can tune comfort to taste.

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