Guides:How to write efficient bug reports/es

Ver · EditarContenido escrito por la comunidad

El siguiente artículo fue creado por la comunidad. Puede contener material no respaldado directamente por el equipo de VRChat. Para obtener más información, considera leer contribuir a la wiki de VRChat.

Ver · EditarEsta página aún no ha sido revisada en busca de errores.

Puedes ayudar a la Wiki de VRChat corrigiéndola.
[Reason: Please proofread, and correct any errors on this page, utilizing the VRChat Wiki Manual of Style.]

Escribir y enviar informes de errores al VRChat's Feedback Board (panel de comentarios de VRChat) de manera efectiva ayudará al equipo de desarrollo a identificar el problema y evitar que vuelva a ocurrir en el futuro.

==Descripción general==

Tupper…? #Severance #VRChat #vrchatcommunity

Load video

YouTube

YouTube might collect personal data. Privacy Policy

Continue Dismiss

Short about VRChat's Feedback Board.

No puedes reportar errores directamente en VRChat, pero puedes enviar informes de errores de forma anónima en feedback.vrchat.com si tienes una cuenta de VRChat. La plataforma utiliza un sistema de tickets de Canny.io, mientras que VRChat utiliza un sistema interno separado para gestionar y dar seguimiento a los tickets.

== Glosario ==

Estos son términos que te ayudarán a entender mejor este artículo.

* Bug: Un defecto o error de software que puede crear un inconveniente al usuario. También conocido como "glitch".
* Build: La 'versión' que ejecuta el software de VRChat. Identificar el número de compilación es crucial para determinar "cuándo" se produjo el error, dentro del programa de actualizaciones constante de VRChat. Por favor, anota el número de compilación en tu informe de error. La beta abierta usa un número de compilación diferente al de la compilación del cliente "Live".
* 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."

== Versiones actuales ==

Software	Versión
VRChat	2026.2.2p1
Versión del cliente	1854
SDK de mundos	3.10.3
SDK de avatares	3.10.3
Creator Companion	2.4.5
Unity	2022.3.22f1

== Qué necesitas para informar de un error ==

=== Iniciar sesión ===
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

=== Registros y archivos adjuntos ===
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

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

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 ==== 

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

Véase también

• Open Beta
• Quality Assurance
• Reporting#Reporting a bug
• Guides:How to submit VRChat feedback

Recursos oficiales

• I found a bug/I want to report a bug on help.vrchat.com
• Where do I find my Output Logs and Crash Dumps? on help.vrchat.com

Recursos de la comunidad

• How to Write a Bug Report: Bug Reporting in Software Testing, by Vijay on www.softwaretestinghelp.com

==Referencias==