Avoiding cooking when caching an interrupted save to disk operation

   2155   0   1
User Avatar
Member
351 posts
Joined: June 2016
Offline
Created a basic 240 frame RBD simulation. Once I was happy with it I wanted to ‘bake it’ so I clicked “save to Disk' on my Output node inside my AutoDOP network.

As a test at frame 120 I interrupted the Save to Disk operation.

I also enabled ”Playback from Saved files“ on the parent AutoDOP node.

So now frames 1-120 are highlited in purple on my timeline.

At a later time I wanted to see if I could complete the ”save to Disk“ of my simulation so for start frame on my Output node I entered 121.

I then clicked ”Save to Disk“ but instead of immediately caching my simulation I see ”DOP cooking frame 1-120" on my timeline and have to wait an hour or more until my caching operation continues on frame 121.

Is there any way of avoiding this cooking operation? It seems unnecessary to me.

On a related topic I thought the whole advantage of the .sim format was that it saved state information, so I shouldn't even have to enter a start frame when continuing an interrupted cache operation. Houdini should ‘know’ where I left off, no?
  • Quick Links