Beta 0.68 (SDK 1.18 ) obsolete

[aoktar]

Beta 0.6.7c does NOT crash Cinema 4D on startup.

However, the problem with halting during render of animations remains.

at this frame can be zero polygon count?

[DennisK4]

Beta 0.6.7c does NOT crash Cinema 4D on startup.

However, the problem with halting during render of animations remains.

at this frame can be zero polygon count?

The frame that halts is not the same for each time I try on the same animation. And there should not be any difference in polygon count compared to the frame before it.

[aoktar]

Beta 0.6.7c does NOT crash Cinema 4D on startup.

However, the problem with halting during render of animations remains.

at this frame can be zero polygon count?

The frame that halts is not the same for each time I try on the same animation. And there should not be any difference in polygon count compared to the frame before it.

ok, can you give me more info about scene or a scene file that can reproduce same effect

[ChrisVis]

Now, that the plugin seems to start up correctly again, I'm curious if there are still issues with the authentication using standalone and the plugin. Please let me know if they still exist.

Thanks,
Marcus

Hi abstrax,

I putted C4DOctane back to my C4D startup layout now and it starts up ok since 0.67b (and 067c), maybe even with 0.64, haven`t tried it with this one. So the licensing problem seems to be gone.
Great!
ChrisVis

[DennisK4]

ok, can you give me more info about scene or a scene file that can reproduce same effect

I can send you the scene file when I get home.

[ChrisVis]

Beta 0.6.7c does NOT crash Cinema 4D on startup.

However, the problem with halting during render of animations remains.

at this frame can be zero polygon count?

The frame that halts is not the same for each time I try on the same animation. And there should not be any difference in polygon count compared to the frame before it.

Hi DennisK4 and aoktar,

I rendered a lot of animation frames this night. First with 0.6.4 and the C4D batch renderer (for the first time). Got random crashes with that one, after like 50 frames, then after even 20 or 10 frames.
So I decided to render with the Preview Renderer again (with full scene update active, only 333ms total export time, about 40s rendering time per frame). With this it rendered 125 frames without problem, rendering done.

After that I tried 0.6.7b, also with Preview Renderer, same settings, same project, only different camera. Then after 106 Frames it suddenly stopped... not crashed, but halted at one frame doing nothing and showing only a black screen forever.
Here is how the log looks like at the beginning of Frame 106:
(Rendering frame:106/250 done:%0 step:1
-Rendering frame:106/250 done:%-1.#IO step:1
-Rendering frame:106/250 done:%-1.#IO step:1
-Rendering frame:106/250 done:%-1.#IO step:1
-Rendering frame:106/250 done:%-1.#IO step:1

Saying this forever after I stopped and startet Preview renderer again. That happend for the first time ever, usually it crashes C4D.

Now testing 0.6.7c, had a crash with same settings using Preview Renderer now after about 20 frames. (Rendering from Frame 110 to 250). So no crash was at the same frame, it really happens randomly.

Only thing I may have been doing different with the 125 frames rendered completely, that I may have left one GTX580 inactive (my viewport one), rendering with only the other 7 GPUs. All other test described I had the Viewport GTX580 card also active in rendering.
So now I am testing the 0.6.7c again with only 7 GPUS and Viewport card inactive, rendered 50 frames without crash so far.

Last year I rendered several 1000 of animation frames with C4D R13 and the exporter plugin and NVIDIA 280.26 driver with Octane 0.258e and all 8 GPUs active... and never had a crash!
I went backwards to this old NVIDIA driver because some guys in the forum told it is the most stable one with octane, as I also experienced. Had several crashes with exact the same settings except newer NVIDIA drivers, thats why I stayed with the old one for a long time.

So now I am with the newest NVIDIA drivers, new C4D R14, new C4Doctane plugin and experiencing these random crashes when rendering animations again. I tend to believe it is a NVIDIA driver problem or something with voxelisation or scene loading to several GPUs.

By the way: The preview rendering frame skipping is still there, when full scene update is inactive.
I also noticed a little bug with GPU activity handling since 0.6.7: When I load a scene and start rendering, C4Doctane by default uses all my 8 GPUs, but in the settings I have 1 inactive. I have to tick and untick it to get it inactive first. Not a big deal, but just wanted to report, maybe you changed something in the GPU settings panel.


At least I can do my work now, even if not everthing works how it should for me, I got workarounds to do final animation renderings inside C4D. The workflow inside C4D is a huge timesaver compared to the exporting and standalone workflow, love how it responses in C4D, setting up lights and other work progress is shown almost instantly
Hope you get these random crash things handled somehow or at least what exact causes the problem.
Keep up the good work!

Cheers,
ChrisVis

[aoktar]

@Chrisvis: are you meaning octane preview rendering? Or Picture Viewer rendering? Actually both supported some functionality now. You can do flytroughts and incremental update geometry animations.
I advice that you use Picture Viewer for final rendering. It's more reliable because it uses c4d native update mechanism. And it's revised for ignored frames

If you get again some errors on rendering, i'll want a scene that can produce this issue.

For gpu settings: it's temproraly removed for a problem. I'm going to add a option for using gpus to render setting

[Jaybee]

Beta 0.67c & R13 = Success!!

@Aoktar, great work. Installed fine (I just needed to copy contents of Libs64 folder files over to main C4D directory) and no conflicts with other plugins.

LiveDB materials and Environment textures working fine and no crashes so far.

Histogram is fixed, no data loss spikes showing.

Top work!

Thanks

[ChrisVis]

@Chrisvis: are you meaning octane preview rendering? Or Picture Viewer rendering? Actually both supported some functionality now. You can do flytroughts and incremental update geometry animations.
I advice that you use Picture Viewer for final rendering. It's more reliable because it uses c4d native update mechanism. And it's revised for ignored frames

If you get again some errors on rendering, i'll want a scene that can produce this issue.

For gpu settings: it's temproraly removed for a problem. I'm going to add a option for using gpus to render setting

Hi aoktar,

I mean octane preview rendering with the "start preview" button, not the picture manager of C4D. Is there another option... what do you mean with C4D Picture Viewer, or is it just some translation thing and the same as C4D Picture Manager?
I got more crashes with Rendering with the Picture Manager than with the Octane Preview Renderer so far...

Now I got an API Error on my running animation with 7 external GPUs with the preview rendering and full scene update active. After about 90 Frames of rendering, 1 of my GTX590 suddenly stopped working:

First time ever I had this error (0.6.7c), Octane stopped rendering, C4D freezed, but no crashreport. That leads me back to my intuition, that there might be some NVIDIA driver GPU syncing problem going on somehow. Bummer...

Is there any console like program out there, that can read out or log the NVIDIA driver activities? That might help in finding the problem here...

[aoktar]

@Chrisvis: this is render settings. http://render.otoy.com/manuals/Cinema4D/?page_id=111

This error window show something gone wrong on render side. Maybe a memory or texture limit problem.
In Octane settings window->others->show log this can show maybe something or check your gpu ram