Civil3D 2025，Dynamo， The “Date Time” node, as shown in the figure, is not applicable to local time in China (UTC+8). This node is not perfect, it is recommended to make modifications.
FYI @solamour
You might wanna go for the DateTime.Now node it uses your current system’s settings.
1 Like
Yes, the Win11 system time is the current date and time of my location.
The “Date Time” node only has an output port, so I understand that the original intention of this node is to create the current date and time. However, there is a time difference of several hours between the date and time of creation and my region.
The Chinese interpretation of the “Date Time” node is also unclear (at least, I didn’t understand its meaning). In summary, I believe that the “Date Time” node is not perfect.
The node Date Time is built to allow you to type whatever time you want in the input field - the initial placement is the current time in UTC as UTC is the standard for datetime comparisons (as 10am for me is4pm for you).
So if you want it to report in your local time, adjust the input field accordingly. The help for the node in question (highlight the node and hit F1 or right click and select ‘help’) will likely shed some light on the use as there is a specific format which must be followed on the input value.
If you want to report the time your computer currently reports, utilize the DateTime.Now now instead. This is converted to your timezone and also updates on each initial run - you can also enable ‘periodic’ run mode to get the time to update at a period you determine. This example shows both nodes in use, with a less likely date in a copy of the Date Time node to illustrate the user controlled input:
3 Likes
Thank you for your answer. I didn’t understand the usage of the “Date Time” node.
1 Like
If you use the function period besides automatic or manual,you would see the usage of the date.time.
Here’s a showcase.
