OctaneRender™ 2021.1 XB1

A forum where development builds are posted for testing by the community.
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
Post Reply
User avatar
funk
Licensed Customer
Posts: 1206
Joined: Mon Feb 07, 2011 1:24 pm
Location: Australia

vijay_thirukonda wrote:
funk wrote:BUG: Compositor color correction ignores "enable imager/post" when disabled on render AOV

I have a render AOV plugged into a color correction. If I disabled the "enable imager" or "enable post processing" checkboxes on the render AOV, nothing changes.
These enable imager/post settings are only used from a top-level node ((i.e.) when connected directly to the AOV output group node) and ignored from any intermediate nodes in the chain. The scene you provided has color correction as a top-level node, which doesn't have those settings. Initially, these settings were intended only on composite AOV nodes, But we extended them to Image AOV output and Render AOV output nodes for debug purposes. If you want to use these settings on any other nodes then you need to connect the node to the composite AOV node and use the composite AOV as a top-level node. Sorry for the confusion and inconvenience, we will revisit this in some future build.

Thanks,
Vijay
Thanks for explaining Vijay. Sorry I completely missed this in the tooltips!

This seems to prevent you from doing anything useful with the "Post Processing" Render AOV (I may be missing something though).

eg. Using a composite AOV output, if I wanted the "main" pass on layer 1 (with no post processing glow), and the "Post Processing" Render AOV (in layer 2 using the add blend mode), I end up getting double the "glow" in my "Out1" output when "enable post processing" is enabled, and NO glow when it's disabled.

So I can't for example, color correct the post processing AOV or change its opacity etc

Is there a way around this? I guess we would really need a separate "post processing" and "imager" node in the compositor.
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
Top
User avatar
funk
Licensed Customer
Posts: 1206
Joined: Mon Feb 07, 2011 1:24 pm
Location: Australia

BUG: Diffuse/Reflection filter have red tint when using d65 white light spectrum

1. Render scene and look at the diffuse filter and reflection filter AOVs. These have a red tint (which is incorrect)
2. If you set kernel > white light spectrum to legacy, it fixes it

It probably affects some other AOVs, but I'll let you guys go through them
Attachments
diffuse_filter_red_tint.ocs
(45.24 KiB) Downloaded 180 times
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
Top
User avatar (Default)
karl
OctaneRender Team
Posts: 396
Joined: Sun Oct 13, 2019 11:26 pm

funk wrote:BUG: Diffuse/Reflection filter have red tint when using d65 white light spectrum

1. Render scene and look at the diffuse filter and reflection filter AOVs. These have a red tint (which is incorrect)
2. If you set kernel > white light spectrum to legacy, it fixes it

It probably affects some other AOVs, but I'll let you guys go through them
This was caused by the same thing as the red tint on denoiser output, so will also be fixed in XB2.
Top
User avatar (Default)
y81r
Licensed Customer
Posts: 64
Joined: Sat May 06, 2017 10:23 pm

Hi Guys, as described here:
viewtopic.php?f=85&t=77937&p=401956#p401955
c4d Test File attached.

Thanks
Yassin
Attachments
VDB_TEST.zip
(9.87 MiB) Downloaded 211 times
Top
User avatar
funk
Licensed Customer
Posts: 1206
Joined: Mon Feb 07, 2011 1:24 pm
Location: Australia

BUG: Custom AOV 1 not working

I have a sample here with 2 materials. One is set to custom aov 1, while the other is set to custom aov 2.

Custom aov 2 is working (I see a red mask), while custom aov 1 doesnt (the aov renders black).
Attachments
custom_aov_1_broken.ocs
(52.02 KiB) Downloaded 192 times
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
Top
User avatar (Default)
nibbler
Licensed Customer
Posts: 54
Joined: Wed Jul 23, 2014 6:50 pm

Great work!

OS X Metal 2021.1 (inclusive Cross Platform Network Rendering!) coming when?

Hardly awaiting it.
Several MacPros + Win PC • Cinema 4d • Octane Mac & Octane Win
Top
User avatar
abstrax
OctaneRender Team
Posts: 5506
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

funk wrote:BUG: Custom AOV 1 not working

I have a sample here with 2 materials. One is set to custom aov 1, while the other is set to custom aov 2.

Custom aov 2 is working (I see a red mask), while custom aov 1 doesnt (the aov renders black).
Thank you for the report. This will be fixed in the next release.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
Top
User avatar
funk
Licensed Customer
Posts: 1206
Joined: Mon Feb 07, 2011 1:24 pm
Location: Australia

Thanks abstrax and karu
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
Top
User avatar
funk
Licensed Customer
Posts: 1206
Joined: Mon Feb 07, 2011 1:24 pm
Location: Australia

BUG: Regression? Failed to build OCIO output LUT: OCIO error: LookTransform: empty destination color space name.

I was testing out an OCIO config Ed O'Connell posted here: https://drive.google.com/file/d/1SB1Sd_ ... 8TQA6/view

If you set:
OCIO View = "TCAMv2 100 nits office: sRGB Display: 2.2 Gamma - Rec.709"
OCIO Look = "4 Medium Contrast" (the other looks work fine)

Octane 2021 fails with a black render and log error:
"Failed to build OCIO output LUT: OCIO error: LookTransform: empty destination color space name."

This works fine in Octane 2020.2.x though. I guess it could be an issue with OCIO v2, since thats new to 2021
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
Top
User avatar (Default)
karl
OctaneRender Team
Posts: 396
Joined: Sun Oct 13, 2019 11:26 pm

funk wrote:BUG: Regression? Failed to build OCIO output LUT: OCIO error: LookTransform: empty destination color space name.

I was testing out an OCIO config Ed O'Connell posted here: https://drive.google.com/file/d/1SB1Sd_ ... 8TQA6/view

If you set:
OCIO View = "TCAMv2 100 nits office: sRGB Display: 2.2 Gamma - Rec.709"
OCIO Look = "4 Medium Contrast" (the other looks work fine)

Octane 2021 fails with a black render and log error:
"Failed to build OCIO output LUT: OCIO error: LookTransform: empty destination color space name."

This works fine in Octane 2020.2.x though. I guess it could be an issue with OCIO v2, since thats new to 2021
This is caused by a bug in OCIO v2 - that look is the only one in the config that works out to be a no-op, and it seems that OCIO hasn't fully anticipated no-op looks. I'll fix it in Octane and file a bug report with the developers of OCIO.

For now, as a workaround, you can just select "None" instead of any look that produces this error message (since such looks are no-ops anyway).
Top
Post Reply

Return to “Development Build Releases”