[KB-018] Why is my X-Force Haptics Kit plunger not registering motion?

Product: X-Force Haptics Kit | Platform: VR (Quest) | Confidence: High

Answer:

If your X-Force Haptics Kit plunger is not registering motion, first verify the kit's independent 24V power, inline switch and SOL/ACC indicators using the power-first branch below. Working controller buttons do not prove kit power. Then check the following:

Firmware version 3.64 for the Arcade2TV-XR controller addresses USB disconnection behavior, which can cause the Meta Quest headset screen to rapidly turn on and off during use. It is also important that the firmware for the dongle is v3.43 and the firmware for the haptics PCB is version 1.8. Arcade2TV-XR controller firmware version 3.64 requires the Haptics Kit firmware to be updated to version 1.8 to ensure full system compatibility, as earlier firmware versions or partial updates may not correct a total lack of plunger response, whereas physical sticking or failure to retract requires a separate mechanical assessment as described below. download firmware V3.64 here: https://cdn.shopify.com/s/files/1/0714/3224/1434/files/Arcade2TV_Wired_Ctrl_APP_3_64.bin?v=1769595306

For the original XR with the separate Haptics Kit, support has described stepped plunger movement in Pinball FX VR as a game-input limitation. A customer reported that Haptics firmware 1.6 did not remove those steps while the physical shaft moved smoothly. There was no subsequent customer-confirmed fix. Support also suggested comparison with Pinball Classics VR or Star Wars Pinball VR through the wireless XInput path, but this thread did not include those test results. Do not call every plunger healthy from that explanation, guarantee smooth input in another title, or promise a future firmware/game fix. Compare physical motion and supported input tests for the exact mode, game and table. Plunger input functionality on the Arcade2TV-XR and X-Force Haptics Kit is dependent on the design of the specific pinball table; tables modeled after real-world machines that do not feature a physical plunger, such as Medieval Madness, will not support plunger input and instead utilize a button for ball launching. While engineering samples of the X-Force Haptics Kit may feature 3D-printed plungers, the final production units will utilize plastic-molded plungers for higher precision.

Slow pulls work but fast pulls are missed in Pinball FX VR

Scope: original Arcade2TV-XR with the separate X-Force Haptics Kit and the keyboard-style Pinball FX VR input path. Do not apply this explanation to every game, input mode or XR MAX revision.

After a matched firmware update, one customer confirmed that the previously dead plunger launched a ball with a slow pull but still missed fast pulls. Support clarified that this game's input path at that time was keyboard-style, not fully analog. A slow, smooth pull is a useful comparison test; it is not evidence of a defective plunger merely because rapid pulls are missed in this game.

  1. Record the game/table, controller, dongle, Haptics PCB versions and connection mode.
  2. Compare a slow smooth pull with a quick pull on a table that has a plunger.
  3. Compare input outside that game using the supported input test for the selected mode. If input works outside the game, report the game-specific difference.
  4. If there is no response in any supported test after the current component-matched firmware checks, contact support with those results. Do not endlessly reflash the same files or infer the exact failed part from this one symptom.

The historic update recovered basic input in this case but did not remove the fast-pull limitation. There is no confirmed future analog-update date. Use the current official component-specific guide, not old ticket version numbers, to select firmware.

Troubleshooting Steps:

For issues with the plunger not functioning in Pinball FX VR, ensure the game is updated to the latest version available on the headset.

The plunger functionality on the X-Force Haptics Kit is specifically implemented using XInput to provide analog input compatibility for pinball software; it is not currently supported in D-input mode.

To verify X-Force Haptics Kit plunger functionality on a PC via a wired USB-B connection, the controller must be set to Keyboard Mode (indicated by a red blinking light), which allows the plunger to register as mouse scrolling in a web browser; successful scrolling confirms that this wired input path is registering movement, not that the entire wireless or in-game path is healthy. To perform a hardware test of the plunger using the Gen 2 wireless dongle and a text editor on a PC, the dongle must be set to blinking red mode for the plunger pulls to register as keystrokes.

To diagnose plunger hardware issues, users should connect the Gen 2 wireless dongle to a PC in blinking purple (Pinball) mode and use the Windows Game Controller settings (joy.cpl); if the analog bar jumps or skips when pulling the plunger, it indicates a hardware issue, whereas smooth movement confirms the hardware is functioning correctly.

When troubleshooting plunger motion issues, customers may be asked to remove the plunger unit, open its casing, and provide clear photos of the two internal optical sensors for diagnosis.

Use an oscilloscope to verify that the plunger module generates square wave pulses on the blue, purple, and orange wires during actuation, which confirms the health of the optical sensors.

For advanced diagnostics, an oscilloscope can be used to observe signal waveforms, data activity, and power delivery at the plunger socket on the haptics PCB.

Plunger encoder data processing and calculation logic are handled directly on the haptics PCB; if the plunger is verified to be generating signals but the system does not respond, the haptics PCB is the likely source of the fault. When diagnosing a non-responsive plunger, if the solenoids, vibration, and physical nudge are all functioning correctly, it confirms the issue is likely a physical defect within the plunger assembly itself.

Wired scrolling works but Quest gameplay still does not

Scope: original Arcade2TV-XR and separate X-Force Haptics Kit. A customer confirmed that the USB-B/red-keyboard-mode browser-scroll test worked, yet plunger input still failed through the dongle on two Quest headsets. That observation does not by itself identify a bad plunger, a Haptics PCB fault or a headset-only problem.

Keep the wired result and test the wireless path separately. Support's next recommendation was to connect the matching wireless dongle to a PC with the supplied USB-C-to-USB-A adapter and test plunger input in its appropriate keyboard profile. A keyboard input viewer can make non-printing keys visible. Record the dongle generation, selected mode, controller/dongle/Haptics versions, exact game/table and whether the wireless PC test registers input. Disconnect controller USB-B data when testing wireless, retaining the correct power connection.

The source case has no reported result for that final wireless test and no confirmed repair. Escalate with these comparisons rather than repeating the already successful wired test or declaring a particular PCB defective.

Common Causes:

Replacement review:

Separate Quest stepped launch from a VPX hold-position problem

A customer using original XR + separate Haptics Kit on Quest 3 reported that updating controller, Haptics PCB and Gen2 dongle together still left Pinball FX VR launch strength in a few steps. Support described the game's input handling as the limitation. Do not promise another firmware update will remove those steps or reuse a historical release number as the current recommendation.

The same customer later reported a different VPX symptom: the virtual plunger kept pulling farther even while the physical plunger was held steady, in purple mode. Support recommended confirming the PC connection and VPX axis assignments, but there was no reported result. That VPX behavior was not established to have the same cause as Quest's stepped launch.

Record exact firmware/profile, VPX build/table and connection. Compare a slow pull and a held position in Windows controller Properties before changing VPX assignments. If Windows holds steady but VPX does not, report the table/mapping difference; if Windows also drifts, send the input-test observation to support. Do not declare a particular board or sensor bad from this symptom alone.

Physical sticking is different from stepped game input

Scope: original Arcade2TV-XR / Tankstick VR with the separate X-Force Haptics Kit. If the shaft physically sticks or does not spring back to rest, separate that mechanical symptom from a smooth shaft whose in-game movement is stepped.

  1. Record whether the physical shaft returns freely and whether launch input continues or fires unexpectedly while it is being pulled.
  2. Tell support which controller, dongle and Haptics PCB updates were already completed. In one reviewed case the matched updates did not remove physical binding or erratic launches; repeating the same update was not the next useful step.
  3. Stop forcing the shaft. Send a short video showing physical travel and the game response, with exact product/revision and previously tried steps. Disconnect power and cables before any support-directed internal inspection.
  4. Support can review the assembly for replacement. Do not assume a sensor, PCB or firmware defect solely from these symptoms. Confirm the applicable part, current availability and service terms with support.

A replacement in that case felt better to the customer on receipt, but had not yet been installed. Receipt and improved hand-feel are not a confirmed in-game repair. A staff suggestion to wipe the shaft also had no reported result; it is not a proven cure or permission to apply lubricant. After an approved replacement, confirm free return and repeat the affected game's launch test, reporting any remaining failure.

Flippers work but plunger and nudge are dead: check independent haptics power

Scope: original Arcade2TV-XR with the separate X-Force Haptics Kit, not XR MAX. Working controller buttons, trackball, firmware detection or flipper input do not establish that the separate kit is powered. A reviewed customer already had Haptics PCB v1.8 and working game flippers after mode correction, but no plunger/nudge and dark SOL/ACC indicators. After support pointed out the inline 24V power switch, turning it on restored operation. This was a combined correct-mode and independent-power recovery, not a firmware-only fix.

  1. Check the supplied 24V adapter connection and its inline switch; the brick's green light alone is insufficient. Observe the panel's SOL/ACC indicators. Keep the controller's appropriate data/power connections separate from the kit's 24V supply.
  2. Verify the required input mode using the actual input test, not decorative light colours. For Windows, press Windows key + R, enter joy.cpl, then open each relevant controller's Properties and identify which responds. The legacy app's missing XInput display does not prove a missing device. Use the documented Pinball/XInput path for analog plunger/nudge testing.
  3. Test plunger and nudge, then SOL control and audio-driven vibration separately. Two flipper solenoids are not the same as the four audio-driven exciters. A bass-audio test checks vibration, not every input.
  4. If the kit stays dark or input still fails, report exact versions, mode, indicator states and already-completed tests to support. Do not keep reflashing an already matched set or guess a bad PCB. Disconnect wall power and external cables before any support-directed internal connector work.

In the same history, removing the spinner path and reconnecting the trackball directly stopped reported USB disconnects before the power fix. That is a separate observation, not proof of a failed spinner or a universal wiring change. Identify the exact mixer/board and connection layout with support before applying it to another setup.

Cleaning did not improve a first-batch plunger

Physical drag or reduced rebound is not the same symptom as a missing electronic plunger axis. In one early-batch case, the customer reported that cleaning residue made almost no difference. Support discussed tighter first-batch tolerances and a later-batch replacement, explicitly without guaranteeing that a replacement would reproduce another unit's feel. The customer declined abrasive work. A replacement was arranged, but its installation and performance were not confirmed.

If cleaning has already failed, record that result rather than repeatedly prescribing it as a proven fix. Send support a short video of the physical movement and identify the unit/revision; ask about an appropriate service or replacement path. Do not infer a successful repair from a shipment or a thank-you. The historical sanding recommendation is not a general DIY procedure: no safe material-removal tolerance or validated sanding outcome was established. Disconnect power before any support-authorized internal inspection.