Capture to custom AOV not working?

Maxon Cinema 4D (Export script developed by abstrax, Integrated Plugin developed by aoktar)

Moderators: ChrisHekman, aoktar

Post Reply
jackplus
Licensed Customer
Posts: 7
Joined: Sun Jul 03, 2016 5:28 pm

Hi,

I'm trying to use the Capture to custom AOV node but seems like it's not working. I am able to create custom AOV based on object/material but not texture. Am I connecting it the wrong way or am I missing something here? I'm using Octane 2020.2.3-R3 on Cinema4D S24.111. I've attached my .c4d file, any help would be great.
Thanks.
Screenshot 2022-03-18 154341.jpg
AOV_Test.zip
(111.51 KiB) Downloaded 84 times
jayroth2020
OctaneRender Team
Posts: 488
Joined: Mon May 04, 2020 7:30 pm

Please use the latest version of the Octane plugin: 2021.1.3
Puget Systems / Intel Core Z790 ATX / RTX 4090 / Cinema 4D
jackplus
Licensed Customer
Posts: 7
Joined: Sun Jul 03, 2016 5:28 pm

jayroth2020 wrote:Please use the latest version of the Octane plugin: 2021.1.3
Thanks Jay. But it's still not working for me.
Screenshot 2022-03-22 170214.jpg
jayroth2020
OctaneRender Team
Posts: 488
Joined: Mon May 04, 2020 7:30 pm

We have discovered a small bug that is causing the AOV to be assigned incorrectly when sent to Octane for render. It is possible to correct this error yourself using Standalone. You can also test this locally with the Octane nodegraph in Live Viewer: select the material with the Capture to Custom AOV node and choose Live Viewer > Help > Show Octane Nodegraph. In the nodegraph, select the CustomTexture node. In the Custom AOV attribute to the right, set the desired Custom AOV, and then immediately close the graph. This will be effective ONLY until you restart Live Viewer, as the bug will then reappear. Therefore, it is necessary to make this change in Standalone for final render, but you can use the Live Viewer nodegraph to diagnose and test this way.
Puget Systems / Intel Core Z790 ATX / RTX 4090 / Cinema 4D
jackplus
Licensed Customer
Posts: 7
Joined: Sun Jul 03, 2016 5:28 pm

jayroth2020 wrote:We have discovered a small bug that is causing the AOV to be assigned incorrectly when sent to Octane for render. It is possible to correct this error yourself using Standalone. You can also test this locally with the Octane nodegraph in Live Viewer: select the material with the Capture to Custom AOV node and choose Live Viewer > Help > Show Octane Nodegraph. In the nodegraph, select the CustomTexture node. In the Custom AOV attribute to the right, set the desired Custom AOV, and then immediately close the graph. This will be effective ONLY until you restart Live Viewer, as the bug will then reappear. Therefore, it is necessary to make this change in Standalone for final render, but you can use the Live Viewer nodegraph to diagnose and test this way.
Thanks, it works! Hope this get fixed soon.
User avatar
aoktar
Octane Plugin Developer
Posts: 16066
Joined: Tue Mar 23, 2010 8:28 pm
Location: Türkiye
Contact:

It will be fixed on next build, based on 2021.1.4 SDK
Octane For Cinema 4D developer / 3d generalist

3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Post Reply

Return to “Maxon Cinema 4D”