Debugging

From Vintage Story Wiki
Revision as of 11:54, 22 May 2020 by Tyron (talk | contribs)
Jump to navigation Jump to search

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. I recommend typing .edi once you made the screenshot. This will disable the additional debug info.
  • On just individual lag spikes, please run the command .debug logticks 20 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

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