Pinball FX VR Quest boundary and Classic-mode recovery

Confirmed Learning

Ticket 31256 produced a customer-confirmed recovery path for a specific Quest / Pinball FX VR symptom cluster:

• the Gen 2 dongle was already fast-blinking red;
• the customer could reach the in-game mode prompt;
• the scene stayed transparent / mixed-VR-like instead of settling cleanly at the table;
• the boundary grid kept reappearing or had to be dismissed manually;
• placing the Quest controllers in the deck and pressing both flippers did not recenter or start play correctly.

For that pattern, the customer reported the following sequence resolved the issue:

1. Fully power off the Meta Quest headset for about 10 seconds after play instead of leaving the previous session hanging.
2. Power off or disconnect the Gen 2 dongle during the reset as well.
3. On the next launch, if the boundary grid appears again, switch the headset to Stationary mode.
4. Stand facing the X-Arcade deck before confirming the game mode.
5. Choose X-Arcade mode when Pinball FX VR asks which control mode to use.
6. Place the Quest controllers in the holders on the X-Arcade deck and press both side flippers simultaneously.
7. On the table-mode selection screen above the backglass, choose Classic.

Following those steps, the customer said the flippers worked as intended again.

How To Reuse It

Use this when a Quest customer reports:

• persistent boundary / passthrough / transparent mixed-VR behavior in Pinball FX VR;
• failure to recenter at the table after selecting X-Arcade mode;
• flippers not taking over even though the dongle appears paired and red/blinking as expected.

Treat this as a runtime/session-reset recovery path before jumping straight to hardware replacement.

Do Not Overclaim

• This is a confirmed fix path for one customer and one symptom pattern, not proof that every flipper failure is caused by boundary state.
• Keep the earlier wireless-mode and dongle-path checks in place: USB-C-only power for wireless use, no rear USB-B data cable during Quest wireless play, and verify the dongle/controller path first.
• If the customer cannot get Quest menu/search input through the dongle at all, use the dongle-path diagnostics first instead of this runtime/boundary branch.

Evidence

The customer later explained that the issue started working again after:

• shutting off the headset and dongle to reset the session;
• changing the boundary prompt to Stationary;
• standing in front of the X-Arcade deck;
• choosing X-Arcade mode;
• placing the controllers in the holders and pressing both flippers;
• then selecting Classic from the three table-mode tiles.

Related Sources

• vault/freshdesk-runs/learnings/2026-06-11-ticket-31256-quest-input-confirms-gen2-dongle-path.md
• vault/freshdesk-runs/learnings/2026-06-12-ticket-31256-fixed-again-ask-what-solved-it.md
• vault/freshdesk-runs/cases/2026-06-10-ticket-31256-pinball-fx-vr-flippers-stopped-quest3.md