OTOY Forums

Posted: **Fri May 16, 2025 1:56 pm**

Updated to Octane 2025.2.0 1.5 to try and fix some bugs, now I just have a new one making my day.

Attached project fails if you render to the render queue, and if you try to run "save project with assets"

Source of the problem is the automatically created rscolorcomp node which is made after running the octane "convert materials" command to convert some native c4d redshift materials into octane equivalents. This was generated in octane 2025.1, but this osl code node seems to be missing in octane 2025.2 ?

project attached

Posted: **Tue May 20, 2025 10:37 am**

Hey

Are you saying when you save the project with Assets, the external OSL node is not taken over?
What if you copy-paste the OSL code into a new OSL Texture node in Octane and make it an internal OSL code, that is not relying on an external file? Does it then render correctly?

Cheers

Posted: **Wed May 21, 2025 1:29 pm**

I loaded a native redshift project into c4d 2025.2 with octane 2025.1 (just one of the c4d content library trees)
I converted the RS materials to Octane materials with the octane convert command
I have saved the project, everything is good.

However since updating octane to 2025.2, c4d/octane now complains that it cannot find the rsColorComp.osl shader. So If I render to render queue, it complains about missing this shader. Or if I run the "save project with assets" command, it tells me it cannot find this osl asset.

The problem comes from the fact that that when octane does the conversion of materials, it hard links to a specific harddrive location:

So as soon as I update to c4d 2026, or update the octane plugin version to 2025.3, or possibly even just try rendering this project on someone else's system, the script file location which octane filled in won't work:

C:\Program Files\Maxon Cinema 4D 2025\plugins\OctaneRender 2025.1\res\rs\rsColorComp.osl

In short, c4d octane creates projects which can only ever work on a single installed version of octane. The moment I update anything, it wont work anymore. Il'l now need to go into every single material and update the path for this octane 2025.1 osl script to the octane 2025.2 folder.

Posted: **Wed May 21, 2025 4:13 pm**

boxfx wrote: Wed May 21, 2025 1:29 pm I loaded a native redshift project into c4d 2025.2 with octane 2025.1 (just one of the c4d content library trees)
I converted the RS materials to Octane materials with the octane convert command
I have saved the project, everything is good.

However since updating octane to 2025.2, c4d/octane now complains that it cannot find the rsColorComp.osl shader. So If I render to render queue, it complains about missing this shader. Or if I run the "save project with assets" command, it tells me it cannot find this osl asset.

The problem comes from the fact that that when octane does the conversion of materials, it hard links to a specific harddrive location:

link.png

So as soon as I update to c4d 2026, or update the octane plugin version to 2025.3, or possibly even just try rendering this project on someone else's system, the script file location which octane filled in won't work:

C:\Program Files\Maxon Cinema 4D 2025\plugins\OctaneRender 2025.1\res\rs\rsColorComp.osl

In short, c4d octane creates projects which can only ever work on a single installed version of octane. The moment I update anything, it wont work anymore. Il'l now need to go into every single material and update the path for this octane 2025.1 osl script to the octane 2025.2 folder.

Thanks for bringing this to our attention. We will change the folder names of the installer/archive so that this stays the same across plugin versions atleast.
Im also gonna take a look if it is possible to have these paths to be relative

OTOY Forums

Missing rsColorComp.osl after 2025.2.0 update

Missing rsColorComp.osl after 2025.2.0 update

Re: Missing rsColorComp.osl after 2025.2.0 update

Re: Missing rsColorComp.osl after 2025.2.0 update

Re: Missing rsColorComp.osl after 2025.2.0 update