That's exactly what I'm talking about. No matter how you build your scene if this is the best way for you to build it — do it. But Octane should not depend on the scene structure while generating the motion blur. I cannot call it a bug, but at least, it's a big usability issue.
Here is a real world example.
Everybody knows that if you want to avoid motion blur on the fast moving object while camera moves with it, then you should attach camera to that object.
Now let's imagine that we want camera to approach a moving object, then travel some time next to it, and then focus on something else. This is how it will look in a 3D editor:
And here is how it looks in the render: the flying object is blurred all the time, and the guys are not at all.
- Final Render
This is the case which I couldn't solve with Octane. There is just no option to render this properly. I also noticed that in simple test scenes Thin Lens camera will render it properly. But if the scene gets more complicated — the higher chance that there will be mistakes in the render. But the Universal camera always renders wrong motion blur.
