If the viewer says No VR headset detected, open the page directly in Meta Quest Browser. This message is expected in desktop Chrome without a connected VR headset.
| Action | Control |
|---|---|
| Move smoothly, up to 0.95 m/s | Left thumbstick, relative to your viewing direction |
| Turn 30° | Right thumbstick left/right; release it before the next turn |
| Teleport | Hold the right trigger, aim at the floor, then release. A green arc and ring mean the destination is valid; a red arc means it is blocked. |
| Return to the hallway | Hold the left Y button for one second |
| Show VR help | Hold the left X button |
| Desktop walkthrough | Click Start walking. WASD to move, mouse to look, Shift to speed up, scroll to adjust speed, Esc to release the cursor. |
VR uses your actual tracked head height and room-scale movement. Desktop eye height is 1.65 m. Walls, furniture and closed doors block stick movement and teleportation. If you physically move into a virtual obstacle, the view fades: step back or hold Y to reset. Doors are fixed in this version.
| Profile | Resolution scale | Foveation |
|---|---|---|
| Balanced | 0.90 | 0.80 |
| Performance | 0.75 | 1.00 |
| Sharpness | 1.00 | 0.50 |
Resolution changes apply the next time you enter VR. All profiles retain the original baked Beauty textures. Quest uses 256-pixel reflection cube faces, the 1024-pixel outdoor background and the existing lightweight glass settings.
The viewer requests 90 Hz when the headset supports it. Actual frame rate depends on the device and scene workload. Expand Walkthrough settings to see frame rate, draw calls, triangle count, estimated texture memory and GPU time when available. Memory estimates exclude the compositor, driver and temporary buffers.
This standalone copy uses local assets and does not include a sign-in service. Public deployment verification is recorded in the delivery report. Movement, collision, teleport and snap-turn logic were tested against the exported scene. Real Meta Quest 3 testing has not been performed. Stereo output, controller behavior, comfort and sustained 90 FPS still need to be checked in the headset.
The English version shares the same models, baked Beauty maps, UV5, textures, reflection maps and panorama as the Russian version. Localization does not change the scene or movement behavior. The original Corona scene remains unchanged.
Localization report · VR implementation report
Open the same HTTPS viewer link in Safari or Chrome. Touch controls activate automatically, or press Touch controls. Move with the left joystick and look by swiping the scene. Press Motion look to look around by turning your device. Allow motion sensors when prompted. Recenter resets the viewing reference; Swipe look returns to finger control. If motion sensors are unavailable or blocked, swipe look remains available. No camera access is required.
The optimized version is selected by default. Under Walkthrough settings → Geometry, switch between Quest — optimized and Previous version. Both use the same original Beauty textures. Measure 5 views measures fixed views in desktop/mobile mode, not headset FPS. For a real headset comparison, press Record VR metrics, enter VR, stand in the hallway and wardrobe, then exit VR and choose Download metrics. Repeat with the previous geometry. The export includes FPS, frame times, rendered triangles, draw calls, room and GPU time where supported.
Device orientation on physical phones/tablets and the optimized version on a real Quest 3 still require hardware testing. 90 FPS is a target, not a verified result.
Quest / mobile update report · Отчёт