Guides:How to write efficient bug reports: Difference between revisions

From VRChat Wiki
← Older edit
VisualWikitext
French Fox (talk | contribs)
automoderated, Community Moderators, Proofreaders
5,428 edits
Marked this version for translation
~Pausbe (talk | contribs)
Community Moderators
1,454 edits
Added guides category.
 
Line 184: Line 184:
</translate>
</translate>
<references />
<references />
[[Category:Guides{{#translation:}}]]

Latest revision as of 20:37, 5 April 2026

Other languages:
V · ECommunity-written content
The following was created by the community. It may contain material not directly endorsed by the VRChat team. To learn more, consider reading Contributing to the VRChat Wiki.
V · EThis page has yet to be proofread for errors
You can help the VRChat Wiki by proofreading it.
[Reason: Please proofread, and correct any errors on this page, utilizing the VRChat Wiki Manual of Style.]

Writing and submitting bug reports to VRChat's Feedback Board effectively, will both help the development team narrow down the problem, and prevent the problem from happening again in the future.

Overview

Thumbnail for Tupper…? #Severance #VRChat #vrchatcommunity

Tupper…? #Severance #VRChat #vrchatcommunity
Load video
YouTube
Short about VRChat's Feedback Board.[1]

You cannot report bugs directly within VRChat, but you can submit bug reports pseudonymously on feedback.vrchat.com if you have a VRChat account. The platform uses a ticketing system powered by Canny.io, while VRChat employs a separate internal system to manage and track tickets.

Glossary

These are terms that will help you understand this article better.

  • Bug: A software defect or error, that can inconvenience the user. Also can be known as a "glitch".
  • Build: The 'version' that VRChat's software is running. Identifying a build number is crucial to identifying "when" the bug took place, within VRChat's constant line-up of updates. Please write the build number in your bug report. Open Beta uses a different build number than the 'Live' client build.
  • Canny: The service that VRChat utilizes to manage their feedback. "Post it on Canny" refers to feedback.vrchat.com.
  • Debug menus: There are various menus for debugging for advanced users, including the Debug UI which can be opened within the Settings tab of the Quick Menu.
  • Hitching: An abrupt 'lag spike', or freezing momentarily when triggered by VRChat trying to process an action. Such as "VRChat hitches and lags when I open the menu, or change into another avatar".
  • Log files: A text document that is generated locally on your device, as VRChat is being used. This provides useful information to the development team, as to which code might be triggering the bug.
  • Reproduction: Also known as 'repro'. Is the ability to trigger the bug on demand, by performing an action, or a series of actions. Example: "Opening the menu triggers and reproduces the bug."

Current builds

Software Version
VRChat 2026.2.2
Client build 1853
Worlds SDK 3.10.3
Avatars SDK 3.10.3
Creator Companion 2.4.5
Unity 2022.3.22f1

What you need for a bug report

Logging in

To begin reporting a bug, please go to feedback.vrchat.com, and proceed to Log In with your VRChat account. If you do not yet have a VRChat account, please proceed to create one on the VRChat website, and optionally, link the accounts together.

Choose a topic that pertains to your bug report. Please also browse through the rest of the topic names, in case if the bug report can be submitted in a more specific thread.

  • Bug Reports: For general bug reports on primary VRChat client builds.
  • Open Beta: For any bug reports that have occurred on an Open Beta build of VRChat.
  • Website: For issues regarding any of VRChat's websites.
  • SDK Bug & Feature Requests: For problems with the VRChat SDK.
  • Creator Companion: For bug reports with the VRChat Creator Companion.

Once a topic is selected, you can search various community threads to see if another user has already posted a bug report regarding the issue. If so, it is encouraged to upvote the post, and leave a comment if any specifications are not listed. If there is not a post that is yet submitted on the issue, please begin writing a bug report.

VRChat's Debug UI

Logs and attachments

Where do I find my Output Logs and Crash Dumps? on help.vrchat.com

It is advisable to attach screenshots, or a video file (up to 8MB) of the issue to your bug report. Any screenshots showcasing the bug, or screenshots of the debug menus will be relevant towards pinpointing the bug. Attaching log files are not always required, but is considered a helpful supplement to include within the bug report.

The Debug dropdown, within the settings tab of the Quick Menu

To acquire a log file, navigate to the Settings tab within the Quick Menu, and scroll to the "Debug" dropdown. Click "Report Bug", which will mark a flagged timestamp within the output log.

PC

On PC, your file explorer will open to the folder where the output log is stored. By default, VRChat's output logs on a PC are located under %USERNAME%\AppData\LocalLow\VRChat\vrchat and named output_log_(date). Check the latest dated file, and attach it to your bug report.

Linux (via Proton)

The location of this folder depends heavily on your distribution[note 1]and how you've installed Steam.

You can usually find the Proton AppData folder for VRChat here:

~/.local/share/Steam/steamapps/compatdata/438100/pfx/drive_c/users/steamuser/AppData/LocalLow/VRChat/VRChat If you installed Steam via FlatPak, it might be here: ~/.var/app/<flatpak-app-id>/(...?)/steamapps/compatdata/438100/pfx/drive_c/users/steamuser/AppData/LocalLow/VRChat/VRChat

  1. ↑ VRChat on Linux via Proton is not directly supported unless you are using VRChat on the Steam Deck.

Meta and Oculus

To get an output log, or crash dump on a Meta device:

  1. Navigate to the Settings page of your Quick Menu
  2. Scroll down to the 'Debug' section
  3. You'll find 3 options here: Full, Errors Only or Off.

Your output logs can be found in the Documents/Logs folder located in the device root when you've connected your Quest to a PC.

Include a detailed description

A detailed bug report should include a brief description of the bug within the title of the bug report, and the build number. Within the summary, please describe the device VRChat is running on, as well as steps on how to reproduce the bug. Describe the intended result, but what had occurred instead.

An example of a good bug report, which includes a build number, description of the bug, proposed reproduction steps and observations, and an image file.

Template for reports[2]

1. Summary > Explain in 2-3 Sentence what this report is about. Include the build number. VRChat crashed when trying to join a friend on build 1XXX.

2. Steps to reproduce the bug: > Write down what you did step by step so someone else can see the problem. For example: 1. Open Main Menu 2. Visit any Profile 3. Double Click "Join" Button

3. What did you expect to happen? > Explain what you thought would happen. For example: To join my friends.

4. What actually happened? > Explain what went wrong. For example: VRChat crashed.

X. Additional details (if any): > Add any other information. For example:

  • Logs (`%appdata%\..\LocalLow\VRChat\VRChat\`, need to be uploaded external)
  • Video (can be uploaded external, such as upload on YouTube)
  • Screenshots (up to 8MB, or need to be uploaded external)
  • Links

See also

Official resources

Community resources

References

  1. ↑ Tupper…? on YouTube.
  2. ↑ What a Bug Report needs - Q&A Team StormRel
Retrieved from "https://wiki.vrchat.com/index.php?title=Guides:How_to_write_efficient_bug_reports&oldid=67386"