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
- Skinned Mesh Renderer with multiple Animator Components does not render when "Optimize Game Objects" is enabled
- [iOS]Certain characters are not displayed when using iOS devices with 18 OS and newer
- Trees do not render in 'Unity Terrain - URP Demo Scene'
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
Resolution Note:
There are no fixes planned for this Bug