TimeSyncMessage is sent reliably, so a late one resets the client clock backwards and stalls its NetworkTransforms
メンテナーはふだん 3 日以内に返信
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 52/100
- issue の種類
- バグ
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
調査の方向性
Start by reading MessageDelivery.cs, NetworkTimeSystem, and NetworkTransform.cs around TickUpdate; the issue identifies these as the points where delivery, clock resets, and skipped transform ticks interact. Reproduce with the stated packet loss and delay, logging ServerTime.Tick and host-observed transform updates. Done means delayed syncs no longer cause backwards clock resets and owned transforms continue sending under the reproduction conditions.
索引モデルが issue の本文から書いたものです。
説明
Description
TimeSyncMessage is sent reliably, although MessageDelivery says it's meant to stay unreliable. Under packet loss a time sync arrives late. The client takes its old host tick as current, its time offset passes HardResetThresholdSec (0.2 s by default), and NetworkTimeSystem hard-resets the client's clock backwards.
After that, NetworkTransformTickRegistration.TickUpdate skips while CurrentTick <= m_LastTick. Every NetworkTransform the client owns therefore sends nothing until its clock passes the last tick it sent. Teammates see that player freeze for up to about 0.5 s and then jump.
Details (line numbers from 2.13.3; the same code is in develop-3.x.x today):
MessageDelivery.cs: the summary ofk_SkipMessageTypessays "Skip the time sync messages since it has always used unreliable network delivery". But the set holds onlyNamedMessageandUnnamed. SoUpdateMessageTypesgivesTimeSyncMessageReliableFragmentedSequenced, andNetworkTimeSystemsends it withMessageDeliveryType<TimeSyncMessage>.DefaultDelivery.NetworkTimeSystem: a sync whose send tick is old by the time it arrives produces a desired offset more than 0.2 s from the current one, so the clock is hard-reset to it, back in time.NetworkTransform.cs:4765(NetworkTransformTickRegistration.TickUpdate):if (CurrentTick <= m_LastTick)with the comment// TODO FIX: The local NetworkTickSystem can invoke with the same network tick as before. After a backward reset, this skips every tick until the clock catches up.
Reproduce Steps
- Host + 1 client (client-server), with the simulated poor connection on the host: about 75 ms delay, ±20 ms jitter and 2% packet loss.
- On the client, log
NetworkManager.ServerTime.Tickevery frame for a few minutes. - Give the client an owner-authoritative
NetworkTransformthat moves continuously, and log on the host when its state updates arrive.
Actual Outcome
About twice a minute the client's ServerTime.Tick steps backwards (one example: 568 → 548). The client's NetworkTransform sends nothing until its tick passes 568 again, so the host sees it stand still for up to about 0.5 s and then jump.
Expected Outcome
A delayed time sync doesn't move a client's clock backwards, and its transforms keep sending. Possible fixes:
- send
TimeSyncMessageunreliably (add it tok_SkipMessageTypes, as the comment intends), so a lost one is replaced by the next a second later instead of arriving late; - or ignore a time sync older than the last one applied;
- and/or let
NetworkTransformTickRegistrationrecover from a backward tick (resetm_LastTick) instead of skipping until the clock catches up.
Screenshots
None. The numbers 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) - Netcode Commit: the v2.13.3 release
- Netcode Topology: Client-Server (host)
Additional Context
- Unity Transport 2.7.4.
- Our workaround: each client raises
NetworkTimeSystem.HardResetThresholdSecto 1 s when it starts. With that, the backward resets went from about two a minute to none in three minutes under the same conditions.
- 主要言語
- C#
- スター
- 2.3k
- フォーク
- 465
- 平均マージ
- 3日 12時間
- マージ済み PR(30日)
- 39
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
Unity-Technologies/com.unity.netcode.gameobjects のほかの issue
-
NetworkTransform: half-float base update dropped as out of order when UseUnreliableDeltas is on, so later deltas decode ~2 m off対応中かも @NoelStephensUnity が 8 日前に担当しました。 オープンport:3.x-completed priority:medium stat:imported type:bug
難易度 4/5 3〜5日 初心者へのやさしさ 57/100
Unity-Technologies/com.unity.netcode.gameobjects#4248 ·
メンテナーはふだん 3 日以内に返信
-
Tracking type:feature-2.x
難易度 5/5 1週間以上 初心者へのやさしさ 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 日前に担当しましたが、オープン中のプルリクエストはありません。 オープンpriority:medium stat:imported type:bug
Unity-Technologies/com.unity.netcode.gameobjects#3553 · コメント 3 件 · リアクション 2 件 · 担当者 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 日以内に返信