Support
Got a question or running into an issue? Check the docs first — most answers are there. For everything else, join the community on Discord.
Discord Community
Ask questions, share your scenes, report issues, and chat with other users and the team directly.
Join the server
Documentation
Step‑by‑step guides for OBS setup, editor shortcuts, URL parameters, and troubleshooting.
Read the docs
Bug Reports
Found something broken? Submit a bug report so we can track and fix it.
Report a bug
Feature Requests
Have an idea? Submit it and vote on what others have suggested to help shape the roadmap.
Share an idea
Common questions
The Gamepad API requires a user interaction (a click or button press) before it activates in most browsers. Open your Scene URL in a regular browser tab and press a button on your controller. Also confirm the controller is connected to the same machine that's running the Browser Source, not just the OBS machine if those are separate.
Check that your Scene URL is correct and your Scene is set as Active on your dashboard. Try pasting the URL directly into a browser to confirm it loads. In OBS, disable "local file", ensure you're using an HTTPS URL, and try "Refresh cache of current page" in the Browser Source properties.
The Scene must run on the machine the controller is plugged into. Add it as a Browser Source on that machine, then send the output to your streaming PC as a video feed via NDI, OBS Teleport, or a capture card. See the Dual‑PC setup section in the docs for details.
Consoles don't expose raw button inputs to a PC browser natively. If your controller connects to a PC via USB or Bluetooth (e.g. DualSense, Xbox), it will work fine. Reading inputs directly from a PS5 or Xbox console is not currently supported.
Shortcuts only fire when the editor canvas is in focus and you're not typing in a text field. Click anywhere in the editor canvas first. See the full keyboard shortcuts reference in the docs.