#Time of day desync

1 messages · Page 1 of 1 (latest)

compact wadi
#

My friend and I were trying to do some stormy night dogfights when the new update came out. However when we tried, only the host got the correct time so if I hosted it would be night for me and day for my friend and if he hosted it would be night for him and day for me.

versed belfry
#

Time of day desync

versed belfry
cloud topaz
#

same

#

different seats in the heli

wraith hemlock
#

Saw the same thing playing a workshop mission. Daytime for me (the host), night time for the other play with me.

Host log:

📎 Player.log
#

And the other player's log (the one with the wrong time of day):

📎 Player.log
granite juniper
#

From today's SUN2 CAW OP, internet went out, relogged and TOD went from late afternoon to midnight

📎 Player.log
halcyon goblet
#

Do we get bug updates? Like "aknowledged" or something? Cause this really bugs me when i join a lobby and the runway lights and shit are off because its already day for the host

cosmic lava
#

Baha is always busy doing things, he will come around and do bug fixing days. Hes probably on a little break or something rn with 1.10 release

weary wind
fervent night
#

If someone joins the lobby after the mission has begun, they get the correct weather as set by the host

undone solstice
cloud hull
#

Aha, the time syncing bit was in a coroutine that only ran in public_testing versions

#

Fixed in 1.10.1

versed belfry
#

Haha nice

spark iris
#

This issue is back in some form. For late joiners it's fine, but for those who were ready before the mission started, they have the wrong ToD. Currently it's reproducable for the CAW Qual mission, but I'm working on making a simpler one to reproduce it.

#

@undone solstice @ruby torrent

#

^ JohnnyEnglish

ruby torrent
undone solstice
spark iris
#

But to recap, if you host a mission, anyone who is in the lobby when the mission starts will see a different ToD from host. Late joiners see it fine, so leaving and rejoining does indeed fix it.

It's most visible in the Both mission in that campaign. It's morning for the host, pitch dark for everyone else.

arctic shell
ruby torrent
#

Something I realised we didn't test was to see if the time sync bug occurs when someone is not in a slot when the host starts the server, but has already joined the server.

spark iris
#

Safe bet that doesn't matter. But for reference, we were usually in the slots and readied up.

serene void
gleaming hazel
#

mine was desynced on the first one and it was just night

#

i disconnected, rejoined and the time of day seems to have matched the host again

solar tartan
#

This seems to be caused by having a custom latitude and/or longitude in a mission

#

Happened to clients playing my custom missions with custom latitude and longitude settings, they joined before mission start. I don't think it's an issue if the mission creator doesn't configure latitude and longitude, but can't really test this myself

#

Could also be caused by custom ToD, though

#

If anyone wants to test this with me, you can ping me around 1800 EU time

undone solstice
#

AC04 is in shambles

shell vault
#

I too am experiencing this.

#

Time does not advance. Initial time matches but the time does not progress for other players, only the host. Time of day was set by mission parameters, not by the lobby.

ornate kraken
#

For what it's worth, I’ve also built a mission with time progression that seems to work reliably for the host as well as clients, based on player feedback.~~ not just for me as the host.~~

The mission sets both weather and time at the start, and time progression is tied to objectives. I recently changed it so that time is frozen until players approach a specific waypoint. At that point, it sets the time scale to 1 and fast-forwards to sunrise. Other players confirmed that this approach works well for them too.

However, in another mission we played (made by someone else) that also enforced time, weather, and location, players told me it appeared to be midday for them while I was still just before sunrise for the entire duration of the mission.

So maybe this issue might be mission specific?

shell vault
#

Well either way it's not working the way it should but thank you for that detail because it could help Baha narrow down what's causing it.

In my case, it was set by the mission, and there was no meddling with time scale. Perhaps for all other players but the host, their client thinks time is not supposed to progress.

ornate kraken
#

Correction: It DOES work for me as a host. So it does function like intended, at least in my case. I wasn't thinking straight, sorry for the confusion. Edited my message above.

prime apex
#

Is there a way to avoid this from happening

#

apparently the host has to set the time after starting the mission

solar tartan
#

fixed this for my missions

solar tartan
prime apex
#

okay thx

shell vault
hexed holly
#

This still happens, has been an issue for a lot of people I’ve been playing with

weary wind
#

Have been experiencing this with a friend, the ToD is sync'd correctly if he quits and rejoins after the mission has started.

shell vault
#

Work-around:

  • Set time speed to 1 at mission start using a trigger/event and this causes time to progress correctly across all clients.
weary wind
#

yeah, sadly not my mission though. I will keep that in mind for when I start making them

tender scarab
tender scarab
#

^ that actually isn't working, I do not have custom coordinates, removed custom weather and set the time to just "night" and every other client sees a different time of day

solar tartan
tender scarab
solar tartan
#

set the custom coordinates to 0, 0, you can enable custom weather

tender scarab
#

I’ll give that a shot, thank you!

cloud hull
#

Fixed in v1.13.0p6