Question Handling Unity Transport errors

Hi, everyone!
I'm going for Netcode custom messages approach for my game with server-client architecture. For sending messages I'm using

NetworkManager.Singleton.CustomMessagingManager.SendNamedMessage(..)

It's nothing special really.
So far messages work quite nicely, but often I'm getting these errors, when I'm trying to send large amounts of packets over 'Reliable' pipes.

Currently unable to queue packet as there is too many inflight packets.
Unable to allocate packet due to buffer overflow.

Which it seems, are coming from Unity Transport. I've digged through the code a little bit and found that the errors were coming from the NetworkDriver. But the driver itself is enclosed in UnityTransport class, and there is no way to access it, as it's private. Here are the methods, sending errors (irrelevant code omitted):

Code (CSharp):

1.  
2. private unsafe void SendBatchedMessage(ulong clientId, ref NativeArray<byte> data, NetworkPipeline pipeline)
3. {
4.             var payloadSize = data.Length + 1;
5.             var result = m_Driver.BeginSend(pipeline, ParseClientId(clientId), out var writer, payloadSize);
6.             if (result == 0)
7.             {
8.                (...)
9.             }
10.  
11.             Debug.LogError($"Error sending the message:{ErrorUtilities.ErrorToString((Networking.Transport.Error.StatusCode)result, clientId)}");
12. }
13.  
14. private unsafe void SendMessageInstantly(ulong clientId, ArraySegment<byte> data, NetworkPipeline pipeline)
15. {
16.             var payloadSize = data.Count + 1 + 4;
17.             var result = m_Driver.BeginSend(pipeline, ParseClientId(clientId), out var writer, payloadSize);
18.  
19.             if (result == 0)
20.             {
21.                 (....)
22.             }
23.  
24.             Debug.LogError($"Error sending the message: {ErrorUtilities.ErrorToString((Networking.Transport.Error.StatusCode)result, clientId)}");
25. }

The response code just goes to the logs and nowhere else, the packet is not being sent either.

The question is: If I can't access the driver\error responses, how am I supposed to account for these errors? I understand, I must be doing something wrong by sending too much data over the time, but how am I supposed to know when it becomes 'too much'?

 

Thank you for the quick response. I'm glad to hear that the problem is acknowledged.

 

Any news about this problem? It's problematic. I have just 2 players and 1 or 2 ServerRPC call per second (max). And i encounter this error on the client side. (host seems to be not affected)

 

Similarly, I was calling 1 RPC on every Update(). 1 host & 1 client.

After a minute or two (I didn't time it) I go the "Error sending the message: Currently unable to queue packet as there is too many inflight packets." on the client.

Now, I'm wondering if I should be using some other Update() that I have not found in the docs.

 

Add my project to now being impacted by this too

 

is a fix pack build available on github ?