Testing Beta 0.87b (SDK 1.20) **updated 04.10**

[immortalartscom]

damn i get doubleframes in my animations!!!!! this is really NOT GOOD! the animation renders 2-3 days and then there are many doubleframes. this WAS an issue! i dont know why this came back. men this is dissapointing...

the render stop bug and the doubleframebug are things which should be rock solid for end of beta. PLEASE AOKTAR! PLEASE FIX THAT OR TAKE A CLOSER LOOK!

[buzby]

Aoktar, I see 0.8.2b in your video was this released or just your copy? I cant get 0.82 to work without crashing, have to keep going back to 0.79

it's very strange some people talking about crashes. But never crashes on my pc's even very complex projects. I'm really fooling with this.
What kind of crashes you say? In live viewer? With geometry updates? R14/R15? i need more details.
Also i saw you thread about phong angles. It seems like bad triangulation issues.

Thanks for the help on the phong I am creating the model in Autodesk inventor, importing into 3DS Max 2013, and then saving as a .obj I am sure something is happening in the process. I will try to save as an FBX with the triangle poly.

On the crash it happens as soon as I try to render in the Live Render window. Update Geometry not checked, Same scene in 0.79 works fine, My specs are in my signature. I wish I had more info Maxon just shuts down and there is no error log.

[ASyme1]

Hi Aoktar-
We are also seeing a lot of the same bugs as these guys. We're getting double frames, freezing after finishing, and lately the animation renders just stop 7-10 frames in. It's not a crash, but it just stops. REALLY bad for my studio. It's to the point that we can't trust using this plugin for jobs. Serious amount of bugs and crashes. I really wish this worked better. I LOVE the Octane renderer and C4D but I can't rely on this for paying projects. We're moving things back to VRAY until some of these bugs are gone for good.

I'll keep testing but not with paying projects.

Thanks
Alec

[aoktar]

hey men, please can someone contact with me. need some tests to fix this defect, our beta test team is missing.

[aoktar]

and last note, this is test release for new features. rendering algorithms and some others is changing still for better stability. need different systems for testing.
if you have problems please stay with your stabile version.

[kirbyzz]

one thing i figured out today...had to work on a other normal c4d-job..no octane.
inside that project i get from my customer was a material with a normal c4d-level layer with a few simple layered materials.

I had to change that level-layer for adjustement but always i touched the layer-chanel cinema crashed...
Then i removed octane plugin from cinema-folder and it worked..don´t know why but i think octane don´t like the cinema 4d own level-layer.
I know for now..is not so bad..after finishing that job i will simply copy the octane back to c4d-folder. I hope this desription helps for fixing,
or please write it to the list, because i know it´s not possible to fix all in same time...

best
fabian

[aoktar]

one thing i figured out today...had to work on a other normal c4d-job..no octane.
inside that project i get from my customer was a material with a normal c4d-level layer with a few simple layered materials.

I had to change that level-layer for adjustement but always i touched the layer-chanel cinema crashed...
Then i removed octane plugin from cinema-folder and it worked..don´t know why but i think octane don´t like the cinema 4d own level-layer.
I know for now..is not so bad..after finishing that job i will simply copy the octane back to c4d-folder. I hope this desription helps for fixing,
or please write it to the list, because i know it´s not possible to fix all in same time...

best
fabian

thanks, i'll check it

[dinf]

I had to change that level-layer for adjustement but always i touched the layer-chanel cinema crashed...

Have seen some very similar: every time I have to edit a non-octane Cinema material, Cinema crashed (click on the texture arrow). Mostly in scenes wich had Octane tags or materials before, but, seldom, also in 'clean' Cinema scenes. Deactivating Octane helped.

[cyartist]

I have been using the latest plugin for different jobs and have not had any freezing or major bugs.

[kirbyzz]

older versions were more stabel with c4d-own options. it´s only a idea but could it be that the geeometry update function
causes all that...it was one of the last points you added i think so.. i know it´s a realy nice feature..i prefer always not to use it and refresh geometrie manually...works for me much more stabel and it works for me in most cases good. i tried but had sometimes wired results..

i think probably that update-function always listen and interfere so the cinema 4d own functions.
for materials it´s the same..if octane materials are refreshing my shortcurs only work after clicking them 3x/6x - then cinema reacts. ..i can not copy and paste coordinates into the coordinate-manager while all materials are loaded/refreshed after opening a scene - they were always reset.. after all oct-materials have loaded/refreshed it works normally.

Maybe i´m completley wrong, it´s only an idea..
I´m only thinking about it why it was more stable before than in the newer versions with that new functions and one
of the biggest new points were the realtime update-functions..probably they cause some of the errors. Has anyone watched something like that?