Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
A New havok Engine will be added that will hopefully fix the memory leak thats causing the super crashes.
Until then, if someone finds a more stable way for longer play time please tell us and the setup you used. or if you somehow find where that memory leak is coming from.
Might of found a workaround that will work for some people who get frequent (every few minutes) Supercrashes.
There is a executable patcher located at the link below.
http://www.ntcore.com/4gb_patch.php
All it dose is it looks at the .exe you point it to and enables the Large memory addressing flag which as the page says allows it to use up to 4 GB of Virtual Ram.
There are other programs that can enable the flag within the .exe but this is the simplest one to use that I have found.
All you do is run the Zipped executable. point it to
Be aware that this isnt a guaranteed foolproof fix. You can and probably will still have supercrashes now and then, but hopefully youl have the less often and your playtime will be extended a fair ammount.
This is the same executable patcher recommended/used by a couple Sins of a Solar empire modders for their various mods as Sins also suffers from the same 2gb Memory limit as Kenshi.
(Mods feel free to edit this post in any manner you see fit.)
I did not really want to make a whole thread about it since I'm sure you guys figured that out.
Start a new save with a start that has multiple characters. Split those characters into as many squads as you want to import. Save the game.
Navigate to the Kenshi's save game location:
C:\Program Files (x86)\Steam\steamapps\common\Kenshi\save (This might be different depending on your OS, or if you installed Steam or Kenshi into a different folder)
Open the save you want to import your characters from, open the platoon folder, find your squads from the list "Nameless_1", and so on if you have more than 1 squad.
Copy these files, and find the platoon folder from the save you want to import htem to and paste those files over the top of the existing ones. This will overwrite the squads in the new save with the squads of the old save.
I would recommend resetting squad positions when you load the save game.
make sure you can see where you want the stove build... put someone in that building and make sure that floor is selected, and pause the game.
Press F12 and make sure that once you do press F12, do not click on anything on the screen other than the edit menu as crashes/bad things can happen.
then click buildings from the edit bar at the top.
in the list that shows up select farming, then in the middle column select cooking stove. now position the stove in the building where you want it and click once, you should get a notice that it has been built, click exit on the edit bar at the top. save your game in a different spot!. then exit the game and then start the game again and hit continue, i would keep the pre-edit save for quie a while, till you are sure that it works well.
While I am not getting terrible performance with my current settings, I do dislike the stutter that occasionally happens. I decided to try something that has worked for people in other games: Go into the nvidia control panel, go to Manage 3d Settings---Program Settings tab--- Then find Kenshi (or add it like I had to)--- change Power Management Mode from "Adaptive" to "Prefer Maximum Performance". This has helped me immensely with the random stutters. Hope this helps someone else!
stop anyone from using (cancel reocurring jobs as well) any "machine" or farm before trying to deconstruct it. It will crash if you attempt to deconstruct and somone tries to use it or is already useing it.
developers should put an "on deconstruct" "stop/deny usage" type instruction prior to beginning the deconstruct process, or pop a message saying can't deconstruct, job is queued message and not allow the deconstruct. depends on how the program is setup.