(Created page with "== Reporting Bugs == # First thing to do will be to check our [https://gitlab.com/veloren/veloren/issues gitlab issues] if this bug is already known. # If not [https://gitlab...") |
mNo edit summary |
||
Line 60: | Line 60: | ||
# Write <code>set RUST_LOG=trace&& veloren-voxygen.exe</code> and hit enter (exactly like here, without whitespace before <code>&&</code>) |
# Write <code>set RUST_LOG=trace&& veloren-voxygen.exe</code> and hit enter (exactly like here, without whitespace before <code>&&</code>) |
||
# The logs will now be printed to the CMD and the folder <code>userdata\voxygen\logs</code> or <code>%appdata%\veloren\</code>. |
# The logs will now be printed to the CMD and the folder <code>userdata\voxygen\logs</code> or <code>%appdata%\veloren\</code>. |
||
[[Category:Sysadmin]] |
Revision as of 09:39, 27 September 2022
Reporting Bugs
- First thing to do will be to check our gitlab issues if this bug is already known.
- If not create an issue with the
Bug template
and try to describe the bug as good as possible, include screenshots if needed. - Upload the log file for additional information which can help us identify the issue. See below how to get logs.
- (Note: make sure no sensitive information is included in the log files)
- Submit the issue
Tip: Incase you do not want to create an gitlab account you can join our discord
and report the bug in #bugs-and-support
.
Collect Logs
If you encounter problems with Veloren, we might ask you for logs or a trace. This tutorial shows you how to collect the logs, depending on your operating system, and the way you have installed Veloren.
By default Veloren server and Voxygen will both produce logs.
They are printed in the terminal/cmd and to a file, called voxygen.log.<todays_date>
. It even prints where the file is located to terminal/cmd:
Nov 25 01:40:14.388 INFO veloren_voxygen::logging: Setup terminal and file logging. logdir="/mnt/games/cargo-build/debug/userdata/voxygen/logs"
By default the granularity is INFO
, but please provide logs on TRACE
level (as shown below).
Search for a message called Tracing is successfully set to TRACE
to verify TRACE
level is enabled.
Linux and MacOS
Airshipper
- Start airshipper with
-vv
argument. - When the game starts it will print to the terminal the location of the log file. Check theAirshipper page.
Compiled
1. Start voxygen with TRACE
level in terminal:
RUST_LOG="trace" ./target/debug/veloren-voxygen # or RUST_LOG="trace" cargo run
2. Copy trace from terminal or the log file mentioned above.
Windows
Airshipper
- Opening a CMD.
- > On Windows press
Windows key + R
. Then typecmd
and hitenter
.
- > On Windows press
- Type
airshipper run -vv
and hit enter. - Run the game (till you encounter the problem).
- The logs should be located in
%Appdata%/airshipper/profiles/default/userdata/voxygen/logs
or check the Airshipper page.
Compiled
Git Bash
-> See Linux/Compiled above
Cmd
- Open a CMD.
- Go to your veloren folder with the
cd
command, e.g.cd C:\Users\<Your Username>\Desktop\veloren
. - Write
set RUST_LOG=trace&& veloren-voxygen.exe
and hit enter (exactly like here, without whitespace before&&
) - The logs will now be printed to the CMD and the folder
userdata\voxygen\logs
or%appdata%\veloren\
.