Quick answer: Save comfort options (vignette strength, snap vs smooth turn, snap angle, locomotion type) to persistent storage and reapply them to the providers on startup.
Comfort settings are critical accessibility controls, and losing them each session forces sensitive players to reconfigure or feel sick. The fix is to serialize the chosen options and, on startup, push them back into the vignette controller, turn provider, and move provider before gameplay begins.
How to fix it
1. Persist the choices
Write each comfort option to durable storage (PlayerPrefs, a save file, or your settings system) whenever the player changes it.
2. Reapply on startup
On load, read the saved values and configure the vignette controller, snap/smooth turn provider, and locomotion provider before the player can move.
3. Expose a comfort menu
Provide an in-VR comfort menu with sensible defaults and an easy reset, so players can retune without editing files.
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.
A crash you can name from its stack trace is a crash you can usually fix in minutes.