Network Transform
Network Transform synchronizes a GameObject's position, rotation, scale, and optional parent. Add it to the object that should move over the network, then choose which peer has authority and which transform properties should be synchronized.
Settings
| Setting | Effect |
|---|---|
| Sync Position | No, Local, or World. Local positions are relative to the active parent; world positions use world space. |
| Sync Rotation | No, Local, or World, with the same space rules as position. |
| Sync Scale | Synchronizes localScale. |
| Sync Parent | Synchronizes SetParent changes when the new parent has a Network Identity. |
| Force Sleep Rigidbody | Forces an attached non-controller Rigidbody to sleep so physics does not fight received transform updates. |
| Interpolate Settings | Chooses whether received position, rotation, and scale values are smoothed. |
| Min Buffer Size | Minimum number of ticks retained for interpolation. |
| Max Buffer Size | Maximum number of ticks retained for interpolation. A larger range absorbs more jitter but can add visual delay. |
| Character Controller Patch | Coordinates a 3D Character Controller while applying received transforms. On the current dev branch it preserves trigger contacts; older versions toggle the controller and can repeat callbacks. |
| Owner Auth | When enabled, the owning client controls the transform. When disabled, the server controls it. |
| Interpolation Timing | Applies interpolation during the selected Unity update phase. Match this to the system that reads or moves the transform. |
| Adaptive Sync | Reduces the send rate while motion can be reconstructed accurately. See Adaptive sync. |
 (1) (1).png)
The Network Transform component
Character Controller observers
Run your movement/input script on the controlling peer. Other peers should display the received pose through Network Transform; a second script calling CharacterController.Move there can fight those updates. Choose authority using your game's ownership/controller rules, including server-controlled characters.
On the current PurrNet dev branch, the Character Controller Patch applies movement through the active controller without disabling and re-enabling it. An unchanged pose does not rebuild contacts, so staying inside one trigger does not repeatedly produce OnTriggerEnter. The received pose remains authoritative when local geometry or Min Move Distance prevents the controller from reaching it. The patch preserves the controller's enabled state and its movement/collision settings.
Movement applied to an observer can still produce local Unity collision/trigger callbacks. Gate gameplay effects to the peer responsible for them. Shape changes, removal, and actual exits/re-entries can legitimately change contacts.
For versions where the patch toggles the controller, repeated trigger entry is a known limitation of that patch. A workaround is to disable the Character Controller on observers and use an ordinary collider for the interactions those observers need. Follow Unity's collider/Rigidbody requirements for that setup; do not add a Rigidbody to an active Character Controller. Keep Network Transform and its interpolation enabled, and check that no observer movement script still writes the transform. The controller/collider choice does not require removing network interpolation.
Delivery and packet loss
Regular transform updates are batched and sent over an unreliable channel to avoid reliable-channel backlog during continuous movement. Current state is delta-compressed against receiver-acknowledged baselines. If a packet is lost, a later update can recover from an acknowledged state instead of permanently applying a delta to the wrong baseline.
PurrNet sends authoritative full-state updates when needed, such as when an observer is added, control changes, or you call ForceSync. In normal use, you do not need to manually resend transforms after packet loss.
ForceSync sends the latest complete state and bypasses the normal compression optimizations:
// Send a full state to every observer.
networkTransform.ForceSync();
// Send a full state to one player.
networkTransform.ForceSync(targetPlayer);Use it for exceptional state changes or recovery logic, not every frame.
Network Transform keeps its regular updates below the transport MTU. The Network Manager's unreliable fragmentation setting mainly matters to other oversized PurrNet messages; transform batching is already MTU-aware.