Render Error with ACES OCIO

Forums: Render Error with ACES OCIO
Maxon Cinema 4D (Export script developed by abstrax, Integrated Plugin developed by aoktar)

Moderator: aoktar

Render Error with ACES OCIO

Postby Maxter » Mon Dec 18, 2023 3:19 pm

Maxter Mon Dec 18, 2023 3:19 pm
Hello,

suddenly Octane can't render with my loaded ACES OCIO. I changed nothing on my PC or project. Even my old scenes are not working anymore.
I get this Error Log:

Started logging on 18.12.23 16:11:17

OctaneRender Studio+ 2023.1.1 (13000100)

OCIO config file:C:\ACES_OpenColorIO-Configs\aces_1.2\config.ocio loaded.
VRAM used/free/max:0Kb/10Gb/10Gb Out-of-core used:0Kb RAM used:12.278Gb total:63.923Gb OpenGL free/total:0/0
Scene created in plugin version 10021701
Scene plugin version is older than version:2023.1.1
Plugin will convert the parameters of displacement texture.
Animated attributes should be changed by manually!
--------------------------- EXPORT LOG ---------------------------
Export materials time= 5.121 ms
Collect objects time= 3.405 ms
Mesh creation time = 103.203 ms.
Failed to build OCIO output transform for imager: No OCIO config loaded
Api update time: 11.515 ms.
MB:0/0 ST/MOV:0/2 Nodes:20 Tris:657k DispTris:0 Hairs:0 Meshes:3
Textures Grey8/16:0/0 Rgb32/64:0/0

I tried to use the Octane version 2022.1 but that doesn't matter. The only way I can now render is to delete the folder with the OCIO...
But this is no option for me :cry:
Octane for Cinema 4D
5950X | 64 GB 3600MHz DDR4 | 2x 3080 RTX 10 GB | 1200W PSU
Maxter
Licensed Customer
Licensed Customer
 
Posts: 21
Joined: Mon Sep 09, 2019 7:10 pm
Location: Germany

Re: Render Error with ACES OCIO

Postby elsksa » Mon Dec 18, 2023 3:46 pm

elsksa Mon Dec 18, 2023 3:46 pm
Maxter wrote:The only way I can now render is to delete the folder with the OCIO...
But this is no option for me

Technically to render out, the ACES config file is not needed.
See this page for reference.
Therefore, it is possible to export as ACES compliant without the config file, by setting the EXR color space to ACEScg AP1, natively included as shown on the page.

The file path seems OK and ends up with config.ocio. That doesn't mean the issue doesn't originate from there, though.

Are the files identical to the original package? Is there any OS file access restriction?

Sharing screen captures of how ACES is setup in Octane C4D (prefs, export and viewing) would be informative.
Does it work during render previews (frame buffer)?
elsksa
Licensed Customer
Licensed Customer
 
Posts: 784
Joined: Sat Jul 24, 2021 1:06 am

Re: Render Error with ACES OCIO

Postby Maxter » Mon Dec 18, 2023 4:07 pm

Maxter Mon Dec 18, 2023 4:07 pm
I heard form this workflow but mine worked with no problems.
I added some screenshots how I setted it up.

Once I removed the OCIO and all links to it, I saved it and restarted C4D. After that I imported the OCIO and
now it works again... I really don't know what the problem was
Attachments
viewer.JPG
ocio.JPG
color_mgmt.JPG
Octane for Cinema 4D
5950X | 64 GB 3600MHz DDR4 | 2x 3080 RTX 10 GB | 1200W PSU
Maxter
Licensed Customer
Licensed Customer
 
Posts: 21
Joined: Mon Sep 09, 2019 7:10 pm
Location: Germany

Return to Maxon Cinema 4D


Who is online

Users browsing this forum: Bing [Bot] and 10 guests

Wed Jun 05, 2024 7:32 am [ UTC ]