C4D 2023 - VDB Issue with a cloner and MographText

[lightborne]

I've noticed an issue where a VDB sequence will not render the full sequence of VDBs if it is inside a cloner and a null with MoGraph Text that is non-editable. I hope I described the setup correctly, below is a screenshot of the hierarchy. The only difference between the BadSetup and the GoodSetup is that I made the Text object editable

Cinema_4D_2023.0.0_-_[VDB-Issue_JJ_v1.c4d_]_-_Good_242.jpg (17.01 KiB) Viewed 1308 times

This happens on C4D 2023. This same setup renders the full VDB sequence correctly on s26

[bepeg4d]

Hi,
I have tried to reproduce the same setup in C4D 2023 and c4doctane 2021.1.6-R4, but the vdb sequence is working as expected here:

Please share a scene with assets that shows the issue, even via Private Message, thanks.

ciao,
Beppe

[lightborne]

Sorry, I re-read my post and I forgot one minor detail. The VDB sequence shows up in the live viewer but it does not show up when rendered from the picture viewer or commandline. Attached is a .c4d scene with the issue, just add in your own VDB sequence to each VDB object. I have takes set up to show/render the good and bad setup

[jayroth2020]

I don't see the attachment...

[bepeg4d]

Hi lightborne,
thanks for the clarification, I was able to reproduce it, no need to share the scene.

The VDB is exported to Picture Viewer, but not updated on next frame.
If you start to render the sequence after few frames, you should see the static vdb.

ciao,
Beppe

[lightborne]

Sorry, I forgot to add the attachment. It should be attached now

VDB-Issue_JJ_v1.zip

VDB Issue

(139.75 KiB) Downloaded 67 times

[aoktar]

I've reproduced the issue. I'll let you what's happening.