Neverending "updating"

[prisonbread]

I've brought this up before (viewtopic.php?f=30&t=64153) and nobody ever responded. Seems like I'm the only one to suffer some of Octane's quirks, but since my issue has returned and halted all progress on a project, I feel I must mention it again. I'm begging for somebody to acknowledge that the situation is strange or to offer some suggestion as to what might be going on!

My problem is that I have a scene that won't render- it prepares for 10 seconds, analyzes frame for 10 seconds, creates geometry for 10 seconds, and then for the remaining 217 seconds it just says "updating." It eventually stops as if it's done rendering and I'm left with a black screen. This simple scene is made up of 2 cloners creating two 4x4x4 stacks of 5 gallon buckets. The project is going to require labels to be on these buckets of course, but in an attempt to troubleshoot and find out what exactly is causing the scene not to render I have removed all textures, HDRI's, etc. Even with nothing but geometry and a white sky texture this damn scene will not render to the PV. I have spent most of the day restarting my computer and force-quitting C4D, just trying to get these pails to render and I'm at my wits end! My rig is pretty suped-up with 64gigs of RAM and twin 1070s, so I really don't think it's a matter of the scene being too heavy; it's something else.

Another odd thing is that when rendering the scene to the LV it takes a really long time and displays erroneous information in the bar at the bottom of the LV during the render. For instance, I am just trying to render 128 samples, yet during the render the picture viewer appears frozen for several seconds at 1728/5000 samples. I dont understand where it's getting that number. When it finally finishes rendering the bar below says it's merely 128 samples and took only 1 second to render while it actually took about a minute to render.

It's a lot of weird stuff going on at once and it's distressing because I simply cannot move forward with what seems like a really simple project. The last thing I want to do is use the standard C4D render, but it's starting to look like I may have to. I have shared the scene and I expect whomever opens it to have zero problems getting it to render, which scares me because it means something about my PC or config is causing this problem. But at least I will know something!

[niestudio]

I don't know if this is a total solution for you, but have you tried ticking render instances in your cloner?
When I open your file and send to octane as is, it takes 2:42
After I tick render instances it takes 0:05

Picture viewer had similar results

Picture_Viewer.jpg (27.02 KiB) Viewed 1338 times

[aoktar]

I don't know if this is a total solution for you, but have you tried ticking render instances in your cloner?
When I open your file and send to octane as is, it takes 2:42
After I tick render instances it takes 0:05

Picture viewer had similar results

The attachment Picture_Viewer.jpg is no longer available

All correct, scene is highly unoptimised. Alse check two pictures for explanation.

[prisonbread]

Niestudio and Ahmet,

Thank you so much for your replies. It's true, the scene was highly unoptimized. Checking "render instances" in the two cloners fixed the problem and I feel foolish for not trying that first; it's octane 101. I've been using octane scatter so long that I forgot the C4D cloner doesn't use instancing unless you tell it to. I will always check that box in the future! I appreciate your time, guys.

-Ben