Andargor

These videos illustrate what I mean for the following on disembark bug. It is incredibly frustrating, and I don't know why we are the only ones seeing it.

On our private server, there is an island of type Mnt_Y_CP_D that has ironwood/twigs. Don't know where that is on official.

Don't know if this will help, but I run a 2x1 on linux on the same physical server, and it uses the same RDB. I started with a 1x1 and expanded to 2x1, did not have to change DB info in ServerGrid.ServerOnly.json. I use Atlas Server Tools: https://github.com/BoiseComputer/atlas-server-tools So, at the very least, I can confirm this works.

FWIW I'm currently testing the following in Game.ini only, no JSON changes in the grid and no wipe: [/Script/ShooterGame.ShooterGameMode] DinoSpawnWeightMultipliers=(DinoNameTag=ShipNPC_Brig,SpawnWeightMultiplier=0.1) After server restart and destroywilddinos in all grids and another restart, so far so good. We had swarms before, and now we get 1 or 2 in open sea, or 5-6 near PVE islands. I chose 0.1 so that I could actually see the change, if any. However, they do seem to accumulate over time, so I will only be sure this worked after a few days.

As an indication, our server has 2 tiles: - A1 with 25 islands: 11GB RAM - B1 with 6 islands: 6 GB RAM

What kind of ship were you using and do you have a pic of your design? Trying to find what the difference is here, because our group has all brigantines, and we all have that issue.

Hmm. Our experience is that having crew or tames on follow and then disembarking, they will disappear 90% of the time, no log message, no notification, nothing. For boarding, using follow to go up ladders or ordering them on ship will kill them about 10% of the time, with a notification that "XXX has been killed" and no other explanation.

Our group is disembarking ships while mounted on tames to avoid them disappearing, but is there a trick to get them on board without them randomly getting killed? EDIT: Linux servers are causing crews and tames to disappear 100% of the time when disembarking.

v19.52 increased CPU usage by up to 20% on my server on all tiles.

I use this variation, works in any location (until server restart): cheat gmsummon "FountainOfYouth_BP_C" 1

Totally unscientific, but like in Ark it seems that if an update is inbound things can get wonky in game, such as interacting with objects, NPCs or containers. Usually giving it a bit of time to update and restarting the game fixes it for me.

Although on that brig I only have the top and bottom decks, I left out the middle one to have the height for a forge, loom and tannery. Maybe that 2 wall high clearance is what allowed my cow to pop out.

Have you tried what got my cow out, get above them, whistle follow (works even if you don't see them) and slowly back away until they pop back up on the floor?

I actually got it out of the bottom of the ship!!!11one! I walked on the deck above it, just over the cow, whistled to follow and backed up a bit, and it popped back up! I had it on Low follow distance, so that helped. But my ship is now slower

It goes 200% faster Seriously though, instead of new features and mechanics, fixing tames that go through floors and randomly disappearing crew should be a priority...

It seems the issue is atlasmanager, I've manually updated to 3583437 and posted an issue on github for atlasmanager

Does the linux server following the same releases as windows? I see that server is up to 18.97, but my linux server is still at 18.9 and atlasmanager is reporting this on an update: Your server is already up to date! The most recent version is 3573591

On our private server, around the time I implemented discovery zones, all of our players stopped gaining XP. Ships gain XP, but not players. Any insights on what might be the cause if anyone has seen this before? EDIT: Our players are lvl 36-45, and this occurs away from Freeports as well, treasure maps, killing, crafting, etc. grant no XP.

I have the following, and the days and nights are longer: DayTimeSpeedScale=0.250000 DayCycleSpeedScale=0.250000 NightTimeSpeedScale=2.000000 However, NightTimeSpeedScale=2 is supposed to make the night pass 2x faster, but that is not working.

NPC Crew and tames on a brigantine that are on follow with the character will disappear if the character leaves the ship. EDIT: THIS HAPPENS 100% OF THE TIME ON LINUX SERVERS EDIT2: This seems fixed in 102.45 (crossing fingers) This was only tested with a brigantine, not the other ships: - Have a bunch of NPC Crew and tames with you on a brigantine - Have them follow you - Jump off the ship - All crew and tames disappear

For anyone having trouble with the missing libssl et al dependencies on ubuntu 18.04, I have successfully installed the following to make things work: apt update apt install libidn11 apt install librtmp1 wget http://ftp.us.debian.org/debian/pool/main/o/openssl/libssl1.0.0_1.0.2l-1~bpo8+1_amd64.deb dpkg -i libssl1.0.0_1.0.2l-1~bpo8+1_amd64.deb wget http://ftp.us.debian.org/debian/pool/main/o/openssl/openssl_1.0.2l-1~bpo8+1_arm64.deb dpkg -i openssl_1.0.2l-1~bpo8+1_arm64.deb apt -y --fix-broken install HTH

I had a working version until last night. I have an update process during the night that restarts the server, and with 18.9 I'm now getting FPlatformMisc::RequestExit(1) as well. Investigating...

Yeah, did not work in the end, still same vitamin drain. It must be some internal parameter that we can't change.

I've been looking at the game files, and in the ShooterGame.pdb file I found some interesting things such as: BaseVitaminsConsumptionRate OverEquilibriumVitaminsConsumptionMultiplier OverEquilibriumVitaminsAdditionMultiplier VitaminEquilibriumThresholdPercent I've tried BaseVitaminsConsumptionRate=0.1 in GameUserSettings.ini, and it _seems_ to slow down vitamin drain, but it's really hard to say. Anyone try this and have results? Also, for allowing pickups at any time, the beta Ark servers have AlwaysAllowStructurePickup=true, but could not find it in Atlas, anyone have a setting that works for this?

Make sure the instances are stopped when editing Engine.ini in each of your tiles. Also, and I thought this was unbelievable until I tried it: there is a date field in the ServerGrid.json file called "Day0", if that date has the year 2019, change it to 2018 and restart. I had %130 usage, with NetServerMaxTickRate=15 it droped to ~70%, with the date set to 2018 it dropped to ~30%. The mind boggles. (see this thread )