TimeSyncMessage is sent reliably, so a late one resets the client clock backwards and stalls its NetworkTransforms
Los mantenedores suelen responder en 3 días
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 52/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- C#
- Estrellas
- 2.3k
- Forks
- 465
- Merge medio
- 3 d 12 h
- PR fusionados (30 d)
- 39
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de Unity-Technologies/com.unity.netcode.gameobjects
-
NetworkTransform: half-float base update dropped as out of order when UseUnreliableDeltas is on, so later deltas decode ~2 m offPosiblemente ocupada @NoelStephensUnity la tomó hace 8 días. Abiertoport:3.x-completed priority:medium stat:imported type:bug
Dificultad 4/5 3-5 días Aptitud para principiantes 57/100
Unity-Technologies/com.unity.netcode.gameobjects#4248 ·
Los mantenedores suelen responder en 3 días
-
Tracking type:feature-2.x
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Unity-Technologies/com.unity.netcode.gameobjects#3870 · 5 comentarios ·
Los mantenedores suelen responder en 3 días
-
Please error, or at least warn, when a managed type is included in INetworkSerializeByMemcpyAbiertoTracking type:feature
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
Unity-Technologies/com.unity.netcode.gameobjects#3830 · 7 comentarios ·
Los mantenedores suelen responder en 3 días
-
priority:medium stat:imported type:feature type:feature-2.x
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
Unity-Technologies/com.unity.netcode.gameobjects#3706 · 5 comentarios ·
Los mantenedores suelen responder en 3 días
-
Client NetworkObjects experience Awake, Start, OnEnable, and TriggerEnter, CollisionEnter at world 0,0,0 upon instantiationQuizá libre de nuevo @NoelStephensUnity la tomó hace 492 días y no hay ningún pull request abierto. Abiertopriority:medium stat:imported type:bug
Unity-Technologies/com.unity.netcode.gameobjects#3553 · 3 comentarios · 2 reacciones · 1 asignado ·
Los mantenedores suelen responder en 3 días
Todos los issues de Unity-Technologies/com.unity.netcode.gameobjects
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
umbraco/Umbraco.Automate#612 ·
Los mantenedores suelen responder en 1 día
-
崩溃日志只按 CRLF 分行Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
PCL-Community/PCL-CE#3872 ·
Los mantenedores suelen responder en 1 día
-
type:task ux
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
elsa-workflows/elsa-foundation#5253 ·
Los mantenedores suelen responder en 1 día