RetroArch Hotkeys and Per-Core Overrides on Odin 3, Thor, and Odin 2

Make RetroArch predictable before tuning it

RetroArch is easier to manage when everyday shortcuts stay consistent and emulator-specific tweaks stay separate. On Odin 3, Thor, and Odin 2, the aim is to build one dependable global configuration, then save only the exceptions for each core or game.

Menu labels and available shortcuts can vary by RetroArch version, menu driver, and controller configuration. Settings can also vary by firmware — check your own device rather than copying button numbers from another owner.

AYNTime is an independent community knowledge base, not affiliated with AYN.

Start with working controls

Before assigning hotkeys:

1. Open RetroArch directly, rather than through a frontend.
2. Check Settings > Input > RetroPad Binds > Port 1 Controls, or the equivalent controller-binding page in your version.
3. Confirm that the handheld controls are assigned to the correct device and that directions, face buttons, Start, and Select work.
4. Load a familiar game and verify normal gameplay input.

RetroArch uses a virtual controller called the RetroPad. Its logical button labels may not match the lettering or layout you expect on the handheld. Follow the binding prompts and test the result.

If Android or an AYN shortcut intercepts a button, avoid using that button for a critical RetroArch action. Test external controllers separately: their device assignments and bindings may differ.

Build a small, safe hotkey set

Open Settings > Input > Hotkeys. Start with just the actions you actually need:

• Menu Toggle: return to RetroArch’s menu during gameplay.
• Save State: create a temporary progress snapshot.
• Load State: restore that snapshot.
• State Slot Increase/Decrease: switch between snapshots without overwriting the same one.
• Fast-Forward Toggle or Fast-Forward Hold: speed through supported sections.

Treat Reset, Quit, and Load State as potentially disruptive. Keep them away from buttons you press reflexively.

For controller shortcuts, Hotkey Enable can act as a modifier: hold that button while pressing another assigned button to trigger an action. Select is a possible choice, but it is not universally ideal because games also use it.

An example plan is:

• Select as Hotkey Enable.
• Select plus one shoulder button for Save State.
• Select plus the other shoulder button for Load State.

These are suggested combinations, not device defaults. Assign each action yourself and check that the modifier behaves as expected. Some versions expose hotkey-enable delay or input-blocking options; their behavior deserves testing before you rely on them.

For menu access, RetroArch may also offer Menu Toggle Controller Combo, a predefined combination separate from ordinary button bindings. Choose a combination unlikely to occur during gameplay.

Test before trusting shortcuts

Use a game where losing a few minutes will not matter:

1. Confirm that ordinary button presses do not activate shortcuts.
2. Open and close the menu with your chosen combination.
3. Select a spare state slot, save a state, move somewhere visibly different, then load it.
4. Check that fast-forward can be stopped reliably.
5. Restart RetroArch and repeat the menu-access test.

Save states are not a replacement for in-game saves. Support and reliability depend on the core, and states may become incompatible after updates.

Once satisfied, close content and use Main Menu > Configuration File > Save Current Configuration to preserve your global baseline. Avoid saving the global configuration while a content-specific override is active.

Know which kind of save you need

RetroArch separates several configuration systems:

• Main configuration: global preferences, including your baseline input and hotkey setup.
• Overrides: supported RetroArch settings scoped to a core, content directory, or game.
• Core options: emulator-specific settings under Quick Menu > Core Options, with their own management controls.
• Input remaps: changes to how RetroPad inputs control the emulated system, saved through Quick Menu > Controls > Manage Remap Files.

Not every setting belongs in an override. For example, use a remap for swapping emulated game buttons, not a fresh global controller binding. Use the core-options menu’s save controls for emulator-specific options; labels vary by version.

Save a per-core override

To give one core a different supported RetroArch setting, such as an aspect-ratio preference:

1. Load content with that core.
2. Change the intended setting.
3. Open Quick Menu > Overrides.
4. Choose Save Core Overrides.
5. Close and reload the content to confirm the change persists.

A core override affects content launched with that core, not necessarily every game from a particular system. If you use two cores for the same system, configure them separately.

Use Save Content Directory Overrides for a folder-specific exception, or Save Game Overrides for one title. More specific scopes can take precedence over broader settings, so avoid creating all three unless necessary.

Fix settings that keep returning

If a setting changes back, check for an automatically loaded override, core-options file, or remap. Also confirm that your frontend launches the same RetroArch installation and core you tested directly.

Remove unwanted overrides through the override menu where available, then reload content. Back up configuration files before editing or deleting them manually. Change one layer at a time so you can identify the cause.

Got a better tip? Share your tested setup or corrections with the AYNTime community.