Octane get stuck "Updating"; have to force-quit C4D Tweet

[prisonbread]

Okay, sorry for blowing up the forums this week, my schedule has had me on projects that keep presenting obstacles in octane and there's no way around, only through!

This issue is very simple, at least a few times a week Octane gets hung up on the updating step. I can save and interact with the project, but the render is stuck updating FOREVER, black screen - see attached. I am forced to quit C4D via the task manager and start over if I wish to attempt to render successfully to the Picture Viewer again. I can tolerate this a few times a week, but this latest scene is causing Octane to lockup on updating every other time I send it to render in the PV. I have noticed that the times it renders successfully, it exports materials (takes like 5 seconds), then updates (takes 1-3 seconds) and then starts rendering. On the occasions that it gets locked up, it skips the exporting materials step and goes straight to the updating step which lasts indefinitely. I have noticed that the times it locks up I have just updated the Live Viewer a few moments before sending to the Picture Viewer. It's like it doesn't want to export the materials again because it just did in order to render to the Live Viewer.

The scene is super simple, it's two objects basically. It's a figurine of a WWII aircraft, sitting on a map which is just a plane with a semi-elaborate texture I put together in Substance Designer. Both textures (plane and map) are using normal, roughness, and diffuse maps, while the map is also using displacement. Could one of these textures be the thing that keeps clogging the pipeline?

Attached is an image of the scene I am trying to render and then an image of it stuck on the updating step of the very same scene just moments after. All I did in between was change the camera imager on my Octane camera and preview that via the Live Viewer. Any ideas are appreciated, because this is really throttling progress on the project.

Thanks for your time,

-Ben

[omardex]

I'm having this very same error in my machine, any light on this?

[aoktar]

I'm having this very same error in my machine, any light on this?

You may have lot of triangles on PV rendering or cuda errors. Delete some part of scene until defeat the problem if it's about limits or cuda errors, etc..
Also check this: https://docs.otoy.com/Cinema4DH/C4DPlug ... Tricks.htm

[omardex]

Thanks aoktar, maybe its the driver I'm on a 980ti with 2 latest versions of the drivers happening, always have to force close the app using task manager.

my scenes are pretty simple sub 200k polys and its happening in different projects.

when I get to my pc I'll check the logs and post them here maybe they help for future references.

also I'm on the 3.08 test build 6.1 of octane if this also helps.

[omardex]

Hi, Attached is the log from an x scene, before the line that says Export log what is written is from the live viewer that load the model correctly and renders accordingly, after the line Export log is from the rendering in the picture viewer.

the scene is a generic one just to illustrate what is happening to me lately in almost all my current projects, if I force quit c4d through the task manager and open it again and render directly it renders normally.

Thanks.

[aoktar]

Could you connect me by PM?

[omardex]

Hi, in my side I doesn't have anymore the issue, after updating to 3.08 RC1 I suppose is a CUDA errors as you said, the 39x.xx drivers have a newer version, with my card and the software surely made some incompatibilities, but as the newer octane uses newer Cuda there are no new issues, at least on my end.

I'm really happy with the new stability.

Thanks!