OTOY Forums

Hi guys,

I have encountered a small issue that requires some help.

Basically, I have tested an animation of flower made by 2 levels of cloners.
However, when I rendered out the animation, it's very different from the hardware preview that I have rendered.

I have also tried adding mograph cache tag but it doesn't seems to do it's job
Heres the link of the files:
https://app.box.com/s/dwtwu7x12mi9q97qy0cu4ebqd6swibiq

I'm using a PC windows 7 platform
i7-5960X CPU @ 3.00GHz
64 GB RAM
Palit GTX 1080

Would appreciate if someone could enlighten me.


Cheers

I have rendered with Octane exactly same thing as your hardware render.

what is your Octane version?

I'm using Octane 3.03.2b

Hi

I could reproduce the problem in R17.053 - 3.03.4-R1.
Force updates / Force On picture Viewer in the Object Tag seems to fix it. I have no idea about what is causing this though.

It would be good to know why 'force updates' exists and what it actually does "under the hood". It's a relatively new feature.

Currently, my workflow is: When you don't know what the hell is going on, just add Object Tag and use force updates.

Regards
Milan

Thanks milanm, it's a little weird but it seems to be working!
Thanks everybody for helping me

Cheers!

There is a problem with "auto detect" for your objects. Geometry detection may not properly detect which objects are changing.
So another solution is "all movable". So PV rendering will be acting as in LV's default option.

I'm trying to fix "Auto detect" for this problem.

Would this also be to blame for jerky camera animation too? I've had a couple of scenes with 3.03.2b where it was like there was a shaky effect applied to the render.

fatfreemedia wrote:Would this also be to blame for jerky camera animation too? I've had a couple of scenes with 3.03.2b where it was like there was a shaky effect applied to the render.

There is some cases in C4D which cause bugging me. You know plugin need to know updated parts to refresh geometries. In some cases we can't catch correctly. It seems belong to unexpected behaviours of C4D in picture viewer rendering. It doesn't acts as in editor mode and LV. For these cases use "force updates in PV" option in object tag. Mostly happens on complex cloner setups with some extra deformers/etc...

Hmm - not a lot of animation happening in the latest scene. Just some spline paths and constraints which I baked out. Will definitely try rendering with resend all scene data/object tags though. Thanks!