Personally I've always found the Cache on File node to be annoying to use, so have stuck with the Mixer Ops though the Cache Manager. Other people have had the opposite experience, but there you go!
A couple of question: after you move the ICE Tree down into the modelling stack are you deleting the simulation one? I'd also recommend to never duplicate ICETrees under any circumstances - copy and paste nodes, sure, but duplicating the Tree (or the model they're contained in) has been as buggy as hell for me. On 28 February 2013 14:13, Morten Bartholdy <[email protected]> wrote: > ** > > I have never been good friends with the caching methods in ICE . What is > the most simple way to write cache and read cache for farm rendering? I am > doing simple particle stuff and just need it to render reliably on the farm > with motionblur. > > > What I do now: Use Cache on File node and cache all simulation samples > and play through the scene to cache. Then I change the node to Read Cache > and I can render on the farm. > > > The thing is, I have tried copying the pointcloud and removing all > other nodes that the Read Cache node and move the ICE Tree away from > simulation mode so I could scrub back and forth and avooid having the cloud > resimulate, but no go. The particles dissappear. I go and browse for them > in the Read Cache node, and they are there, but still I don't get any > particles. > > > I know plenty of you use it all the time and have no (?) problems with > it, but i only use ICE for simulation on occasion, so it is almost new to > me every time I pick it up again, so please bear with me. > > > How is this supposed to work? Thanks! > > > > A tired pixelbender - Morten > > > > > > >
