Correct, first column is UTC and second column is your Local time
1 Like
well darn
00:00 utc was only 15 minutes ago PST *if I havenât gotten something backwards, which happens
that might have been a good screen shot to get
*or now that I think again UTC is forward from here so 00:00 would be 17:00 PST (17:00 + 7hrs)?
1 Like
I will try to do this today! But I have a hard time knowing what time I need to be on in EST over here stateside.
https://project-skyscraper.vectorcmdr.xyz/tools/?window_sync
Left column is UTC and right column will be the time it is for you locally.
00:00 UTC, 08:00 UTC and 16:00 UTC seem to be the times people enjoy aiming for, but any time here will do really. The synchronization time is every 16 minutes.
5 Likes
I have created a vibe coded artifact to show you what I mean, and also help out the community. I have hosted it on a site that hosts Claude HTMLs.
By standing at your 0,0 location, the planet time in your visor should sync up with the planet time clock on the site. Mine does, and it has about a 1-second margin of error.
I have added a manual converter that allows operators to check any specific times in either direction.
You can check the predicted wave shifts from your site to get in-game times. For example, the next three predicted wave shift times are as follows:
- 14:24:00 UTC = 13:12 Shared Dream Time
- 14:40:00 UTC = 02:00 Shared Dream Time
- 14:56:00 UTC = 14:48 Shared Dream Time
This is temporary. I figure you can make a much better clock for your OPS Centre.
EDIT: Removed 15 and 16 minute chart panel links since their panels werenât built into the HTML and didnât show up.
My guess is we should be taking screenshots at the predicted wave shift times. My original charts for 15 and 16 minutes were built as examples of the formula. The formula holds down to the second throughout the day. Unless you move away from the 0,0 coords.
Here is the site:
Example:
5 Likes
I know yesterday people were talking about 3 Big Sync times. Iâm not sure if thatâs still relevant or not because any screenshot of those 16-minute intervals will do. I just woke up and have some scrolling to do. But if Iâm reading correctly that youâre east coast, the next Big Sync is 12 noon for you
5 Likes
Definitely not, no. At the time of your post, it was ~14:15 UTC, so 15 minutes before that would just have been about 14:00.
4 Likes
Youâre the best, man, thanks! Playing catch-up at work and the little one at home has kept me too busy to be up to speed. 
much obliged!
4 Likes
No worries, was away for 24 hours myself so when I came in last night I found all the different timestamps and time regions very confusing too, now that Iâm on the other side of confusion the least I can do is help others get past that hurdle when I can <3
1 Like
I sure hope everyone is still sitting at 0,0 coords
I vote for the 24:00 UTC sync (especially since many of us already saved that data last night)
6 Likes
I vote for this too mostly because I already took my snaps for this time in UTC and it seems a lot of other folk did too.
However I donât think it would be too bad if we have a few differing UTC times that other groups of operators have been taking snaps of at the same time.
If we had a batch set from 00:00, 08:00 and 16:00 (all UTC times) I think this would be just as beneficial to system and these times might suit other operators more.
Here are those times in your local time region
00:00 UTC = 12:00:00 AM
08:00 UTC = 8:00:00 AM
16:00 UTC = 4:00:00 PM
Folks have been submitting to a google form as well so maybe @YourBasicMaths can use the data from those entries to see what times had the largest operator attach rate with which to submit sync data from.
7 Likes
Just to confirm, is that the one coming up in an hour, or one that Iâm about to miss in two minutes?
2 Likes
But what if that is why System keeps failing? Maybe System needs to try a different sync time.
Since Archie just sent an email with the words âas a wholeâ bolded, what if itâs supposed to be at 18:00 UTC? Thatâs the only time in a 24 hour period where the dream time matches the UTC time with a whole number. I realize we are reading âas a wholeâ to mean all of us, but what if itâs a double meaning?
6 Likes
thank you
1 Like
@vector_cmdr says we have 9 submissions from last nightâs 00:00 UTC
4 Likes
Cool, doesnât look like everyone used the sheet either or it was posted after they took them and went to bed etc.
Counting the etarc posts from last night, there were 13 posts reporting 00:00 UTC with an in-game time of 18:00
Only some are slightly off by 1-6 mins in-game time due to not getting the screenshot button pressed on the second the clock ticked over to 00:00 UTC, but this is within the drift time error of 16 seconds that System said was acceptable. Probably why they gave us that margin for error in the first place.
3 Likes
Same analysis again, 18:00 at 00:00 UTC world, 1 minute UTC sync interval checks.
But, Iâm still thinking there might be other worlds with different time at 00:00 UTC.
1 Like
so should we be posting screen shots in order to link them with the googledocs sync data?
Iâve been taking the option of not submitting the screen shots with my sync data submissions mostly because I donât have a link for them.
1 Like
Itâs entirely optional according to the submission form so I wouldnât worry too much about it if you canât link to a photo. Others have posted them here first, then used the link from the discourse forums image url or post url when submitting to the form.
If you have no way of transferring images to web browser for posting or should image posting on the site require a certain trust level based on activity, donât worry too much about it as the image segment of the form is deemed optional.
3 Likes
My itchy F12 trigger finger could not wait another second or 2âŚ
1 Like