Houdini to ORBX motion blur Tweet

[blobbybarack]

Hi there, this problem is without doubt a real nightmare in production...even more when you are doing cars or Helicopter scene etc...
I ve just find some temp fix who could maybe be usefull to someone. This is not ideal and have some drawback but should work for many case.

In Houdini multiply the framerate by the number of step you really need let s say 10.
This step number should set to 10 in the MB steps tab too.
if fps is 24 so it will be 240 fps now...if range is 1 to 50 it should now be 1 to 500.
Export your Orbx. In octane render standalone set back your original fps to what it should really be 24 here.

MB should be ok.

This should be painless if you have only object transform in your scene....could be a pain in the (x) if you have backed stuffs integer frame animation, non constant topology,etc....

[james_conkle]

Hello Juango, I was wondering if this has been addressed in the 2021.1.5 build? If not will it be mentioned in the release notes when it is fixed? I’d hate to keep posting here asking about it - I don’t want to be annoying.

[juanjgon]

Nope, sorry. I've not found the source of this problem yet. Did you have a chance to check if Octane 2022.1 still has the same issues?
viewtopic.php?f=102&t=79890

Thanks,
-Juanjo

[blobbybarack]

Like James i'm really sorry to add more complain to this particular problem and i perfectly get that this can be tricky to resolve.
Just want to mention this post again and the test scene shipped.
viewtopic.php?f=103&t=79742
In some way this can be related to the same problem maybe it could help you to solve this issue with a fresh look. MB issues are maybe not directly related to Orbx but a larger problem related to how Houdini sample velocity and send it back to Octane.