Dev console server output timestamps are nonsensical again

[RuizuKun_Dev (Kitsune)]

Reproduction Steps

1. Publish game
2. Playtest
3. Observe

Nonsensical Timestamps

Nonsensical Timestamps.rbxl (28.6 KB)

Code

local iteration = 0

while true do
	task.wait(1)
	iteration += 1
	task.defer(print, "print", iteration)
	task.defer(warn, "warn", iteration)
	task.defer(error, "error "..iteration)
end

Expected Behavior
I expect the timestamps to make sense and accurate.

Actual Behavior

The time doesn’t make sense and makes it extremely difficult and frustrating to debug our games properly when using print, warn and error

Issue Area: Engine
Issue Type: Other
Impact: High
Frequency: Constantly
Date First Experienced: 2021-09-01 00:09:00 (+07:00)
Date Last Experienced: 2021-09-20 00:09:00 (+07:00)

---

Dev console server output timestamps are nonsensical

Timestamps in the dev console became nonsensical sometime in the past few days, always displaying somewhere in the range of 20:00:00. It’s affecting my game Starscape, but I see it in other places as well. [image] I seem to be able to reproduce the issue in every place I go to. I’m using Windows 10 and I’m in the Pacific time zone.

[gigagiele]

Hi, thanks for the report. I seem to be unable to reproduce this issue on my end, does it still occur on yours?

[ZolarKeth]

On my end it seems to be working properly for the client output, but not the server. All these prints were made within seconds of each other using the server command line.

[RuizuKun_Dev (Kitsune)]

yes it’s still happening, the output is from the Server

[PezzoGuy (Pezzo)]

Can confirm that this is still happening. As said above, client console is fine, but server console is all over the place. This is making it very difficult to diagnose a critical bug in our game.

PLEASE don’t make the developers wait a year for it to be fixed like last time.

[mishajones]

Hello! Bumping this thread because it’s been over 4 months here. It is quite hard to debug with this issue, so it would be great if this was looked into again.

Another server output example

[rickje139]

Same thing happens to me, it only shows the incorrect timestamps on the server logs, the client logs are fine.

[ILoveCzechRepublic]

Same here, I wonder why this has not been solved. Does it affect just somebody?

[PezzoGuy (Pezzo)]

Looks like a potential fix is coming: Release Notes for 512