Hi, and thank you so much for introducing me to this package.
Best regards, Christian Stan
I actually think the limits are with using the dateTime method as you are limited to what you can do.

Somewhere on the Git, there is a document with all options for DateTime.
Usually, I use Date.Now node, turn it into a string type and get the the last char which is usually the second, so it increases from 0 to 9 every second. This can be a starting point for you. ![]()
Yep ![]()
We haven’t had the best luck with international shipping. But, we will explore this idea for the future.![]()
But good news- We still have loads of these stickers. So, next time you bump into one of the Dynamo team members at an event, you can grab some. ![]()
Hola amigos buenas!! ![]()
I’m happy to finally get a new challenge, regarding the problems with periodic mode, I agree that it is not easy to make Dynamo work sequentially, but time already moves sequentially; it is just a matter of comparing it at the moment. Perhaps this approach will help. For a long time, the standard in cinema was 24/s means 24 frames by second, so 1 second have 1000 ms then 1000ms / 24 frames = 41.66 ms the logic is that:
1/s = 1000 ms
2/s = 500 ms
4/s = 250 ms
6/s = 166.666666 ms
12/s = 83.33333 ms
Like that you must to match the object(s) instantce that correspond to that instant on the second, this way you can simulate cinematics, the time itself handle the positions, rotation or wathever movement you place, the real problem is if your pc have enough power to render the objects in time, I let you an example, hope this info helps you!!
(I used 12 frames / second; works quite well)
Does node to code work?
So you could create a number slider for the frame rate
So you can test
Just want to confirm are multiple entries allowed?
Yes, multiple entries (within reason) are allowed. I will update the initial post to say 3 entries per person max.
I was not able to achieve this smoothness even with this package, may be it’s because of my geometry. I’m just gonna speed up my screen record ![]()
Hi All, been a bit quiet this year, learnt a few more code languages that I reckon I was planning to though.
Hoping that I have some bandwidth to be a bit more active next year!
Here’s a transformation from 2025 to 2026, running at periodic 100ms.
Hope everyone has a good end of year break ![]()
![]()
From 2025 to 2026.dyn (23.6 KB)
I’m not in the contest (Autodesk employees are excluded), and this doesn’t say “happy 2025”, but here’s a little inspiration for everyone:
Just decorating the tree..
![]()
This is done with a view extension , code here . Probably doesn’t fit the cretaria though haha ![]()

Hi,
I am posting my entry outside of the contest because it requires a Leap Motion Controller (UltraLeap).
What if you could touch Dynamo solids?
However, if by chance a Dynamo user has a Leep controller, here is the dyn (with the instructions to install library for Leep Controler)
Dynamo_Challenge_leap_motion_happy_year_2026_DYN3_v1.2.dyn (22.5 KB)
More info here
Happy holidays to everyone!





