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
ModsandSavesdirectories. - Copied mod archives may reside in an installation folder other than the one currently being launched.
Persistent StartPos compatibility
TheStartPos 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:
- 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.
- Resume Celeste and finish any room transition or cutscene.
- Check whether the snapshot is missing, damaged, or from a different runtime or mod set.
- See StartPos recovery for the complete persistent-snapshot checks.
Savestate map compatibility
The separate Capture StartPos State and Restore StartPos State bindings use the active 1-9 savestate slot. Per-map overrides apply to this savestate path. Find Always Use Broker and Allow Unsafe StartPos Restore underCurrent Map Compatibility in Everest’s Akron options. Use the unsafe restore option only for controlled testing in a non-submission setup.
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.