Controller Passthrough
Basic Setup
| Step |
Action |
| 1 |
Open the input tool for your device. |
| 2 |
Refresh and select the device. Under Preferences â Other, enable Developer Mode. |
| 3 |
Enable Write to Controller Output in the input tool. |
| 4 |
Start the input tool. |
| 5 |
Open Device Monitor and confirm the IN values respond. |
| 6 |
Configure and start one destination: ViGEm Output, Titan Bridge, Makcu Bridge, or Remote Play. |
| 7 |
Confirm Device Monitor shows the expected OUT values. |
Add GPC3 Processing
| Step |
Action |
| 1 |
Turn off Write to Controller Output in the input tool so GPC 3 is the only tool producing final output. |
| 2 |
Compile and select a script in GPC 3. |
| 3 |
Optionally choose a .ipt Input Translator profile. |
| 4 |
Start GPC 3, then start the destination. |
| 5 |
Compare IN and OUT in Device Monitor to confirm the script changes. |
Common Paths
| Goal |
Source |
Destination |
| Xbox-style controller in a PC game |
XInput Input |
ViGEm Output â Xbox 360 |
| DualSense in a PC game |
DS5 Input |
ViGEm Output â Xbox 360 or DualShock 4 |
| PlayStation console output |
Any supported input |
PS Remote Play, Titan Bridge, or Makcu Bridge |
| Xbox console output |
Any supported input |
Xbox Remote Play, Titan Bridge, or Makcu Bridge |
| Keyboard/mouse conversion |
KBM Input |
GPC 3 with an Input Translator, then a supported output |
If a PC game reacts twice, it is probably seeing both the physical controller and the virtual output. Close other controller-remapping software and ensure the game uses only the intended output device.
Troubleshooting
- No IN values: refresh and reselect the physical device, then restart the input tool.
- IN moves but OUT does not: for direct passthrough, confirm Developer Mode and Write to Controller Output are enabled. For a processed path, leave direct write off and confirm GPC 3 is running.
- OUT moves but the target does not: check the destination's connection, controller type, and run status.
See Also