Multiple timemachines intermittently causes broken behavior

I’ve encountered an issue where, if I have a bunch of TimeMachines in my network, it causes them to become corrupted. I’ve created a minimal test case (close to minimal, anyhow) that demonstrates the bug. timemachine_bug.toe (4.4 KB)

Video demo: https://youtu.be/m_jkRKopfoQ In the video, all the timeTwirl Base nodes should be displaying identical content, as they are identical copies of the same network. In my much larger network, I was getting different types of failure modes on top of the ones in my video, such as time displacement not matching the input gradient.

Build 2025.31550 (I wasn’t having this issue on the 2023 builds). Running on Windows 11, AMD Ryzen 9 7940HS with Radeon 780M Graphics (4.00 GHz)

I just tried with 2025.31740 and the behavior is present in that build too.

Hello @xxv

Thank you for reporting the problem. I’m able to replicate the issue. We’ll have a look.

A fix will be included in the next build we release.

1 Like