Confirmedusers
13,514
edits
Debugging: Difference between revisions
From Vintage Story Wiki
Marked this version for translation
Mirotworez (talk | contribs) (add translate tag) |
Mirotworez (talk | contribs) (Marked this version for translation) |
||
| Line 1: | Line 1: | ||
<languages/><translate> | <languages/><translate> | ||
<!--T:1--> | |||
{{GameVersion|1.15}} | {{GameVersion|1.15}} | ||
<!--T:2--> | |||
Some info on how to track down issues. For players and modders alike. | Some info on how to track down issues. For players and modders alike. | ||
<!--T:3--> | |||
__TOC__ | __TOC__ | ||
== Debugging performance issues == | == Debugging performance issues == <!--T:4--> | ||
<!--T:5--> | |||
If you want to report a vanilla game performance issue, please supply the following info | If you want to report a vanilla game performance issue, please supply the following info | ||
<!--T:6--> | |||
* The type of lag: Overally low framerate, short or long lag spikes? | * The type of lag: Overally low framerate, short or long lag spikes? | ||
* Is it Client or Server lag: | * Is it Client or Server lag: | ||
| Line 15: | Line 20: | ||
** Server lag symptoms: A disconnected icon on the top right corner, have blocks reappearing, animals not moving, broken blocks taking a while before their drops appear | ** Server lag symptoms: A disconnected icon on the top right corner, have blocks reappearing, animals not moving, broken blocks taking a while before their drops appear | ||
<!--T:7--> | |||
If its client lag | If its client lag | ||
* Whats the framerate and fps graph look like? (hit CTRL+F3 to see) | * Whats the framerate and fps graph look like? (hit CTRL+F3 to see) | ||
| Line 22: | Line 28: | ||
* 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. | * 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. | ||
<!--T:8--> | |||
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 100</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 100</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 | ||
== Improving Server Performance == | == Improving Server Performance == <!--T:9--> | ||
<!--T:10--> | |||
* Make sure the savegame is on an SSD | * Make sure the savegame is on an SSD | ||
* Make sure 2+ GB of system ram stays free | * Make sure 2+ GB of system ram stays free | ||
| Line 33: | Line 41: | ||
* in <code>servermagicnum.json</code> DefaultEntityTrackingRange = set to 3 (reduce the range at which distance creatures are still active from 128 blocks to 96 blocks) | * in <code>servermagicnum.json</code> DefaultEntityTrackingRange = set to 3 (reduce the range at which distance creatures are still active from 128 blocks to 96 blocks) | ||
<!--T:11--> | |||
{{Navbox/modding|Vintage Story}} | {{Navbox/modding|Vintage Story}} | ||
</translate> | </translate> | ||
