VR Command Console – Keyboard-Free Runtime Console


There’s no dedicated keyboard in a headset. ... VR Command Console fixes that. ... It works with any OpenXR headset straight away, and also with XR Interaction Toolkit or your ... Roadmap:


by LongDev


Price History +

Turn any method, property or field into a 3D button in your headset with one attribute. A radial debug menu for VR, Console and desktop.
  • Attributes: [ConsoleCommand], [ConsoleGroup], [ConsoleRange], Confirm = true
  • Parameter types: bool, enum, int/float (stepper), string options. One parameter per command.
  • Input:OpenXR controller ray + trigger via the Input System, no rig references needed
    XR Interaction Toolkit 3.x adapter (ray, poke, near-far), optional
    Custom rays: VRConsole.TrySelect(origin, direction)
    Desktop: mouse and F8
  • Summoning: triple-tap the menu button, or use hub button mode. The menu can be placed in front of the head, lazy-follow you, or attach to the wrist.
  • Pause helper: resume with any trigger pull, even when tracking is frozen
  • Optional haptics and click sounds
  • Themes as assets (Dark, High Contrast). One shader/material that works in URP, HDRP and Built-in.
  • Release builds: the runtime assembly is stripped, and the attribute API has no dependencies
  • Editor: Setup Wizard, Project Settings page, Command Browser with play-mode invoke
  • Includes: full source, two sample scenes, EditMode and PlayMode tests, documentation in Markdown and PDF
  • Requirements: Unity 2022.3 LTS or newer
    Input System (required)
    TextMeshPro essentials (imported by the Setup Wizard)
    For VR: XR Plug-in Management + OpenXR
  • Limitations: not networked; commands run on the headset that selects them. Ofcourse you can add your own networking behind it.

There’s no dedicated keyboard in a headset.

Debug actions in a VR prototype end up as hotkeys you can’t press or gestures you have to invent. VR Command Console fixes that. Add [ConsoleCommand] to a method, property or field and it appears as a button in a radial menu that you can point at, shoot, poke or click.


[ConsoleCommand("Enemies/Spawn Wave")] void SpawnWave() { ... }


Commands sort themselves into groups. Bools become toggles and enums become one button per value. Numbers get a stepper ring, and risky actions can ask “Sure?” before they run. A status line under the ring shows the result of each command.


It works with any OpenXR headset straight away, and also with XR Interaction Toolkit or your own gun or hand ray. On desktop you can test with the mouse. When you ship, the console is removed from release builds automatically and your attributes still compile.



Roadmap:

  • Nested groups
  • Favourites and recents
  • Multiple parameters per command
  • More parameter types (vector3, color, transform)

Support

Discord channel for questions and support