hi.. Grain sim again.. i have a complex animated static collision object, and with the uniform divisions turned up sufficiently high, it takes a good percentage of my sim time “calculating SDF”
so i thought it would be a good idea to cache out the collision volume.
following info i found around here, i set the file mode in the static object DOP to “write” and set it to output “collision.$f4.simdata”
i then played throught the timeline, with a very low resolution (big particle separation|) grain sim,.
this gave me a folder full of 22 meg simdata files.
i then set the file mode in the static object DOP to “read” and pointed it to those files.
id assume that would be all i have to do?
however when i sim, it -still- spends ages “calculating SDF” and doesnt seem any faster than previously.
what did i miss?
thanks, Robin.
cached collision volume workflow?
3219 4 0- robinlawrie
- Member
- 57 posts
- Joined: Feb. 2014
- Offline
- robinlawrie
- Member
- 57 posts
- Joined: Feb. 2014
- Offline
- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
- robinlawrie
- Member
- 57 posts
- Joined: Feb. 2014
- Offline
- circusmonkey
- Member
- 2624 posts
- Joined: Aug. 2006
- Offline
Why> Dops is for simulation, anything you do there will require running out the simulation. In sops this is not the case. So write out the geometry acting as a collision proxy volume. Doing this your optimizing your DOP sim.
How > Turn your geometry into a vdb volume > feed into DOps select the path to the proxy volume.
Rob
How > Turn your geometry into a vdb volume > feed into DOps select the path to the proxy volume.
Rob
Gone fishing
-
- Quick Links