Framerate and Performance: Difference between revisions

From Vintage Story Wiki
no edit summary
No edit summary
No edit summary
Line 34: Line 34:


<!--T:35-->
<!--T:35-->
1. If, in Single Player, you run into large lag spikes after some time playing you could be bottlenecked by lack of system memory (in extreme cases it can also crash with OutOfMemory exceptions, including graphics OutOfMemory issues). Vintage Story needs about 4GB-6GB of free RAM to run smoothly, plus approximately 2GB of headroom for your graphics drivers.  While the game is playable if you have 8 GB or less RAM, that may not be enough for totally smooth performance.  To help smoothness with low amounts of memory, in the game settings, try reducing view distance to 256 blocks, 192 blocks or even less and then you should be able to run the game on most systems with low RAM: it is also wise to close your web browser and all other running programs. If it's your own computer it is well worth considering purchasing more RAM, upgrading to 16GB or even 32GB or more. Buying more RAM can be a cost-effective upgrade in comparison to a new graphics card or CPU.  
1. If, in Single Player, you run into large lag spikes after some time playing you could be bottlenecked by lack of system memory (in extreme cases it can also crash with OutOfMemory exceptions, including graphics OutOfMemory issues). On Medium settings, Vintage Story needs about 4GB-6GB of free RAM to run smoothly, plus approximately 2GB of headroom for your graphics drivers.  While the game is playable if you have 8 GB or less system RAM, that may not be enough for totally smooth performance; 16 GB of system memory is recommended.  To help smoothness with low amounts of memory, in the game settings, try reducing view distance to 192 blocks or even less and then you should be able to run the game on most systems with low RAM: it is also wise to close your web browser and all other running programs. If it's your own computer it is well worth considering purchasing more RAM, upgrading to 16GB or even 32GB or more. Buying more RAM can be a cost-effective upgrade in comparison to a new graphics card or CPU.  


<!--T:23-->
<!--T:23-->
Another option is to try playing the same game in multiplayer. You can run a dedicated server on another computer on your local network (copy the save file over to it, run VintagestoryServer.exe, and connect to it using its IP address) or you can rent an online server (for example, the VintageHosting service). A multiplayer game has reduced RAM usage and reduced % CPU usage on your gaming computer.  
Another option is to try playing the same game in multiplayer. You can run a dedicated server on another computer on your local network (copy the save file over to it, run VintagestoryServer.exe, and connect to it using its IP address) or you can rent an online server (for example, the VintageHosting service) or join an existing multiplayer server. A multiplayer game has reduced RAM usage and reduced % CPU usage on your gaming computer.  


<!--T:9-->
<!--T:9-->
Line 52: Line 52:


<!--T:12-->
<!--T:12-->
4. The game supports 4k screens. Even so, the size of that screen places higher demands on the GPU and so framerates may be lower. On ultra-HD monitors, you can experiment with turning down the desktop resolution to a lower HD setting like 1920x1080. You can also keep an ultra-HD desktop resolution but use the in-game Graphics settings option for Resolution scaling, for example 50% or 75% resolution will still look good on a 4k screen, but with much less burden on the GPU - effectively it scales down the resolution of the scene for drawing purposes but then sharpens it to maintain a crisp appearance at 4k resolution.
4. The game supports 4k screens. Even so, the size of that screen places higher demands on the GPU and so framerates may be lower. On ultra-HD monitors, you can experiment with turning down the desktop resolution to a lower HD setting like 1920x1080. You can also keep an ultra-HD desktop resolution but use the in-game Graphics settings option for Resolution scaling, for example 50% or 75% resolution will still look good on a 4k screen, but with much less burden on the GPU - effectively it scales down the resolution of the scene for drawing purposes but keeps edges sharp to maintain a crisp appearance at 4k resolution.


<!--T:13-->
<!--T:13-->
5. Make sure your CPU is not overheating and therefore "thermally throttling". If you run Vintage Story with no VSync and unlimited frame rate, it will push one of your CPU cores to 100% permanently. That in turn will cause the CPU internal temperature to rise. You can monitor temperatures using a free 'Hardware Monitor' tool, or just listen to the fan noise ramping up! If the CPU internal temperature is approaching maximum allowed levels (90-100 °C on a modern CPU, that's hot enough to boil water) then the CPU should automatically switch to running slower than its maximum speed, this is "thermal throttling". This will slow down the game's performance. To prevent this thermal issue, use VSync or max frame rate limits to prevent your CPU cores reaching 100% usage - limiting the max frame rate to something sensible like 60fps or 72fps allows the system to rest for a short while between frames, and therefore reduces the chance of overheating. At unlimited frame rates GPUs can also overheat and thermally throttle, again the solution is a combination of proper cooling of the GPU, and not pushing graphics settings to their max limit.
5. Make sure your CPU is not overheating and therefore "thermally throttling". If you run Vintage Story with no VSync and unlimited frame rate, it will push one of your CPU cores to 100% permanently. That in turn will cause the CPU internal temperature to rise. You can monitor temperatures using a free 'Hardware Monitor' tool, or just listen to the fan noise ramping up! If the CPU internal temperature is approaching maximum allowed levels (90-100 °C on a modern CPU, that's hot enough to boil water) then the CPU will automatically switch to running slower than its maximum speed, this is "thermal throttling". This will slow down the game's performance. To prevent this thermal issue, use VSync or max frame rate limits to prevent your CPU cores reaching 100% usage - limiting the max frame rate to something sensible like 60fps or 72fps allows the system to rest for a short while between frames, and therefore reduces the chance of overheating. At unlimited frame rates, GPUs can also overheat and thermally throttle, again the solution is a combination of proper cooling of the GPU, and not pushing graphics settings to their max limit.


<!--T:14-->
<!--T:14-->
Line 62: Line 62:
<!--T:15-->
<!--T:15-->
''(Note that VintageStory does use multithreading for efficient performance. That is why the game runs best on a CPU with 4 cores or more. But the main rendering thread, which is one of the limits on FPS, runs on a single core.)''
''(Note that VintageStory does use multithreading for efficient performance. That is why the game runs best on a CPU with 4 cores or more. But the main rendering thread, which is one of the limits on FPS, runs on a single core.)''
<!--T:16-->
''Tip: Always make sure your PC is properly cooled (and if it's a laptop, don't rest it on a bed or couch!)  Ask yourself this: if I opened the PC case and directed a powerful desk fan into it, would I have better frame rates?  If the answer is "Yes" then you need to resolve the cooling issues before looking at other causes.''


<!--T:20-->
<!--T:20-->
6. If you experience lag spikes with no obvious cause in the game (you have a good GPU, reasonable graphics settings not too high, and plenty of RAM free) the cause could be [[Framerate_and_Performance#Causes outside Vintage Story|outside Vintage Story]]. For example, Discord seems to cause occasional lag spikes on some systems.
6. If you experience lag spikes with no obvious cause in the game (you have a good GPU, reasonable graphics settings not too high, and plenty of RAM free) the cause could be [[Framerate_and_Performance#Causes outside Vintage Story|outside Vintage Story]]. For example, Discord has been known to cause occasional lag spikes on some systems.


''Tip: You can troubleshoot the possible causes of lag spikes yourself by running the command <code>.debug logticks 50</code> and then afterwards examining the `client-main.txt` log file in VintagestoryData/Logs.''  You can ask a more experienced player or a team member for help interpreting the output.
''Tip: You can troubleshoot the possible causes of lag spikes yourself by running the command <code>.debug logticks 50</code> and then afterwards examining the `client-main.txt` log file in VintagestoryData/Logs.''  You can ask a more experienced player or a team member for help interpreting the output.
Confirmedusers, editor
348

edits