Skip to content

Have an issue? SEND YOUR DAMN LOGS

DeliciousMeatPop edited this page Aug 10, 2026 · 1 revision

How to Send Us Your Log (step-by-step)

TAKE A DAMN SCREENSHOT!

If something's broken - a game won't install, the app won't find your headset, a download keeps failing - the log file tells us exactly what happened. This page walks you through sending it. It takes about 30 seconds. For some reason people think saying "its broken" or "it's not working" and sending a phone pic of the error is enough info, its not. Its much more helpful to explain the issue in full and upload your log.

You do not need to find any files. VR CyberDeck can upload the log for you and give you a short code to paste to us. Start with Method 1.


⭐ Method 1 — Upload from inside the app (do this one)

  1. Make the problem happen first. Whatever went wrong — the failed install, the "can't find device" error — trigger it once before uploading, so it's fresh in the log. If it already just happened, you're good.
  2. Open Other Settings (the gear icon in the left sidebar in server mode, or the bottom right button above the 'Enter Server Mode" button in sideloader mode).
  3. Scroll to the Log Upload section.
  4. Click the green Upload to rentry.co button.
  5. Wait a second. You'll see "Log uploaded to rentry.co! Code copied to clipboard."
  6. A Share Code appears (something like um97vyeb) — it's already copied to your clipboard. If you want to copy it again, hit Copy Code.
  7. Paste that code to us (in the telegram / reddit / GitHub issue where you were asked). That's it. ✅

The code is all we need — we open it at rentry.co/<your-code>. You can paste either the code (um97vyeb) or the full link (rentry.co/um97vyeb). If you are on reddit only send the code, it will auto delete any post or comment with a rentry link in it!


🚑 Method 2 — The app won't even start (error screen)

If VR CyberDeck fails on launch and you're stuck on a setup/dependency error screen (no sidebar, no Settings), the same buttons are right there on that screen:

  1. On the error screen, find the log buttons near the bottom.
  2. Click Upload Log (or Open Log Folder if upload fails).
  3. Copy the code/URL it shows and paste it to us.

🛠️ Method 3 — Do it manually (if upload fails)

If the in-app upload fails (no internet, rentry down, corporate firewall), send us the file directly.

Step A — Find main.log

The easy way: in the app, Settings → Log Upload → Open Log Folder (or Open Log File). That opens the exact folder for you — grab main.log.

If you can't open the app at all, the file lives here:

OS Path (paste into your file explorer's address bar)
Windows %APPDATA%\VR CyberDeck\logs\main.log
macOS ~/Library/Application Support/VR CyberDeck/logs/main.log
Linux ~/.config/VR CyberDeck/logs/main.log

On Windows, copy %APPDATA%\VR CyberDeck\logs into the File Explorer address bar (top of the window) and press Enter — it jumps straight there. On macOS, in Finder press Cmd+Shift+G and paste the path. (If you built/ran a dev version, the folder is lowercase vr-cyberdeck instead of VR CyberDeck.)

Step B — Send it

  • Drag main.log straight into the Discord chat, or
  • Upload its contents to https://rentry.co yourself (New → paste → Save) and send us the link, or
  • Attach it to your GitHub issue.

What to actually send us

  • ✅ The rentry code or link (Method 1), or the main.log file (Method 3).
  • ✅ A one-line description of what you were doing ("installing Beat Saber, got X error").
  • ❌ You do not need screenshots of the log, retyped error text, or your whole %APPDATA% folder — just the code or the file.

"Is it safe? What's in the log?"

  • The log records what the app did: dependency setup, device detection, downloads, installs, and any errors. It's plain text — you can open main.log and read it yourself.
  • rentry pastes are unlisted (only people with the link/code can see them). If you're still not comfortable, use Method 3 and DM the file privately.

Troubleshooting the upload itself

  • "Upload failed" → use Method 3 (Open Log Folder → send main.log).
  • Nothing got copied to your clipboard → the Share Code and URL are still shown on screen; select and copy them by hand, or hit Copy Code.
  • You uploaded too early (before the error happened) → reproduce the problem, then upload again to get a fresh code.
  • The log looks huge/old → that's fine, we only read the relevant part.