Legion Go FPS mode setup turns the original Legion Go’s detachable right TrueStrike controller into a mouse-style aiming device. It is not merely a preset for shooters: the hardware switch on the right controller changes input behavior, and Lenovo supplies a small base that positions the controller vertically. On the 8APU1, use this mode for games with mouse-and-keyboard controls, not for titles that require two XInput gamepad sticks. Follow the connection and sensitivity checks in order, then test cursor movement outside the game before adjusting in-game bindings.
Prepare the Legion Go controllers and FPS mouse base
This procedure is for Legion Go 8APU1, Type 83E1, on Windows 11. Charge the two controllers, update Legion Space through trusted Lenovo channels, and find the included right-controller mouse base. The main unit’s kickstand keeps the display visible while the controllers are detached. A level, clean tabletop or mouse mat helps the optical sensor track; reflective glass is a poor test surface.
Set up FPS mode step by step
- Close the active game and save progress. Extend the Legion Go kickstand on a stable surface; do not block the top exhaust.
- Release the right TrueStrike controller using its mechanical release button and slide it out gently. Do not force the controller sideways against the rail.
- Insert the right controller vertically into the dedicated FPS mouse base, with the bottom optical sensor oriented toward the desk. Confirm that it is seated rather than balancing loosely.
- Move the physical FPS mode switch on the bottom of the right controller to FPS. Lenovo’s user guide identifies this as the switch that enables FPS mode, so changing only an in-game preset is not equivalent.
- Open Legion Space’s controller settings and check available FPS-specific mappings or mouse sensitivity. Lenovo has noted that mouse DPI settings appear when FPS mode is actually enabled; they may not appear in ordinary gamepad mode.
- Start a game with mouse and keyboard support. Move the upright right controller to aim, use the left controller for movement where mapped, and test click/fire, reload and interact in a safe menu or training area.
- To return to handheld play, exit the game, move the hardware switch back, remove the mouse base and reattach the controller until it seats properly.
Input mapping and game compatibility
Mouse movement from the sensor is not the same as the right analog stick. Games with native mouse plus keyboard controls usually provide more direct mapping, but titles that aggressively switch their UI between controller and keyboard prompts can be awkward. If a game refuses simultaneous analog movement and mouse aim, map movement to keyboard keys or use standard dual-controller XInput instead. Check anti-cheat and game policies before running input emulators.
The RB shoulder control is identified as M1 in FPS mode on Lenovo’s original guide; do not assume every printed label means the same thing in both modes. Back buttons and wheel can be remapped where Legion Space supports it. Verify the current button map with a menu before entering a competitive match.
Fix a mouse that does not track
First look beneath the right controller to make sure the sensor is not obstructed and that the FPS switch is engaged. Change to a matte surface, then test pointer movement on the Windows desktop. If desktop movement works but the game will not respond, the issue is likely game focus, input mode, or key mapping rather than the optical hardware. If neither desktop nor game moves, reattach the controller, check charging and connection, restart Legion Space and test again.
A sudden change in aim speed often comes from multiple sensitivity multipliers: Legion Space DPI, Windows pointer settings, and the game’s own mouse sensitivity. Establish one baseline at a time and avoid changing all three simultaneously. If pointer movement is erratic only over one surface, replace the surface before resetting firmware.
FPS mode versus gyro aiming
Lenovo’s original 8APU1 user guide states that its gyro behavior settings are unavailable under FPS mode. Therefore, do not promise combined Lenovo gyro aiming and FPS optical-mouse mode in the same controller configuration. For handheld gyro aiming, switch back to normal controller mode and set gyro behavior in Legion Space or a supported game’s input system.
Map one FPS-mode game without conflicting input schemes
Start with the optical pointer working on the Windows desktop, then open one shooter that supports mouse-and-keyboard bindings. Map one left-hand movement key and one right-hand mouse action, test both in a training area, and record whether switching prompts interrupt the game. If a game forces XInput and mouse input to alternate, return to a single control scheme rather than installing an input emulator. Document the exact game, Legion Space layout and FPS switch state before making further changes.
Concrete binding check: In a game with user-editable mouse-and-keyboard controls, verify that the left-hand movement control produces forward/back/strafe input and that the detached right controller produces mouse movement and primary click. Test movement, camera, fire and menu navigation individually in a training area. Do not assume a right-stick sensitivity setting controls the optical sensor: the game can expose a separate mouse-sensitivity scale.
If prompts alternate between controller and keyboard while aiming, temporarily choose one supported scheme for that game and clear duplicate bindings only after saving the original layout. Expected result: stable cursor movement on the desktop and stable camera movement in-game without control prompts rapidly switching. If the desktop pointer fails too, investigate the FPS switch, base seating and sensor surface before editing the game’s controls.
A title that blocks simultaneous mouse and gamepad input may repeatedly switch on-screen prompts; use one consistent input scheme for the trial. Lenovo also states gyro behavior settings are unavailable in FPS mode. Do not test gyro and optical FPS mouse control as if they were the same input path, and do not repeat the hardware test in every later troubleshooting section.
Quick validation and rollback
Confirm three items: pointer moves in Windows; primary mouse clicks register; the game recognizes the chosen keyboard/mouse controls. If the first two pass but the game fails, return to the game’s input bindings. If the sensor fails everywhere, test on a different surface and restart the controller. To undo the entire configuration, turn off FPS mode and reattach the controller: the gamepad should once again present normal controller behavior.
