rubyvision
Dashboard

Setup & troubleshooting

Start here on your first launch, or jump to the issue you are seeing.

Your first session

  1. Sign in to the dashboard, download your Ruby loader, and run it once.
  2. Finish browser pairing and keep Ruby open while it prepares your PC. Approve the driver installer if prompted.
  3. Required: open Fortnite and copy its settings from the setup video below. Ruby won't work without them.
  4. Open Fortnite. Capture starts automatically once Ruby is ready; the dashboard unlocks when it does.

Returning user? Launch the same loader, and open Fortnite. Your settings and cached engine are saved.

Required setup video. Ruby won't work until your Fortnite settings match it. It also plays inside the dashboard while Ruby is setting up.

It does not work on the first launch

  1. Check the setup message first. Downloads and the first engine build can take several minutes. Keep Ruby open while progress is changing; later launches reuse the saved files.
  2. Approve the Windows driver installer prompt if it appears. Check the taskbar if you cannot see it. If installation asks for a restart, restart Windows before trying again.
  3. Once setup is ready, open Fortnite with the required settings from the setup video, and Ruby starts capturing on its own. A capture failure retries automatically without restarting Ruby.
  4. If the app remains unresponsive, use Close desktop app, wait for it to exit, and run the Ruby loader again. If the website cannot reach it, end the Ruby Vision process in Windows Task Manager, then launch the loader once; capture starts again automatically.

Gateway timeout or desktop app not connected

  1. Not connected means the website cannot currently confirm the desktop connection. It does not prove the desktop process has closed.
  2. If Ruby is already open, leave it running for about a minute while it reconnects. Check your internet connection, especially after sleep or changing networks. If the website says its live status connection was lost, it reconnects automatically too.
  3. If the problem continues, reload the dashboard and check that the browser and desktop pairing use the same account. Finish any pending sign-in or pairing prompt.
  4. If a version mismatch is shown, close Ruby and run the loader to update. Download the current loader from the dashboard if prompted. Reinstalling repeatedly will not fix a server outage; report persistent failures with the exact message and time.

Capture fails or no captured frames arrive

  1. Wait until Fortnite reaches its lobby, check its settings match the setup video (required), and keep the game visible.
  2. Screen capture is built in and does not conflict with other capture tools; OBS can stay open while Ruby runs.
  3. Read the capture error on the dashboard and follow that specific instruction. Only run Ruby as administrator if the error says the game is running with higher privileges.
  4. Capture retries on its own once the cause is fixed. If it keeps failing, close Ruby, restart Fortnite, and try again with the game visible.

Capture works but aim does not move

  1. Confirm aim is enabled and check your activation key and current weapon settings in the dashboard.
  2. If the driver installation was canceled or failed, close Ruby and relaunch the loader to retry. Approve the installer prompt and restart Windows if requested.
  3. If it still fails, share the startup error with support. Avoid deleting the engine cache or resetting your linked device as a first step; neither repairs a missing controller driver.

Still stuck?

Contact support with the exact error, when it happened, your GPU, and whether this is your first launch. For crashes or fatal startup errors, paste %LOCALAPPDATA%\RubyVision\logs into File Explorer and look for last-crash.log. Only share it privately with support after checking its contents.

Return to dashboard Contact support on Discord