Skip to content
OmniControlOmniControl

Troubleshooting

Most OmniControl problems trace back to one setting being off or one driver needing a repair. Find the section that matches your symptom below, and work through the short, self-contained fix.

Controller and emulation

The game does not see my controller

If your inputs light up inside OmniControl but the game ignores them, the game is waiting on the virtual pad, not your physical hardware. Emulation is what presents your controller to the game, and it is a Pro feature.

1

Confirm an emulation output is active

Open Emulation and start a virtual Xbox 360 or DualShock 4 output. The game reads the virtual pad; your physical controller feeds it.
2

Check ViGEmBus is installed

The virtual pad runs on the ViGEmBus kernel driver, which is installed separately from the Drivers card in Settings and is NOT carried by the OmniControl installer. If Windows was reset or refreshed, ViGEmBus went with it and reinstalling OmniControl does not bring it back. If it is missing, emulation will not start.
3

Pick the device in the game

In the game's own controller settings, select the Xbox or PlayStation device that now appears. Some games only bind to the first controller they detect, so unplug pads you are not using.

Emulation will not start

If the emulation output fails to arm, the ViGEmBus driver is usually the cause.

1

Repair the driver

Open Settings and look at the Drivers card. If ViGEmBus is not marked installed, press Install and approve the Windows prompt. Re-running the OmniControl installer does not do this: the driver is a separate package, so a Windows reset or refresh removes it while leaving OmniControl in place. Your profiles are untouched either way.
2

Restart and retry

Reboot Windows after the repair, reopen OmniControl, and start the output again from Emulation.

A game blocks the virtual pad

Some titles, usually those with anti-cheat, detect and reject virtual or ViGEm controllers on purpose. This is expected. OmniControl presents a genuine device through ViGEmBus rather than an injector, but that does not exempt any game's rules, and OmniControl does not bypass a block. If a game refuses the virtual pad, it will not work there by design.

Keyboard, mouse, and aim

Aim drifts in Keyboard & Mouse

If the aim stick over- or under-turns compared to your mouse, or the crosshair sails past where you pointed and keeps gliding, the saved turn rate no longer matches the game. Keyboard & Mouse is a Pro feature because it drives the virtual pad through Emulation.

1

Re-run turn-match

Line up a fixed in-game landmark, press F8 to start, turn exactly one full 360-degree circle with the mouse until the landmark lines up again, then press F8 to stop. F8 works from any focused window and saves the result per game.
2

Measure your DPI

Run the DPI drag wizard once so cm/360 is accurate. OmniControl cannot read DPI from the mouse directly, so it counts raw mouse counts over a known physical drag distance. DPI is stored per mouse.
3

Raise the game's controller sensitivity

The aim stick can only turn as fast as the game lets a controller turn at full deflection. Set the in-game controller sensitivity high, often to maximum, so more of your mouse motion maps 1:1 before it saturates.

Tip

Recalibrate turn-match any time you change the in-game controller sensitivity, since the two are linked. The Overlay mirrors the Keyboard & Mouse pad, so you can confirm WASD, aim, and buttons are firing. Full setup is in the Keyboard & Mouse guide.

Profiles

My profile does not switch automatically

Automatic per-game switching is Game automation, a Pro feature. A profile only loads on its own when it is tied to a game in your library.

1

Attach the profile to the game

Add the game to your library and link the profile you want. See Game profiles for the full workflow.
2

Confirm the game is detected

The matching profile loads when the game takes focus and restores the previous one when you leave. If nothing loads, check that the game appears in the library grid. You can always switch profiles manually with one click.

Hardware

My sticks drift on their own

Small unwanted stick movement at rest is usually physical stick drift, which OmniControl can measure and compensate for underneath your tuning.

1

Run Calibration

Open Calibration and follow the guided wizard. It measures stick and trigger drift and stores a snapshot in the active profile. Run it first, before other tuning.
2

Add a small deadzone

If a light drift remains, raise the deadzone slightly in Sticks. A larger outer deadzone or anti-deadzone can help with worn hardware.

Note

Calibration is stored per profile, so run it again for each profile where you notice drift.

DualSense extras are missing

Adaptive-trigger effects, gyro and motion, the touchpad, and the lightbar are DualSense features that come over USB only. Over Bluetooth these extras are not available, though standard remapping and emulation still work wirelessly.

Tip

Connect the DualSense with a USB cable to restore the extras. Related settings live in Motion aiming, Trigger tuning, Adaptive triggers, and Lightbar.

Anti-cheat and scope

Anti-cheat boundary

OmniControl is built for single-player and controller-friendly games. It is not a tool for defeating anti-cheat, and kernel-level anti-cheat competitive shooters are out of scope by design. We ship no Keyboard & Mouse presets for competitive shooters that pair kernel anti-cheat with controller aim assist, and that is a choice about what we publish rather than a lock on your machine. If a game rejects a virtual controller, that is expected, and OmniControl does not work around it.

Still stuck

If none of the above resolves it, ask in the community. Include your controller model, whether you are on USB or Bluetooth, and the game.

Join the OmniControl DiscordQuestions, setup help, and release news from the people building it.

You may also find your answer in the FAQ.