Account or activation is not working
Sign in with the account used for your subscription. If your activation code expires, run Rivio: Connect Account again and approve the new request. Never approve a request you did not start.
Check the plan and devices on your Account page. If a payment completed but access has not updated, refresh the account page and reconnect the extension. Keep the payment receipt for support; do not send passwords or full payment details.
Studio does not connect
- Keep VS Code open on the intended workspace and grant workspace trust.
- Check that only one copy of the Rivio Studio plugin is installed. Restart Studio after replacing the plugin.
- Run Rivio: Connect Studio → Copy Connection Details and pair again from the Studio Rivio widget.
- Allow the plugin’s localhost HTTP permission. Confirm your firewall is not blocking the local connection.
- Check Rivio Output and Studio Output for the specific error.
Your assistant cannot see Rivio
Keep the intended project open in Rivio, grant workspace trust, and check your active subscription. In Explorer’s … menu beside Settings, choose Install MCP, select your client, and restart the assistant.
Setup detects Node.js 18 or newer and can prompt you to select an existing installation. If setup fails, choose View Details. If the project, Node.js, or Rivio extension folder moved, run Install MCP again.
If the endpoint did not start, run Rivio: Start MCP, then reload your assistant’s MCP servers. Approve the server if your assistant asks. Assistants using native VS Code extension tools need Rivio enabled in their tool picker instead.
When multiple Rivio windows use the same game folder, close the duplicate window and reconnect. Inspect an interrupted operation before retrying it.
An edit is missing or was overwritten
For a Rojo project, verify the correct .project.json is selected and that Rojo’s Studio plugin is connected to its server. A Rivio connection alone does not start Rojo synchronization.
Stop playtesting before making persistent Studio changes. If Rojo owns a value, edit its source rather than competing with a later sync.
If Rivio reports a source conflict, reopen or refresh the script before retrying. Inspect the latest source so you do not overwrite someone else’s change.
An asset or capture is missing
For game assets, confirm the file exists and the correct Roblox asset has been published with the right permissions. Local registration is not publication.
For playtest captures and input, check Roblox Studio’s MCP setting and the selected Studio target. Use Rivio: Bind Studio Target if similar or unsaved places cannot be distinguished.
For audio, check your ElevenLabs key, account credits, and voice access. For Blender, check the executable path and connected session.
Send a useful support report
Include your Rivio version, Windows version, the feature involved, what you expected, and the steps that reproduce the problem. Add the relevant error text and a screenshot if helpful.
Remove API keys, pairing details, passwords, private project code, and unrelated personal data. Contact Rivio using the Contact page.