OTOY Forums

very simple scene with rings and clonner, livepreview is working well, but Octane crushed everytime i try to render it.

the scene is ready, so everybody just hit [RENDER}


PS. i think that the problem for Octane is that a lot of clones are in one point and overlapping. Check attached file in message below with solved word

i exported clonner to alembic file and than merged it, octane still crushes

semi solved: setting clonner count to lower number (20 for example) everything begins to work.

i calculated: 60 clones of sweep produce about 12mln polygons, ofcourse this is to musch, but in clonner "render instances" is ON, but octane seems to ignore it and making "true" geometry

Hi arleksey,
please, copy and paste all the scene elements in a new fresh scene because your render settings are messing up with c4d native options mixed with octane You must see the green bar + info if octane is rendering correctly inside Picture Viewer.
Next time, is better to create a newer render setting octane specific if you already have a c4d render setting active
ciao beppe

solved: i fixed by animating cloner quantity, so geometry doesn`t mixed in one point

bepeg4d wrote:Hi arleksey,
please, copy and paste all the scene elements in a new fresh scene because your render settings are messing up with c4d native options mixed with octane
ciao beppe

you are rendering wrong time, try to start render 70 to 80 frame in file you`ve attached

everything goes great after clonns start to rotate

Wait! There is a crash on Renderer side, propably due driver.

aoktar wrote:Wait! There is a crash on Renderer side, propably due driver.

i tried on five different machines with different software (drivers) and hardware. No one could render this scene.

check the fix file i`ve attached few messages upper, that works great with 60 clones

I assume there is some many badly wrong usages for octane. See image for crash output.
To make the objects zero sized as you make circle=0 radius can cause this. It generates a lot of points at same coordinate and can crash the renderer's geometry engine or driver i suppose.
Event it happens on LV while going to between 80-90 frames.
I'm checking more.....

i think that the bad place is 90-91 frames, where geometry was collapsed and start to rotate