Jump to content

Caching VDB's - reducing size


Recommended Posts

A question regarding the caching of VDB's from a smoke simulation.

Currently see well over 160 million vel voxels when I load some cached vdbs from a sim.

That combined with 5 substeps necessary in my simulation is choking my Threadripper, simulation times are simply too long.

Since all I really need are density voxels (and optionally temperature or heat) for rendering, does it make sense to delete these vel voxels just before caching?


Link to comment
Share on other sites

absolutely. only cache the fields you need. If you need vel for motion blur, you could resample the vel VDB to 1/3 of the resolution, that's usually enough for motionblur. Also make sure to save out 16bit fields instead of 32bit

and one more big saving comes from compressing the volume as well as masking the vel field by the density field

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...