Join hundreds of racers just like you! We love to help answer questions and race together.


Can I Let Iracing Handle Buttons While Using Vjoy

Solve ‘can i let iracing handle buttons while using vjoy’ — iRacing drivers: quick, clear steps to fix button conflicts and restore proper controls quickly.


If you’re asking “can i let iracing handle buttons while using vjoy”, the short answer is: yes — but only if you configure devices so iRacing sees your real wheel/pad and not just the virtual vJoy device. You’re in the right place to fix conflicts fast and get buttons working again.

can i let iracing handle buttons while using vjoy

Quick answer: Yes — iRacing can manage button mappings while vJoy is installed, but iRacing must detect the physical device you want it to handle. If vJoy sits between the hardware and the sim as the active input, iRacing will see vJoy, not your wheel. Change device order or disable vJoy for buttons so iRacing can handle them directly.

What’s really going on

vJoy is a virtual joystick driver that apps use to inject inputs or merge devices. It doesn’t map buttons by itself; it presents a virtual device to Windows. iRacing lists any input device Windows exposes. If vJoy is the only device providing the button signals, iRacing can only map those vJoy buttons. That creates confusion when you expect iRacing to handle your wheel or button box directly.

Symptoms:

  • Buttons don’t show under the correct device in iRacing.
  • Button presses feel “double” or unresponsive.
  • External apps (macros, launchers) were using vJoy and changed routing.

Step-by-step fix

  1. Check Windows Game Controllers: open “Set up USB game controllers” and confirm your physical wheel/button box appears and responds.
  2. Disable vJoy temporarily: open the vJoy configuration or device manager and disable the virtual device so Windows and iRacing only see the real hardware.
  3. Start iRacing and go to Options → Controls → Calibrate Devices. Make sure iRacing lists your physical device and map buttons there.
  4. If you need vJoy for another app, enable it after mapping and use a tool (like vJoy feeder or UCR) to route only the inputs you want into vJoy — leave button inputs for the physical device.
  5. Save your control profile in iRacing and test in a practice session. If buttons still misbehave, repeat with vJoy disabled to confirm device mapping is correct.

Extra tips / checklist

  • Always map buttons in iRacing while vJoy is disabled to avoid accidental assignment to the virtual device.
  • If you use middleware (UCR, vJoy feeder), document each routed input so you can troubleshoot quickly.
  • Use Device Manager to rename or identify devices; identical names confuse iRacing.
  • Restart iRacing after changing device status — the sim caches device lists.
  • If a third-party app needs vJoy, prefer routing non-button signals (like telemetry or blends) through vJoy and keep buttons native.

FAQs

Q: Will disabling vJoy break other apps I use? A: It can. Disable vJoy only for mapping and testing, then re-enable and selectively route inputs if needed.

Q: Can iRacing map buttons from a vJoy device? A: Yes. iRacing will map whatever Windows exposes. But mapping to the virtual device makes troubleshooting harder.

Q: My buttons double-trigger after enabling vJoy. What now? A: Likely both physical and virtual devices send the same input. Disable vJoy, remap in iRacing, then reintroduce vJoy with careful routing.

Q: Do I need special software to split inputs between vJoy and my wheel? A: Tools like UCR or vJoy feeder let you control which signals go into the virtual device. Use them to prevent button collisions.

Wrap-up

You can let iRacing handle buttons while using vJoy, but only if iRacing sees the correct device. Disable vJoy to map buttons, then re-enable it with selective routing if necessary. Test in practice laps and keep a saved control profile so you can recover quickly.