coldino / Larkator

ARK dino locator that uses your saved .ark
MIT License
54 stars 18 forks source link

Error: Capacity was less than current size #83

Closed KumaDeBeer closed 2 years ago

KumaDeBeer commented 2 years ago

I've been playing on a Nitrado server I bought(rent?). I download the save file via a FTP on a daily base. Since this morning I have been getting the following error: Capacity was less than current size. Parameter name: value. This doesn't happen with Single Player save files. The save file from the server is 45,975 KB while the one from single player is 53,769 KB. I also reboot the server to update the save file, but that didn't yield any differences.

Map I'm playing on is The Island.

image

xradius17 commented 2 years ago

I "think" this is an issue with the PAX event happening in ark currently. Larkator still works on saves that do not have any PAX colored dinos, wild or tamed in the save file. Once you tame a dino from the event or have any wild dinos from the event, Lakator throws the error you posted. Hopes this helps the devs resolve the issue.

KumaDeBeer commented 2 years ago

I "think" this is an issue with the PAX event happening in ark currently. Larkator still works on saves that do not have any PAX colored dinos, wild or tamed in the save file. Once you tame a dino from the event or have any wild dinos from the event, Lakator throws the error you posted. Hopes this helps the devs resolve the issue.

I'll try to turn the event off, wipe wild dinosaurs and restart the server in a couple minutes, will update if that helps

xradius17 commented 2 years ago

Make sure you don't have any tames from the event either.

xradius17 commented 2 years ago

Looks like it is the PAX update itself. server version 349.10. It is happening for me on multiple maps. Fordur, Lost Island, and Crystal Isles.

KumaDeBeer commented 2 years ago

Looks like it is the PAX update itself. server version 349.10. It is happening for me on multiple maps. Fordur, Lost Island, and Crystal Isles.

I killed all tames from the last 24 hours, luckily it werent that many. The error still persists, so might be the patch itself yeah

Onatel commented 2 years ago

Hi there, good to see I´m not the only one with this error. I´ve the same on my dedicated ARK-Server, on the Fjordur-Map.

coldino commented 2 years ago

Yup, there has been a mysterious format change in the save file. Currently only affects the server builds, and unfortunately does not come with a change to the version field in the files.

Thanks to @alex4401 and @cadon the SavegameToolkit now has a quick workaround in place. I'll put a release of Larkator out today containing it.

That said, Wildcard themselves don't seem to be aware of the change or the difference between client and server saves right now. Hopefully we can clear some of this up in future.

coldino commented 2 years ago

v1.18 is released with this fix (5ec6f0d87508b4b162533bdcae1c676a4875aba2). Seems to work for both old and new, client and server.

Feels like this is something that might need to evolve over time, so let me know if you see more problems.

xradius17 commented 2 years ago

Thank you!

KumaDeBeer commented 2 years ago

v1.18 is released with this fix (5ec6f0d). Seems to work for both old and new, client and server.

Feels like this is something that might need to evolve over time, so let me know if you see more problems.

Great, thanks for the effort and quick fix!

Onatel commented 2 years ago

Thx a lot for the quick fix.