Hi everyone,
I've been using labs file cache node to do wedges for my flip simulation, I set up 10 wedges with two attributes. I found it seemed like the node is wedging the 10 wedges (caching all the wedges to disk) at the same time instead one by one. Is it how the node works or should I change some parameters?

Thank you!

Below is my setup

I'm trying to understand the same problem and so far I have not found a way, it just simply evaluates the wedges parallel and does not wait for the batch to end as compared to TOP wedge daisy-chaining. This question has been asked before, but for some reason, it gets no answers, maybe people are not using it that much and rely on the TOPs setups.

Here [www.youtube.com] is a video that explains bit theLabs File Cache workflow and how it's intended to be used, but even when sending it to TOPs, I can't make it work. This is good information despite the fact it does not help with the issue discussed.

Hey there !
I've been having the same issue with wedges with Labs filecache node, it was running them all at same time. But I could get one sim running after the other, by doing this :

Unchecking the simulation checkbox (it seems to not be really needed for the cache to run frame by frame anyway)


This unlocks the 'One Batch at a Time' checkbox in Scheduling Tab. From there I set my batch size to be my full frame range (i'm simming 210 frames in my case)


And that made it ! It ran one sim after the other


I'm just wedging one attribute in my case though, not sure if wedging of two attributes can cause any issue.

I'm also using Explicit filepath, because I like to set my cache name based on $OS and i find the labs Filecache in Constructed mode tend to turn that expression to hard text once executed, so i just stick with explicit as a old habit currently.

Hope it works for you !