First four frames rendering weird...

Sat Jun 27, 2015 7:24 pm

The first four frames of my animation are rendering at really odd times and all look completely different (darker then lighter then darker again). At frame 5 the animation looks good and is stable at around 2mins a frame from then on until the end of the sequence.

I've done a search to see if others have had this issue. It all seems to be a bit of a jumble of answers... I've updated to latest version and still its not right.

I have stripped my scene back and have object tags on the animated objects. I've tried various different settings and the issue remains.

Any ideas please?

Thanks,

Sat Jun 27, 2015 8:40 pm

If you tried the everythings, please post a scene to check it. Without a scene that's hard to estimate.

Sat Jun 27, 2015 9:31 pm

It turned out to be the Mograph in my scene that was causing the issue.... I guess it was something to do with the conversion to Octane??

I baked all of it with Nitrobake and now it renders fine.

cheers.

Sat Jun 27, 2015 9:37 pm

bleepurchin wrote:It turned out to be the Mograph in my scene that was causing the issue.... I guess it was something to do with the conversion to Octane??

I baked all of it with Nitrobake and now it renders fine.

cheers.

Some ideas comes to mind so. Maybe you have lot of movable geometries. There is a 32k nodes limitation for Octane Node Graph. Can be? Each movable object will generate at least two or three nodes on Octane side. So 10k movable objects can cause 20-30k nodes. If you hit this limit it can crash or stall for a while.

Sat Jun 27, 2015 10:05 pm

got you.

Bit of a relief its easy to bake it all with Nitrobake right??

Sat Jun 27, 2015 10:18 pm

bleepurchin wrote:got you.

Bit of a relief its easy to bake it all with Nitrobake right??

are you baking as single object? If so this corrects my idea. If you can try to use render instances avoid lot of usage of Octane nodes. Render instances will be exported as arrays in a scatter node. So will not generate lot of Octane nodes. On future versions, i'll try to avoid this problem. But it's complicated work and i need to have fully stable 2.xx version until 3.0 comes.