CINEVERSITY

Hi Frischvergiftung,

Yes, that list needs to come in on time! 😉

Fingers crossed it works.

Have a great Sunday!

You're very welcome, AlexC.

My best wishes for your project!

Hi schnoidl,

If I get your question correctly since your question leaves out all the details, you have imported a VDB sequence via VDB Loader and used the Volume Surface object to get polygons. If you used a 3rd party plugin for that, please check with the tech support/forum.

Export your setup as an OBJ sequence (animated). Then reload it. There you get no option to delete a little polygon artifact. That is your question, correct?

Check your sequence, and note the frames you like to work on.

Switch off the Instance. Then twirl opens the hierarchy and sets the Display Tag so all your objects of that sequence become visible.

The top object in that hierarchy to not visible (two red dots, Object Manager).

Each frame you like to work on set to be visible (two green Dots, Object Manager)
Create your changes.

All the best

You're very welcome, Alex.

The idea was to provide these dynamic or progressive Voxels to limit the memory needed. The more classic approach is to define a single space that requires a lot of memory from the start.
But, yes, when you go tiny, as mentioned, you quickly have a thousand times more of these cubes, which goes tough on the memory then.

In the old Pyro (two decades ago), there was a 2D version for a more distant objects, I wish we had that also here, even just to comp on the 3D view 🙂

All the best