Difference between revisions of "Debugging"

From Vintage Story Wiki
Jump to navigation Jump to search
(One intermediate revision by the same user not shown)
Line 13: Line 13:
 
* Whats your graphics settings and what graphics card and RAM capacity do you have?
 
* Whats your graphics settings and what graphics card and RAM capacity do you have?
 
* Whats the current memory usage? How long have you been playing? Is it single player or multiplayer?
 
* Whats the current memory usage? How long have you been playing? Is it single player or multiplayer?
* Make a screenshot of the frame profiler output (hit CTRL+F10 to toggle). Before screenshotting please also type the command <code>.edi</code> to get additional frame profiler output. I recommend typing <code>.edi</code> once you made the screenshot. This will disable the additional debug info.  
+
* Make a screenshot of the frame profiler output (hit CTRL+F10 to toggle). Before screenshotting please also type the command <code>.edi</code> to get additional frame profiler output.  
* On just individual lag spikes, please run the command <code>.debug logticks 20</code> let it run for a while and then send us the client-main.txt, it's found in <code>%appdata%/VintagestoryData/Logs</code>.  Run the same command again to disable the logging
+
* On just individual lag spikes, please run the command <code>.debug logticks 20</code> if you are usually above 60 fps, or <code>.debug logticks 40</code> if you are usually above 30 fps. Let it run for a while and then send us the client-main.txt, it's found in <code>%appdata%/VintagestoryData/Logs</code>.  Run the same command again to disable the logging. Please make sure that here too, extended debug info (via <code>.edi</code>) is enabled.
  
 
If its server lag and you are the owner or on single player
 
If its server lag and you are the owner or on single player
 
* Run the command <code>/debug logticks 60</code> let it run for a while and then send us the server-main.txt, it's found in <code>%appdata%/VintagestoryData/Logs</code>.  Run the same command again to disable the logging
 
* Run the command <code>/debug logticks 60</code> let it run for a while and then send us the server-main.txt, it's found in <code>%appdata%/VintagestoryData/Logs</code>.  Run the same command again to disable the logging

Revision as of 21:45, 29 July 2020

Some info on how to track down issues. For players and modders alike.


Debugging performance issues

If you want to report a vanilla game performance issue, please supply the following info

  • The type of lag: Overally low framerate, short or long lag spikes?
  • Is it Client or Server lag: If on client the framerate will be low or the screen will be frozen. If its server lag you might get a disconnected icon on the top right corner, have blocks reappearing or animals not moving

If its client lag

  • Whats the framerate and fps graph look like? (hit CTRL+F3 to see)
  • Whats your graphics settings and what graphics card and RAM capacity do you have?
  • Whats the current memory usage? How long have you been playing? Is it single player or multiplayer?
  • Make a screenshot of the frame profiler output (hit CTRL+F10 to toggle). Before screenshotting please also type the command .edi to get additional frame profiler output.
  • On just individual lag spikes, please run the command .debug logticks 20 if you are usually above 60 fps, or .debug logticks 40 if you are usually above 30 fps. Let it run for a while and then send us the client-main.txt, it's found in %appdata%/VintagestoryData/Logs. Run the same command again to disable the logging. Please make sure that here too, extended debug info (via .edi) is enabled.

If its server lag and you are the owner or on single player

  • Run the command /debug logticks 60 let it run for a while and then send us the server-main.txt, it's found in %appdata%/VintagestoryData/Logs. Run the same command again to disable the logging