OctaneRender™ 2021.1 XB1 Tweet

[Kalua]

Thanks! Good to know.
I think is C4D which is setting 100 as default - or perhaps pre-2020 shaders are set to 100 when reloaded.
Regards,

[mojave]

BUG: RTX On renders this wrong (EDIT: on a 3090)

The last scene I was working on in 2020.2.3 looks completely wrong in 2021.1 XB1, and Im not really using any advanced features. I've started reducing the scene and have found at least 1 issue with RTX on, rendering incorrectly.

rtx_on_is_wrong.png

This issue will be fixed in the next release. Thank you for your help.

[funk]

BUG: RTX On renders this wrong (EDIT: on a 3090)

The last scene I was working on in 2020.2.3 looks completely wrong in 2021.1 XB1, and Im not really using any advanced features. I've started reducing the scene and have found at least 1 issue with RTX on, rendering incorrectly.

rtx_on_is_wrong.png

This issue will be fixed in the next release. Thank you for your help.

Great news. Thanks Mojave

[funk]

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.

[funk]

BUG: Compositor color correction INVERT does nothing

Just use the previous post's OCS and try to use INVERT on the color correction node. It does nothing

[funk]

BUG: OSL error in this example

I was just doing some random stuff in the new release and this node setup gives me an OSL error

Render the scene and look at the log viewer:

Code: Select all

<nodes>:38: error: indexing into non-array or non-component type

We generated invalid OSL code
<nodes>:38: error: indexing into non-array or non-component type

Failed to compile OSL shader.


[funk]

BUG: Anisotropy still looks faceted (no change from 2020.2.3)

Im trying to test anisotropy to match the smooth results from the first post, but I'm seeing no change from 2020.2.3

aniso_test_01.png (71.41 KiB) Viewed 5341 times

Is there something I'm missing or is this broken in this release?

EDIT: It seems to be because the modo plugin exports geometry with unwelded vertices. I can force "merge unwelded vertices" in the plugin per mesh, but I'm wondering if this could be made to work with the current unwelded geo?

[funk]

BUG: Toon material using camera light has blue tint when using d65 white light spectrum

1. If you render this scene, the toon material has a blue tint (which is incorrect)
2. If you set kernel > white light spectrum to legacy, it fixes it

[karl]

BUG: Compositor color correction INVERT does nothing

Just use the previous post's OCS and try to use INVERT on the color correction node. It does nothing

BUG: Toon material using camera light has blue tint when using d65 white light spectrum

1. If you render this scene, the toon material has a blue tint (which is incorrect)
2. If you set kernel > white light spectrum to legacy, it fixes it

toon_d65_color_tint.png

Thanks for the reports - these two issues will be fixed in the next build.

[vijay]

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