Export translations

Settings

Group

Language

Format

Export for off-line translation

Export in native format

<languages/>
{{WIP|Being revised for the .net 7 upgrade}}
<div lang="en" dir="ltr" class="mw-content-ltr">
Vintage Story aims to be a high-performance game even on non-gaming hardware, such as laptops. For high-end gaming hardware, it should be possible to achieve high framerates (100fps or more) even with all graphics settings maximized.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Generally, each new major version of Vintage Story should have better performance: version 1.15 was noticeably better than 1.14, for example. Also, Vintage Story switched from .NET 4 to .NET 7, which resulted in drastically better performance for clients and servers alike. Be sure to run the most recent version to ensure you are running with the best performance possible.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===Basic performance tips - if the game runs slow===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
With appropriate settings, most players should be able to achieve playable framerates (such as 30fps) even on older hardware. Make sure to read through the {{ll|Troubleshooting_Guide#Game_Runs_Slow|Game Runs Slow Guide}}.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have only integrated graphics (e.g. Intel Core with Iris), use graphics settings Medium or Low, or even lower.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===Advanced Tips for Maximizing Performance===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
1. If, in Single Player, you run into large lag spikes after a few minutes of play, and you have 8 GB or less RAM, you could be bottlenecked by lack of system memory (in extreme cases it can also crash with OutOfMemory exceptions, including graphics OutOfMemory issues). 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 ideally. Buying more RAM is quite cost effective in comparison to a new graphics card or CPU.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
2. It may help to play the game in Full Screen mode, not Windowed mode or Borderless.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
3. Vintage Story has a wide range of graphics settings. In the Settings menu, Graphics tab, click "Show all available settings" to see them all. Adjusting these up or down, and switching on or off the fancier elements, can have a huge effect on performance, especially on older or mid-range graphics cards (GPUs). The tooltips on each control on the Graphics settings page should give you some pointers. Switching off Shadows, SSAO and Bloom will have the biggest effect on framerate for most people. Even dropping your Shadows and SSAO from the highest settings down a notch should grant a significant gain in framerate.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Also check that you didn't limit framerate accidentally in the Graphics settings page by setting "Max FPS" to too low a figure - while tweaking framerate performance it's probably best to set that to Unlimited.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
''Large view distances or unusually high world heights have an effect not only on the framerate (fps) on screen, but also performance throughout the game. If everything is sluggish or there are frequent lag spikes, try turning down the view distance. The game is balanced to be smooth and playable on most modern PCs at view distances around 256 blocks to 512 blocks, depending on your hardware. Playing at above 512 blocks is certainly possible on most PCs - but long-term play at such large view distances with max graphics is best left only for high-end gaming PCs who followed the advice in step #1...''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
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.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
''Tip: on a multi-core PC, the overall CPU usage percentage shown by Windows can look small even if one core is maxed out. For example, with 8 cores, one core maxed out at 100% would only be 12.5% CPU usage overall. To see what's really going on, you need to use a non-Microsoft tool like Hardware Monitor.''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
''(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.)''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
6. If your settings seem well adjusted most of the time but you still experience occasional short, stuttering lag spikes especially when moving larger distances across the world, try '''increasing''' the Chunk upload rate limiter setting. First try increasing it to its maximum setting, fly around the world some distance, and if that has fixed the lag spike problem, in slow steps bring the slider back down to a level which still does not produce lag spikes. (The game cannot automatically adjust this setting, the correct value depends on the unique combination of your graphics hardware's capabilities, overall system speed, and other adjustable graphics settings such as view distance.)
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
7. In Single player or if using your own server (see #1 above), you can tweak server performance by adjusting the "servermagicnumbers.json". The magic numbers default values are aimed at a typical Vintage Story multiplayer server with let's say 3 or 4 players, playing over the internet, so some of them can be increased if it's only 1 player on your own machine.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
8. There's a known issue on '''Radeon''' graphics cards - including high end Radeon cards - about GPU availability, more like memory lock contention. The issue is normally only seen on max graphics settings (with shadows enabled) and is most obvious when moving across the map so that a lot of new map loads, there can be '''noticeable frame rate drops and stutter'''. Game version 1.15.7 and above has a change that slightly improves this, we hope to do even more to work around it in future versions, but it is a hardware/GPU issue. For anyone bothered by the issue, a solution is to ease the pressure on the GPU by turning down some of the top end settings (SSAO and Shadows or reduce the MaxFPS) so that the GPU has some idle time each frame.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
9. The Occlusion Culling graphics setting is recommended on any modern multi-core CPU (4 cores or more) - it uses one additional CPU thread but leads to less work for the GPU. This can drastically increase performance while playing with high render distances.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
10. For very low end hardware, it can help to play on worlds that are only 192 or 128 blocks tall.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
11. Some game scenes are more complex and will lead to FPS drops for most players. Examples are deep forests with many leaves, towns with many chiselled blocks, and the Resonance Archives.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
12. If you are having issues with stuttering, and have RAM to spare, such as 16gb+ of RAM in your system, you can try disabling the Optimize Ram option. You cannot do this ingame, so you’ll need to navigate to <code>%appdata%</code> in your file explorer, and locate your <code>VintageStory</code> folder (or right-click on your Vintage Story shortcut icon and select "Open file location"). In there you’ll find <code>clientsettings.json</code>. Find the line that includes <code>OptimizeRam</code> and check to see what value it is set to. It should be set by default to either <code>1</code> or <code>2</code>. If you set this to <code>0</code> and save the file, it will disable the setting the next time you start your game. When in game you can ensure that it is disabled by looking at the Optimize Ram graphics setting and it will have a blank entry. This may improve your issues with stuttering or microstuttering.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
:''See also:'' {{ll|Troubleshooting_Guide#Game_Runs_Slow|Troubleshooting Guide}}
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
====For Linux users====
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
A simple method to increase performance may be to enable mesa_glthread by running the game with: <code>mesa_glthread=true mono Vintagestory.exe</code>
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
There is a [https://www.vintagestory.at/forums/topic/10479-linux-beginner-guide-mesa_glthread-boost-your-performance-today/ beginners guide] on this on the forums. 
One user [https://www.vintagestory.at/forums/topic/6298-boost-linux-performace/ on the forums] suggests running the game with <code>strangle 60 mono ./Vintagestory.exe</code> to fix issues with input lag.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===Balancing performance, temperature and power consumption===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* For the reasons given in #5 above, it is recommended not to run with Unlimited FPS, but instead to limit the FPS. The main reason to do this is so that your CPU will not be maxed out with one core at 100% all the time, which can lead to overheating or even (in the long term) a shorter lifetime for your CPU. If FPS is limited in any of the ways on offer, it allows the CPU to "rest" in between frames, and that in turn means the CPU takes less power and runs cooler, so that system fans can be quieter, etc, etc.
* FPS can be limited through the graphics settings. This can be done either by using the MaxFPS slider, or using VSync, or the third VSync option is a combination of both. You can also limit FPS on some GPUs from the driver level, such as Nvidia's control panel.
* Most modern graphics cards - even internal graphics on laptops - have a VSync feature. If VSync is on, then the game engine will not render frames more quickly than they can be drawn on the actual connected display. This allows the CPU to rest sometimes, waiting until the display is ready to render the next frame, so the CPU will not be at 100%. But sometimes graphics drivers behave strangely with VSync, for example there can be global overrides to switch it off - in this case, Vintage Story's VSync setting will seem not to have any effect, it will be like having framerate unlimited.
* VSync may help with graphical "tearing" issues, although these do not occur on all systems - they are more common on specialised low-latency gaming monitors so if you have one of those (lucky you!) then VSync is your best option.
* Generally, we recommend first trying the game with VSync switched on.
* The alternative recommendation is to play with VSync switched off and MaxFPS set to a figure slightly higher than the frame rate you want to see (remember it's the maximum, not the average). For example, if you want to play at average 60fps then set MaxFPS to somewhere around 70-75fps.
* On a Windows PC (but not Linux or Mac) there is an issue where if you are using MaxFPS alone (not VSync) to control the framerate, the Windows timer is not very precise. In practice, in the frame rate meter, what this looks like is the frame rate seems to stick at specific step levels like 48fps or 32fps instead of the 60fps you want. This issue is caused by the Windows system interval timer and there's not much the Vintage Story dev team can do about it: even if we take it by the scruff of the neck, other Windows applications running on your PC can change that timer at any time. Therefore, on a Windows PC with a display refresh rate of 60 fps, you may need to experiment a little - it also depends what other applications are running on your system. For some people it works best to set MaxFPS higher than the level you want. So, if you want 60fps, set MaxFPS somewhere in the range 70-75fps (you can experiment!), and if all is going well then, the Windows system interval timer will drop that down to its next step level which might be 64fps. 64fps is good, it's close to 60fps which the display requires.
* On a Windows PC another option is to embrace 32fps, so set your MaxFPS slightly higher than 32fps (say around 40 fps) and you should find that Windows effect drops it down and locks it at 32fps. The reason for doing this is to have a steady constant FPS, no matter what is happening on screen. A constant 32fps should look smooth, as long as it's steady. That's better than TV shows and sports (30fps) or movies (24fps).
* Some players want lag (latency) to be as low as possible, in that case you can try setting MaxFPS at a much higher number like 100 or 120fps. Even a high number like that will have cooling benefits on a high -powered gaming PC which can reach framerates of 150 or more in Vintage Story.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
===Thinking about what is on-screen===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* Vintage Story framerates can change a lot depending on the complexity of what is on screen.
* To see this, with unlimited MaxFPS, try looking straight up into the sky - you should see the frame rate increase dramatically
* Normally the most complex scenes, causing the lowest FPS, are thick, deep forests. It's because of all the leaves, and each leaf block is slightly transparent, so everything behind leaf blocks also has to be drawn - the depth of field is huge.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The main way to control CPU and GPU usage is using the '''Vsync''' and '''Max FPS''' settings in the graphics settings as described above.
* One path to optimize both: pick a framerate you want e.g. 60 fps. Now with '''VSync''' off and '''Max FPS''' unlimited, adjust the graphics settings that heavily affect framerate (view distance, godrays & bloom, shadows, SSAO) to hit a framerate that's about 15%-20% better than you want, e.g. 70 fps or 80 fps. When the game can comfortably hit that, now set '''Max FPS''' to 60fps and '''VSync''' to 'On + Sleep'. This should produce a stable 60fps, a smooth game with no lag spikes, and less than 100% CPU and GPU usage so that your fans run quietly.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
=== Server Performance ===
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you are a server owner and suffer from lag issues on the server.
* Make sure it's not 3rd party mods causing it
* If you have more than a couple of players, make sure your hardware is strong enough to support your player base. Virtual Servers have a tendency to perform rather badly at 10+ players. Bare metal works best.
* You can run <code>/debug logticks 100</code> to see where most time is spent on, feel free to ping tyron on discord to interpret the results or ask others in discord if they are familiar with the issues.
</div>

Anonymous

Search

Export translations

Namespaces

More

Page actions

Navigation

Navigation

VS related links

Community portal

Wiki tools

Wiki tools

Anonymous

Search

Export translations

Navigation

Wiki tools

Page tools