Vireo

Build a scene. Play it in the same workspace.

The Windows editor combines a Vulkan viewport, scene hierarchy, component inspectors, and asset browsing. Viewport picking synchronizes with hierarchy selection. Translate, rotate, and scale gizmos support local/world modes, snapping, and selection framing; Maya-style Alt-drag controls provide orbit, pan, and dolly navigation.

Play in Editor starts the real game from freshly cooked content, using desktop input to exercise the experience. Stop returns to the authoring state while preserving the scene, selection, unsaved edits, and undo/redo history. Cook Preview separately inspects the serialized scene that the runtime will load.

Find assets and follow their relationships.

The Content Browser presents project assets with thumbnails, search, and type categories. Meshes expose named material slots; references connect worlds, surfaces, hand sets, environments, and game-specific assets. Reference navigation moves from an assignment to the asset it uses.

The asset database tracks direct users and dependencies, supports registered asset types, and saves each library back to its source file. The editor’s “Used By” and “Depends On” inspection helps trace how content is connected before changing it.

Author reusable objects with editable component hierarchies.

Scenes store persistent actors, components, parent-child relationships, and transforms. An Actor Definition packages a reusable component tree. Instances expand that definition into the scene, while sparse overrides hold the changes made to an individual copy.

The Actor Editor isolates a definition for inspection and editing. Shared definitions keep repeated props or hand assemblies consistent, while scene overrides allow local variation. Stable IDs preserve references through the authoring and cooking process.

Build a surface with typed nodes and a fixed PBR output.

Material graphs connect scalar, color, texture, channel, blend, levels, normal-generation, and reroute nodes to a StandardPBR output. Socket types are checked, cyclic connections are rejected, and invalid rewires retain the previous valid connection.

Graphs are authoring assets. At cook time, constant expressions resolve to PBR factors and static image expressions bake to textures. The headset receives prepared material data and compressed textures; the graph editor and graph evaluator stay in the authoring pipeline.

Bring a room into the engine and shape its atmosphere.

Static GLB and OBJ worlds can carry geometry, sections, transforms, and material bindings. HDR or EXR environment maps supply diffuse irradiance and filtered specular reflections. Exposure, IBL intensity, sky visibility, and rotation control the environment.

Editable directional, point, and spot lights add direct illumination. A bounded rig supports a designated shadow caster with a focused board-local volume. Desktop and Quest share the core GGX metallic/roughness shading equations, with normal mapping, environment reflections, and tone mapping.

Coordinate motion, effects, sound, and haptics.

Animation assets define keyframed translation, rotation, scale, visibility, scalar, and color tracks. Playback supports once, loop, and ping-pong modes. Layered animation and cross-fades combine actions, with semantic animation sets resolving the clip for a particular event.

Choreography sequences bind participant roles to clips and timed events. VR Chess uses presentation profiles for moves, captures, castling, promotion, and match-ending moments. Authored effects and sound cues follow those events, while reconciliation keeps the final presentation aligned with the committed game state.

Give game events a reusable sound vocabulary.

Sound assets and semantic cue mappings connect gameplay events to recorded waves and authored sound programs. The sound-graph system defines typed control and audio connections, parameters, patches, and presets, which compile into runtime programs.

The playback systems include listener-relative positioning, attenuation, buses, mono output, and a synchronized two-stem music transport with cross-fades. VR Chess uses distinct cues for hover, grabbing, move commitment, capture, rejection, promotion, and results. Sound captions provide a visual counterpart to the game’s cues.

Connect tracked input to an authored experience.

The Quest host uses OpenXR views, controller poses, actions, and haptics. Replaceable hand meshes have material assignments and grip calibration. Interaction systems handle hover, grab, candidate targets, commit, cancellation, and tracking loss.

Spatial UI documents describe panels, text, buttons, images, grids, and progress indicators. Text measurement, wrapping, paging, and oriented-panel hit tests support readable in-world screens. VR Chess exposes larger text, color-blind-safe board highlights, reduced motion, mono audio, sound captions, and high-contrast menus.

Comfort turning, room recentering, and grab-based locomotion are implemented systems. Controller alignment, readable panel placement, comfort, and sustained frame pacing remain subject to retail-headset acceptance.

A complete game loop to exercise the engine.

VR Chess combines the engine’s room, rendering, input, presentation, audio, and UI systems. Its rules core covers legal moves, castling, en passant, all promotion choices, check, mate, stalemate, and draw conditions. Timed matches add increment, pause/resume, timeout, results, and restart.

A local opponent searches asynchronously with difficulty budgets, cancellation, and stale-position checks. Match persistence stores progress across interruptions. Move history, FEN/SAN notation, and PGN serialization keep the game record separate from its visual presentation.

Player profiles support progression, a mastery track, cosmetic collections, and an earned-points store. These project gameplay systems use reusable profile and economy services, with the store spending in-game currency.

Turn editable source content into a runtime package.

A project declares its scenes, startup state, asset libraries, and game module. Validation checks references and content contracts. Deterministic cooking prepares scene graphs, meshes, PBR records, environment lighting, animation, sound, and compressed textures; incremental caching avoids repeating unchanged work.

Publish Dev builds the prepared Quest content into an Android package. Raw authoring geometry, HDRI files, and graph layouts stay out of the runtime package. The update pipeline checks package size, hash, application ID, version, and signer before requesting Android installation.

Shared contracts between the tools and runtime.

The native engine separates reusable scene, asset, interaction, and runtime services from individual game modules. A blank project can cook without chess content. Windows tools use Qt; the runtime uses Vulkan and OpenXR, including a multiview stereo path on Quest.

Implemented systems, with acceptance boundaries kept visible.

Vireo is in active development. Its Windows editor, content pipeline, and connected gameplay systems have desktop and automated integration evidence. Retail Quest acceptance remains open for controller alignment, presentation, audio, comfort, performance under thermal load, update delivery, and longer play sessions.

Animation coverage here refers to rigid/property animation and choreography. Skeletal animation, polished visual editors for every asset family, full online play, and store readiness are not presented as finished features. Baked indirect lighting and networking foundations have implementation work, but this page does not imply complete end-to-end acceptance.