Change log
[0.4.1] - 2020-09-10
New features
- Added
NetworkDriver.GetEventQueueSizeForConnection
which allows you to check how many pending events a connection has.
Changes
Fixes
- Fixed a compatibility isue with DOTS Runetime.
Upgrade guide
[0.4.0-preview.3] - 2020-08-21
New features
- Added a new fragmentation pipeline which allows you to send messages larger than one MTU. If the
FragmentationPipelineStage
is part of the pipeline you are trying to send with theNetworkDriver
will allow arequiredPayloadSize
larger than one MTU to be specified and split the message into multiple packages.
Changes
- The methods to read and write strings in the
DataStreamReader
/DataStreamWriter
have been changed to useFixedString<N>
instead ofNativeString<N>
. The name of the methods have also changed fromReadString
toReadFixedString64
- and similar changes for write and the packed version of the calls. The calls supportFixedString32
,FixedString64
,FixedString128
,FixedString512
andFixedString4096
. - Minimum required unity version has changed to 2020.1.2.
Fixes
Upgrade guide
The data stream methods for reading and writing strings have changed, they now take FixedString64
instead of NativeString64
and the names have changed as follows: DataStreamReader.ReadString
-> DataStreamReader.ReadFixedString64
, DataStreamReader.ReadPackedStringDelta
-> DataStreamReader.ReadPackedFixedString64Delta
, DataStreamWriter.WriteString
-> DataStreamWriter.WriteFixedString64
, DataStreamWriter.WritePackedStringDelta
-> DataStreamWriter.WritePackedFixedString64Delta
.
The transport now requires Unity 2020.1.2.
[0.3.1-preview.4] - 2020-06-05
New features
Changes
- Added a new
requiredPayloadSize
parameter toBeginSend
. The required size cannot be larger thanNetworkParameterConstants.MTU
. - Added errorcode parameter to a
network_set_nonblocking
,network_set_send_buffer_size
andnetwork_set_receive_buffer_size
inNativeBindings
. - Additional APIs added to
NativeBindings
:network_set_blocking
,network_get_send_buffer_size
,network_get_receive_buffer_size
,network_set_receive_timeout
,network_set_send_timeout
. - Implemented
NetworkEndPoint.AddressAsString
.
Fixes
- Fixed an issue in the reliable pipeline which would cause it to not recover if one end did not receive packages for a while.
- Fixed
NetworkInterfaceEndPoint
andNetworkEndPoint
GetHashCode
implementation. - Fixed invalid use of strings when specifying the size of socket buffers in the native bindings
Upgrade guide
[0.3.0-preview.6] - 2020-02-24
New features
Changes
- Pipelines are now registered by calling
NetworkPipelineStageCollection.RegisterPipelineStage
before creating aNetworkDriver
. The built-in pipelines do not require explicit registration. The interface for implementing pipelines has been changed to support this. - NetworkDriver is no longer a generic type. You pass it an interface when creating the
NetworkDriver
, which means you can switch between backends without modifying all usage of the driver. There is a newNetworkDriver.Create
which creates a driver with the defaultNetworkInterface
. It is also possible to create anew NetworkDriver
by passing aNetworkInterface
instance as the first argument. NetworkDriver.Send
is replaced byBeginSend
andEndSend
. This allows us to do less data copying when sending messages. The interface for implementing new network interfaces has been changed to support this.DataStreamReader
andDataStreamWriter
no longer owns any memory. They are just reading/writing the data of aNativeArray<byte>
.DataStreamWriter
has explicit types for all Write methods.DataStreamReader.Context
has been removed.- Error handling for
DataStreamWriter
has been improved, on failure it returns false and setsDataStreamWriter.HasFailedWrites
to true.DataStreamReader
returns a default value and setsDataStreamReader.HasFailedReads
to true.DataStreamReader
will throw an exception instead of returning a default value in the editor. - IPCManager is no longer public, it is still possible to create a
NetworkDriver
with aIPCNetworkInterface
. - Added
NetworkDriver.ScheduleFlushSend
which must be called to guarantee that messages are send before next call toNetworkDriver.ScheduleUpdate
. - Added
NetworkDriver.LastUpdateTime
to get the update time theNetworkDriver
used for the most recent update. - Removed the IPC address family, use a IPv4 localhost address instead.
Fixes
- Fixed a memory overflow in the reliability pipeline.
- Made the soaker report locale independent.
Upgrade guide
Creation and type of NetworkDriver
has changed, use NetworkDriver.Create
or pass an instance of a NetworkInterface
to the NetworkDriver
constructor.
NetworkDriver.Send
has been replaced by a pair of NetworkDriver.BeginSend
and NetworkDriver.EndSend
. Calling BeginSend
will return a DataStreamWriter
to which you write the data. The DataStreamWriter
is then passed to EndSend
.
All write calls in DataStreamWriter
need an explicit type, for example Write(0)
should be replaced by WriteInt(0)
.
DataStreamWriter
no longer shares current position between copies, if you call a method which writes you must pass it by ref for the modifications to apply.
DataStreamWriter
no longer returns a DeferedWriter, you need to take a copy of the writer at the point you want to make modifications and use the copy to overwrite data later.
DataStreamWriter
is no longer disposable. If you use the allocating constructor you need to use Allocator.Temp
, if you pass a NativeArray<byte>
to the constructor the NativeArray
owns the memory.
DataStreamReader.Context
no longer exists, you need to pass the DataStreamReader
itself by ref if you read in a different function.
The interface for network pipelines has been changed.
The interface for network interfaces has been changed.
[0.2.3-preview.0] - 2019-12-12
New features
Changes
- Added reading and write methods for NativeString64 to DataStream.
Fixes
Upgrade guide
[0.2.2-preview.2] - 2019-12-05
New features
Changes
- Added a stress test for parallel sending of data.
- Upgraded collections to 0.3.0.
Fixes
- Fixed a race condition in IPCNetworkInterface.
- Changed NetworkEventQueue to use UnsafeList to get some type safety.
- Fixed an out-of-bounds access in the reliable sequenced pipeline.
- Fixed spelling and broken links in the documentation.
Upgrade guide
[0.2.1-preview.1] - 2019-11-28
New features
Changes
Fixes
- Added missing bindings for Linux and Android
Upgrade guide
[0.2.0-preview.4] - 2019-11-26
New features
Changes
- Added support for unquantized floats to
DataStream
class. - Added
NetworkConfigParameter.maxFrameTimeMS
so you to allow longer frame times when debugging to prevent disconnections due to timeout. - Allow "1.1.1.1:1234" strings when parsing the IP string in the NetworkEndPoint class, it will use the port part when it's present.
- Reliable pipeline now doesn't require parameters passed in (uses default window size of 32)
- Added Read/Write of ulong to
DataStream
. - Made it possible to get connection state from the parallel NetworkDriver.
- Added
LengthInBits
to theDataStreamWriter
.
Fixes
- Do not push data events to disconnected connections. Fixes an error about resetting the queue with pending messages
- Made the endian checks in
DataStream
compatible with latest version of burst.
Upgrade guide
[0.1.2-preview.1] - 2019-07-17
New features
- Added a new Ping-Multiplay sample based on the Ping sample
- Created to be the main sample for demonstrating Multiplay compatibility and best practices (SQP usage, IP binding, etc.)
- Contains both client and server code. Additional details in readme in
/Assets/Samples/Ping-Multiplay/
.
- DedicatedServerConfig: added arguments for
-fps
and-timeout
- NetworkEndPoint: Added a
TryParse()
method which returns false if parsing fails- Note: The
Parse()
method returns a default IP / Endpoint if parsing fails, but a method that could report failure was needed for the Multiplay sample
- Note: The
- CommandLine:
- Added a
HasArgument()
method which returns true if an argument is present - Added a
PrintArgsToLog()
method which is a simple way to print launch args to logs - Added a
TryUpdateVariableWithArgValue()
method which updates a ref var only if an arg was found and successfully parsed
- Added a
Changes
- Deleted existing SQP code and added reference to SQP Package (now in staging)
- Removed SQP server usage from basic Ping sample
- Note: The SQP server was only needed for Multiplay compatibility, so the addition of Ping-Multiplay allowed us to remove SQP from Ping
Fixes
- DedicatedServerConfig: Vsync is now disabled programmatically if requesting an FPS different from the current screen refresh rate
Upgrade guide
[0.1.1-preview.1] - 2019-06-05
New features
- Moved MatchMaking to a package and supporting code to a separate folder.
Fixes
- Fixed an issue with the reliable pipeline not resending when completely idle.
Upgrade guide
[0.1.0-preview.1] - 2019-04-16
New features
- Added network pipelines to enable processing of outgoing and incomming packets. The available pipeline stages are
ReliableSequencedPipelineStage
for reliable UDP messages andSimulatorPipelineStage
for emulating network conditions such as high latency and packet loss. See the pipeline documentation for more information. - Added reading and writing of packed signed and unsigned integers to
DataStream
. These new methods use huffman encoding to reduce the size of transfered data for small numbers.
Changes
- Enable Burst compilation for most jobs
- Made it possible to get the remote endpoint for a connection
- Replacing EndPoint parsing with custom code to avoid having a dependency on System.Net
- Change the ping sample command-line parameters for server to -port and -query_port
- For matchmaking - use an Assignment object containing the ConnectionString, the Roster, and an AssignmentError string instead of just the ConnectionString.
Fixes
- Fixed an issue with building iOS on Windows
- Fixed inconsistent error handling between platforms when the network buffer is full
Upgrade guide
Unity 2019.1 is now required.
BasicNetworkDriver
has been renamed to GenericNetworkDriver
and a new UdpNetworkDriver
helper class is also available.
System.Net EndPoints can no longer be used as addresses, use the new NetworkEndpoint struct instead.