Remapping

Remapping sends any control on your pad to any output you choose. Edit the layout while a game runs, or freeze it with a hotkey so a stray press does not change your setup mid-match.

Overview

The OmniControl remapper turns one physical layout into as many logical layouts as you need. Any button, stick, trigger, or paddle can send a different controller input, a keyboard key, a mouse action, or a macro. On top of that base, three tools multiply what a single pad can do: shift layers add a second meaning to every control while a modifier is held, combos bind an action to two or more controls at once, and turbo repeats an output while you hold a control.

Basic button, key, and mouse mapping is free. Controller-to-controller remaps reach a game through Emulation, which is a Pro feature, because the game reads OmniControl's virtual pad rather than your physical one. Keyboard and mouse bindings are different: they are injected off the live input stream and work on their own, so a free user can bind pad controls to keys and clicks without emulation running. Every mapping saves inside the active profile.

How it works

OmniControl reads your controller and shows it as a live 3D model. When you assign an output to a control, OmniControl intercepts that control's signal and substitutes the output you chose. The original signal no longer passes through once the control is remapped.

Where the output lands depends on its type. Keyboard and mouse outputs are injected into Windows off the live input stream, so they take effect immediately with no emulation. Controller-input outputs (for example, moving the A button to B, or a paddle to a bumper) only reach a game when Emulation is running, because the game sees the virtual Xbox 360 or DualShock 4 pad that OmniControl presents. You can build and preview a full controller remap for free; it takes effect in-game once you start Emulation.

Shift layers, combos, and turbo sit on top of the base map:

• Shift layers give a control a second meaning while a chosen modifier is held. Hold the shift control and every mapped button on that layer sends its alternate output, so one pad carries two complete sets of bindings.
• Combos bind an output to two or more controls pressed together. This adds actions without spending single buttons.
• Turbo repeats an output for as long as you hold the control, at a rate you set. Use it for inputs you would otherwise tap quickly.

Getting started

For controller-to-controller remaps to reach a game, start Emulation so the game reads OmniControl's virtual pad.

Common use cases

• Paddle and back-button assignment. Send an Xbox Elite Series 2 or DualSense Edge paddle to any face button or bumper so you keep your thumbs on the sticks.
• Keyboard and mouse output from a pad. Bind pad controls to keys and clicks for games, launchers, or media apps that expect a keyboard and mouse. These bindings work without Emulation.
• Two layouts on one pad. Put movement and combat on the base layer and menus, emotes, or a build wheel on a shift layer, switched by a held modifier.
• Rapid actions with turbo. Map a repeated tap (reload cancel, semi-auto fire, menu scroll) to a single held control.
• Fixing an awkward default. Swap two buttons a game will not let you rebind, then present the corrected layout through Emulation.

Best practices

• Map the base layer first and confirm each control in the live viewer before adding shift layers, combos, or turbo.
• Keep the shift modifier on a control you rarely need during action, such as a paddle or a bumper.
• Save one profile per game so each title keeps its own layout. See Profiles for how profiles are matched and stored.
• Remember that controller-input outputs need Emulation to reach a game, while keyboard and mouse outputs do not. Test controller remaps with Emulation running.
• Pair remapping with stick tuning and trigger feel in the same profile so the whole controller behaves consistently.

Tips

For repeated multi-step sequences, record a macro and bind it to a single control instead of building a long combo chain.

Troubleshooting

• A controller remap does not work in-game. Controller-to-controller outputs reach a game only through Emulation. Start Emulation and confirm the game is reading the virtual pad. Keyboard and mouse outputs do not need this.
• I cannot edit a mapping during play. The map is probably frozen. Press the freeze hotkey to unlock editing.
• My changes did not carry over to another game. Mappings save per profile. Load or create the correct profile for that game, then remap.
• A game blocks the virtual controller. Some titles, usually those with anti-cheat, reject virtual controllers on purpose. OmniControl does not bypass that. Read the boundary note below.

FAQ

Is remapping free?

Yes. Basic button, key, mouse, and macro binding is free. Controller-to-controller remaps only reach a game through Emulation, which is part of Pro. See pricing for the split.

Can one control do two different things?

Yes. Use a shift layer to give the control a second meaning while a modifier is held, so it sends its normal output on the base layer and an alternate output on the shift layer.

Do keyboard and mouse bindings need Emulation?

No. Keyboard and mouse outputs are injected off the live input stream and work on their own. Only controller-input outputs need Emulation to reach a game.

Where are my mappings saved?

Inside the active profile, alongside shift layers, combos, turbo, stick curves, trigger feel, the emulation output, and the calibration snapshot. The matching profile loads when a game takes focus.

What can I map a control to?

Another controller input, a keyboard key, a mouse action, or a recorded macro. Any button, stick, trigger, or paddle can drive any of those outputs.