You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to migrate an UnreliableRemoteEvent over to Red and started seeing oversized payloads.
Normally we're able to fit under the 900 byte limit, but going through Red makes it overflow by 500-600 bytes.
Is there anything you guys could do to shrink the overhead of what's being sent over the unreliable wire?
The text was updated successfully, but these errors were encountered:
This behavior happens because Red batches all fires into one remote fire, which can cause it to go over the size limit. Many times this is desirable behavior because it saves a lot of bandwidth, but it can also be undesirable with unreliable remotes in particular because of the size limit.
I think the best way to fix this is to make different channels for unreliables so that they can be batched only when desired. Unfortunately that's difficult and isn't cleanly backwards compatible from what I can tell, so making unreliables not batched is likely the best solution we can implement.
I tried to migrate an UnreliableRemoteEvent over to Red and started seeing oversized payloads.
Normally we're able to fit under the 900 byte limit, but going through Red makes it overflow by 500-600 bytes.
Is there anything you guys could do to shrink the overhead of what's being sent over the unreliable wire?
The text was updated successfully, but these errors were encountered: