Outgoing Reliable Buffer Overflow

[123]

Since v293.100 - Homestead! update, everytime I transfer within the cluster I play on, I get the error "Outgoing Reliable Buffer Overflow".

This error was common before, but only if you have an abundance of inventory on your character when transferring.

I can transfer successfully with 5 items or less, but anything more than that, I will get this error.

Has anyone else had the same issues since v293.100? Has anyone discovered a resolution to this problem?

[Captpickles]

Nope and nope. I transferred last night on my cluster without issue. The solution is simple. Upload your items.

[AncientLotus]

Usually when you get this error is has to do with engram points. like an autoengram mod or something. try using a mindwipe if you can, this can fix that error alot of the times.

[KitsuneShiro]

It's all the engrams points, they make your character file too big.

[123]

Thanks all for the commentary..

I have tried the mindwipe to no avail.

It seems I can transfer(no issue) with less than 5 items in my inventory. Anything over that and I get the buffer overflow consistently.

This all started happening post patch v293.100, and I am not the only person this is happening to on our unofficial cluster(cluster has been up and running for a couple of years so its not something new). It's happening to every player.

There are times we get a fatal error as well in the transfer process. Again all new since the patch.

All of these transfers are performed using the S+ Tek Transmitter

I am going to try it with the server oblisk's and see if that works.

[KitsuneShiro]

What mods do you use?

Like what modded items are you transferring?

[123]

S+, Resource Stacks, Utilities Plus

those are the only mods associated with my inventory, the rest is vanilla items

[KitsuneShiro]

You still using the resource stack mod that hasn't been updated since 2017?

[KitsuneShiro]

Try transfers with no modded items.

Has the server(s) be restart? Basic server maintenance (router restart, OS updates) etc?

[123]

The cluster owner has, yes that is correct

[KitsuneShiro]

Here is how the wise mod author Lethal explains it.

Originally posted by Lethal:

So for clients there is a buffer, kind of like memory, where it holds data waiting to be processed by the client. This could be anything that replicates to your client and everything in effect contributes to this buffer. It could be polygons and tri's from rendering, animations, number of engrams learned, items on you (cryopods have the biggest impact since it's holding dino data in a tiny item), dinos, structures (dynamic changing ones have the biggest impact), and every time you open an inventory holding Ark Data than all three tabs of data get replicated to you, and there's more. Everything that your client actually has to process goes towards this. When the buffer limit is reached than "unreliable" events (or those set to not be absolutely mandatory in firing) will cease to fire, but events set as "reliable" have that mandatory flag and if it can't execute than it causes a hard failure. It's hard to define what is set as reliable but we can imagine that events tied to a player connecting would be considered reliable whereas throwing an item on the ground to trigger the respective animation would be unreliable. Thus, when this client data reaches it's limit and you trigger a reliable event... this is how you get: Reliable Outgoing Buffer Overflow.

In short, your client/game is processing too much data. Lowering graphics or learning less engrams or anything to reduce your data to process will help. Also, the faster your storage device (SSDs win here), the faster it can process this data which helps it from overflowing. The faster it processes out, the less chance of it reaching the limit.

[123]

That is a great description of the event, and understandable as well.

I get it. I am just trying to figure out the culprit that was obviously affected by that patch.

Thanks again for the input.

[KitsuneShiro]

Lethal is so smart. And it seems he has been answering posts in the bug subforum.

The biggest this the patch added was even more engram points.

[Toooni]

The solution for that is:
Let the admin delete your profile in the cluster directory
(No server restart and things like that needed, only delete the file which has the id of your steamplayerid. )

The reason for the problem is:
Each time you travel, this stores your implant in the cluster profile. So this profile gets bigger and bigger and bigger...
Once the profile has some size, it starts to generate such problems.


Wildcard said before a few patches that they fixed that... but nah, they didn't.

[AncientLotus]

Are you by chance using any autoengram? like the ini code to give all engrams, or the mod.

[123]

Originally posted by Toooni:

The solution for that is:
Let the admin delete your profile in the cluster directory
(No server restart and things like that needed, only delete the file which has the id of your steamplayerid. )

The reason for the problem is:
Each time you travel, this stores your implant in the cluster profile. So this profile gets bigger and bigger and bigger...
Once the profile has some size, it starts to generate such problems.


Wildcard said before a few patches that they fixed that... but nah, they didn't.

This did not work unfortunately