TimeSyncMessage is sent reliably, so a late one resets the client clock backwards and stalls its NetworkTransforms
Mantenedores costumam responder em até 3 dias
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 52/100
- Tipo de issue
- Bug
- Clareza
- Claramente especificada
- Status de atividade
- Ativa
- Domínio
- distributed-systems, networking
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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.
- Linguagem predominante
- C#
- Estrelas
- 2.3k
- Forks
- 465
- Merge médio
- 3d 12h
- PRs com merge (30d)
- 39
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais 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 offTalvez já em andamento @NoelStephensUnity assumiu há 8 dias. Abertaport:3.x-completed priority:medium stat:imported type:bug
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 57/100
Unity-Technologies/com.unity.netcode.gameobjects#4248 ·
Mantenedores costumam responder em até 3 dias
-
Tracking type:feature-2.x
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 35/100
Unity-Technologies/com.unity.netcode.gameobjects#3870 · 5 comentários ·
Mantenedores costumam responder em até 3 dias
-
Tracking type:feature
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 48/100
Unity-Technologies/com.unity.netcode.gameobjects#3830 · 7 comentários ·
Mantenedores costumam responder em até 3 dias
-
priority:medium stat:imported type:feature type:feature-2.x
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 42/100
Unity-Technologies/com.unity.netcode.gameobjects#3706 · 5 comentários ·
Mantenedores costumam responder em até 3 dias
-
Client NetworkObjects experience Awake, Start, OnEnable, and TriggerEnter, CollisionEnter at world 0,0,0 upon instantiationTalvez livre de novo @NoelStephensUnity assumiu há 492 dias e não há nenhum pull request aberto. Abertapriority:medium stat:imported type:bug
Unity-Technologies/com.unity.netcode.gameobjects#3553 · 3 comentários · 2 reações · 1 responsável ·
Mantenedores costumam responder em até 3 dias
Todas as issues de Unity-Technologies/com.unity.netcode.gameobjects
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
umbraco/Umbraco.Automate#612 ·
Mantenedores costumam responder em até 1 dia
-
崩溃日志只按 CRLF 分行Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
PCL-Community/PCL-CE#3872 ·
Mantenedores costumam responder em até 1 dia
-
type:task ux
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
elsa-workflows/elsa-foundation#5253 ·
Mantenedores costumam responder em até 1 dia