Debugging: Difference between revisions

From Vintage Story Wiki
(Created page with "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 supp...")
 
No edit summary
Line 10: Line 10:


If its client lag
If its client lag
* Whats the framerate? (hit CTRL+F3 to see)
* Whats the framerate and fps graph look like? (hit CTRL+F3 to see)
* Whats your graphics settings
* Whats your graphics settings and your graphics card?
* 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)
* Make a screenshot of the frame profiler output (hit CTRL+F10 to toggle)
* On just individual lag spikes, please run the command '.debug logticks 40' let it run for a while and send in the client-main.txt
* On just individual lag spikes, please run the command '.debug logticks 40' let it run for a while and send in the client-main.txt

Revision as of 14:19, 14 May 2019

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 your graphics card?
  • 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)
  • On just individual lag spikes, please run the command '.debug logticks 40' let it run for a while and send in the client-main.txt