When I enable octane block rendering, the OCIO crash window always pops up. This has been going on for a week. This problem makes my rendering work very unpleasant, please help me see how to solve this problem.
Crash log:
Started logging on 15.04.23 15:54:09
OctaneRender Studio+ 2022.1.1 (12000102)
OCIO config file:C:\Software\OpenColorIO-Configs-feature-aces-1.2-config\aces_1.2\config.ocio loaded.
VRAM used/free/max:0Kb/24Gb/24Gb Out-of-core used:0Kb RAM used:12.781Gb total:63.863Gb OpenGL free/total:0/0
FumeFx library initialisation error!
--------------------------- EXPORT LOG ---------------------------
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Shader error.....
Export materials time= 32965.984 ms
Collect objects time= 5.119 ms
Mesh creation time = 1584.304 ms.
Api update time: 3.515 ms.
VRAM used/free/max:7.698Gb/13.141Gb/24Gb Out-of-core used:0Kb RAM used:26.914Gb total:63.863Gb OpenGL free/total:0/0
device 0: data size doesn't match memory size
MB:0/0 ST/MOV:0/613 Nodes:1382 Tris:10.223m DispTris:0 Hairs:0 Meshes:633
Textures Grey8/16:28/9 Rgb32/64:40/6
Enable zone renderer OCIO file crash
Hi,
First of all, here is the Octane for Cinema 4D forum section link: viewforum.php?f=30 where to post Octane C4D related matters.
Regarding the issue:
• it doesn't seem to be related to OCIO.
• have you considered the "ACES checkbox" instead of loading it through OCIO? Usually, majority of users don't actually have the necessity to load the OCIO config. My assumptions may be off for your case.
• worth double-checking what's going on (troubleshooting) at material/shading level.
First of all, here is the Octane for Cinema 4D forum section link: viewforum.php?f=30 where to post Octane C4D related matters.
Regarding the issue:
• it doesn't seem to be related to OCIO.
• have you considered the "ACES checkbox" instead of loading it through OCIO? Usually, majority of users don't actually have the necessity to load the OCIO config. My assumptions may be off for your case.
• worth double-checking what's going on (troubleshooting) at material/shading level.