Player Guide/Reporting a Bug
From Victor Romeo Sierra Wiki
More actions
If something looks wrong mid-mission -- a stuck AI, a missing menu, a CSAR pickup that won't trigger -- you can flag it without leaving DCS.
- 1. Personal Menu -> Report a bug.
- 2. In chat you will see: "Bug #XXXXXX captured. Type details in chat; report submits 120s after your last message. Stay quiet to submit as-is."
- 3. Type whatever's useful: what you were doing, what happened, callsigns and times if relevant. Every message you send resets the 120-second timer, so you can keep adding context over several minutes.
- 4. When you stop typing for 120 seconds straight, the report posts to the #bug-report channel on Discord and you get a confirmation in chat with a short summary.
The report automatically captures your name, aircraft, position (described as "3 mi NE of Aleppo airport"), recent VRS log warnings and errors, mission time, module versions, and the current server git HEAD. You don't need to repeat any of that -- just describe the player-visible symptom.
What it does
- Captures your current state and recent in-game errors automatically.
- Opens a 120-second chat window. Type any extra detail you want included, or let it time out.
- Posts to the dedicated bug-report Discord channel with everything attached.
When to use
- Something didn't work as expected.
- You got an error message in-game.
- F10 menu missing a command.
- AI behaving strangely.
- Anything that looks off, even subtly.
What to include
- What you were trying to do.
- What happened instead.
- Roughly when (mission time is captured automatically).
The more context, the faster it gets fixed.
Notes
- One report per pilot every 5 minutes. Trigger again inside the window and chat will tell you when you can retry.
- Your chat broadcasts normally while the capture window is open -- other players can still see what you type.
- Use this for things that look broken. Balance feedback and feature requests still belong in Discord.