GameLoop keymapping not working — which break is yours

Open GameLoop and press F1 (or click the keyboard icon in the toolbar) to toggle keymapping on and off. If that toggle does nothing — keymapping is enabled but your keys still produce no response — note which symptom below matches yours.

The five types fail for different reasons and need different fixes.

---

Type 1: All custom keys stopped working after a GameLoop update

After GameLoop updates itself (or after a Tencent app launcher update), custom keymapping profiles sometimes reset for affected games. The keymapper still opens, but your button layout shows the default positions rather than your setup.

What happened: Major version bumps in GameLoop occasionally migrate keymapping storage to a new format, leaving old profiles in a location the new version no longer reads.

Fix: If you used GameLoop's Export function before the update, go to Settings → Keymapping → Import and load your file. The file is typically named after the game and ends in .json.

If you did not export: rebuild the profile manually, then export immediately. The Export button is in the upper-right corner of the keymapping editor. Store the file somewhere GameLoop cannot reach — your Desktop or Documents folder, not inside the GameLoop data directory.

---

Type 2: Keys show active in the keymapper but do nothing in-game

The keymapping editor shows your layout correctly. Keymapping is toggled on. But pressing any mapped key in-game does nothing — not even the fire button.

Cause A — the game window lost input focus. Click directly on the game's visible area to recapture focus, then try your keys. This happens most often when a Windows notification, another application, or a background process briefly stole the foreground.

Cause B — the game is in touchscreen-only mode. Certain game modes, including some cut-scenes, tutorial sections, and dialogue sequences, disable keymapping temporarily and revert to touch-only input. GameLoop cannot override this. Wait for the sequence to end; keymapping will resume automatically.

Cause C — the keymapping overlay failed to load. Close the game but keep GameLoop open. Relaunch the game from inside GameLoop. This reloads the overlay process that connects keymapping to the Android layer.

If none of these apply and the problem started immediately after a Windows update: check that GameLoop is still in the Windows firewall exception list, and check that your keyboard is not being intercepted by a background remapping tool such as AutoHotkey, SharpKeys, or gaming peripheral software.

---

Type 3: Smart Keymapping keeps overriding your custom layout

GameLoop's Smart Keymapping reads the game's UI in real time and automatically assigns keys to buttons it recognises. Every time the screen changes significantly — entering a new mode, loading a match, or after a game update — it may re-detect and remap.

If you have a custom layout but Smart Keymapping redetects over it, your custom buttons disappear or shift.

Fix: Switch the keymapping mode from Smart to Custom for this game.

In the keymapping editor, look for a mode toggle at the top — it may appear as a switch labelled Smart / Custom or as separate tabs. Switching to Custom locks GameLoop out of the auto-detection loop. Your layout stays fixed regardless of what the game's UI shows.

Once you are on Custom mode, save the profile. Smart Keymapping will not interfere with saved Custom profiles during a session, but verify on next launch that the mode has stayed on Custom — some early versions of GameLoop reset this on relaunch.

---

Type 4: Mouse movement works but ADS aim feels wrong after changes

The mouse moves the camera. You can look around. But aiming down sights (ADS), scoped view, or precise micro-adjustments feel different than they did before — either too fast, too slow, or jumpy.

This is not a keymapping problem. It is a sensitivity calibration issue.

Two things change this without you touching the in-game sensitivity slider:

1. GameLoop's mouse sensitivity multiplier. In GameLoop settings, look for the mouse sensitivity setting (sometimes labelled DPI or sensitivity within the emulator, not the game). If a GameLoop update reset this to default, your effective sensitivity changed even if the in-game number stayed the same.

1. Your mouse DPI changed. If you have a mouse with onboard DPI switching (a button on the mouse), check that you are on the same DPI profile you used when you calibrated in-game sensitivity.

Recalibrate: set the in-game sensitivity to a known value, set GameLoop's emulator-level mouse setting to its default, then adjust in-game until aiming feels right. Write down the final pair so the next update does not leave you hunting again.

---

Type 5: The keymapping profile for this game has disappeared

The profile is simply gone — you open the keymapping editor for a game you had configured and find only the default layout.

GameLoop stores keymapping profiles locally, per Windows user account, in its own data directory. Three things delete them:

If GameLoop has a cloud sync feature enabled (a cloud icon in the keymapping editor or account settings), signing back in should restore profiles synced before the deletion. If cloud sync was not on, the profile is gone.

Recovery is rebuild-from-scratch. After rebuilding: enable cloud sync if available, and use the Export function to keep a local backup.

---

What does not fix these problems

If keymapping is working but feels physically wrong — keys lag behind your presses, or the screen scrolls after releasing a key — that is an input latency problem, not a keymapping problem. The cause is usually high emulator CPU load or a slow polling rate on the USB connection.