Checking VR support…
Quest Browser requires HTTPS. Upload this folder or ZIP's index.html to Cloudflare Pages, open its HTTPS link on your Quest 3, then choose Enter VR.
“Optical vs estimated” is only distinguishable if Quest Browser exposes emulatedPosition. Otherwise state is reported as unknown, not falsely claimed as optical.
● green = live pose ● amber = fallback ● blue = saved backswing
Attach the LEFT Quest controller securely to your WIN short bat. Use the RIGHT controller as a pointer to mark the bottom knob, then the tip. Press the free controller's trigger to record each point. The app measures the real knob-to-tip distance and aligns the virtual bat to the mounted controller. If the right controller is unavailable, use manual axis and offset settings. The right controller will never drive your swing. You can separately choose where you hold the virtual bat in Tracking setup.
Ready — enter VR before measuring.
Two-point measurement estimates the bat axis and effective length relative to the controller's tracked grip pose. It cannot guarantee exact alignment during tracking loss. Hold both controllers steady when capturing points.
Pick your hold point with the slider. In VR, enable bat placement, touch the virtual bat with the RIGHT controller, hold its trigger and move it to adjust its position. Release to keep it there; save settings to retain it. During placement, pitching pauses and trigger measurement is disabled.
Regulation preset: the pitch starts 50 ft from home plate at a 1.10 m release height, follows gravity and crosses the plate at about 0.85 m. This is a reproducible reference pitch, not every legal pitch. Actual release position, strike rules and pitch style vary by league. The batter/headset remains in a safe stationary VR play area; virtual field distance does not require walking.
50 ft from rubber to plate. Flight follows gravity; pitch apex/placement configurable.
The 50-foot field is drawn at real VR scale, but this remains a simplified reference pitch. Real league rules, measured release velocity and a calibrated ball profile still need testing.
Replay stores controller and computed virtual bat positions, not headset video. No private recording leaves the browser unless you export it. Invalid/estimated tracking is highlighted, and questionable contact is excluded from trusted reports.
Test how barrel speed, impact position, vertical offset, and bat attack angle change a hit. The same collision/flight solver is used for VR contacts. Results are model estimates, not verified real-world measurements. The original Smart/Raw/Hold tracking is preserved.
The simplified collision uses an apparent restitution with an off-sweet-spot efficiency penalty and tangential spin approximation. Flight integrates gravity, quadratic drag and a capped Magnus force. Softball coefficients are provisional, not equipment-certified. Negative launch angles strike the ground quickly.
Records appear here after physics bench simulations or tracked VR contact. Every 10 records forms a set.
In VR, occluded/emulated controller positions are marked uncertain. This report does not diagnose hitting technique or claim measured exit velocity.
Session history stays in this browser unless exported.
In VR, stand in a ready stance and glance back at the controller on your bat for about half a second. If it is tracked and near your gaze, the game records its real-world backswing position. Face the pitcher again, then make a slow practice swing at the incoming white practice ball. The swept-contact test uses estimated collision outcomes and flight; it has not been calibrated against real softball measurements. Practice pitches now originate 50 feet from home plate and follow a gravity-based arc peaking around 8 feet. This is a reference pitch, not a complete release or strike-zone simulator. You can also skip looking back and use regular tracking.
Use the settings on this page before entering VR. You can press the A or X button to manually record a new backswing; press B or Y to set your current direction as “facing the pitcher.” These buttons work only when the relevant controller is recognized and gamepad mapping permits.
Forearm warning: standard WebXR does not expose forearm/elbow tracking here. If wrist joints are available in simultaneous hand tracking, the lab uses wrist movement as an early warning. Otherwise it clearly labels its controller-motion proxy. This is not true forearm detection. This is a prototype, not a proven tracking fix. A browser does not expose the controller's raw accelerometer stream or Meta's complete forearm tracking SDK. We can stabilize and blend WebXR poses but cannot reconstruct arbitrary fast motion that was never measured.