Caveat: Dyverso object not rendering correctly?

[FSchmidt]

Hi, we just solved a problem that also other people might encounter. We were simulating a simple scene in which an elastic object (via Dyverso Domain > Elastic) drooped under gravity. Simulation worked fine as well as rendering via the "Fire" or "Maxwell Preview" buttons. However, when rendering the very same scene via a Python script or via the "Send to Maxwell Command Line" button, only the last frame of the object was rendered in all frames. After trying different alternatives, we found that the "Animation (.sd)" box was not ticked in "Export > Export Central" and that ticking that box solved the problem. Note that while this solution makes sense, it is somewhat counterintuitive that the box is not ticked automatically when adding an elastic Dyverso Domain to an object. Hopefully, this post will save other people the same trouble

[Thomas Schlick]

I'll take a look at this issue, because the object should be rendered correctly without the "Animation (.sd)" option, because all the information is actually stored in the global "ANIMATION (.sd)". There's obviously something broken here when you trigger a render job via the command line or a script.

Thanks for letting us know and we appreciate that you've been able to share a workaround already

Cheers,
Thomas

[FSchmidt]

You're welcome

[Thomas Schlick]

Just to keep you updated: I can confirm your observations and the object doesn't move in the render when only the global ANIMATION.sd is active. Your workaround fixes this issue.

Again, thanks for pointing us to this issue. We've filed a bug report.