Scimitar Side Buttons Work in iCUE but Not In-Game: How to Fix Action Mapping

Published on 2026-11-08 ยท 7 min read ยท By MiniTestLab Engineering Team ยท Category: Mouse Hardware

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Mouse Tester

If your Corsair Scimitar side buttons register in iCUE but do nothing in-game, the problem is almost always a macro layer conflict or a keybind mismatch between what iCUE is outputting and what the game is listening for. The Scimitar's 12-button side grid uses a dedicated STM32 microcontroller to handle button matrix scanning, and iCUE sits on top of that hardware layer translating physical presses into HID reports. When those HID reports carry G-key macro identifiers instead of standard keyboard scancodes, most games drop them entirely because their input handlers only parse standard HID usage IDs. The fix is in the assignment type, not the hardware.

Confirm the Hardware Is Actually Working First

Before touching software, verify the side buttons are physically functional. Run a quick hardware check at Mouse Test and click each of the 12 side buttons while watching the on-screen grid. If every button lights up its corresponding zone, your Omron D2FC-F-7N microswitches (used on most Scimitar Pro and Elite variants) and the ribbon cable connecting the side panel PCB to the main board are intact. If some buttons fail here, the issue is physical: either a faulty microswitch, a partially unseated ZIF ribbon connector on the side panel, or a cracked solder joint on the button matrix. That is a separate repair path entirely.

If all 12 buttons register on that test page but still do nothing in-game, proceed below. The hardware is fine.

The Real Cause: Macro Actions vs. Keyboard Remaps in iCUE

iCUE offers several assignment types for each side button. Most users who hit this problem have their buttons set to one of the following wrong types:

The assignment type that works universally is Remap to Keystroke. This outputs a plain HID keyboard scancode that the game sees as a real key press, identical to pressing that key on your keyboard. Set every side button to Remap to Keystroke and map each one to whichever keyboard key your game action is bound to.

Exact path in iCUE 5.x: Open iCUE, select your Scimitar from the device list, click Actions in the left rail, select the profile tied to your game, click the side button you want to fix, choose Remap Button, then select Keyboard Key from the type dropdown, and press the target key. Hit Save. Repeat for all 12.

Game-Specific Fixes: WoW, FFXIV, and Persistent Failures

For players with corsair scimitar side buttons not working in wow or corsair scimitar side buttons not working in ffxiv, the layering issue has one additional wrinkle: both games use their own keybind systems that must match what iCUE outputs exactly.

In World of Warcraft, open Key Bindings from the game menu, find the action you want on a side button, click its binding field, then physically press that side button on the Scimitar. WoW will read the scancode iCUE is sending. If iCUE is outputting Numpad 1 through Numpad 12, WoW will display those. Confirm the binding saves and test in combat. If WoW shows nothing when you press the side button during binding, iCUE is still outputting a macro packet, not a keystroke. Go back and fix the assignment type first.

In Final Fantasy XIV, navigate to System Menu > Keybind > Custom. The process is identical: click the action slot, press the Scimitar side button, confirm. FFXIV is stricter about modifier keys, so avoid assigning side buttons to combinations like Ctrl+Shift+F-key unless you have confirmed iCUE is sending that exact chord.

GameKeybind Menu PathCommon Failure ReasonRecommended iCUE Output
World of WarcraftMenu > Key BindingsMacro packet, not scancodeNumpad 1-12 or F13-F24
Final Fantasy XIVSystem > Keybind > CustomModifier chord mismatchSingle key, no modifiers
Valorant (Vanguard)Settings > ControlsAnti-cheat blocks macro HIDRemap to Keystroke only
Destiny 2Settings > Keyboard/MouseProfile not auto-switchingKeystroke, correct profile active

F13 through F24 are the cleanest output choices for side buttons. These scancodes exist on the HID spec but have no physical key on standard keyboards, so they will never accidentally trigger a Windows shortcut. Every modern game that accepts keyboard input will accept F13-F24.

Mac-Specific Issues with Scimitar Side Buttons

For corsair scimitar side buttons not working on mac, the problem stack is different. iCUE for macOS requires Input Monitoring and Accessibility permissions under System Settings > Privacy & Security. Without both, iCUE can read button presses but cannot inject keystrokes into other applications. Grant both permissions, then fully quit and relaunch iCUE using Cmd+Q, not just closing the window.

macOS also sandboxes some App Store games in ways that block synthetic HID input from third-party drivers. If a game was installed via the Mac App Store and side buttons still fail after fixing permissions, the game's sandbox is the wall. Games installed through Steam or Battle.net do not have this restriction.

Additionally, verify your polling rate is not set above 500 Hz on older Mac hardware. Open iCUE, go to Device Settings for the Scimitar, and check the Polling Rate slider. Drop it to 500 Hz if you are on a Mac with a USB 2.0 hub in the chain. You can verify actual polling rate behavior with the Mouse Polling Rate Test.

Profile Auto-Switching Is Not Loading Your Layout

A frequently missed cause: iCUE's profile auto-switching is not activating your game profile when the game launches. Your default profile may have the side buttons unassigned or set to macros, while your game profile has correct keystroke remaps. The game never gets the right layout because iCUE never switched profiles.

Fix this in iCUE 5.x: go to Settings > General > Profile Auto-Activation, click the plus icon, browse to your game's executable (.exe on Windows, .app on Mac), and link it to the correct Scimitar profile. Test by closing and reopening the game. Also confirm the profile you linked actually has Remap to Keystroke assignments on all 12 buttons, not macros inherited from a template.

Use the Double Click Test after any firmware update to confirm the primary left and right click buttons did not pick up unintended behavior during the update process. Scimitar firmware updates occasionally reset custom profiles.

Frequently Asked Questions

Why do my Scimitar side buttons work in iCUE's button tester but not in any game?

iCUE's internal tester reads raw hardware events directly from the STM32 button matrix, bypassing the HID output layer entirely. A button can pass that test while still outputting a macro packet that games reject. Switch every assignment to Remap to Keystroke and retest in-game.

My Scimitar side buttons stopped working in WoW after a patch. What changed?

WoW patches occasionally reset custom keybinds to defaults. Open Key Bindings, find your affected actions, and re-bind them by pressing the Scimitar side button in the binding field. Also check that iCUE did not revert to a default profile after a background update.

Can I use the Scimitar side buttons in FFXIV without iCUE installed?

Yes. The Scimitar stores one hardware profile in onboard memory. Program it in iCUE using Remap to Keystroke assignments, then enable Hardware Lighting and Actions mode under Device Settings. The button assignments persist without iCUE running, though you lose per-profile switching.

Do Scimitar side buttons work on Mac without iCUE?

The onboard hardware profile works on Mac for keystroke remaps stored in device memory. Without iCUE, you cannot switch profiles or use software macros. For corsair scimitar side buttons not working on mac in specific apps, check Input Monitoring permissions before assuming a hardware fault.

Should I use Numpad keys or F13-F24 for side button assignments?

F13-F24 are cleaner. Numpad keys conflict with Windows numlock state and some games interpret them differently depending on numlock. F13-F24 have no OS-level shortcuts and are universally accepted as plain keyboard input by game engines.

Will anti-cheat software ban me for using Scimitar side buttons?

No, provided you use Remap to Keystroke assignments, not recorded macros. Keystroke remaps are indistinguishable from standard keyboard input at the HID level. Recorded macros with inhuman timing patterns are what anti-cheat heuristics flag. Do not use timed macro sequences in competitive games.

Launch Companion Diagnostic Tool

Test your hardware right now in your browser with zero install:

Open Mouse Tester