In Falsus Keys Not Working? How to Fix Keys Not Registering

Your taps come out as misses even though you know you hit the notes — or worse, you hold two lane keys and only one of them registers. If your keys are not working in In Falsus, here is the short answer up front: in most reported cases it is not a game bug — it is your keyboard's rollover limit. In Falsus is a 6-key rhythm game that routinely asks for several simultaneous presses, and many keyboards physically cannot send them all. This guide shows you how to confirm that in about a minute, then walks through every fix from free to "new keyboard".

Why keys stop registering in In Falsus

The default layout is a one-handed 6K scheme: LShift, A, S, D, F and Space, with LShift and Space on the side lanes and A/S/D/F in the middle (details in our controls guide). Hold notes and dense patterns regularly need two or three keys at once — and on ULT/FBD difficulty, all six.

Most membrane and laptop keyboards wire their keys into a shared circuit matrix. Press the wrong combination and some keys become invisible to the PC. This is called ghosting, and the number of keys a board can report at once is its rollover. Office keyboards typically guarantee only 2-key rollover; gaming boards advertise 6KRO (six simultaneous keys) or full n-key rollover (NKRO), where every key is registered independently.

Community reports match this exactly. In the Steam thread "keys not registering?", a player found that hold notes on A and D would not register together — holding one made the other go dark — and replies pointed to keyboard ghosting and to SOCD settings on the player's keyboard. In another thread, a laptop player simply cannot press all six keys at once when charts demand it. In both cases, the game was innocent.

Step 0: Test your keyboard first (60 seconds)

Before changing anything, prove where the problem lives:

1. Open an online keyboard rollover / ghosting test (search "keyboard ghosting test").
2. Hold your six lane keys at once — LShift + A + S + D + F + Space by default — and watch which ones light up.
3. Also test the specific pairs that fail in-game, like A + D.

If keys drop out in the tester, no in-game setting can fix it: those presses never reach Windows. If everything registers in the tester but not in the game, jump straight to the software fixes below.

Fix 1: Turn off Windows accessibility key features (free)

Two Windows features are notorious for eating game input — and one of them is directly provoked by the default In Falsus layout:

• Sticky Keys activates when you press Shift five times in a row — and LShift is a default lane key. When it pops up mid-chart, it steals focus and swallows inputs.
• Filter Keys tells Windows to ignore brief or repeated keystrokes — catastrophic in a rhythm game.

Open Settings → Accessibility → Keyboard and switch both off, including their activation shortcuts.

Fix 2: USB port and power saving (free)

• Plug the keyboard into a rear motherboard USB port, not a front-panel header or a USB hub.
• Disable USB power saving: in Device Manager, open your USB hubs' Power Management tab and uncheck "Allow the computer to turn off this device"; also set USB selective suspend to Disabled in your power plan.
• If your keyboard software offers a 1000 Hz polling rate, enable it.

Dropped or delayed packets look exactly like missed inputs on dense charts.

Fix 3: Rebind to a combination that rolls over (free)

Every Floor lane is rebindable in the game's settings. Use your Step 0 results: pick six keys that register together cleanly — often keys from different rows, which sit on different parts of the matrix — and keep the layout comfortable for one hand. Test on a MIN-difficulty chart before judging it. Our keybinds article covers rebind strategy in depth.

Fix 4: Stop software from intercepting your keys (free)

If the hardware test passes, something between the keyboard and the game is eating input. Check, in order:

• Macro and remapping tools — AutoHotkey scripts, vendor "game mode" software, lighting suites with macro layers. Close them completely for a test run; stacked remapping layers are a classic input-dropper.
• Overlays — Discord, GeForce Experience, Xbox Game Bar. Disable their in-game overlays temporarily.
• IME / language bar — if you type in Chinese, Japanese, or Korean, the input method editor can intercept keys before the game sees them. Press Win + Space and switch to the English keyboard layout before launching.
• SOCD / Snap Tap on hall-effect keyboards — boards like Wooting and Razer ship features that force opposing keys (like A and D) to cancel or override each other. Great for shooters, fatal for a rhythm game that wants both held at once. Turn off SOCD / Snap Tap / last-input-priority in your keyboard's software. Community-reported: this was the culprit in the A + D hold-note thread.
• Steam Input — In Falsus has no controller support, but an active controller config can still sit between your keyboard and the game. Steam library → In Falsus → Properties → Controller → Disable Steam Input, then relaunch.

Fix 5: A keyboard with n-key rollover (the hardware fix)

If no six-key combination on your board registers cleanly, you have hit the hardware wall. The real fix is a keyboard with NKRO: every key is scanned independently, so all six lanes register at once, every time. A 6KRO board guarantees six simultaneous keys — enough on paper for In Falsus — but matrix quirks can still block specific combinations, so NKRO is the safer buy.

The good news: NKRO is standard on most mechanical keyboards, including budget ones. Some boards only enable it over USB with a toggle (often Fn plus a function key) or in their software — check the manual. Players report the game feeling instantly fairer after switching.

Steam Deck and controller players

Ghosting is a keyboard problem, so Deck and gamepad players hit a different version of this: input that feels unreliable is usually Steam Input mapping or button latency, not rollover. In Falsus has no native controller support, so everything goes through Steam Input — and if your physical keyboard seems dead while a controller config is active, disable Steam Input as described above. Full setup notes are in our controller and Steam Deck guide.

Still stuck?

If your keyboard passes the rollover test, every software layer is off, and notes still drop, report it: post in the In Falsus Steam community discussions with your keyboard model, what you have tried, and exactly which key combinations fail. Detailed reports are what turn into patches — and the existing input threads are the best place to compare notes with players on the same hardware.

Once your inputs behave, dial in the rest of your setup: the controls guide explains the default layout and remapping flow, our keybinds and keyboard setup article goes deeper on ergonomic layouts, the hand placement guide keeps your wrists alive on long sessions, and the beginner's guide covers everything after that.