HELP CENTER · GAMING GUIDE

Gamepad & controller setup.

Pair Xbox, DualSense, Switch Pro, or any MFi controller to your phone or laptop and play PC games on the host. Native gamepad events, analog triggers, rumble, and DualSense passthrough — no extra drivers, no remapping.

Last updated 2026-05-27 4 steps · ~3 min Xbox · PlayStation · Switch Pro · MFi · 8BitDo

Remio turns your phone, tablet, or laptop into a wireless gamepad bridge for your PC. Pair a controller to the client device, connect to your host, and the game on the host detects a real-looking Xbox or PlayStation pad — analog sticks, pressure triggers, rumble, even DualSense adaptive triggers. Three minutes from unboxing the controller to a Steam game launching with the right button prompts.

Overview

A controller doesn't have to be physically plugged into the gaming PC to play games on it. Remio captures every gamepad event at the client — buttons, sticks, triggers, rumble requests — and forwards them to the host on a dedicated low-latency channel. The host then injects them as if a controller were locally connected.

On a Windows host, Remio creates a virtual Xbox 360 or DualShock controller using ViGEmBus. The game sees a real XInput or DirectInput device and detects it through whatever API it normally uses — no SDK changes, no compatibility shims, no Steam Input remapping. On a Mac host, the controller appears through the GameController framework as an MFi-style pad, which every modern Mac game supports natively.

Latency is gamepad-friendly. Input events ride a dedicated channel separate from pointer and keyboard, with no batching: under 2 ms over LAN from button press to host injection, and typically 10–30 ms over a healthy WAN connection. The gamepad path is faster than the video round-trip, so the game reacts before you see the previous frame.

Prerequisites

  • A modern controller — Xbox Wireless / Series / Elite, PlayStation DualShock 4 / DualSense, Nintendo Switch Pro, 8BitDo, or any MFi / XInput / DirectInput device.
  • Remio Client on iOS, iPadOS, Android, macOS, or Windows — latest version recommended.
  • Remio Host on a Windows 10/11 or macOS 13+ machine.
  • Bluetooth or USB-C on the client device. USB-C is always lower latency than Bluetooth when both are available.
  • (Windows host only) ViGEmBus driver — installed automatically with Remio Host on first launch.

Supported controllers

Almost every controller you'd reasonably want to game with works. Some highlights of what each model brings:

  • Xbox Wireless / Series / Elite — Bluetooth or USB-C. The reference XInput pad on Windows. All buttons, sticks, triggers, rumble, and Elite-only paddles forward correctly.
  • PlayStation DualShock 4 / DualSense — Bluetooth or USB-C. DualSense gyro, touchpad as a button, light bar, and adaptive triggers all pass through to a Windows host. macOS clients also expose the DualSense as a first-class controller.
  • Nintendo Switch Pro Controller — Bluetooth. Buttons remap to the Xbox layout on Windows hosts; the Capture and Home buttons are treated as Back and Guide.
  • 8BitDo — most modern models. Bluetooth or USB. Pro 2, Ultimate, SN30 Pro, and arcade sticks all work; mode switches on the controller still apply.
  • MFi-certified iOS controllers — Backbone, Razer Kishi, GameSir, Rotor Riot, etc. Apple's GameController framework picks them up automatically and Remio forwards everything it exposes.
  • Any XInput / DirectInput controller on Windows — if Windows sees the device, Remio Client picks it up and bridges it to the host. Wired arcade sticks, racing wheels (limited — see troubleshooting), generic USB pads all qualify.
  1. 01

    Pair the controller to your client device

    Use your client device's standard pairing flow — Remio doesn't replace it. Once the OS shows the controller as connected, Remio Client picks it up automatically.

    • iOS / iPadOS Client — Settings → Bluetooth. Put the controller in pairing mode (Xbox: hold the small sync button for 3 s; DualSense: hold PS + Share until the light bar pulses; Switch Pro: hold the sync button next to the USB-C port). Tap the controller name when it appears.
    • Android Client — Settings → Connected devices → Pair new device. Same controller-side steps as above. Galaxy devices list the controller under "Other devices".
    • macOS Client — System Settings → Bluetooth. Put the controller in pairing mode and click Connect when it appears in Nearby Devices.
    • Windows Client — Settings → Bluetooth & Devices → Add device → Bluetooth. Or plug a USB-C cable for instant connection without pairing.

    Verify the OS reports the controller as connected before opening Remio. A failed pair at the OS level can't be fixed inside Remio.

    TIP

    Wired USB-C is always lower latency than Bluetooth. If you're playing competitively over a flaky Wi-Fi connection, plug the controller in.

  2. 02

    Open Remio Client and connect to the host

    Launch Remio Client. When you connect to a host, the controller is automatically forwarded. The HUD shows a small gamepad indicator when input is flowing — solid means events are reaching the host, blinking means the controller is detected but inactive.

    You can plug or unplug controllers mid-session. Hot-add and hot-remove both work without disconnecting the stream.

    • iOS / iPadOS / macOS — controller events flow as soon as the Apple GameController framework reports the device.
    • Android — Android's InputManager picks up the controller; events are forwarded the moment the first button is pressed.
    • Windows — XInput is preferred; DirectInput devices are bridged as XInput on the host.
  3. 03

    Verify the host sees a virtual controller

    Before launching a game, do a quick sanity check on the host. This avoids spending ten minutes in a game menu debugging what turns out to be an OS-level issue.

    • Windows host — press Win + R, type joy.cpl, Enter. You should see "Xbox 360 Controller" or "Wireless Controller" listed. Click Properties → Test. Move sticks and press buttons; the test panel should respond in real time.
    • Mac host — open System Settings → Game Controllers (macOS 14+). Sticks, triggers, and buttons should all light up.
    • Both — if the controller doesn't appear here, the issue is between client and host (not the game). Skip to troubleshooting.
    # Gamepad event flow
Controller → Bluetooth/USB → Client device OS
Client OS → Remio Client captures gamepad events
Remio Client → forwards over dedicated input channel
Remio Host → injects natively:
   Windows: virtual Xbox 360 / DualShock via ViGEmBus
   macOS:   MFi-style controller via GameController framework
Game on host → reads as if controller were locally connected
Total latency: under 2 ms on LAN, 10-30 ms on WAN
  4. 04

    Launch a game and test everything

    Open the game on the host. Three quick checks:

    • Sticks — full 16-bit precision. Slow nudges should produce slow movement, not snap-to-direction. Camera control in any 3D game is the best stress test.
    • Triggers — drive a vehicle, draw a bow, modulate a weapon. Triggers should feel analog, not on/off.
    • Rumble — fire a weapon, crash into something, take damage. The controller should vibrate exactly as it would when plugged into the host directly.

    If all three work, the entire chain is healthy. If only sticks work but rumble doesn't, the controller hardware doesn't support rumble or the game isn't requesting it — not a Remio issue.

    PERFORMANCE

    Gamepad events bypass the keyboard and mouse input buffer entirely. Your stick movement reaches the host on a dedicated channel with no batching — that's why fighting-game inputs and FPS aim feel native instead of streamed.

What the host sees

The host doesn't see your real controller hardware — it sees a virtual controller created by Remio. This matters because it's why games "just work" without any special integration.

  • Windows host (ViGEmBus) — Remio installs ViGEmBus on first launch and uses it to create a virtual Xbox 360 controller for most pads, or a virtual DualShock 4 when a DualSense or DS4 is detected on an iOS client. Games read the virtual device through XInput or DirectInput exactly like a real pad.
  • Mac host (GameController framework) — Remio uses Apple's IOHID layer plus the GameController framework to register a virtual MFi controller. Mac games written for Apple Arcade or modern Steam ports detect it natively.
  • No driver shenanigans — once ViGEmBus is installed (Windows) or the GameController framework is initialized (Mac), no further setup is needed. The device looks real to every game and every diagnostic tool.

This abstraction is why Switch Pro buttons map automatically to the Xbox layout, why obscure DirectInput pads work in modern XInput-only games, and why you don't see "unknown controller" prompts.

DualSense adaptive triggers and haptics

The DualSense has features no other controller has — adaptive triggers that resist your finger, fine haptics that simulate textures, and a built-in gyroscope. Remio supports each, but with platform constraints worth knowing.

  • iOS Client → Windows Host — full DualSense passthrough. Adaptive trigger resistance commands from the game (Returnal, Death Stranding Director's Cut, Forza Horizon 5, Stellar Blade) pass straight through to the controller. Gyro aiming is forwarded as raw axis data the game can read.
  • macOS Client → Windows Host — same as above for adaptive triggers. macOS Sonoma and later expose enough of the DualSense surface for Remio to forward most of it.
  • Any Client → macOS Host — adaptive triggers are off. macOS doesn't expose adaptive trigger control to third-party apps through GameController, so Remio can't forward the command even if the game requests it. Triggers still read as analog, but they don't push back.
  • Light bar & touchpad — touchpad click works as the standard "touchpad button". Touchpad swipes and the light bar are not forwarded; if a game depends on them, plug the DualSense directly into the host.

Rumble and haptic feedback

Rumble is bidirectional. The game on the host requests rumble; Remio forwards the request back to the client; the controller hardware vibrates. The full path takes the same low-latency channel as input, so vibration starts within a frame or two of the in-game event.

  • Xbox Wireless — full rumble support including impulse triggers on Series controllers. Strong and weak motors plus the small trigger motors all activate.
  • DualShock 4 / DualSense — standard rumble plus DualSense fine haptics. The fine haptics are forwarded as PCM audio waveforms the way Sony designed them, so haptics in Astro's Playroom-style games still feel like a heartbeat instead of a buzz.
  • Switch Pro — HD rumble works on Windows hosts; Mac host support is limited because of how Apple exposes the device.
  • 8BitDo — varies by model. Pro 2 and Ultimate support rumble; older Bluetooth pads typically don't.

Up to 4 controllers — local co-op

You can pair up to 4 controllers to a single Remio Client and play local co-op on the host. The XInput limit of 4 controllers on Windows applies; macOS hosts can go higher but most games cap at 4 anyway.

Player assignment is by pairing order — the first controller paired is Player 1, the second is Player 2, etc. The HUD shows player numbers next to each gamepad indicator so you know which is which before you press start.

Couch co-op variant: each player can run Remio Client on their own phone, all connecting to the same host. Each phone's controller becomes a separate player on the host. Useful for fighting games and party titles where everyone wants their own screen.

Latency optimization for gaming

Default settings are tuned for fast feedback, but a few choices push latency even lower for fighting games, rhythm games, or competitive shooters.

  • Wired controller — USB-C beats Bluetooth every time. 1–2 ms vs 5–8 ms at the controller-to-client hop.
  • 5 GHz Wi-Fi to the client — 2.4 GHz Wi-Fi shares spectrum with most Bluetooth controllers and microwaves. The interference shows up as input stutter.
  • Ethernet to the host — wire the host PC if possible. Eliminates uplink jitter from the host side.
  • Low-latency mode in client settings — Settings → Streaming → Low latency. Disables a buffer frame at the cost of slightly more bitrate variance.
  • Direct LAN connection — when client and host are on the same network, Remio uses a direct peer-to-peer path that doesn't touch the public internet. See direct LAN connection.

Troubleshooting

  • Controller pairs to phone but game doesn't see it — the host game must use a standard controller API. Modern Steam, Game Pass, and Epic titles all do. Some indie and older games sniff the USB device directly; for those, plug the controller into the host PC, not the phone.
  • Triggers feel binary instead of pressure sensitive — check the host game's settings; some shooters have an option for "analog triggers" that defaults off. Also confirm Settings → Gamepad → Analog Trigger Precision in Remio Client is set to High.
  • Rumble doesn't work — confirm both the controller hardware supports rumble and the game has rumble enabled. Some PC ports of console games disable rumble by default; check graphics or input settings for a toggle.
  • Wrong button prompts shown (Xbox glyphs on a PlayStation pad) — most modern Steam games auto-detect the underlying controller and switch glyphs. If not, set the controller layout manually in the game options. This is a per-game setting, not a Remio setting.
  • Stick drift only over Remio (not on host directly) — your client device's gamepad driver is forwarding noisy input. Update the client OS to the latest version; on Android, raise Settings → Gamepad → Stick Deadzone slightly.
  • Switch Pro disconnects after a few minutes — older firmwares have aggressive sleep behavior over Bluetooth. Update the controller via the Nintendo Switch console once, then re-pair.
  • Racing wheel or HOTAS not detected — these usually need their own driver on the host PC (Logitech G HUB, Thrustmaster TM Hub, etc.). Remio bridges generic axes but specialized devices with force feedback need to be plugged directly into the host.
  • Controller works in one game but not another — that's an issue with the game, not Remio. Confirm the game supports controller input at all; some PC strategy titles ignore gamepad input entirely.
FREQUENTLY ASKED

Gamepad & controller FAQ

Which controllers work with Remio?

Almost every modern gamepad — Xbox Wireless / Series / Elite, PlayStation DualShock 4, PlayStation DualSense, Nintendo Switch Pro, 8BitDo (most models), and any MFi-certified iOS controller. On Windows hosts, any XInput or DirectInput device works because the controller is bridged through a virtual Xbox 360 pad.

Does the game actually see my controller on the host PC?

Yes. Remio injects gamepad events natively — on a Windows host it creates a virtual Xbox 360 or DualShock controller using ViGEmBus, so the game sees a real-looking pad and detects it through XInput or DirectInput. On a Mac host, the controller is presented through the GameController framework so any Mac game that supports an MFi pad works without changes.

Do triggers stay pressure-sensitive over Remio?

Yes. L2/R2 and LT/RT triggers are forwarded as full 16-bit analog values, not buttons. Driving games, shooters with weapon tension, and flight sims that depend on analog throttle all behave correctly.

Does rumble / haptic feedback work?

Yes, both directions. When the host game triggers rumble, Remio forwards the strong + weak motor values back to your controller. Xbox Wireless, DualShock 4, DualSense, and most 8BitDo pads vibrate exactly as they would when plugged into the host directly.

Do DualSense adaptive triggers work?

On iOS Client → Windows Host, yes — adaptive trigger resistance commands pass through as part of the DualSense passthrough so games like Returnal, Death Stranding, and Forza set the trigger tension you expect. On macOS hosts, adaptive triggers are off because macOS doesn't expose adaptive trigger control to third-party apps.

Can I use more than one controller at the same time?

Yes, up to 4 controllers — the XInput limit on Windows hosts. The first controller paired becomes Player 1, the second Player 2, and so on. Local couch co-op with friends each holding a phone works the same way.

Why does the game show Xbox button prompts when I'm using a PlayStation pad?

On Windows hosts, Remio bridges the controller as a virtual Xbox 360 pad by default — that's the standard XInput device every PC game supports. Most modern games (Steam, Game Pass titles) detect the underlying DualSense and switch to PlayStation glyphs automatically. If not, enable PlayStation prompts in the game's settings.

Headset audio through the controller — does that work?

Not over Remio. Headset audio through the controller's 3.5mm jack stays on your phone or laptop. For low-latency game audio, plug a headset directly into the host PC, or pair Bluetooth audio directly with the host. Remio's game audio still flows back to the client through the stream itself.