Guides

Troubleshooting

Solutions for the most common issues encountered when using VMSC.

TikTok Connection Issues

Rate Limit Errors

TikTok enforces rate limits on its LIVE API. If you see connection failures or "rate limited" messages:

  • Wait at least 30 seconds before attempting to reconnect.
  • Avoid rapidly toggling the TikTok connection on and off.
  • If using TikFinity as a bridge source, make sure only one application is connecting to TikTok at a time to avoid doubling the request rate.

Sign API Issues

VMSC relies on a signing service to authenticate with TikTok LIVE. If you see Sign API errors:

  • Check the VMSC status bar — a red indicator means the Sign API is unreachable.
  • Verify your internet connection is stable.
  • The service may be temporarily down — check the Vryionic Discord for announcements.

VRChat OSC Not Working

If OSC messages from VMSC are not reaching VRChat:

  • Enable OSC in VRChat: Open the VRChat Action Menu, go to Options > OSC > Enabled. OSC is off by default.
  • Check the port: VRChat listens on UDP port 9000 by default. Make sure VMSC is configured to send to the same port in Settings > Outputs > VRChat OSC.
  • Firewall: Windows Firewall may block UDP traffic. Add an exception for VMSC or allow traffic on port 9000.
  • Reset OSC config: In VRChat, go to Options > OSC > Reset Config. This regenerates the OSC parameter files and can fix stale mappings.
  • Verify addresses: Use the OSC Monitor widget in VMSC to confirm messages are being sent. If the monitor shows outgoing packets but VRChat is not responding, the issue is on the VRChat side.

PiShock Not Responding

If PiShock actions trigger in VMSC but nothing happens on the device:

  • API key: Verify your PiShock API key and username are entered correctly in Settings > Outputs > PiShock. Copy them fresh from the PiShock dashboard if unsure.
  • Share code: Each device requires a valid share code. Make sure the share code in your action configuration matches the one on your PiShock account.
  • WebSocket status: VMSC connects to PiShock over WebSocket. Check the connection indicator in Settings — it should show Connected.
  • Device online: The PiShock hub must be powered on, connected to WiFi, and linked to your account.
  • Intensity limits: PiShock enforces per-share-code intensity limits. If the action intensity exceeds the share code maximum, the request is silently rejected.

Overlay Blank in OBS

If your OBS browser source shows a blank page:

  • Check the URL: Open http://localhost:7890 in your regular browser. If it does not load, the VMSC overlay server is not running.
  • Check the port: The default port is 7890. If you changed it in Settings, update the URL in OBS to match.
  • VMSC must be running: The overlay server only starts when VMSC is open. Launch VMSC before starting your OBS scene.
  • Refresh the source: Right-click the browser source in OBS and select Properties, then click Refresh cache of current page.
  • See the OBS Browser Source Setup guide for detailed configuration steps.

App Won't Start

  • Antivirus interference: Windows Defender or third-party antivirus may quarantine VMSC files. Add the install directory to your exclusion list and reinstall if needed.
  • Corrupted config: Delete or rename %APPDATA%\vmsc and relaunch. VMSC will create fresh defaults. Re-import your setup from a backup afterward.
  • GPU driver crash: A Vulkan driver issue can cause a crash. Update GPU drivers, or delete %APPDATA%\vmsc\models to skip AI initialization.

Updater Fails

  • Check your internet connection — the updater downloads the new installer from the update server.
  • Antivirus may block the download. Temporarily disable real-time protection and retry.
  • If auto-update is consistently failing, download the latest installer manually from Patreon and install it over the existing installation. Your configuration is preserved.

Performance Issues

  • OSC listener frequency: Reduce the polling rate in Settings > Outputs > VRChat OSC > Listener Frequency if many parameters update rapidly.
  • Overlay complexity: Simplify layouts with many widgets or video elements, or split content across multiple overlays.
  • AI model: Disable the Gemma 3 1B model from the AI page if you are not using AI features to free VRAM.
  • Viewer database size: Export and archive old viewer records if the Viewers page becomes slow.

Common Error Messages

Error Cause Solution
EADDRINUSE :7890 Another process is using the overlay port Close the conflicting application or change the VMSC port in Settings
License validation failed Gatekeeper server unreachable or subscription expired Check internet connection and verify your Patreon subscription is active
Vulkan device not found No compatible GPU for AI features Update GPU drivers or disable AI features — everything else works without Vulkan
WebSocket connection failed Overlay or PiShock connection dropped Check internet stability and restart the affected connection from Settings
SQLITE_BUSY Viewer database locked by concurrent access Restart VMSC — this resolves most database lock issues
Still Stuck?

Join the Vryionic Discord and describe your issue in the support channel. Include the error message and your VMSC version number (found in Settings > General > About).