Search Issue Tracker
In Progress
Under Consideration for 1.2.X
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/]
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Fix for 2022.3.X: Flickering of HDRP Directional Light shadows with DirectionalMixedCachedShadows when in an Entities Graphics rendered Subscene
- "Objects are trying to be loaded during a domain backup." errors on entering Playmode
- Transform Node does not have outputs when it is created
- Changing the Default Icon does not change the executable's icon when re-building the project
- Texture is stored upside down when using Blit
Add comment