Extended Reality (XR)
Holograms & Experiential
Digital Twins, BIM & AI
Industrial & Vocational Simulators
EHS Safety VR Modules
Defense, Medical & EdTech Labs
Case studies
Solutions · Extended reality
Culenz builds custom virtual reality software for training, sales and live events across India and Dubai. We develop in Unity and Unreal Engine, test every build on the headset you will use, and hand over an installable build. Clients include BMW Motorrad and Audi India.
01 — Definition
Virtual reality software development is building interactive 3D applications that run on a head-mounted display (HMD). The software tracks the user's head and hands, then redraws the scene for both eyes many times per second. Done well, users feel present in the space and remember it.
Done poorly, they feel sick within minutes. Most of our engineering effort goes into preventing that.
02 — Under the hood
A headset running at 90 Hz must draw a new frame every 11.1 milliseconds, for both eyes. We build in Unity or Unreal Engine and profile on the target headset, not just a desktop PC. If a scene misses the budget, we simplify geometry, lighting or effects until it holds.
72 Hz = 13.9 ms · 90 Hz = 11.1 ms · 120 Hz = 8.3 ms per frame
Six degrees of freedom (6DoF) tracking follows head position and rotation, so users can lean, crouch and walk. Three degrees of freedom (3DoF) tracks rotation only, which suits seated 360° video. Comfort research commonly cites motion-to-photon latency under 20 milliseconds as the target.
6DoF: position + rotation · 3DoF: rotation only
Field of view (FOV) is how much of the scene users see at once, roughly 90° to 110° on current standalone headsets. We size text and controls for that view, so labels stay readable without leaning in. Meta Quest 3 supports refresh rates from 72 Hz to 120 Hz.
FOV · pixels per degree · refresh rate (Hz)
Spatial audio places each sound at its source, so users turn towards a voice or alarm naturally. Haptic feedback adds controller vibration when users touch, grab or press something. Together they confirm each action, which matters most in training.
Positional audio · controller haptics
Standalone builds install on headsets such as Meta Quest 3 and run without a PC. PC VR builds run on a workstation for the highest visual detail. WebXR builds open from a browser link, with no app store or install.
Android APK (Quest) · Windows PC VR · WebXR
03 — Compare formats
Each format trades visual detail against setup effort. Pick the one that matches where and how people will use it.
| Format | Movement | Visual detail | Setup per user | Best for | Not right when |
|---|---|---|---|---|---|
| Standalone headset | 6DoF | Good, limited by a mobile chip | Put on the headset | Training rooms, sales offices, roadshows | You need photoreal detail across a large scene |
| PC VR | 6DoF | Highest | Headset tethered to a workstation | Showrooms, design reviews, flagship installs | Users must move between locations |
| WebXR (browser) | 6DoF on headsets; touch or mouse elsewhere | Moderate | Open a link | Campaigns, remote buyers, quick access | Scenes are heavy or must work offline |
| 360° video | 3DoF | Real filmed footage | Phone, browser or headset | Live events, real places, tours | Users must interact or move freely |
04 — Delivery & testing
We agree goals, audience, target headset and success measures in writing.
Signed scope document
We block out every scene in simple shapes, and you try them in the headset.
You approve scale, layout and flow
Artists and developers add final models, lighting, audio and interactions.
Frame time within budget on the target device
First-time users try the build while we watch for confusion and discomfort. Usability research shows five test users uncover most problems.
No forced camera motion; tasks finished without help
We install the build, configure the headsets and train your staff to run it.
Signed acceptance checklist
05 — Production case study
06 — FAQs
The cost of a VR app is driven by 3D content, interactivity and target devices. Reusing your existing CAD or BIM models lowers cost, and so does targeting one headset model. Culenz prices each project after a free scoping call, listing content, devices and support as separate lines.
We develop mainly for standalone headsets such as Meta Quest 3, plus PC VR headsets for fixed stations. Browser-based WebXR builds cover users without headsets. We choose the device during scoping, based on where the experience runs, how many people use it and your budget.
We use both engines: Unity suits standalone headsets and projects that need fast iteration on mobile chips. Unreal Engine suits photoreal architecture and product visuals on PC VR. We pick the engine during scoping and explain why, because switching engines mid-project costs time and budget.
Ownership is set in the contract before work starts. Clients typically choose between a full transfer of source and assets, or a licence to use the finished build. Ask for the terms you need on the scoping call, and we will write them into the scope.
VR training works best alongside classroom sessions, not instead of them. Use VR for tasks that are dangerous, expensive or rare to practise in real life. A 2020 PwC study found VR learners trained up to four times faster than classroom learners on soft-skills courses.
Yes, we design kiosk-style builds that start from a single button and reset for the next user. Before handover, we train your staff to clean, charge and restart the headsets. Remote support and annual maintenance can be added when an installation runs for many months.
Book a free demo and see what Culenz can build for you.