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 am having an odd issue where sending fragmented messages over the relay causes a IndexOutOfRangeException. Sending over fragmented channels works fine, but as soon as the message is too large and needs to be fragmented, issues occur.
This issue doesn't happen without the relay.
Sending a fragmented message from the Server to the Client causes this to be repeatedly output into the Relay server itself
[ERROR] Exception during loop: System.ArgumentException: Offset and length were out of bounds for the array or count is greater than the number of elements from index to the end of the source collection.
at System.ThrowHelper.ThrowArraySegmentCtorValidationFailedExceptions(Array array, Int32 offset, Int32 count)
at MLAPI.Relay.Transports.UnetTransport.Poll(UInt64& connectionId, Byte& channelId, ArraySegment`1& payload) in C:\Users\dylanpdx\Source\Repos\MLAPI.Relay\MLAPI.Relay\Transports\UnetTransport.cs:line 44
at MLAPI.Relay.Program.RunLoop() in C:\Users\dylanpdx\Source\Repos\MLAPI.Relay\MLAPI.Relay\Program.cs:line 241
at MLAPI.Relay.Program.Main(String[] args) in C:\Users\dylanpdx\Source\Repos\MLAPI.Relay\MLAPI.Relay\Program.cs:line 221
Sending a fragmented message from a Client to the Server causes this to be repeatedly thrown into the Host PC (not the relay server)
I am using the UNET transport, and the config.json is configured correctly (no CRC errors). I've also made no changes to the source code, i've only compiled it and am running the server on Linux
The text was updated successfully, but these errors were encountered:
Hello,
I am having an odd issue where sending fragmented messages over the relay causes a IndexOutOfRangeException. Sending over fragmented channels works fine, but as soon as the message is too large and needs to be fragmented, issues occur.
This issue doesn't happen without the relay.
Sending a fragmented message from the Server to the Client causes this to be repeatedly output into the Relay server itself
Sending a fragmented message from a Client to the Server causes this to be repeatedly thrown into the Host PC (not the relay server)
I am using the UNET transport, and the config.json is configured correctly (no CRC errors). I've also made no changes to the source code, i've only compiled it and am running the server on Linux
The text was updated successfully, but these errors were encountered: