Component Time sync seems to persistently drop certain frames. I was helping an animator look into an export issue and it seems like if you run a COMP with component time non-independently, it winds up dropping sync for certain frame numbers. When this happens the nested COMP’s time component simply doesn’t move to the next frame. In most cases the subsequent frame will run and be back in sync.
I set up a new project to try and diagnose it here:
nestedSyncBug.toe (7.9 KB)
For example, frame 63 (00:00:01:02 @60) seems to never cook in the nested COMP while it is not running independently.
When frame 64 comes along the nested COMP catches back up by skipping 1:02 entirely.
There’s also a whole trio of frames that are persistently one off from 125-127.
The included toe tries to log the skipped frames. The same frames seem to get skipped regardless of whether i run it on my PC or my macboook.