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
S+ have both the Tek and the older one. since there has been a fundamental change in how the storage works (server side they dropped having 2000 stacks and made it just 1 stack to save some megabytes of RAM per server).
I saw in the document that there was a setting to use UseOptimizedDediStorage. I couldnt find out what this did, all the documents it linked to was removed. This setting is still set to false. It sounds like UseOptimizedDediStorage might enable the change you mentioned. I havnt been able to locate any documents that specify what this setting did.
Instead of using a mod to increase the stacking size of items, I bumped up the stack size multiplier built in to 3x. Also added a few stack size rules for prime meat and mutton. I thought we might be storing to much material but we are only using 1700 out of 10000 slots available in our biggest dedicated storage.
Configuration can be found here:
https://pastebin.com/n4j6b7x6
S+ Dedicated Storage
S+ Tek Storage
The stack change* in Dedicated Storage is done by Wildcard in the ARK game itself and on server - I do not know what impact it had on server-client interface, just staying clear as possible because it is one possible cause of errors.
I do not crash having a few of the S+ Dedicated Storage (I only just got the Engram unlocked so only have a few). Specifically I have 2 nonmod Dedicated Storage Element Shards in both** (crate drops from before engram) and 5 S+ Dedicated Storage with Fiber, Thatch, Wood, Stone, Flint. All 7 near each other, but only touching their own type 2 and 5.
I have not used the Vivarium or Aggregator. The aggregate command in the S+ storage I can use without crashing. But it may also depend on what you pull and what other structures are near. Just like the Vivarium can possible be the issue depending what eggs you get near.
I do not have UseOptimizedDediStorage in GameUserSettings.ini, the Dedi options I do have are:
(grouped)
DedicatedStorageAllowNonStackables=false
DedicatedIntakeMaxRangeInFoundations=50
DediInterfaceDinoBlacklist=
DediInterfaceDinoWhitelist=
DediInterfaceMinUploadInterval=10
(and by itself)
DedicatedStorageSlotCount=10000
But all this text just to say, I can use the S+ Dedicated Storage (Genesis 2, not 1), don't know if the other can be a problem.
* https://survivetheark.com/index.php?/forums/topic/636218-community-crunch-284-dedicated-storage-change-evo-event-and-more/
**The first stopped at 300000 shards once, so I made the second contain Shards too thinking it was full. But now they are 19968 and 313096, I just link Stryder to the one when harvesting space, then occasionally empty some down to the other, not knowing what the max actually is.
**Scratch the below. Everything worked fine until a world save occurred. I will try splitting up or dumping some of the resources to see if this changes anything for me.
----Whats odd is everything works as it should when someone is online. As long as my base doesn't enter stasis (my theory) than no one crashes. I am not sure if this affects saving on the back end, meaning if I restarted the server it would load again. For this particular issue, I had to revert back to the last time someone visited the base. Everyone transferred off to do something on the other maps, which meant I used the save done 18 hours ago. A more recent save worked with SS but an older save was needed to get s+ working again.
I read that you can prevent stasis by setting a dino on wonder on the hitching post. I attached someone to see if this helps. I also stopped the S+ Aggregator from collecting more fiber. I mostly use the Vivarium to collect element shards. I have two and they mostly contain clones griffons, managarmr, and recently added gachas. I had a few gachas on the S+ Gavager but I boxed those up to see if they were causing the crash.----
Your line of thought make sense. I reverted back to an older save and removed all 72 S+ Dedicated Storage boxes to rule it out. I thought things were back in order but a few hours later it crashed. I got a slightly different message this time around that I can research at least.
Do you use the AllowIntegratedSPlusStructures setting?
Fatal error!
VERSION: 358.17
ShooterGameServer.exe!FHangThreadWatcher::HangeDetected() (0x00007ff6b76fa1f0) + 0 bytes [f:\build\lostisland\engine\source\runtime\engine\private\gameengine.cpp:172]
ShooterGameServer.exe!FHangThreadWatcher::Run() (0x00007ff6b76fa143) + 0 bytes [f:\build\lostisland\engine\source\runtime\engine\private\gameengine.cpp:136]
ShooterGameServer.exe!FRunnableThreadWin::Run() (0x00007ff6b7131caf) + 0 bytes [f:\build\lostisland\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:73]
ShooterGameServer.exe!FRunnableThreadWin::GuardedRun() (0x00007ff6b7131ba8) + 8 bytes [f:\build\lostisland\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:26]
KERNEL32.DLL!UnknownFunction (0x00007ffc77777344) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007ffc78ae26b1) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007ffc78ae26b1) + 0 bytes [UnknownFile:0]
Last Replicated Actor PlayerPawnTest_Male_C_5
Last Remote Function InitializeState_Multicast
We left Genesis 1 thinking something was corrupted on the map. The issue followed us to the Island where we moved the propagator. I found that the issue could be replicated if I only used the 731604991 - S+ plugin on both The Island and Genesis 1. This may be a bug, or I exceeded an unknown limit on the ini settings. When I setup the cluster a few months ago I changed the default PropagatorFuelInterval=86400 to 172800(3 days) to make it cheaper for everyone to use when we got to a point it was unlocked.
When we first used the Propagator, it showed the correct time in the UI and worked as expected. After some unknown time, it would cause anyone who rendered the base after it was in stasis for a bit to crash the whole server. After removing PropagatorFuelInterval, no more crashes have been occurring. Genesis 1 save that I thought was corrupted worked again.
S+ does not have a discord\discussion board. Hopefully this helps someone in the future. I appreciate everyone help to narrow down the issue.
I recently done some tests with the Hitchpost. It is only the leashed dino that is kept out of stasis, the entire base still enters stasis. If you use a Maewing to feed kid dinos, each kid dino needs leashed, leashing the Maewing is not enough. I am guessing the Maewing as trough will work without leash, but I did not test that.
S+ does have discussions, Steam Website ASE section: (line immediately below "ARK: Survival Evolved") Workshop -> (line below the icon picture of girl with Assault Rifle and Rocket Launcher on a Raptor) -> Discussions
I am sorry I missed the question, I see you found the culprit, but for anyone messing around with this in future - here is my setting.
AllowIntegratedSPlusStructures=True
Same for all servers I checked. As I remember it, it is a must for something I use and has always been on for any server I ran with S+ on it.
Good style posting your findings.
Are you referring to this? https://steamcommunity.com/workshop/discussions/?appid=346110. Thanks for pointing this out, I should have created this discussion under the mod sub. Some of the mods have their own dedicated discussion\discord section under their workshop. S+ used to have one but it looks like it was locked at some point in the past. At least I cant find it and Google searches lead me to a locked discussion board.
Yes, apologies. Not a dedicated S+ area, but it is semi active for ASE mods.
Not trying to say you posted in the wrong section. It wasn't really narrowed down all that much when you wrote the first post.