Using blocks for extremely long animations actually saves memory. I’m talking about 10+ frames.
2 Likes
A table:
| Trigger chain | My method (with props) | frame # |
|---|---|---|
| 40 | 540 | Frame 1 |
| 80 | 540 (550) | Frame 2 |
| 120 | 540 (560) | Frame 3 |
| 400 | 540 (640) | Frame 10 |
| 1200 | 540 (940) | Frame 30 |
| 2000 | 540 (1040) | Frame 50 |
| 4000 | 540 (1540) | Frame 100 |
| 40000 | 540 (10540) | Frame 1000 |
| 120000 | 540 (30540) | Frame 3000 |
| 200000 | 540 (50540) | Frame 5000 |
| 4,000,000 | 540 (1,000,540) | Frame 100,000 |
All while maintaining the benefits of trigger chains (being able to edit the time between frames)
(No one in their right mind would do anything over 3k frames in gimkit tho THE MEMORY)
3 Likes
So yes, trigger chain is better for less than 14 frames, then my method becomes superior
And because the wire repeaters also need one unit for every frame, they’ll also eventually be defeated by my system.
Wire repeaters (with wires) succumb at frame 21.
2 Likes
so there is more than 1 trigger
My system only uses one trigger.