What causes motion and photosensitivity issues?

Heavy camera motion, screen shake, and rapid flashing can cause discomfort, nausea, or seizures, and without options to reduce them, affected players cannot safely play.

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 a Game That Causes Motion or Photosensitivity Issues

Quick answer: Offer options to reduce camera motion, screen shake, and flashing, avoid dangerous flash rates, and warn about photosensitive content.

Motion and flashing issues exclude or endanger players. Reduce-motion options fix it. Here is how.

How to fix it

1. Offer reduce-motion options

Provide settings to reduce or disable camera shake, motion blur, screen-space motion, and aggressive camera movement, so players prone to motion sickness can play comfortably.

2. Avoid dangerous flashing

Rapid, high-contrast flashing can trigger seizures. Avoid flash rates in the dangerous range, offer a reduce-flashing option, and test content against photosensitivity guidelines.

3. Warn about photosensitive content

Include a photosensitivity warning and, where relevant, flag specific content. Combined with options to reduce it, this lets affected players make informed choices and play safely.

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.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.