Doomsday

[LegoProfessor]

So, I found the cause of the timestamp-error:
The date reach 31.12.9999
Is that the doomsday in C:S?
And how to set the time back to (say) 26.10.2022?
Any idea ....

[LegoProfessor]

I found a mod to reset the date
but still after a few "days":

Simulation error: Argument is out of range.
  at System.DateTime..ctor (Boolean check, TimeSpan value) [0x00000] in <filename unknown>:0 
  at System.DateTime.op_Addition (DateTime d, TimeSpan t) [0x00000] in <filename unknown>:0 
  at SimulationManager.SimulationStep () [0x00000] in <filename unknown>:0 
  at SimulationManager.SimulationThread () [0x00000] in <filename unknown>:0   [Core]

Grumbel :-(
Is there really a hard end in the game?
After 10000 hours of playing, there is no future ?
I want my money and/or time back ...

[snowflitzer]

Ask Avanya but that could be more a computer issues :)

[LegoProfessor]

Originally posted by snowflitzer:

Ask Avanya but that could be more a computer issues :)

I don't belive so.
As I see the time running, the 31. Dec 9999 shows up and with the next step the game going crasy.
And the timespane (from the (other) error message)is outside the range of vaild

ArgumentOutOfRangeException: Value 3155621232800778773 is outside the valid range [0,3155378975999999999].
Parameter name: ticks
at System.DateTime..ctor (Int64 ticks) [0x00000] in <filename unknown>:0
at SimulationManager.Update () [0x00000] in <filename unknown>:0

So I do have in my game
hours played: 10005
date: 31.12.9999 (31. Dec. 9999)
Timeticks: 3155621232800778773

Found this in web:
DateTime.MaxValue = 3155621232800778773
"The value of this constant is equivalent to 23:59:59.9999999 UTC, December 31, 9999 in the Gregorian calendar, exactly one 100-nanosecond tick before 00:00:00 UTC, January 1, 10000."

And this looks like, there is a upper limted in playing C:S :-(

I did try to reset the date but the game still goes crasy
There are more timestamps then the date that overflow

Question is: How to solve this issue?
It would be okay for me to start with 1. Jan. 0001 but how?

[OldyButCrafty]

As Marty McFly said to Doc; "Heavy".
A real life space time continuum conundrum this is.

[OldyButCrafty]

I assume this is the mod you tried that did not work?
https://steamcommunity.com/id/cgameworld/myworkshopfiles/?appid=255710

[OldyButCrafty]

Sorry the above was a link to author. Below is the actual mod.
https://steamcommunity.com/sharedfiles/filedetails/?id=1729576238&insideModal=0

[LegoProfessor]

Originally posted by OLDYBUTCRAFTY:

Sorry the above was a link to author. Below is the actual mod.
https://steamcommunity.com/sharedfiles/filedetails/?id=1729576238&insideModal=0

Yes, I have installed this mod and could successfully set the date.
But unfortunately this reset only the displayed date, an internal timestamp still has an overflow :-(

[OldyButCrafty]

Originally posted by LegoProfessor:

Yes, I have installed this mod and could successfully set the date.
But unfortunately this reset only the displayed date, an internal timestamp still has an overflow :-( [/quote]

That is terrible. Are you playing in Linux? I am not aware of that limit in Windows.

[LegoProfessor]

Originally posted by OLDYBUTCRAFTY:

Originally posted by LegoProfessor:

Yes, I have installed this mod and could successfully set the date.
But unfortunately this reset only the displayed date, an internal timestamp still has an overflow :-(

That is terrible. Are you playing in Linux? I am not aware of that limit in Windows. [/quote]
I'm on Windows. But the limit is the same. Internal they using a Int64 timestamp. How to know: Googleing around ad found, thet there are In64 timestamp with max-value excatly like in the error message and this max is interpreted 31. Dec. 9999

[MessengerOfRage]

well, thank you for the heads up Lego!
I will rethink my habbit of letting it run on fast speed while detailing.

[OldyButCrafty]

This is really serious. This thread needs to be bumped until we attract a skilled moder to help us understand if it can be addressed by mod.

[mistermcd]

Would be interesting to know if this issue will happen if using the Real Time mod. I've been using that mod on a city I started Aug 23rd, 2022 and the in game date is now November 27, 2022 ( ihave the night time rate set to 5x and the day time rate set to 4x realtime...)

https://steamcommunity.com/sharedfiles/filedetails/?id=1420955187

McD

[de.abacus]

Originally posted by LegoProfessor:

Found this in web:
DateTime.MaxValue = 3155621232800778773
"The value of this constant is equivalent to 23:59:59.9999999 UTC, December 31, 9999 in the Gregorian calendar, exactly one 100-nanosecond tick before 00:00:00 UTC, January 1, 10000."

And this looks like, there is a upper limted in playing C:S :-(

don't think that around that day/time they generated traffic as we know it
:-)

[OldyButCrafty]

Originally posted by de.abacus:

Originally posted by LegoProfessor:

Found this in web:
DateTime.MaxValue = 3155621232800778773
"The value of this constant is equivalent to 23:59:59.9999999 UTC, December 31, 9999 in the Gregorian calendar, exactly one 100-nanosecond tick before 00:00:00 UTC, January 1, 10000."

And this looks like, there is a upper limted in playing C:S :-(

don't think that around that day/time they generated traffic as we know it
:-)

Yes, maybe you saw this link?
https://learn.microsoft.com/en-us/dotnet/api/system.datetime.maxvalue?view=net-7.0#applies-to

It does not say it applies to Windows? Other things including bits of MacOS but no mention of Windows.

[de.abacus]

Originally posted by OLDYBUTCRAFTY:

It does not say it applies to Windows? Other things including bits of MacOS but no mention of Windows.

as I understood it, it is a .NET limitation