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
- [URP] Invalid update of shader stripping settings
- [HDRP] Errors on Shader stripper that do not stripp shaders.
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
Resolution Note:
There are no fixes planned for this Bug