Game Crashes

If a game won’t launch or behaves oddly, work through the checks below. These are the causes Sakura’s engine layer and settings can actually explain — if none apply, see Support with the game name and what you’re seeing.

Symptom: Trying to launch a game shows an alert: “This game runs on a different engine than the one already used this session. Close and reopen the app, then launch this game first.” with Close App and Cancel.

Cause: Sakura can only load one engine family — classic NScripter/ONScripter or ONScripter-RU — per app session, because both link the same lower-level audio/video library and can’t safely coexist in one process. If you launch a game on one engine family and then try to launch a different game that needs the other family (or a second ONScripter-RU game in the same session), Sakura has to stop you rather than risk a crash.

Solution: Tap Close App, reopen Sakura, and launch the game you actually want first. This is expected behavior, not a bug — it only happens when you switch between engine families (or launch a second ONScripter-RU game) within the same session.

Symptom: A game runs, but behaves like the wrong engine — e.g. an ONScripter-RU game (like an Umineko release) is missing display filters, translation, or font options, or a classic game doesn’t behave as expected.

Cause: Sakura auto-detects each game’s engine from its files, but detection can occasionally pick the wrong family for an unusual or repackaged game.

Solution: Open Game Settings for that game and check the Engine picker (Auto / ONScripter / ONScripter-RU). If it’s set to a specific engine, try Auto first; if Auto is picking wrong, set it explicitly to the engine you know the game needs.

Symptom: A game imports fine but fails to load its data, or its archive (arc*.nsa) appears to contain garbage/misaligned data.

Cause: Some games ship an .nsa archive with a byte offset baked in by the original release (a header or padding before the real archive data begins).

Solution: Open Game Settings for the game and set NSA Offset to the byte offset the game expects (0 = none, the default). This applies at the next launch.

Symptom: A game’s saves or configuration seem to be looking for an ID that doesn’t match how Sakura registered it.

Solution: Open Game Settings and set Game ID (a save/registry key override). Leave it empty unless you have a specific reason to override it — this applies at the next launch.

Symptom: Sound stutters, crackles, or drops out during gameplay.

Solution: Open Game Settings (or global Settings > ONScripter Engine) and raise Audio Buffer (default 8 KB, range 1–64 KB). Larger buffers reduce glitches at the cost of a little extra latency; if you instead need lower latency and don’t hear glitches, you can lower it.

• Check the Engine picker first — most launch oddities trace back to a game running on the wrong engine family.
• Per-game settings can override globals — if a game behaves differently than you expect, check whether Use Global Settings is off for it and review the per-game values underneath.
• Re-import if a game seems structurally broken — see Import Problems for format and detection issues.
• Report what you can’t explain — if a game crashes outright and none of the above applies, get in touch via Support with the game name and engine (classic or ONScripter-RU, shown on the game’s detail page).