One angle I’d add to what @viajantedoceu said: sometimes the controller is actually reaching the remote system, but the app ignores it because it is running in the wrong session.
A few non-USB things to verify:
- If this is Windows, make sure the app is launched in the active console session, not a disconnected RDP session
- Check Device Manager on the VM for hidden game controllers
- Some cloud gaming apps only read controller input at startup, so plug/attach first, then launch
- Steam Input, DS4Windows, reWASD, or x360ce on the remote side can translate awkward controllers into XInput
I slightly disagree that passthrough is always the first fix. For some apps, controller emulation on the VM is cleaner than raw forwarding.
If you do need true device forwarding, FlexiHub is worth trying.
Pros:
- forwards the actual USB device
- useful for stubborn apps that need native detection
Cons:
- extra layer means more latency risk
- setup can be fiddly on locked-down cloud hosts
- not every anti-cheat or kernel-level app plays nicely with forwarded devices
Also, if this is for gaming, anti-cheat can be the real blocker, not the controller.