Troubleshooting

Quick fixes for the most common problems, grouped by symptom. If nothing here helps, grab the game’s logs (see Where to find logs) and reach out via the Support page.

• “Unsupported archive format” — Aurora accepts zip, 7z, rar, tar, tar.gz, and bz2 archives. If your download is a self-extracting .exe installer, extract it on a computer first and repack the game folder as one of the supported formats.
• “No RPG Maker game found in this archive” — Aurora looks inside the archive for the game’s files (Game.ini or game data for XP/VX/VX Ace; index.html plus a js folder for MV/MZ). Make sure the archive actually contains the full game folder, not just a launcher or a partial download. See File Formats.
• “Insufficient Disk Space” — Extraction needs free space of roughly 2–3× the archive size. Free up storage and retry the import.
• “Copy Failed” — Aurora couldn’t read the archive from its source location. If it lives in a cloud provider (iCloud Drive, Google Drive, etc.), make sure it’s fully downloaded to the device first, then try again.

Try these in order:

1. Switch the Ruby runtime. Open the game’s Settings → Compatibility → Ruby Runtime and try a different option (Auto / Modern 3.1 / Legacy 1.8 / Ace 1.9). Older games (roughly pre-2012 XP/VX titles) often need Legacy (1.8); the change applies on the next launch. See Supported Engines for which runtime fits which era.
2. Turn off Debug / Cheat Mode. If the game stopped launching right after you enabled cheats, disable Debug / Cheat Mode in the game’s Settings → Cheats. Some games have debug menus that crash at boot.
3. Check the game is complete. Some fan games are distributed as source repositories that are missing their full asset packs (battler sprite packs, generated spritesheets, and similar). These crash at or shortly after startup with errors about missing files or bitmaps. Re-download the official full release of the game and import that instead.
4. Read the log. The game usually writes the exact error before quitting — see Where to find logs.

• Check the game’s logs right after the crash — most script errors are recorded there with the failing script name, which often points at a missing file or a bug in the game itself.
• Try the Compatibility toggles in the game’s Settings: Known-Game Fixes and Error Tolerance Shims can work around common script problems.
• Missing-file errors mid-game usually mean an incomplete download (see above) or, for older XP/VX games, missing RTP assets — Aurora can download or import RTPs; see the RTP guide.
• If the crash is reproducible, note what you did right before it and include that with the log in a support request.

• Blurry or overly sharp pixels — Toggle Smooth Scaling in the game’s Settings → Display.
• Stretched picture — Enable Fixed Aspect Ratio in Settings → Display.
• Wrong or glitchy map tiles — Turn off Native Tilemap in the game’s Settings → Compatibility (applies at next launch) and report the game so we can fix the fast path.
• Missing or black sprites/tiles — Almost always missing game assets, not an Aurora bug. Re-import a complete copy of the game (see Game crashes at launch).

• Aurora plays audio even with the silent/ring switch on, so start with volume: the device volume buttons, then the Master Volume slider in Aurora’s Settings. If you use Bluetooth audio, disconnect and reconnect it.
• Music missing only in one place (e.g. the intro) while sound effects work is usually the game’s own scripts, not Aurora — try the same spot in another game to compare.
• If a game is fully silent while others play fine, check its logs for audio errors and send them to support.

Aurora Link discovers nearby players over the local network, so both devices need permission and connectivity:

1. Local Network permission — on both devices. Go to iOS Settings → Privacy & Security → Local Network and make sure Aurora is enabled. This is the most common cause: iOS asks once, and reinstalling the app resets the choice.
2. Same Wi-Fi network — both devices should be on the same network, and Wi-Fi should be on (not just cellular).
3. Both players in the lobby — one device hosts a session; the other should see it appear in the Link lobby within a few seconds.
4. Online sessions: same app version — if online matchmaking stalls forever, make sure both devices run the same release of Aurora (a TestFlight/beta copy and an App Store copy can’t always match with each other).

See the Aurora Link guide for full setup steps.

Every game keeps its own error logs:

1. Open the game’s detail page in your library
2. Open the menu and tap Logs
3. Select a log and use the Share button to save or send it

When a game hits a script error, it writes the details to its log before quitting — this is the single most useful thing to attach to a support request.

Head to the Support page for how to reach us and what to include in a report (Aurora version, device, game name, steps, and logs).