feat(VR): add wand pointing

[alandtse]

Summary by CodeRabbit

• New Features
  • Added wand pointing as an alternate, toggleable input method for VR overlays with wand-driven cursor and dual-stick scrolling.
  • Renamed settings section to "Input Settings" and added a Wand Pointing toggle plus thumbstick deadzone/scroll behavior.
  • Added wand-first input behavior with automatic fallback to thumbstick/cursor.
  • Added a Wand Pointing diagnostics panel showing enable state, intersection status, UVs, controller index, and ray info.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds wand-pointing support for VR overlays: new EnableWandPointing setting, wand intersection utilities, thumbstick→scroll processing, cursor mapping from wand UVs, UI/diagnostics updates, and integration into controller input flow to prefer wand-driven cursor with legacy fallback.

Changes

Cohort / File(s)	Summary
VR Feature Core src/Features/VR.h, src/Features/VR.cpp	Introduce EnableWandPointing in VR::Settings; add WandIntersectionState and wandState; new APIs ComputeWandIntersection, UpdateCursorFromWandPointing, ProcessThumbstickScroll; rename UI section to "Input Settings"; add wand diagnostics panel; adjust ProcessControllerInputForImGui to prefer wand cursor and enable dual-stick scrolling.
VR Utilities src/Utils/VRUtils.h, src/Utils/VRUtils.cpp	Add Util::ComputeWandIntersection(...) declaration and implementation to raycast controller pose against overlays and return UV coordinates.

Sequence Diagram

sequenceDiagram
    participant Controller as VR Controller
    participant Input as ProcessControllerInputForImGui
    participant Util as VR Utils
    participant Overlay as VR Overlay
    participant ImGui as ImGui IO

    Controller->>Input: provide controller state & poses
    alt EnableWandPointing == true
        Input->>Util: ComputeWandIntersection(overlayHandle, controllerIndex)
        Util->>Overlay: ComputeOverlayIntersection(rayOrigin, rayDir)
        Overlay-->>Util: intersection result + UVs
        Util-->>Input: intersection true + UV
        Input->>ImGui: UpdateCursorFromWandPointing() (set io.MousePos, events)
    else
        Input->>Input: ProcessThumbstickScroll() -> accumulate + emit mouse wheel / cursor moves
        Input->>ImGui: emit traditional cursor/scroll events
    end
    ImGui-->>Controller: interaction feedback (click/hover)

Loading

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Suggested reviewers

• doodlum

Poem

🐰 I am a rabbit, nose aglow,

Wands now point where overlays show.
Rays find UVs, the cursor hops,
Thumbsticks whisper, diagnostics pops.
Hop—click—scroll—let interfaces grow.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 42.86% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main feature addition: wand pointing support in the VR system. It directly reflects the primary changes across all modified files.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Using provided base ref: 347b612
Using base ref: 347b612
Base commit date: 2026-01-31T21:23:57+10:00 (Saturday, January 31, 2026 09:23 PM)
No actionable suggestions for changed features.

[Copilot]

Pull request overview

This PR adds VR controller wand/ray-cast pointing functionality to allow users to point at UI overlays using their VR controllers, providing a modern and intuitive alternative to thumbstick-based cursor control.

Changes:

• Adds wand pointing utility function to compute ray-overlay intersections using OpenVR's built-in ray-casting API
• Implements wand pointing feature with automatic cursor positioning from controller ray intersections
• Refactors input handling to support both wand pointing (both controllers scroll) and traditional thumbstick control (one for cursor, one for scroll)
• Adds comprehensive diagnostics UI showing wand state, intersection status, UV coordinates, and ray geometry

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.

File	Description
src/Utils/VRUtils.h	Adds declaration and documentation for ComputeWandIntersection utility function
src/Utils/VRUtils.cpp	Implements wand pointing ray-casting logic using OpenVR's ComputeOverlayIntersection API
src/Features/VR.h	Adds wand pointing settings, state structure (WandIntersectionState), and method declarations
src/Features/VR.cpp	Implements wand pointing feature with settings UI, diagnostics display, refactored input handling, and controller-to-overlay intersection logic

[coderabbitai]

Actionable comments posted: 3

🤖 Fix all issues with AI agents

In `@src/Features/VR.cpp`:
- Around line 1966-1998: The function VR::ProcessThumbstickScroll uses static
floats scrollAccumX/Y shared across all calls, causing accumulators to bleed
between controllers; replace these static scalars with per-controller (and
per-thumbstickIndex) accumulators—e.g., a map keyed by a unique controller
identifier (use controllerState pointer/address or a controller ID field) and
thumbstickIndex—to store X/Y accumulators, update the map entries instead of the
static variables, and clear/remove the specific entry when you reset
accumulators to 0.0f so each controller/thumbstick has its own independent
scrollAccumX/Y and no cross-talk.
- Around line 2580-2642: UpdateCursorFromWandPointing can return early while
leaving wandState.isIntersecting and wandHandledCursor set, which breaks
thumbstick cursor control; whenever you return early (e.g., after checking
pointingController == vr::k_unTrackedDeviceIndexInvalid or after checking both
menuOverlayHandle and menuControllerOverlayHandle with no intersection),
explicitly reset wandState.isIntersecting = false and wandHandledCursor = false
(or the equivalent members) before returning so the cursor mode isn't left
stale; locate these changes in the UpdateCursorFromWandPointing function and
near the checks involving pointingController, menuOverlayHandle, and
menuControllerOverlayHandle.

In `@src/Utils/VRUtils.cpp`:
- Around line 298-333: ComputeWandIntersection currently indexes
poses[controllerIndex] without ensuring controllerIndex is within bounds; add a
guard that controllerIndex is != vr::k_unTrackedDeviceIndexInvalid and
controllerIndex < vr::k_unMaxTrackedDeviceCount before any access to poses (move
or duplicate the check to before the poses[] access after
GetDeviceToAbsoluteTrackingPoseCompatible), so that ComputeWandIntersection,
which uses poses and controllerIndex, returns false if the index is out of range
and avoids reading past the poses array.

[github-actions]

✅ A pre-release build is available for this PR:
Download