x particles OpenOVDB Mesher Motion Blur
Moderators: ChrisHekman, aoktar
Hi everyone, so I have a scene where I have particles simulating water splashing on an object. I then turn on the XYZ Velocity checkbox to create tags to then later be put into octanes 'Object Tag' with the motion blur set as 'Vertex Speed'. I then put each tag where they belong. After that, I cache the simulation and turn all the options in the 'Octane Camera tag' for motion blur. But motion blur doesn't show up. After doing some trial and error, I found out that If I Cache everything but the OVDBMesher, I do get motion blur. Now my question is. Is this the way works with this workflow or did I miss something to make it work properly? The moment I cache the OVDBMesher all motion blur is gone. Thanks for taking your time to read this.
Octane doesn't care how vertex tags re generated. It takes if there is really proper data. There may be a bug for XP
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
- james_conkle
- Posts: 162
- Joined: Sun Oct 27, 2019 10:28 pm
- Location: Brooklyn, NY
- Contact:
Howdy I have the exact same problem! It isn't an Octane issue it's XP. When the mesher is "live" it generates xyz vertex maps like we all love. If you XPcache the mesher the tags are still there but if you click on them you can no longer see any vertex data. So that sucks - but if you keep the mesher live and only cache particles that can get you to the point where you can refine your mesher (watch with the filters they can destroy the motion blur data) and then right click the mesher and tell c4d to bake as an alembic. It'll probably be big but you'll have a nice cached mesh and those vertex tags will have data!
Octane C4D Plugin 2021.1 / C4D R25.015
UNIT 0: 2080ti / 6700K / 64GB / 500w
UNIT 1: 2x 3090 / 3970x / 128GB ECC / 1600w
UNIT 2: 5500M / 9980HK / 32GB / 95w
RNDR Artist Calculator
UNIT 0: 2080ti / 6700K / 64GB / 500w
UNIT 1: 2x 3090 / 3970x / 128GB ECC / 1600w
UNIT 2: 5500M / 9980HK / 32GB / 95w
RNDR Artist Calculator
Thank you both for your answers, I don't know why I didn't get a notification about your replies.But I will definitely try the method explained. Thank you for your help!james_conkle wrote:Howdy I have the exact same problem! It isn't an Octane issue it's XP. When the mesher is "live" it generates xyz vertex maps like we all love. If you XPcache the mesher the tags are still there but if you click on them you can no longer see any vertex data. So that sucks - but if you keep the mesher live and only cache particles that can get you to the point where you can refine your mesher (watch with the filters they can destroy the motion blur data) and then right click the mesher and tell c4d to bake as an alembic. It'll probably be big but you'll have a nice cached mesh and those vertex tags will have data!