Page 1 of 1

Tried to access attribute via invalid ID A_COMPATIBILITY_VER

Posted: Thu Aug 17, 2023 1:03 pm
by Vivimagic
Cinema 4D 2023.2.2 - Octane Render 2022.1.1r6

I have opened an old scene to grab some materials for a new scene file. When I send the scene to the IPR for the first time the IPR gives me an error and error the log comes up.

Code: Select all

Started logging on 17.08.23 13:59:37

OctaneRender Studio+ 2022.1.1 (12000102)

VRAM used/free/max:0Kb/23.988Gb/23.988Gb  Out-of-core used:0Kb  RAM used:31.437Gb total:94.632Gb  OpenGL free/total:0/0
C:\Program Files\Maxon Cinema 4D 2023\plugins\c4doctane/res/32x/clear.png
--------------------------- EXPORT LOG ---------------------------
Tried to access attribute via invalid ID A_COMPATIBILITY_VERSION (438)
Tried to access attribute via invalid ID A_COMPATIBILITY_VERSION (438)
Tried to access attribute via invalid ID A_COMPATIBILITY_VERSION (438)
Tried to access attribute via invalid ID A_COMPATIBILITY_VERSION (438)
Tried to access attribute via invalid ID A_COMPATIBILITY_VERSION (438)
Tried to access attribute via invalid ID A_COMPATIBILITY_VERSION (438)
Tried to access attribute via invalid ID A_COMPATIBILITY_VERSION (438)
Tried to access attribute via invalid ID A_COMPATIBILITY_VERSION (438)
Export materials time= 2281.901 ms
Collect objects time= 12.171 ms
Mesh creation time = 1966.625 ms.
Failed to build OCIO output transform: No OCIO config loaded
Api update time: 6.093 ms.
 MB:0/0  ST/MOV:0/723  Nodes:2101  Tris:6.514m  DispTris:0  Hairs:0  Meshes:694
 Textures Grey8/16:0/0  Rgb32/64:5/0
Don't know what exactly it referencing but it stopping the render to happen as it just shows a black box in the IPR.
The issue is that if I send this to the farm and if each node has trouble starting up with the errors I won't be able to render on the farm.

Any idea what to do to fix the the error?

Can't send file due to NDA.

Re: Tried to access attribute via invalid ID A_COMPATIBILITY_VER

Posted: Thu Aug 17, 2023 1:27 pm
by aoktar
It's not an error would cause any trouble for you. It's an warning we trying to access unavailable attribute in a node.