We are a team of game dev engineers with 12 years of VR development experience. We have delivered over 30 projects for various platforms. Moving controls from a flat screen to VR means starting from scratch. Familiar patterns (action button, cursor, grid inventory) in virtual reality are either inconvenient, cause motion sickness, or break immersion. Good VR interaction mechanics should be obvious without a tutorial: the user reaches out and grabs an object because that is how the physical world works.
Why Grab Mechanics Fail Most Often
Object interaction is the core mechanic of most VR games, and this is where things go wrong most often. Problem number one: penetration through colliders. When a player physically reaches for an object, their hand-controller may pass through a table, wall, or the object itself. A physical collider on the hand with isKinematic = false solves this but creates another issue: the hand starts jerking when contacting surfaces due to conflict between tracking positioning and the physics engine.
The working solution we use in XR Interaction Toolkit (https://learn.microsoft.com/en-us/unity/) is to separate the visual hand (follows tracking without physics) and the physics hand (Rigidbody with collider, follows tracking position via joint). When trying to pass through an object, the physics hand stops, the visual hand continues moving—and a small discrepancy (up to 5–8 cm) remains imperceptible thanks to haptic feedback triggered at the moment of contact. This is called the phantom hand approach, and it is 2× more effective than naive hand collision in reducing clipping issues.
The second common mistake is incorrect attachment point when picking up an object. If the object snaps to the hand bone position without considering orientation, the player sees the object sticking out of the palm at an unnatural angle. In XR Interaction Toolkit, this is solved via Attach Transform on each XRGrabInteractable: a separate empty object with the correct position and rotation relative to the item, indicating exactly how the object rests in the hand.
How to Ensure Comfortable VR Locomotion?
VR locomotion is the second most challenging task in VR. Smooth stick movement causes motion sickness in a significant portion of the audience. Teleportation is safe but breaks immersion in some genres. The solution is usually hybrid.
XR Interaction Toolkit provides ready components: TeleportationProvider, SnapTurnProvider, ContinuousMoveProvider. But out of the box, they require tuning for a specific game. For shooters, smooth locomotion with vignette (peripheral darkening during movement) is usually needed—this reduces motion sickness by 40–60% according to Oculus Research. We expose the vignette intensity parameter in Comfort Settings so the player can disable it if desired.
For spatial puzzles and horror games, VR teleportation works better—it preserves tension and does not cause discomfort. Implementation uses TeleportationArea and TeleportationAnchor components, with arc visualization via XRInteractorLineVisual and TeleportationProvider on the Locomotion System.
Approach comparison: teleportation gives no motion sickness but medium immersion, smooth + vignette gives high immersion with 2.5× less motion sickness than smooth without vignette, and room-scale walking gives absolute immersion with no sickness. Teleportation is recommended for puzzles, horror, quests; smooth with vignette for shooters and simulators; room-scale for small-world action games.
An important nuance: if the player can physically walk around the room, you must account for their physical position within the Guardian/Boundary area affecting in-game position. When implementing mechanics that require precise positioning (e.g., pressing a button at a specific spot within 5 cm accuracy), you need to check not only the world coordinates of the controller but also its relative position to the camera.
What's Included in Turnkey VR Mechanics Development?
We provide a full cycle: from prototyping to integration on target platforms (SteamVR, Oculus Quest, Android XR). Each stage is accompanied by documentation and code review. Our turnkey development starts at $5,000 for basic grab and teleportation, and clients typically save 30% compared to building in-house.
- Requirements analysis: identify key mechanics, platforms, constraints (e.g., FPS budget of 72 FPS on Quest, room-scale, supported controllers).
- Prototyping: fast MVP in Unity with XR Device Simulator—without a headset—to test interaction hypotheses.
- Implementation: write core mechanics including VR grab, VR locomotion, UI in virtual reality, and VR haptic feedback. Use XR Interaction Toolkit, custom shaders, and animations.
- Testing: real headset tests with a group of 10+ users with varying motion sickness tolerance. Fix penetrations, non-intuitive grabs, and kinematic errors. We measure success by a 90% reduction in motion sickness complaints.
- Documentation: diagrams of Attach Transforms, haptic settings, rules for game designers.
- Deployment and support: build configuration for each platform, optimization of draw calls and asset streaming, source code and instructions handover.
Estimated timeline: basic VR grab + locomotion (teleportation) takes 1–2 weeks; physics grab + two-handed VR interaction takes 2–4 weeks; full mechanics set (grab + UI + locomotion + haptics) takes 4–8 weeks; custom physics interaction system takes 6–12 weeks.
Pro tip: For testing, use at least 10 people with different motion sickness tolerance levels to ensure robust results.
What Are Non-Standard Mechanics and How to Implement Them?
Two-handed VR interaction: holding a long weapon with both hands requires TwoHandedGrab with correct object orientation calculation using two attachment points. In XR Interaction Toolkit, this is implemented via TwoHandInteractionAffordance or a custom XRGrabInteractable with an overridden CalculateInteractorPosition.
VR haptic feedback as an information channel: controller vibration is not just tactility—it's feedback. Different intensity and patterns (short pulse vs. rising vibration) convey different states: picking up a light object vs. heavy, contact with a hot surface vs. cold. Through XRBaseController.SendHapticImpulse(amplitude, duration) this is implemented in a few lines, but the game designer must specify concrete parameters for each case.
UI in virtual reality: standard Canvas in Worldspace mode, interaction via XRUIInputModule instead of the standard StandaloneInputModule. Laser pointer from the controller via XRRayInteractor. The main rule: UI should be in a physically reachable zone or interacted with via ray, but must not require precision smaller than 1–2 cm—controller tracking with an extended arm has an error of up to 5–10 mm, making small buttons a pain.
Contact us to evaluate your project. We guarantee immersion and no motion sickness. Request a consultation and get a detailed development plan.