NetworkTransform: half-float base update dropped as out of order when UseUnreliableDeltas is on, so later deltas decode ~2 m off
维护者通常 3 天内回复
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 57/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 领域
- 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 内容生成。
描述
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):
- When an axis's delta reaches
NetworkDeltaPosition.MaxDeltaBeforeAdjustment(2 m), the delta collapses into a new base. That state is flaggedSynchronizeBaseHalfFloatand sent reliably (NetworkTransformState.NetworkSerialize,NetworkTransform.cs:739-747:UseHalfFloatPrecision && NetworkDeltaPosition.CollapsedDeltaIntoBase→ReliableSequenced = true). - The deltas that follow go unreliably. Under jitter or a lost packet, a newer unreliable delta can arrive before the reliable base update.
- When the base update then arrives, it has an older tick than the state already applied.
OnNetworkStateChangeddrops it (NetworkTransform.cs:3326):
Teleports and frame syncs are exempt, but a base sync isn't.if (UseUnreliableDeltas && oldState.NetworkTick > newState.NetworkTick && !newState.FlagStates.IsTeleportingNextFrame && !newState.FlagStates.UnreliableFrameSync) { return; } - The non-authority's
NetworkDeltaPositionkeeps the old base, so every later half-float delta decodes about 2 m off until a frame sync corrects it.
Reproduce Steps
- A player prefab with an owner-authoritative
NetworkTransform:UseHalfFloatPrecisionon,UseUnreliableDeltason, position synced on all axes, interpolation on. - 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).
- The client walks in a straight line at about 4.5 m/s for 20–30 s.
- 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
SynchronizeBaseHalfFloatstates from the out-of-order rule, as teleports and frame syncs are; - or apply the base of a dropped state to
NetworkDeltaPositioneven 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.xand 3.2.0: the same check is atNetworkTransform.cs:3345there) - 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
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
Unity-Technologies/com.unity.netcode.gameobjects 的其他 Issue
-
TimeSyncMessage is sent reliably, so a late one resets the client clock backwards and stalls its NetworkTransforms可能已有人在做 @reginaldalfret 于 7 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 52/100
Unity-Technologies/com.unity.netcode.gameobjects#4249 ·
维护者通常 3 天内回复
-
Tracking type:feature-2.x
难度 5/5 一周以上 新手友好度 35/100
Unity-Technologies/com.unity.netcode.gameobjects#3870 · 5 条评论 ·
维护者通常 3 天内回复
-
Tracking type:feature
难度 4/5 3-5 天 新手友好度 48/100
Unity-Technologies/com.unity.netcode.gameobjects#3830 · 7 条评论 ·
维护者通常 3 天内回复
-
priority:medium stat:imported type:feature type:feature-2.x
难度 4/5 3-5 天 新手友好度 42/100
Unity-Technologies/com.unity.netcode.gameobjects#3706 · 5 条评论 ·
维护者通常 3 天内回复
-
Client NetworkObjects experience Awake, Start, OnEnable, and TriggerEnter, CollisionEnter at world 0,0,0 upon instantiation可能重新可做 @NoelStephensUnity 于 492 天前认领,目前没有进行中的 PR。 未关闭priority:medium stat:imported type:bug
Unity-Technologies/com.unity.netcode.gameobjects#3553 · 3 条评论 · 2 个 reaction · 已指派 1 人 ·
维护者通常 3 天内回复
查看 Unity-Technologies/com.unity.netcode.gameobjects 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
umbraco/Umbraco.Automate#612 ·
维护者通常 1 天内回复
-
崩溃日志只按 CRLF 分行未关闭
难度 2/5 1-3 小时 新手友好度 72/100
PCL-Community/PCL-CE#3872 ·
维护者通常 1 天内回复
-
type:task ux
难度 2/5 1-3 小时 新手友好度 72/100
elsa-workflows/elsa-foundation#5253 ·
维护者通常 1 天内回复