OTOY Forums

DennisK4 wrote:

ChrisVis wrote:Ok, so now my animation with the picture manager stuck on frame 66 (0.6.7c), gpus are unloaded and nothing happens, staying there till 22 Minutes now. No Crash, but Render Hang Up... I can close the picture Manager and start again or resume... but loose a lot of time, if I don`t babysitt my render.

PictureManagerStopsRendering.jpg

Will try the same scene without the textures later...

I have the exact same problem.

for every scene or a spesific one?

aoktar wrote:

DennisK4 wrote:

ChrisVis wrote:Ok, so now my animation with the picture manager stuck on frame 66 (0.6.7c), gpus are unloaded and nothing happens, staying there till 22 Minutes now. No Crash, but Render Hang Up... I can close the picture Manager and start again or resume... but loose a lot of time, if I don`t babysitt my render.

PictureManagerStopsRendering.jpg

Will try the same scene without the textures later...

I have the exact same problem.

for every scene or a spesific one?

For both of the two different scenes I have tested.

I will send one of them to you in a moment.

By the way, if you do not have any problems with rendering animations could you say which Nvidia drivers you are using and if you leave one GPU to handle everything else while the rest are used for rendering?

Hi aoktar and DennisK4,

I now have rendered the same scene again with C4D picture manager renderer (C4Doctane 0.6.7c), full scene update active, 1024x576Pixel, 400 maxsamples, about 5-8s each frame and rendered 250 frames without hang up or crash! Used 7 GPUs this time (viewport GPU active for rendering this time, only one deactivated in the turbobox) and NVIDIA driver version 320.18 (driver version like all other tests before). So seems to be no driver or viewport GPU problem?
Only difference in the scene I described before: I converted the C4D material with the imagetexture on it (the 8bit greyscale PSD) to an octane material.

May this really have caused the problem (or problem with greyscale images)?

Oh and another difference... we had weather change now with 12 degree cooldown, and my GPUs also cooled down about 10 degrees... so max temp is 60 degree now again. But shouldn`t Nvidia GPUs work perfectly with temps of 80-90 degrees (aircooling)? Or is there a max temp limit for stable 24/7 usage? Or maybe the VRAM got to hot? Didn`t found a program yet to readout the RAM temperature, if one exists.

Maybe also important to mention: Most of the scenes I am working with at the moment were created in R13 and now opened, edited to octane needs and saved in R14. Before I used the same scenes with R13 and the exporter plugin and the Octane standalone 0.258e without crashing.
Most are only simple camera animations with a little bit of object movement, low texture count and mid to high material counts (about 50 different materials I think). Nothing to complex.

I have one or two projects made with R14, I will do some testing with them later.

@aoktar: The crash on frame 66 happened with full scene update active in the C4D picture manager, and with 2 textures in the scene as described. Simple camera movement and a simple scaling animation of a specific object in the scene. Non of the 2 textures are animated in any way. After converting the one C4D material with a texture to octane material it finally rendered without a problem.

Please don`t remove the preview renderer yet: I have still seen some differences in the final renderings of the preview renderer and the picture manager renderer. Will try to recreate a scene and upload it for testing. It is in terms of color and sommetimes even things show up I don`t see in the preview manager. I have linear workflow in C4D project settings activated and color profile set to sRGB. With picture Manager rendering I do not get the same results like in the octane preview window. In the C4D renderer settings under "save" I choose color profile "linear" or "sRGB IEC61966-2.1", but both look different. I can also choose my monitors color space there, which gets closer to the colors I see in the preview window, but not 100% the same.

@DennisK4: What are your specific configurations (C4D Version, scene, material and texture counts and so on)? Maybe we can find some similar things causing the problem... for now I think of a texture load/VRAM sync problem.

@ChrisVis:
Hi, I'm not thinking texture usage can be a problem. Because standart images is converting to octane imagetexture when sending. I'm doing several render tests currently and i cannot reproduce frame halt or ignore problem.

80-90 degree is normal for this gpus i think. But i cannot guarantee non error for 7/24 working in this temperature. I'm not sure about that.

Older scene with exporter works nicely. But integrated plugin has much more functionality. And it's working in backgroud as a supervisor. For this reason some we have some difficulity.

Anymore don't change view profile to linear. Only need is input profile to linear. Plugin uses and convert colors to linear for matching in liveviewer or picture viewer. Also material previews.

Tried many things and works pretty stable so far........BUT....

as soon as i enable update geometry the thing crashes randomly. Sometimes it works 1 Minute, sometimes 5 minutes, sometimes 15 Minutes! This update geometry function, in 3ds max called movable proxy, is the MOST IMPOSTANT thing for real time animation setup. It has not worked stable in any version till now. Achmed you really have to fix that now, thats the very most important thing for animation. Still renderings can be done in the standalone, we need c4d for animation and thatfor update geometry is essential. It is experimental since every release? When will it be final and stable? Please!

Kind regards Chris!

cfrank78 wrote:Tried many things and works pretty stable so far........BUT....

as soon as i enable update geometry the thing crashes randomly. Sometimes it works 1 Minute, sometimes 5 minutes, sometimes 15 Minutes! This update geometry function, in 3ds max called movable proxy, is the MOST IMPOSTANT thing for real time animation setup. It has not worked stable in any version till now. Achmed you really have to fix that now, thats the very most important thing for animation. Still renderings can be done in the standalone, we need c4d for animation and thatfor update geometry is essential. It is experimental since every release? When will it be final and stable? Please!

Kind regards Chris!

at first thanks you. This feature has changed completely as far as first implementation. We will get to stable every function together sdk 1.20. So it's matter of days or weeks depends to sdk.

Same crash when playing with cloners objets when live viewer is on

Hi Aoktar,

great work !!

At the 0.6.8a everything works fine.
No more problem with material!
Not any crash yet!
And special thnx for the function to turn of the geometry update at the rendersettings. This saves houres of time for simple flythroug-animations in big scenes.

The problem of saving twice the same frame was only at the previewer which I used for flythrougs as the final render always does update geometry for every frame. Now this doesn't count any more.

I'm very happy

Hey Achmed!

Please don´t get me wrong in my last post. I know that you have a lot of work and its really a hard work. I really appreciate the work you do, honestly, so please dont missunderstand me. All i wanted to say is, that this feature with updated geometry, is for people like me so important, cause then it is possible for us to use the, what we call here, "real power" of that amazing render engine.

I am pretty sure you understand how it is when you have a complex szene, many sliders, many lights, many materials, a neck breaking deadline and.....crash crash, crash. Can be pretty frustrating

In Case of geometry update there is no stable version, where i can go back, if i have a important project. I really hope youll fix that soon and if i can help in any way, just let me know!

Trying now 0.6.8a and will give feedback!

Kind regards Crhris!

The 0.68a-R14 zip archive has another zip archive labled c4dOctane=0.68a-r14.zip within.
That has another copy of the c4dOctane.cdl64. Where does this file go?