Why does my cutscene crash on console but not PC?

That pattern strongly points at video/codec issues, the cutscene's video format is supported on PC but not the console (or vice versa), so playback crashes on the platform that can't decode it. Use a format the target platform supports, verify the video file is valid in that build, and handle playback failure gracefully by skipping rather than crashing.

Why does my cutscene crash only sometimes?

That points at a state-assumption bug: the cutscene assumes certain objects, actors, or game state exist and are in a particular condition, and it crashes only when the player reaches it in a state you didn't anticipate (via an unexpected path or order). Test the cutscene from multiple approach paths and states, not just the happy path, and make it robust to the state it actually encounters.

Why Does My Game Crash During Cutscenes?

Q: Why does my game crash during cutscenes?

Usually one of three causes: video playback or codec problems (a format the platform can't decode, or a missing/corrupt video file), a missing or broken cutscene asset, or a scripted-sequence bug where the cutscene assumes game state, objects, or actors that aren't actually guaranteed. The stack trace and whether it's platform-specific tell you which.

Quick answer: Your game crashes during cutscenes because of something specific to how cutscenes work: video playback or codec issues (a format the platform can't decode, or a missing/corrupt video), a missing or broken cutscene asset, or scripted-sequence bugs where the timeline assumes game state or objects that aren't guaranteed. The stack trace and whether it's platform-specific tell you which.

A crash during a cutscene is frustrating for players because it interrupts a narrative moment, often at the same point every time. Cutscenes are a distinct kind of content (scripted sequences, often with video and timed events), so they have their own crash causes, and because they're frequently linear and repeatable, the crashes are often consistent and reproducible.

Common Cutscene Crash Causes

Cutscenes crash for reasons specific to how they work. Video playback: if the cutscene plays a video, a codec or format the platform can't decode, or a missing/corrupt video file, can crash playback, and this is often platform-specific (a format that works on one platform fails on another). Missing/broken assets: the cutscene references a model, animation, or audio track that isn't present or fails to load. And scripted-sequence bugs: the timeline assumes certain game state, objects, or actors exist and are in a particular condition, and if they're not (because the player reached the cutscene via an unexpected path or state), the sequence crashes.

A cutscene crash that's platform-specific points at video/codec; one that always happens at the same beat points at that beat's assets or scripted logic; one tied to how the player got there points at a state assumption.

How to Diagnose It

Cutscenes are often linear and repeatable, so you can usually reproduce the crash by playing to that cutscene, making the trace easy to get. The trace distinguishes the causes: a trace in video/media playback points at codec/format; a trace in asset loading points at a missing asset; a trace in your cutscene/sequencer logic points at a scripted-sequence bug. Platform-specificity (crashes on console but not PC) strongly suggests video/codec.

Bugnet captures the trace, device context, and platform with each crash and groups them, so a cutscene crash shows whether it clusters by platform (codec) or hits everyone at that beat (asset/logic). The platform breakdown is especially useful for video issues, commonly a format supported on some platforms and not others.

What to Do About It

For video/codec, use a platform-supported format and handle playback failure gracefully (skip rather than crash). For missing assets, ensure they're in the build and load them defensively. For scripted-sequence bugs, make the cutscene robust to the state it actually encounters rather than assuming objects exist, and test it from multiple approach paths. Always make cutscenes skippable so a failure doesn't strand the player.

See our guide on fixing a game that crashes during a cutscene for the steps. Testing cutscenes from multiple states (not just the happy path) is what catches the state-assumption crashes.

Cutscene crashes are video/codec, missing assets, or scripted-sequence state assumptions. The trace and platform breakdown tell you which, and always make cutscenes skippable.