The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Additional documentation and release notes are available at [Multiplayer Documentation](https://docs-multiplayer.unity3d.com). ## [1.0.0-pre.8] - 2022-04-27 ### Changed - `unmanaged` structs are no longer universally accepted as RPC parameters because some structs (i.e., structs with pointers in them, such as `NativeList<T>`) can't be supported by the default memcpy struct serializer. Structs that are intended to be serialized across the network must add `INetworkSerializeByMemcpy` to the interface list (i.e., `struct Foo : INetworkSerializeByMemcpy`). This interface is empty and just serves to mark the struct as compatible with memcpy serialization. For external structs you can't edit, you can pass them to RPCs by wrapping them in `ForceNetworkSerializeByMemcpy<T>`. (#1901) ### Removed - Removed `SIPTransport` (#1870) - Removed `ClientNetworkTransform` from the package samples and moved to Boss Room's Utilities package which can be found [here](https://github.com/Unity-Technologies/com.unity.multiplayer.samples.coop/blob/main/Packages/com.unity.multiplayer.samples.coop/Utilities/Net/ClientAuthority/ClientNetworkTransform.cs). ### Fixed - Fixed `NetworkTransform` generating false positive rotation delta checks when rolling over between 0 and 360 degrees. (#1890) - Fixed client throwing an exception if it has messages in the outbound queue when processing the `NetworkEvent.Disconnect` event and is using UTP. (#1884) - Fixed issue during client synchronization if 'ValidateSceneBeforeLoading' returned false it would halt the client synchronization process resulting in a client that was approved but not synchronized or fully connected with the server. (#1883) - Fixed an issue where UNetTransport.StartServer would return success even if the underlying transport failed to start (#854) - Passing generic types to RPCs no longer causes a native crash (#1901) - Fixed an issue where calling `Shutdown` on a `NetworkManager` that was already shut down would cause an immediate shutdown the next time it was started (basically the fix makes `Shutdown` idempotent). (#1877)
50 lines
1.3 KiB
C#
50 lines
1.3 KiB
C#
#if UNITY_UNET_PRESENT
|
|
#pragma warning disable 618 // disable is obsolete
|
|
using NUnit.Framework;
|
|
using Unity.Netcode.Transports.UNET;
|
|
using UnityEngine;
|
|
using UnityEngine.TestTools;
|
|
|
|
namespace Unity.Netcode.EditorTests
|
|
{
|
|
public class UNetTransportTests
|
|
{
|
|
[Test]
|
|
public void StartServerReturnsFalseOnFailure()
|
|
{
|
|
UNetTransport unet1 = null;
|
|
UNetTransport unet2 = null;
|
|
|
|
try
|
|
{
|
|
// Arrange
|
|
|
|
// We're expecting an error from UNET, but don't care to validate the specific message
|
|
LogAssert.ignoreFailingMessages = true;
|
|
|
|
var go = new GameObject();
|
|
unet1 = go.AddComponent<UNetTransport>();
|
|
unet1.ServerListenPort = 1;
|
|
unet1.Initialize();
|
|
unet1.StartServer();
|
|
unet2 = go.AddComponent<UNetTransport>();
|
|
unet2.ServerListenPort = 1;
|
|
unet2.Initialize();
|
|
|
|
// Act
|
|
var result = unet2.StartServer();
|
|
|
|
// Assert
|
|
Assert.IsFalse(result, "UNET fails to initialize against port already in use");
|
|
}
|
|
finally
|
|
{
|
|
unet1?.Shutdown();
|
|
unet2?.Shutdown();
|
|
}
|
|
}
|
|
}
|
|
}
|
|
#pragma warning restore 618
|
|
#endif
|