Octane 4 transplating keyframes onto wrong objects

[boxfx]

We've switched over to octane 4 and it is giving us some serious headaches. In a nutshell, when rendering out the final animations we find that octane is transplanting PSR data from one object onto another. In our full scene, half of the project comes out unusable with some objects duplicating 2-3 times in new locations. This always happens when keyframes are used to hide or show objects (traffic light buttons or via octane tag visibility) This all worked fine in 3.07 but goes wonky in 4.0

Attached is a very trimmed down version, just hit render to picture viewer and let the 6 frames render. The large square exists only once, yet when rendered to the picture viewer it duplicates itself and takes on the coordinates of the other unrelated animated object.

Lots of changes will prevent the issue, many unrelated things which make no sense. If you make the extrude editable, it works. If you move a keyframe it works, if you change the hierarchy in any way, it works. If you disable motion blur, it works. However this isn't enough to fix our full project where these changes will still leave many parts broken.

Tried different drivers
Tried different machines with other gpus
Tried with and without network rendering
Tried with R19 and R20

Win 10
Geforce 980 / 980ti / 1060 / 1080 (ie tried on 4 systems)
64 gigs
driver 417.01 plus a few others
extra cude lib for octane 4 installed
c4d plugin 4.00
octane standalone 4.00
c4d 19.068 / 20.030

-Mash

[aoktar]

Thanks for good scene. I'm looking in to...

[aoktar]

One thing I found that's strange, It's working well If I create new octane camera or render from perspective view. Are your scenes and camera are created with V3?

[boxfx]

This project started in V3, yes. But there shouldn't be anything strange with it. I even tried deleting the octane camera tag and adding a fresh one (+turn on motion blur)

[aoktar]

This project started in V3, yes. But there shouldn't be anything strange with it. I even tried deleting the octane camera tag and adding a fresh one (+turn on motion blur)

Ok I found, It's related with motion engine. Motion blur in camera tag.

[boxfx]

Just tested here, this doesn't fix the problem for me. If I create a new octane 4 camera and dial in the same settings (motion blur, 0.025s shutter etc) then it still breaks.

[boxfx]

I should also add, disabling motion blur fixes the problem here. but there are other sections in the scene where turning off motion blur (in the camera tag and render settings) does not fix it.

[aoktar]

Just tested here, this doesn't fix the problem for me. If I create a new octane 4 camera and dial in the same settings (motion blur, 0.025s shutter etc) then it still breaks.

As I said that It looks like related motion blur calculation. Are you asking why another mblur controls are not fixing the issue? It's about the pattern of algorithms about motion blur sections. There's definitely a bug, seems like it appeared after R20 adaptation.

[boxfx]

im just pointing out that this general problem happens throughout the project. Disabling motion blur fixes this small example posted here, but in other places in the project, switching off motion blur still leaves duplicated objects in strange locations. But naturally I don't know how it all works internally.

[aoktar]

Could you post another example as you mentioned without mblur?