- Posts: 32
- Joined: Mon Sep 25, 2017 7:46 pm
I think I'm suffering from this as well. But in my case it seems like it can't update the exr sequence even if I disable and enable the loader again.
For example, I have a 3D animation that I comp into footage with 100 frames. I assemble everything and know it works for the next 100 frame, too. I set the length in the loader manually to 200 frames.
Then put the rest of the animation into the deadline render queue, then the Fusion comp. No matter what I do, Fusion will not recognize the image sequence after the initial 100 frames. Even if I set the "Missing images " mode to Wait. Then it will wait indefinitely.
If I open the project now, even disabling and enabling the loader won't show me the new frames. Selecting "Autodetect framerange" will usually work in that it correctly detects the number of frames, but the loader itself won't load any images after the initial 100.
The only solution so far is creating a new loader and having all animations already completely rendered before starting in Fusion. Which is sad because it completely destroys the ideas behind manually changing the Loaders length or using the Wait mode.
I wasn't able to confidently reproduce this yet or I would've sent a bug report already.
And this won't be an issue with deadline as A) it happens in Fusion 17 without ever touching deadline in a project and B) Deadline simply triggers the native Fusion Render node.