Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.2.0
Issue ID
N4EBUG-82
Regression
No
Netcode's CommandSendSystem does not yet recognize maxMessageSize parameter on NetworkSettings
Newly introduced in Transport 2.1 is the maxMessageSize parameter found on NetworkSettings, a customizable max packet size for restricting the size of packets other than 1400 bytes what was previously hardcoded into NetworkParameterConstants.MTU.
Netcode's CommandSendSystem does not yet recognize MaxMessageSize so changing this value will cause the send system to break when the system will want to send bigger packages then allowed in the CommandSendSystem by this value.
The thread can be find [[here|https://forum.unity.com/threads/1-2-0-exp-3-commandsendsystem-should-use-maxmessagesize-parameter-instead-of-hardcoded-mtu.1517500/]|https://forum.unity.com/threads/1-2-0-exp-3-commandsendsystem-should-use-maxmessagesize-parameter-instead-of-hardcoded-mtu.1517500/]
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
There are no fixes planned for this Bug