1.0.0-pre.10
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
Additional documentation and release notes are available at Multiplayer Documentation.
[1.0.0-pre.10] - 2022-06-21
Added
- Added a new
OnTransportFailure
callback toNetworkManager
. This callback is invoked when the manager'sNetworkTransport
encounters an unrecoverable error. Transport failures also cause theNetworkManager
to shut down. Currently, this is only used byUnityTransport
to signal a timeout of its connection to the Unity Relay servers. (#1994) - Added
NetworkEvent.TransportFailure
, which can be used by implementations ofNetworkTransport
to signal toNetworkManager
that an unrecoverable error was encountered. (#1994) - Added test to ensure a warning occurs when nesting NetworkObjects in a NetworkPrefab (#1969)
- Added
NetworkManager.RemoveNetworkPrefab(...)
to remove a prefab from the prefabs list (#1950)
Changed
- Updated
UnityTransport
dependency oncom.unity.transport
to 1.1.0. (#2025) - (API Breaking)
ConnectionApprovalCallback
is no longer anevent
and will not allow more than 1 handler registered at a time. Also,ConnectionApprovalCallback
is now aFunc<>
takingConnectionApprovalRequest
in and returningConnectionApprovalResponse
back out (#1972)
Removed
Fixed
- Fixed issue where dynamically spawned
NetworkObject
s could throw an exception if the scene of origin handle was zero (0) and theNetworkObject
was already spawned. (#2017) - Fixed issue where
NetworkObject.Observers
was not being cleared when despawned. (#2009) - Fixed
NetworkAnimator
could not run in the server authoritative mode. (#2003) - Fixed issue where late joining clients would get a soft synchronization error if any in-scene placed NetworkObjects were parented under another
NetworkObject
. (#1985) - Fixed issue where
NetworkBehaviourReference
would throw a type cast exception if usingNetworkBehaviourReference.TryGet
and the component type was not found. (#1984) - Fixed
NetworkSceneManager
was not sending scene event notifications for the currently active scene and any additively loaded scenes when loading a new scene inLoadSceneMode.Single
mode. (#1975) - Fixed issue where one or more clients disconnecting during a scene event would cause
LoadEventCompleted
orUnloadEventCompleted
to wait until theNetworkConfig.LoadSceneTimeOut
period before being triggered. (#1973) - Fixed issues when multiple
ConnectionApprovalCallback
s were registered (#1972) - Fixed a regression in serialization support:
FixedString
,Vector2Int
, andVector3Int
types can now be used in NetworkVariables and RPCs again without requiring aForceNetworkSerializeByMemcpy<>
wrapper. (#1961) - Fixed generic types that inherit from NetworkBehaviour causing crashes at compile time. (#1976)
- Fixed endless dialog boxes when adding a
NetworkBehaviour
to aNetworkManager
or vice-versa. (#1947) - Fixed
NetworkAnimator
issue where it was only synchronizing parameters if the layer or state changed or was transitioning between states. (#1946) - Fixed
NetworkAnimator
issue where when it did detect a parameter had changed it would send all parameters as opposed to only the parameters that changed. (#1946) - Fixed
NetworkAnimator
issue where it was not always disposing theNativeArray
that is allocated when spawned. (#1946) - Fixed
NetworkAnimator
issue where it was not taking the animation speed or state speed multiplier into consideration. (#1946) - Fixed
NetworkAnimator
issue where it was not properly synchronizing late joining clients if they joined whileAnimator
was transitioning between states. (#1946) - Fixed
NetworkAnimator
issue where the server was not relaying changes to non-owner clients when a client was the owner. (#1946) - Fixed issue where the
PacketLoss
metric for tools would return the packet loss over a connection lifetime instead of a single frame. (#2004)