Arcade2TV-XR Gen2 dongle pairing and wireless mode

Useful Answer

The Gen2 wireless dongle is required for X-Force Haptics Kit features such as haptics and plunger support. The standard Tankstick VR / Arcade2TV-XR bundle normally ships with a Gen1 dongle, while every X-Force Haptics Kit includes the Gen2 dongle.

Visual identification:

Gen2 adds haptics/plunger support, VR pinball support such as Pinball Classic VR, better compatibility with third-party battery head straps such as BoboVR or Meta Elite, and independent mode switching including a dedicated Pinball FX VR mode.

Firmware compatibility matters:

A Gen2 critical firmware update can resolve Quest 3 screen flickering / flashing and forced dongle reconnects during Pinball FX VR sessions. The validated update path used all three matching components: Arcade2TV-XR controller firmware v3.64, haptics PCB firmware v1.8, and Gen2 dongle firmware v3.43V2. Run the Arcade2TV updater as administrator and only flash each firmware file to its matching component.

Use the current Arcade2TV updater, not an older copy. One resolved case found that updater v1.01.14 completed correctly, while older updater v1.01.6 could finish in only a few seconds and leave an incomplete install even if the displayed version looked correct. During each firmware flash, connect only the component being updated; leaving the controller USB connected while trying to flash the dongle can apply the wrong firmware path and cause confusing failures.

The dongles use 2.4G wireless rather than Bluetooth to keep latency low.

After any firmware update, re-pair the Gen2 dongle with the Arcade2TV-XR.

After a haptics-kit install or firmware update, a software Factory Reset can also clear stale mappings. One confirmed case had flipper buttons failing after install; pressing Factory Reset in the firmware app made the buttons register again, then installing the corrected firmware allowed stable play.

Wireless-mode checklist:

Button-hold duration matters on the Gen2 dongle. If a customer thinks the dongle is the wrong version or will not pair because the light color changes unexpectedly, have them repeat the button-hold steps carefully and watch for the intended color / blink pattern; one confirmed case was resolved when the customer realized different hold lengths cycle different colors or states.

For Meta Quest / Pinball FX VR troubleshooting, red keyboard mode on the dongle can be used as a quick trackball/cursor test before entering the game. For Pinball FX VR, set the Gen2 dongle to the required mode before launching the game. In one resolved case, the controller worked after support had the customer switch the dongle to keyboard/red mode before starting Pinball FX VR.

If Pinball FX VR stops accepting the inserted Quest controllers after a Meta controller update, re-pair the wireless dongle before replacing hardware. One resolved case recovered the white-button handshake by powering the Arcade2TV-XR only from USB-C wall power, leaving USB-B disconnected, holding the dongle side button while plugging it into the Quest, then releasing after about one second. A fast-blinking dongle LED indicates successful pairing.

For a lost or replacement dongle, slow blinking means the dongle is searching and has not paired to the controller yet. Power the Arcade2TV-XR from USB-C wall power only, keep USB-B disconnected, hold the dongle side button while plugging it into the Meta headset, then release after about one second. If it stays slow-blinking, repeat the pairing attempt. One Pinball FX VR case where the flipper buttons would not register was fixed after this replacement-dongle pairing process.

The Arcade2TV-XR wireless dongle is proprietary; do not expect an off-the-shelf Bluetooth or third-party USB receiver to pair in its place. If support sends a replacement dongle, pair it with the same side-button hold process before testing gameplay.

If a replacement dongle still stays slow-blinking, try the Quest power sequence as part of the same troubleshooting path. One confirmed customer was trying to pair while the headset was already on; the dongle was recognized after the customer connected the dongle first, then powered on the headset with the dongle attached. A full headset reboot can reset the Quest USB connection state.

For Steam Deck, the same wireless-mode rules still apply: factory reset from Keyboard Mode over USB-B if needed, then disconnect USB-B for wireless play, power the controller over USB-C only, and re-pair the Gen2 dongle after firmware changes. One customer confirmed the setup worked on Steam Deck after following this reset and re-pairing path.

For Visual Pinball X / SteamVR on PC, plug the Gen2 dongle into the PC that is actually running VPX and SteamVR. The dongle sends input only to the device it is physically plugged into; it does not forward Arcade2TV input from a Quest headset back to a PC through Steam Link, Virtual Desktop, Meta Remote Desktop, Wi-Fi, or Ethernet. If the dongle is plugged into the Quest, Quest-native games may see it, but PC VR software on another machine will not receive that input through the headset.

For other Zen pinball tables outside the native Pinball FX VR path, use the Gen2 dongle's purple / XInput mode. In that mode the controller is seen as a standard gamepad; nudge behavior may feel different because movement is translated into analog stick data rather than the native digital slap behavior.

For Meta Quest 3S audio with the haptics kit, do not plug a USB-C audio splitter into the Gen2 dongle. The USB-C port on the Gen2 dongle is for charging only and does not pass audio or data.

Correct Quest 3S connection order:

To test the haptics speakers and vibration without the Quest, plug the 3.5mm cable into a phone or PC and play music. If the VIB dial is up, the flipper-area vibration modules should respond to bass/audio.

For Meta Quest 2, the Gen2 dongle can be compatible, but the headset port layout may create a physical clearance problem when the dongle and audio cable are both needed. Workarounds:

The firmware does not need to be reinstalled after restarting a Quest headset. If the headset stops seeing the dongle after a restart or power loss:

If a Quest 3 only powers the dongle after pass-through power is briefly connected, treat it as a USB handshake/startup issue rather than proof that the dongle must always be externally powered. Reboot the headset or reconnect the dongle a few times, and attach the external battery before connecting the dongle to improve the initial handshake. Once the dongle is recognized and transmitting controller input, it is powered by the Quest headset; the pass-through port is only for headset charging.

If Arcade2TV-XR worked on Quest, then stops after the customer used the USB-B cable on a PC, first return the controller to wireless mode by disconnecting USB-B and powering the unit from USB-C wall power only. Then reboot the Meta Quest headset before plugging the dongle back in. One confirmed Quest 3 case recovered immediately after the headset reboot, even though USB-B had already been disconnected.

After firmware updates, pairing changes, or mode confusion, a full shutdown and reboot of the headset/controller path can clear stale state. One resolved haptics-kit case started working after the customer shut everything down and rebooted.

Some third-party battery straps can still show non-critical pass-through behavior even after the critical dongle update. In one confirmed Quest 3 + BoboVR M3 Pro case, the critical update fixed the screen flicker completely, but the battery strap occasionally beeped and the Quest showed slow-charging notifications after longer sessions. Support treated that remaining behavior as likely chip / hardware-level charging pass-through behavior rather than something fully controlled by firmware. If attaching a power cable to the dongle breaks the Quest connection, test connecting the power source to the dongle before plugging the dongle into the headset. Avoid heavy hanging cable strain on the dongle's USB-C male plug, because that can damage the port. A confirmed replacement-dongle case worked after the new proprietary dongle was paired normally.

One customer-reported third-party strap that worked with the Arcade2TV dongle was the KIWI design K4 Boost Battery Head Strap for Meta Quest 3 / 3S. Treat this as field feedback rather than a blanket compatibility guarantee; if a strap causes USB handshake or dongle dropouts, fall back to direct headset connection or a full headset reboot.

Source Context

One customer had firmware and wireless-mode confusion after updating the Arcade2TV-XR and Gen2 dongle. Another had no haptics-kit audio from a Quest 3S because the splitter was placed after the Gen2 dongle; support clarified that the hub must connect directly to the headset and the dongle/audio cable should connect through that hub. Quest 2 support raised the related physical-clearance issue, where a short USB-C extender or USB-C hub may be required. Later threads clarified Gen1 vs Gen2 identification, confirmed that haptics kits include Gen2, confirmed that using the included USB-C-to-USB-A dongle adapter directly into the PC allowed firmware/input detection to work, confirmed Steam Deck use after reset/re-pairing, confirmed that setting the dongle mode before launching Pinball FX VR can resolve otherwise confusing post-install behavior, clarified purple/XInput mode for other Zen tables, confirmed that downgrading a Gen1 setup back to v2.27 restored Pinball FX VR behavior after v3.x confusion, confirmed that v3.04 beta could make Zaccaria / Steam pinball work while breaking current-dongle Pinball FX VR until v2.27 was restored, confirmed that v2.28 can fix Gen1/v2.27 disconnections without requiring a Gen2/haptics firmware path, confirmed that a full shutdown/reboot can clear post-pairing haptics/Quest state and a Quest 3 no-dongle-light case after wired PC use, confirmed that Gen2 dongle button-hold timing can explain unexpected color changes during pairing, confirmed that using the current updater and isolating the component being flashed can fix bad or cross-target firmware attempts, clarified that SteamVR/VPX needs the dongle plugged into the PC rather than relayed through a Quest headset, confirmed that re-pairing the dongle fixed a post-Meta-controller-update Pinball FX VR controller insertion failure, confirmed that replacement-dongle pairing fixed Pinball FX VR flipper-button registration when the dongle had only been slow-blinking, confirmed that powering the Quest on with the replacement dongle already attached can resolve headset recognition/pairing confusion, added field feedback that the KIWI K4 Boost head strap worked with the dongle for one customer, added a customer-confirmed Quest 3 pass-through power explanation for initial dongle handshakes, confirmed that the dongle is proprietary and cannot be replaced by a generic receiver, and confirmed that the Gen2 critical update path fixed Quest 3 screen flickering while leaving some BoboVR M3 Pro slow-charging beeps as a likely pass-through hardware limitation.