RetroArch Android touch, mouse, and lightgun setup / 2026-08-09

Set up RetroArch overlay mouse, lightgun, and pointer input on Android

Enable pointing input alongside overlay buttons, then separate port, trigger, gesture, core-option, and platform-touch behavior.

10 minute touch setupCurrent RetroArch overlay pointing-device behavior; core support, pointer coordinates, gestures, and physical lightgun hardware vary by package and device

Set up RetroArch overlay mouse, lightgun, and pointer input on Android

Enable `Overlay Lightgun, Mouse, and Pointer` only for a core and authorized test that needs pointing input. Choose the correct port and device type, then test cursor motion, primary trigger, off-screen behavior, and one overlay button separately. Libretro notes that this mode overrides platform-specific touchscreen controls, so turn it back off if ordinary touch navigation or a core's native touchscreen path stops working.

Do this in order

  1. 01

    Record RetroArch, core, authorized content receipt, overlay preset, selected port, core device type, orientation, and whether native touch currently works.

  2. 02

    Back up the configuration, enable overlay mouse/lightgun/pointer input, and keep every other overlay, remap, and hotkey setting unchanged.

  3. 03

    Choose mouse, lightgun, or pointer behavior for the exact core, and set the intended port rather than broadcasting a guessed input across players.

  4. 04

    Test one-finger movement, primary tap or trigger, overlay buttons, edge aiming, and the menu using a neutral screen before changing timing thresholds.

  5. 05

    If multi-touch gestures are confused, adjust long-press, double-tap, swipe, or trigger delay one value at a time; a one-frame trigger delay is the documented starting point for distinguishing touch counts.

  6. 06

    Disable the feature and restore the backup if native touchscreen input, menu control, physical controllers, or another core regresses; save only a narrow verified profile.

Decision and diagnostic table

SymptomLikely layerNext check
Cursor moves but trigger failsPort, device type, or trigger mappingVerify core input and primary tap
Overlay buttons work; pointer absentPointing feature disabled or unsupportedCheck feature and core device
Native touchscreen stops workingDocumented overrideDisable overlay pointing mode
Two-finger taps misreadGesture or trigger timingAdjust one threshold and retest

Pointer input can coexist with gamepad buttons

The feature lets an overlay send pointing coordinates while its buttons continue to emit gamepad input. Prove each path separately because a visible overlay image does not establish a working mouse or lightgun device.

The feature replaces another touch path

Libretro explicitly warns that overlay pointing input overrides platform-specific touchscreen controls. That is useful for a lightgun or mouse workflow but can be the direct cause of a regression in a core that expects native touch.

Timing distinguishes gestures

Long presses, double-tap holds, multi-finger clicks, swipes, and lightgun triggers share a small touch surface. Change one threshold only after the port and device type are correct, and keep the default or backup close for recovery.

First-party sources

Related guides