OTOY Forums

UON.Visuals wrote: Fri Sep 05, 2025 4:38 am I narrowed it down! It's definitely Octane because it doesn't happen in the standard renderer.
The leak in my project is caused by a spline/sweep object with a lot of points. Every frame rendered, the ram doesn't get flushed or something and the ram fills up more. I can fill up my ram withing a few minutes just by cranking the points to ridiculous levels while removing everything else so each frame takes a couple seconds to render.
I can send an example scene if you want.

Secretwoodsrl wrote: Thu Sep 04, 2025 8:57 am

Tim_Twisted wrote: Thu Sep 04, 2025 6:54 am

Secretwoodsrl wrote: Wed Sep 03, 2025 3:45 pm The "Use denoised beauty pass" option in Render Settings -> OctaneRender still doesn't work.
I prefer not to use the Octane Render AOV Manager (most of the time) since C4D native saving system is more straightforward and it works better with C4D Render Queue.
The bug was introduced in v1.6.1 Hotfix, so for now I’ve rolled back to v1.6.

Outside of the file name, is there a difference between using this and a standard Demain pass? If you only want a single file, you can just uncheck Beauty.

We use Render Queue in C4D a lot. The issue is that Render Queue always saves frames using C4D’s native saving system, regardless of whether we enable it or not in the render settings.
So if we use Octane Render AOV Manager to export our frames, we'll end with duplicate frames using Render Queue:
- One output created by C4D’s native saving system
- One output created by Octane’s AOV export settings.
So every time we have to manually delete the unwanted frames made by Render Queue/C4D Saving System and just keep only the correct ones exported by Octane.

It's not a big deal, but sometimes those unwanted frames can fill our storage.

Powel2097 wrote: Fri Sep 05, 2025 8:33 am I know it is not a fix, but setting up the C4D Saving option to mp4, gives you just one file to delete instead of whole img sequences. Even if it is off, Render queue just gives you one mp4.
I was struggeling with that myself.

jalejune wrote: Mon Sep 08, 2025 9:53 pm I think this release is mis-labeled - headline says 2025.2.3-v1.7.0

but .zip downloads say 2025.3-v1.7.0

i've been looking for a 2025.2.3 stand alone build for mac until I noticed this error.

If I'm wrong...apologies

astrofalcon wrote: Wed Sep 10, 2025 4:35 pm Is there a build that correctly detects/supports Cinema 4D 2026 yet? Will that come with v1.7.1?

Can we just manually install this build for Cinema 4D 2026?

Thank you!

ChrisHekman wrote: Wed Sep 10, 2025 5:42 pm

astrofalcon wrote: Wed Sep 10, 2025 4:35 pm Is there a build that correctly detects/supports Cinema 4D 2026 yet? Will that come with v1.7.1?

Can we just manually install this build for Cinema 4D 2026?

Thank you!

We have a working C4D R2026 version atm. We are aiming to release it with 1.7.1 yes