Programming Event Logic for VR Game Levels

We program event logic for VR game levels. It's not just scripting triggers in OnTriggerEnter — it's managing narrative order, environment state, NPC reactions, and tutorial prompts in a three-dimensional space where the player can look anywhere, stand anywhere, and interact with objects in any order. A linear script breaks down by the third step: the player picked up an item before a dialogue triggered — and the system doesn't know its current state.

Why Simple Event Logic Breaks in VR

The most common problem is state serialization via boolean flags. bool doorOpened, bool npcGreeted, bool puzzleSolved in a GameManager. With 15 flags, combinatorial bugs start: the npcGreeted flag is set, but doorOpened is not, yet the player is already inside — because they walked through a wall on re-entry. Debugging this without an explicit state model is nearly impossible.

A second case is concurrent events. The player picks up a key and simultaneously steps on a door trigger. Both events fire in the same frame; OnTriggerEnter and XRGrabInteractable.SelectEntered execute in an indeterminate order. If the logic doesn't account for ordering, state desynchronizes.

A third problem is specific to VR simulators: skipping mandatory steps. The instructor designed a required sequence, but in VR the user can physically perform step 5 before step 2. We need a system that either softly blocks premature actions or adapts the scenario to the actual order of user actions.

How to Build a Fault-Tolerant Event System

The foundation is a State Machine with explicit states and transitions. Not flags, but enum LevelState { Introduction, PuzzleActive, DoorUnlocked, Completed } with methods like TryTransition(LevelState target).

For complex non-linear scenarios, we use a hierarchical State Machine or Behavior Tree:

• BehaviorDesigner or a custom BT for NPC reactions
• For overall level logic — our own LevelOrchestrator built on IEnumerator-based coroutines or UniTask

Event Bus — a central event broker. All level components publish events to the bus without knowing about each other: EventBus.Publish(new KeyPickedUpEvent(keyId)). LevelOrchestrator subscribes to relevant events and updates the State Machine. This breaks direct dependencies between Trigger components and the Orchestrator.

We implement this via event Action<T> or ScriptableObject-based EventChannel (pattern from Unite Austin 2017): [CreateAssetMenu] KeyPickedUpEventChannel : EventChannelBase<KeyPickedUpEvent>. Each EventChannel is a separate asset; references between components are wired through the Inspector — not via Find().

Checkpoint system — critical for simulators: each completed step is serialized into SessionData. On replay or resume after pause, the state is restored exactly. We save not flags, but a snapshot of the State Machine state plus a list of completed events with timestamps.

Specifics of VR Narrative

In VR, the player looks wherever they want, so the classic "narrative event in the center of the screen" doesn't work. We need mechanisms for gently directing attention:

Spatial Audio Cue: Sound emanates from a point of interest — the player naturally turns. Implemented via AudioSource with 3D spatial blend + ReverbZone.

Peripheral Attention Trigger: A bright effect (particles, light) in the peripheral field of view — more effective than an arrow UI indicator.

NPC Look At: The NPC looks at the player and starts dialogue only when the player looks at it (angle < 45°). Checked via Vector3.Dot(playerHeadForward, directionToNPC). This prevents dialogue starting "from behind."

From a specific case: in a VR fire safety trainer, the player must perform 7 evacuation steps in strict order. Initially the logic used flags — during testing, 40% of users found a way to break the scenario. After rewriting to an explicit State Machine with TryTransition(), validation of the order became part of the architecture, not a set of if-checks. Error-free completion rate rose from 55% to 89%.

Debugging and Tools

Custom Level State Viewer — an Editor Window that displays the current State Machine state in real time during Play Mode. A list of active events, transition history, pending events in the queue. Without this tool, debugging event logic is like Debug.Log() in the dark.

Event Log: all events are recorded with timestamps and stack traces into a circular buffer. When a bug occurs, immediate answer to "what happened before this?"

What’s Included in Our Work

• Designing the State Machine and state diagram
• Implementing Event Bus with subscriptions via ScriptableObject
• Integration with XR Interaction Toolkit, Unity Analytics
• Developing debugging tools (Level State Viewer, Event Log)
• Testing edge cases: parallel events, skipped steps, replay
• Scenario documentation and API for extension

Work Process

1. Scenario analysis. We dissect the level logic, identify states, events, and dependencies.
2. State Machine design. State diagram and transitions before any code.
3. Development. EventBus, Orchestrator, integration with VR components (XR Interaction Toolkit events).
4. Debugging tools. Level State Viewer, Event Log.
5. Testing. All edge cases: parallel events, skipped steps, replay.

Pricing is calculated after scenario analysis and assessment of transition logic complexity. Contact us for a project evaluation — we work turnkey, guaranteeing logic stability. Over 5 years of VR development experience and more than 15 completed projects.

VR and AR Development

When we first launch a project in a VR headset, most teams face the same thing: technically everything works, but in the headset either motion sickness occurs, or hands 'float' with a delay, or the scene looks jerky at the periphery. These are not bugs in the usual sense — they are a consequence of the fact that VR/AR development requires a different approach to render architecture, interaction, and UX from the very beginning of the project. Our experience: over 7 years in game dev, 15+ completed VR/AR projects for Meta Quest, SteamVR, PSVR2, HoloLens. We work with teams that need not just a prototype but a production‑ready application with a stable frame rate.

Platforms and SDKs

We work with all relevant stacks. We use OpenXR as the base layer wherever possible — it provides cross‑platform compatibility between Meta, Valve Index, HP Reverb and other PC VR devices. On top of OpenXR, we build on the XR Interaction Toolkit (Unity) or VR Expansion Plugin (Unreal). Contact us for a stack assessment tailored to your project.

How to minimize motion sickness in VR locomotion?

Locomotion — the main source of motion sickness for inexperienced VR users. According to research, about 70% of users experience discomfort with improper movement settings Oculus Developer Guidelines. Teleportation — standard navigation method when smooth movement is undesirable.

Components from XR Interaction Toolkit: TeleportationArea, TeleportationAnchor, TeleportationProvider. Basic implementation works out of the box, but for production we refine it in four steps:

1. Setting up XRRayInteractor with a curved ray (Bend Ray) — the teleportation arc looks more natural than a straight ray and is perceived better by users.
2. Adding a valid landing zone — a visual indicator changes color when hovering over an obstacle (red/green).
3. Implementing fade transition — smooth screen fade (black fade) before teleportation reduces disorientation.
4. Rotation snapping — after teleportation we offer snap rotation by 45° or 90° instead of smooth, reducing motion sickness risk.

For projects requiring smooth locomotion (action games, simulators), we use comfort settings: vignetting during movement, reducing FOV during acceleration. Settings are available to the user in the menu — different people have different sensitivity thresholds. The difference between kinematic and physics‑based movement: kinematic gives instant hand following but lets objects pass through walls; physics‑based via Joint provides realistic collisions but requires velocity damping and max joint force tuning. We choose based on the type of interaction.

How to make object grabbing in VR physically realistic?

This is the most underestimated part of VR development. Clients often perceive it as 'just hand animation', but in practice it is a complex system where physical correctness, responsiveness, and comfort conflict.

Grab (grabbing)

XR Interaction Toolkit provides three types of Interactable for grabbing:

• XRGrabInteractable — standard grab, object follows controller via physics joint or direct position/rotation
• XRSimpleInteractable — for objects without physical movement (buttons, levers)
• Custom Interactable by inheriting from XRBaseInteractable

Attach Transform — a frequently ignored detail. Each Interactable must have a properly configured Attach Transform (the point where the hand 'attaches'). Without it, the pistol grip will be at the center of the mesh, not where it is held.

For weapons and tools with two‑handed grab — a separate TwoHandGrab system: leading hand determines position, the second — orientation. XR Interaction Toolkit supports this via XRTwoHandGrabInteractable or custom logic with two Attach Points.

Throw (throwing)

Velocity smoothing is critical for realistic throwing because the Rigidbody.velocity at the moment of controller release reflects instantaneous speed, often incorrect due to tracking discretization. The user makes a quick wrist movement — but the object flies half as fast.

Solution: velocity smoothing over the last N frames (typically 5–10 frames, ~80–160 ms at 60 Hz) before release. XR Interaction Toolkit does this via VelocityEstimator. Additionally, we apply a velocity scaling multiplier — a small speed increase (1.2–1.5×) makes throws subjectively more satisfying. Angular velocity (for objects that should spin in flight) is also averaged similarly.

AR: Plane Tracking and Environment Interaction

AR adds a different class of problems — working with real, unpredictable environment. AR Foundation — a cross‑platform layer on top of ARKit and ARCore. Most basic features (plane detection, raycasting, image tracking, face tracking) are available through a unified API.

Plane Detection

ARPlaneManager detects horizontal and vertical planes. Practical nuances:

• Initialization takes time — the user must look around the room while the system builds a map. An explicit onboarding with instruction 'slowly move the camera across surfaces' is needed.
• Planes are unstable — their boundaries and position are updated as data accumulates. Objects placed on a plane need to be attached via parent to ARPlane, not to world coordinates.
• Plane merging — two detected floor segments may merge into one, moving the anchor. For critical anchors, use ARAnchor instead of direct attachment to the plane.

Image tracking (via ARTrackedImageManager) quality directly depends on the quality of reference images. Images with high detail frequency and contrasting edges (like a QR code but stylish) track more reliably than smooth logos. ARCore Geospatial API — for outdoor AR with real‑world coordinate binding (accuracy up to 10 cm in well‑mapped areas).

Optimization for VR: Frame Rate and Comfort

VR requires stable high frame rate. About 60% of development time in mobile VR goes to optimization, not functionality — retrofit costs twice as much as proper architecture from the first sprint.

Single Pass Instanced Rendering

The main render optimization in VR. Without it, the scene is rendered twice (once per eye), doubling draw calls. Single Pass Instanced renders both eyes in one pass via instancing: geometry is processed once, the shader gets two view/projection matrices through GPU instancing. Enabled in Unity via XR Plug-in Management > Rendering Mode: Single Pass Instanced. Important: custom shaders must support SPI — standard URP/HDRP shaders support it, custom HLSL requires modifications (UNITY_SETUP_STEREO_EYE_INDEX_POST_VERTEX and related macros). Applying this technique reduces draw calls by 40–50%, making it twice as efficient as naive double rendering.

Foveated Rendering

On Meta Quest, Fixed Foveated Rendering (FFR) is available — reducing resolution at the periphery where visual acuity is lower. Configured via OVRManager or Meta XR SDK:

OVRManager.fixedFoveatedRenderingLevel = OVRManager.FixedFoveatedRenderingLevel.High;
OVRManager.useDynamicFixedFoveatedRendering = true;

Dynamic FFR automatically increases the level when frame rate drops — more convenient than fixed in scenes with variable load.

IPD and Comfort Settings

IPD (Inter‑Pupillary Distance) — affects depth perception. At the programmable level on most devices, only reading IPD is available (OVRPlugin.GetSystemDisplayFrequency), physical adjustment is on the headset. For applications requiring precise positioning (medical simulators, training), we account for IPD in scene scale calculations.

Haptics

Haptic feedback — an underestimated tool. Even a simple vibration response when grabbing an object or hitting significantly increases the sense of presence. On average, integrating haptic patterns takes 30–80 hours per project.

XR Haptics via OpenXR:

var hapticImpulse = new UnityEngine.XR.HapticCapabilities();
InputDevice device = InputDevices.GetDeviceAtXRNode(XRNode.RightHand);
device.SendHapticImpulse(0, amplitude: 0.5f, duration: 0.1f);

For complex patterns (tactile 'texture' of a surface when touched, increasing vibration when drawing a bowstring) we use Meta Haptics Studio — allows designing haptic clips visually. This can reduce time spent on manual haptic tuning by about 30%.

What does VR/AR application development include?

When ordering a turnkey project, we provide the following deliverables:

• Architectural document with stack description, render logic, and interaction system
• Working prototype (MVP) for testing on target device
• Integration of necessary SDKs (Meta XR, OpenXR, AR Foundation, etc.)
• Optimization for target frequencies 72/90/120 Hz with draw call and FPS profiling
• Testing on physical hardware (Quest, SteamVR, HoloLens) with user involvement
• Full documentation for build, deployment, and support
• Training for the client's team (workshop on XR Toolkit)
• Warranty support for 1 month after delivery

What affects cost and timeline?

VR/AR projects are more expensive than regular games of similar scope. Iterations are slower — each fix must be tested in the headset, an emulator does not convey the real experience. Motion sickness forces reworking some conceptual decisions after the first playtest. Optimization takes a significant portion of time — for mobile VR (Quest) up to 60–70% of the cycle. For Quest projects, we start optimization from the first sprint. The cost of basic SDK integration (XR Interaction Toolkit) varies depending on the scope of custom Interactable. Typical budgets for a full Quest project range from $25,000 to $80,000 depending on complexity, number of custom interactions, and depth of optimization. Proper architectural planning from sprint one typically saves 40% on later rework compared to fixing performance bottlenecks retroactively.

Get a consultation on your project — we will assess the task, stack, and timelines. Order turnkey VR/AR application development with a guaranteed stable frame rate.