![]() ![]() Originally posted by Hammer:Does that mean on windows the 64 BAT should look like this (the part that's relevant here)Īs an example that is - or do I need to make it same format as existing one with say 16000m rather than 16G ? In turn, my settings for the launch script looked like this: I've found the fix was to simply turn up -Xms to the average amount of memory the game uses while running on average, and giving -Xmx and additional 2GB over that (though that might be excessive). This means that (unless I'm way off the mark here) whenever the game hits over roughly 1.2GB in memory used (which it often can with a heavily modded game) it will attempt to clear memory to 720MB used, this means that some things loaded in to memory need to be reloaded, and after this point it's essentially black magic to me. ![]() ![]() Now I'm far more of a C type of guy, but I've worked with java a bit, and from what I recall (and feel free to correct me if I'm wrong) -Xms is the setting for the total memory used by the JVM's garbage collection system, meaning it tries to clear to that amount of memory periodically.Īs for -Xmx, I BELIEVE that is the total memory the JVM is allowed to use, or the point at which it starts to run garbage collection. I looked into the engine for the game itself and it turns out it's built in java, and after looking through the game folders I found that the startup shell script for the game has the following JVM settings. I found it a little strange, the stutter didn't seem to be the game locking up under load so much as if it was waiting for a running thread to rejoin.Īfter poking around with just playing the vanilla version with spawn settings turned way up and corpse persistence increased, I noticed that I was starting to run in to the same thing even with all the zombies being killed, while my system memory sat at 10 GB / 16 GB used. Some more stuff in “Saves\Multiplayer\servertest”.Forgive the wall of text, the technical details are here mostly for the developers and anyone interested in it.Īs of recent, I've been noticing far more stuttering in game, something that, after investigation, seemed to be tied to the mods I had active (though it's not explicitly the fault of the mods themselves, so please hear me out here). Server db is in the “db” folder and SQLite browser – is able to open it. Once satisfied relaunch the server as the first time by starting “StartServer64MP.bat”. This is where you can set the server name as well as a password and much more.ĭefault port is 16261, make sure this is forwarded! (Look for port forwarding on the internet if you don’t know how) The server is named by default “servertest”, its config is in the “Server” folder inside “servertest.ini”. Windows + r to execute it will open the folder: The configs and saves are in %UserProfile%/Zomboid This section is still being written but here are my findings: This is required a first time to initialize the multiplayer map and other files. Once it’s done you can exit the window which will stop the server. This should look like this:ĭouble click “StartServer64MP.bat”, this will open a windows terminal which will ask you to set an admin password: This will open the folder where the server is installed. ![]() Right click the server in your list on the left -> Properties.You should do the procedure for both the game and the server. If you are wondering why and how I have in my listing please refer to the announcement link shared in the introduction section, it is explained there. In your library display your “Tools” (just below “Home”), look for “Project Zomboid Dedicated Server” and install it. For everyone else your steam account must own the game. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |