Confirmedusers
13,514
edits
Troubleshooting Guide: Difference between revisions
From Vintage Story Wiki
Marked this version for translation
No edit summary |
Mirotworez (talk | contribs) (Marked this version for translation) |
||
| (6 intermediate revisions by one other user not shown) | |||
| Line 36: | Line 36: | ||
The game needs around 4 GB of free RAM to run smoothly, or more than that if you use integrated graphics (because it uses system memory as GPU memory). You can try to free up memory by closing all other applications, setting the in-game viewing distance lower, setting the music volume to 0 and set RAM optimization to "aggressive" in the game's graphics settings. If your computer does not have 4 GB of free RAM, you can perhaps still play on minimum settings, for example a view distance of 96 or less. | The game needs around 4 GB of free RAM to run smoothly, or more than that if you use integrated graphics (because it uses system memory as GPU memory). You can try to free up memory by closing all other applications, setting the in-game viewing distance lower, setting the music volume to 0 and set RAM optimization to "aggressive" in the game's graphics settings. If your computer does not have 4 GB of free RAM, you can perhaps still play on minimum settings, for example a view distance of 96 or less. | ||
<!--T:27--> | |||
A graphics card can also run out of memory, causing the game to crash. Possible causes include: other active games or processes on your computer which also use graphics card resources (including some webpages or video players); two copies of Vintage Story running at the same time; a previous hard crash of any game or application such that graphics resources were not properly freed (try re-starting your system!); ultra-high view distances; fancy shader mods. If it happens repeatedly without any of these causes and even after re-starting your system, then try reducing graphics settings in Vintage Story: you can access the settings from the Main Menu before starting the game. | A graphics card can also run out of memory, causing the game to crash. Possible causes include: other active games or processes on your computer which also use graphics card resources (including some webpages or video players); two copies of Vintage Story running at the same time; a previous hard crash of any game or application such that graphics resources were not properly freed (try re-starting your system!); ultra-high view distances; fancy shader mods. If it happens repeatedly without any of these causes and even after re-starting your system, then try reducing graphics settings in Vintage Story: you can access the settings from the Main Menu before starting the game. | ||
| Line 71: | Line 72: | ||
* Please do not run the game from an external drive or network share. | * Please do not run the game from an external drive or network share. | ||
* Running on a virtual machine (VM) may also cause performance issues. | * Running on a virtual machine (VM) may also cause performance issues. | ||
* The game requires 4GB of free memory (RAM) | * The game requires 4GB of free memory (RAM) - or perhaps more like 6 GB if playing on a laptop with integrated graphics. You can look in Task Manager how much you have before you start the game. More RAM than that will not help greatly (except by ensuring that other system processes do not impact on Vintage Story's memory needs). Exception: if you want to run a local Vintage Story server on the same computer - which can help performance - then you need 8GB of free memory. | ||
* Some people have reported that Windows 10 update version 2004 causes lag issues in games (especially in "Game Mode" in Windows Settings); if you have the choice, we recommend Windows 10 version 1903 as the most stable Windows 10 version for gaming. | * Some people have reported that Windows 10 update version 2004 causes lag issues in games (especially in "Game Mode" in Windows Settings); if you have the choice, we recommend Windows 10 version 1903 as the most stable Windows 10 version for gaming. | ||
* If you're playing multiplayer, it's best to be in the same geographic region as the server you are playing on. See next section below. | * If you're playing multiplayer, it's best to be in the same geographic region as the server you are playing on. See next section below. | ||
| Line 81: | Line 82: | ||
* In game version 1.16.5, there are reports that a mod (we do not know which one!) can cause multiplayer connection issues or disconnects. If playing with a large mod list and you have connection issues and you have control over the mods on the server as well, try reducing the mod list (for both the server and the players) until the issue is fixed: as a start, test whether you can connect to the server with no mods except Vintage Story's "vanilla" mods Survival, Creative and Essential | * In game version 1.16.5, there are reports that a mod (we do not know which one!) can cause multiplayer connection issues or disconnects. If playing with a large mod list and you have connection issues and you have control over the mods on the server as well, try reducing the mod list (for both the server and the players) until the issue is fixed: as a start, test whether you can connect to the server with no mods except Vintage Story's "vanilla" mods Survival, Creative and Essential | ||
* If you are the server owner: | * If you are the server owner: | ||
** The Server might be struggling. Be sure to meet the server's minimum requirements. Many concurrent players requires extra hardware. You can also try adjusting the Magic Numbers on the server. | ** The Server might be struggling. Be sure to meet the server's minimum requirements. Many concurrent players requires extra hardware. You can also try [[Debugging#Improving_Server_Performance|adjusting the Magic Numbers]] on the server. | ||
** Also check out the [[Debugging]] page. You can use tick logging (logticks) to perhaps identify the specific cause of lag. | ** Also check out the [[Debugging]] page. You can use tick logging (logticks) to perhaps identify the specific cause of lag. | ||
** Auto-save every few minutes will cause 1-2 seconds of lag when it saves. That is unavoidable if you want to protect the game progression using auto-save (strongly recommended). A fast CPU and a fast solid state disk system can improve this but it will always take some time. | ** Auto-save every few minutes will cause 1-2 seconds of lag when it saves. That is unavoidable if you want to protect the game progression using auto-save (strongly recommended). A fast CPU and a fast solid state disk system can improve this but it will always take some time. | ||
| Line 89: | Line 90: | ||
<!--T:20--> | <!--T:20--> | ||
If you are the server owner: | |||
* Make sure your Firewall does not block internet access for VintagestoryServer.exe | * Make sure your Firewall does not block internet access for VintagestoryServer.exe | ||
* If you are hosting | * Test whether another computer on your local network (Wifi or directly plugged in) can connect to the server | ||
* If you are hosting yourself for public access - making a multiplayer server at home, for friends or others outside your home to access - you either need to [[Setting_up_a_Multiplayer_Server|set up port forwarding on your router]] or use a VPN, like hamachi | |||
<!--T:28--> | |||
If you are the player: | |||
* Make sure your Firewall does not block internet access for Vintagestory.exe | |||
* Make sure your game version matches the server game version: you can download an update, or download an earlier version of the game, from the Client Area / Downloads at www.vintagestory.at | |||
* The server might have a "whitelist" of allowed players: if you are a new player not on the list, try contacting the server owner | |||
* Test whether you are able to connect to other multiplayer servers, for example the Official Public Test Server | |||
===AccessViolation (0xC0000005)=== <!--T:21--> | ===AccessViolation (0xC0000005)=== <!--T:21--> | ||
| Line 102: | Line 112: | ||
* Overclocking processors | * Overclocking processors | ||
==Game | ==Game Servers on Linux== <!--T:23--> | ||
===Error: Garbage collector could not allocate 16384u bytes of memory for major heap section.=== <!--T:24--> | ===Error: Garbage collector could not allocate 16384u bytes of memory for major heap section.=== <!--T:24--> | ||
