NetworkTransform: half-float base update dropped as out of order when UseUnreliableDeltas is on, so later deltas decode ~2 m off

未關閉
#4,248 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 3 天內回覆

@NoelStephensUnity 已經在處理了。

開始於 2026年11月13日。

  • #4252 來自 @NoelStephensUnity —— 未關閉

評估

難度
4/5
預估耗時
3-5 天
新手友好度
57/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
csharp, unity
領域
networking

研究方向

Start in NetworkTransform.cs at the out-of-order check in OnNetworkStateChanged (around line 3326 in 2.13.3) and the serialization logic around lines 739–747 that marks half-float base updates reliable. Trace how SynchronizeBaseHalfFloat updates NetworkDeltaPosition when a late state arrives. Done when a late base is retained or applied so subsequent deltas decode against it; verify with the described jitter and packet-loss reproduction.

由索引模型根據 Issue 內容生成。

描述

port:3.x-completed priority:medium stat:imported type:bug
Description

With UseHalfFloatPrecision and UseUnreliableDeltas both on, a non-authority NetworkTransform can lose a half-float base update and then decode every following delta against the old base. The object is drawn about 2 m off (one MaxDeltaBeforeAdjustment step) until the next unreliable frame sync, up to a second later.

How it happens (line numbers from 2.13.3; the same code is in develop-3.x.x today):

  1. When an axis's delta reaches NetworkDeltaPosition.MaxDeltaBeforeAdjustment (2 m), the delta collapses into a new base. That state is flagged SynchronizeBaseHalfFloat and sent reliably (NetworkTransformState.NetworkSerialize, NetworkTransform.cs:739-747: UseHalfFloatPrecision && NetworkDeltaPosition.CollapsedDeltaIntoBase → ReliableSequenced = true).
  2. The deltas that follow go unreliably. Under jitter or a lost packet, a newer unreliable delta can arrive before the reliable base update.
  3. When the base update then arrives, it has an older tick than the state already applied. OnNetworkStateChanged drops it (NetworkTransform.cs:3326):
    if (UseUnreliableDeltas && oldState.NetworkTick > newState.NetworkTick && !newState.FlagStates.IsTeleportingNextFrame && !newState.FlagStates.UnreliableFrameSync)
    {
        return;
    }
    
    Teleports and frame syncs are exempt, but a base sync isn't.
  4. The non-authority's NetworkDeltaPosition keeps the old base, so every later half-float delta decodes about 2 m off until a frame sync corrects it.
Reproduce Steps
  1. A player prefab with an owner-authoritative NetworkTransform: UseHalfFloatPrecision on, UseUnreliableDeltas on, position synced on all axes, interpolation on.
  2. Host + 1 client (client-server). Simulate a poor connection on the host: about 75 ms delay with ±20 ms jitter and 2% packet loss (Unity Transport's simulator pipeline, or the Multiplayer Tools network simulator).
  3. The client walks in a straight line at about 4.5 m/s for 20–30 s.
  4. On the host, compare its copy of the client's player with the client's real position (log both every frame).
Actual Outcome

The host's copy usually trails by about 0.6 m, but every few seconds it jumps 2 m or more off for up to a second. In our measurements it was 2.5–4.6 m behind during those stretches. Logging NetworkDeltaPosition on both sides during one of them: the host's base on the walking axis was 4.17 m while the client's was 6.25 m (one 2 m step plus the delta).

Expected Outcome

A late base update is still applied (at least its base), so later deltas decode against the right base. Two possible fixes:

  • exempt SynchronizeBaseHalfFloat states from the out-of-order rule, as teleports and frame syncs are;
  • or apply the base of a dropped state to NetworkDeltaPosition even when its position is ignored.
Screenshots

None. The numbers above come from per-frame logs.

Environment
  • OS: Windows 11 Pro
  • Unity Version: 6000.3.27f1
  • Netcode Version: 2.13.3 (also present in develop-3.x.x and 3.2.0: the same check is at NetworkTransform.cs:3345 there)
  • Netcode Commit: the v2.13.3 release
  • Netcode Topology: Client-Server (host)
Additional Context
  • Unity Transport 2.7.4.
  • With full-precision positions (half floats off, unreliable deltas kept) the host's copy stays within 0.82 m over the same walk, so the drops come from the base sync.
  • Our workaround: never combine half floats with unreliable deltas on a NetworkTransform.
  • Earlier half-float fixes (#2791, #2922) don't cover this ordering case, as far as we can tell.
主要語言
C#
星號
2.3k
分支
465
平均合併
3 天 12 小時
30 天內合併 PR
39

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

Unity-Technologies/com.unity.netcode.gameobjects 的其他 Issue

查看 Unity-Technologies/com.unity.netcode.gameobjects 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。