Skip to main content
Akron runs inside Everest. Compatibility issues usually come from the active installation path, map-specific behavior, missing external tools, or platform-specific file locations.

​
Installation and prefix issues

If files are in the correct locations but Akron fails to load, verify the active runtime:
  • Steam and Steam Flatpak may use different filesystem roots.
  • Wine or Proton prefixes may isolate Celeste data.
  • Portable installations may use their own Mods and Saves directories.
  • Copied mod archives may reside in an installation folder other than the one currently being launched.

​
Persistent StartPos compatibility

The StartPos tab’s persistent Set and Load actions use Akron’s native runtime snapshot path. Current-map broker and unsafe-native overrides do not control this path. If persistent StartPos Load fails:
  1. Confirm that the saved StartPos belongs to the current map and save-file slot. Its saved room can differ from the room you load from.
  2. Resume Celeste and finish any room transition or cutscene.
  3. Check whether the snapshot is missing, damaged, or from a different runtime or mod set.
  4. See StartPos recovery for the complete persistent-snapshot checks.

​
Speedrun Tool savestates

The Speedrun Tool Capture State and Speedrun Tool Restore State bindings drive Speedrun Tool’s active 1-9 savestate slot. They are Speedrun Tool’s feature; Akron only forwards to it, and they have nothing to do with Akron’s StartPos.

​
External tool compatibility

Motion Smoothing’s current compatibility notes call out two cases that matter in Akron:
  • Fancy camera smoothing changes Celeste’s rendering pipeline and is currently documented as incompatible with auspicioushelper.
  • Dynamic framerate mode allows arbitrary FPS, but can conflict with mods that hook the main XNA tick path.
  • Interpolate object smoothing can add 1-2 frames of input delay, so Akron treats that selected value as Cheat even though the Extrapolate object-smoothing value is Normal clear.

​
Rendering and capture

Visual verification is necessary for rendering-sensitive features, including overlays, hitboxes, camera, zoom, death transitions, room captures, map captures, and screenshots. When rendering differs across hosts, include the host, platform, map SID, visible policy/status state, Akron setup, and screenshot evidence in the issue.