Pro tip: Some extreme gameplay actions and settings (e.g. 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. 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 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.Ī graphics card can also run out of memory, causing the game to crash. 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. 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). Load your savegame in repair mode, fly to the crashing spot, leave the world and run the game normally again. NullReferenceException in Entity*.FromBytes() If you update game versions, and the 'remapping' dialog pops up asking if you want to make a backup (backup enabled by default), make sure you have plenty of disk space free for the backup, the backup process will need a lot of space on the hard drive where your Temp files folder is located. A Vintage Story savegame varies in size depending on how much of the map you have explored, it could be a few GB in size. The game will crash if you run out of disk space during a save, and likely also corrupt your savegame. Vintage Story also makes heavy use of shaders. Updating graphics drivers may help if there are visual issues or graphics (OpenGL) related crashes. ![]() Tip: If there's a crash report and in the report the top line of the code ends with _patch0 or similar (look for the word patch!) then it's probably a mod issue. If disabling mods, you should keep the Vintage Story "vanilla" mods enabled, that's Creative, Essentials and Survival! Check the Mod DB comments and forum page for the mod, or talk to other players using the mod. See if an update for the mod is available, generally you should use the latest version. Checking that mods aren't the source of the problem is a good place to start. Generally if updating Vintage Story to a new version like 1.16.5, you should also update all of your mods at the same time (though, some mods are fine with game updates). But using 3rd-party mods may possibly cause issues with the game, especially if the mod is not updated for the current Vintage Story game version you are playing. We encourage modding Vintage Story - see the amazing mods on the Mod DB. If you are playing with mods and you update Vintage Story without also updating the mods, some of the mods may have issues: see the next question! You could try asking other players on Discord, or if all else fails, try re-installing a previous version of Vintage Story which was stable. ![]() Normally updates add new features and fix older bugs, but very occasionally something breaks in the process. Vintage Story releases new updates several times each year. Having trouble getting the game to run correctly? Here's a list of common problems and fixes. 2.1 Error: Garbage collector could not allocate 16384u bytes of memory for major heap section.1.4 Multiplayer lag / Host not responding messages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |