18-LAB / Documentation

Troubleshooting vosulay

Missing or blank overlays

Symptom What to check
Nothing appears in game Focus a supported game, clear tray → Hide vosulay, check the placement is Enabled and inside the viewport.
Installed counters are missing Run the backend separately. Verify Settings → Advanced → vosu URL and restart after changing it. Default is http://127.0.0.1:24050/.
Counter catalog reports a failure Restore backend reachability, then use the catalog's retry action.
Linux game was already running Live attachment may be restricted. Restart through the refreshed shortcut or use the documented preload/Vulkan layer. Do not weaken ptrace policy to bypass it.
Overlay broke after replacing files Keep the host, injected libraries and CEF runtime from the same complete package. Exit the host and close the game before replacing libraries.
Windows with tosu behaves incorrectly Disable tosu's In-Game Overlay; two overlay hosts in the same game are unsupported. See Windows.
A counter relying on vosu-only data stays empty with tosu tosu does not provide vosu's /websocket/v2/subscribe. Use the backend required by the counter.
A different running game was selected Selection follows game focus, not process start/enumeration order. Focus the intended supported game.

Keep overlays in view only constrains the selected placement during editing. It does not automatically relocate every off-screen counter.

Editor and input

Symptom Fix or explanation
Edit shortcut has no effect Focus the attached game; Linux shortcuts run through game input and Windows edit toggle is focus-gated. Default is Ctrl+Shift+Space.
Windows reports a hotkey registration warning Another app owns the chord. Choose a different one in Settings → Shortcuts.
Tray Edit mode is checked but input is not captured Focus the game. The request stays pending until then; selecting it again cancels it.
Editor disappears while switching windows Default focus-loss behavior ends editing. Turn off Leave edit mode when the game loses focus to retain it visually.
Input capture fails or vosulay exits Capture/heartbeat failures release input or terminate the host within the five-second safety bound. Restart vosulay if needed.
No Linux tray icon Your desktop needs StatusNotifierItem tray support.
Starting the app again exits immediately Single-instance behavior: a host is already running. Hiding is not quitting; use Exit vosulay.

Startup and saving

Remote page problems

Symptom Check
Local counters work but remote page does not A remote-port bind failure does not stop the separate in-game broker. Check logs and choose an available listener port; restart after changing it.
LAN device cannot reach a page Default listener is loopback-only. Set a LAN interface IP or 0.0.0.0, list the client's IP, restart, and use the host's actual LAN address in the URL.
Remote counters cannot reach backend data Backend permissions must allow the vosulay host, not each viewing device.
OBS/browser page is not editable The plain /overlay address is always view-only. Enable Allow editing on this computer and open http://manage.localhost:<port>/overlay on that computer, then press the edit shortcut inside the page. Load it directly, not inside another page's frame.
vosulay --toggle-edit or --quit fails Status 1 means vosulay is not running for this user, or rejected the command; --toggle-edit has no effect in --server-only mode. With the game unfocused, --toggle-edit waits for focus like the tray item.
OBS display capture contains vosulay Expected: Linux game-capture exclusion does not apply to Display Capture. Windows third-party-overlay capture settings are not a guaranteed exclusion switch.

See Remote profiles before widening listener access.

Get help

For setup questions, use Discussions → Q&A. Report reproducible bugs with the bug form, including vosulay version, OS, game/backend versions and logs.

If a counter works standalone but not in vosulay, use the counter compatibility form. cef.log is in cef-cache beside the selected configuration. Review logs and redact private URLs/paths before posting. Report security problems privately.

Sources: troubleshooting, operations, support, save-error behavior.

Edit this page on GitHub