Xparticle OpenVDBmesher have buggy motion blur in Octane!

[911ljt]

Hi, I m using the latest version of Octane 2021.1.3, and latest Xp 1036.
I found a serious problem with Cached Motion blur of OpenVDB mesher. My openVDBmesher can indeed export proper Velocity data (double checked with Insydium devs), so my mesh should have motion blur even all my settings should be correct (correct me if i m wrong). When the mesher is not cached, motion blur seems works fine, but as long as I cached it then it stopped working. I tried using Cycle4D still no motion blur. a very tiny Scene file with cached file attached below. Hope everyone can help a brother out one more time. Thank u!!!

I am not sure its bug from Xp or Octane. Can some one check the motion blur problem for me?
The project file with cache in attachments and here is the video i recorded showing this problem. I dont wanna make alembic to make it work.

Thank you!

[james_conkle]

It’s a problem in XP when using their cache tool. It doesn’t do a good job of keeping the vertex data so the best bet is to use the XP cache to cash your particle simulation and then once you setup your mesher right click on the mesher in the item manager and select the option that creates an alembic.

[aoktar]

Actually you are saying enough proofs that's not an Octane problem. We just read the data from vertex tag. We cannot fix if data is broken. Also this is not first report about this problem. Please keep tracking it with xp team.