OctaneRender™ 2020.2.3

[PolderAnimation]

I have two bug reports

1. region render does not render region but whole image.

2. Octane has an issue with getting the P_FOCAL_LENGTH pin value from an alembic camera.
We use a scripted graph to get all needed camera info from the alembic camera and plug them into a thinLensCamera node so we can adjust other parameters still.
Up to and including octane 2020.2.1 this works perfect, but in 2020.2.3 the focal length does not seem to get updated when skipping through the timeline.
Attached is an example orbx to showcase the issue. The scripted graph code can be read by opening the orbx in a text editor.

[funk]

BUG: Compositing nodes not matching Main Beauty Pass

I ran into an issue with compositing nodes.

When using a "Render AOV output" directly, or through a "Composite AOV output layer", the output should be an exact match to the Main beauty pass.

This is not the case in my attached scene and screenshots:

oct_2020_2_compositor_clipping_bugs_002.png

There appears to be some kind of clipping (?) causing levels to be different in 1 AOV, and colors to change in the other.

NOTE: You'll need to make sure the ACES OCIO config is set in preferences.

[karl]

BUG: Compositing nodes not matching Main Beauty Pass

I ran into an issue with compositing nodes.

When using a "Render AOV output" directly, or through a "Composite AOV output layer", the output should be an exact match to the Main beauty pass.

This is not the case in my attached scene and screenshots:

oct_2020_2_compositor_clipping_bugs_002.png

There appears to be some kind of clipping (?) causing levels to be different in 1 AOV, and colors to change in the other.

NOTE: You'll need to make sure the ACES OCIO config is set in preferences.

Hi Funk, I've found the two problems (clipping extremely saturated colors and missing scaling of post processing). With the fixes (which should be in the next release) all three images match exactly. For posterity, OCIO isn't actually required to produce the issues if you use an intermediate value of "Saturate to white".

[funk]

Thanks karu

[enricocerica]

Hi Enrico,
could you share a screenshot of the log window after/during crash?

ciao Beppe

I tried to reproduce the problem to include the log and surprisingly I can't reproduce this issue I got for several months.
I gradually added all my video cards while rendering and was astonished to see that I got no failed one ...
Tried several times and no, seems to work fine.
I think I updated to the last Nvidia drivers recently and maybe some Windows updates too ...
Very confused but happy as well
Hope it will stay.

[bepeg4d]

Hi Enrico,
great

Yes updating Win 10 to 2004 or greater is crucial for stability with recent Nvidia drivers.

Happy GPU rendering,
ciao Beppe

[PolderAnimation]

NEVERMIND THIS POST

I also want to ask again for the functionality to make searching for node (when creating them) faster. For example Nuke and Houdini use the TAB menu. When pressing TAB you can start typing and the node you are searching for appears. This works incredible intuitive and fast and works way better than right mouse button click and looking through a whole menu and finding you nodes.

I already posted this in the feature request and a lot of people like the idea.

https://render.otoy.com/requests/?qa=46 ... how=46#q46

[galleon27]

I also want to ask again for the functionality to make searching for node (when creating them) faster. For example Nuke and Houdini use the TAB menu. When pressing TAB you can start typing and the node you are searching for appears. This works incredible intuitive and fast and works way better than right mouse button click and looking through a whole menu and finding you nodes.

I already posted this in the feature request and a lot of people like the idea.

https://render.otoy.com/requests/?qa=46 ... how=46#q46

Press Space

[PolderAnimation]

I also want to ask again for the functionality to make searching for node (when creating them) faster. For example Nuke and Houdini use the TAB menu. When pressing TAB you can start typing and the node you are searching for appears. This works incredible intuitive and fast and works way better than right mouse button click and looking through a whole menu and finding you nodes.

I already posted this in the feature request and a lot of people like the idea.

https://render.otoy.com/requests/?qa=46 ... how=46#q46

Press Space

wauw... thanks. just out of curiosity how long is this feature in octane?

[abstrax]

I have two bug reports

1. region render does not render region but whole image.

You most likely have deep pixel rendering enabled or some Cryptomatte passes. In both cases the interactive render region doesn't work, which is currently a limitation. We hope to have that limitation removed at some point in the future, but didn't have the chance to do that yet.

2. Octane has an issue with getting the P_FOCAL_LENGTH pin value from an alembic camera.
We use a scripted graph to get all needed camera info from the alembic camera and plug them into a thinLensCamera node so we can adjust other parameters still.
Up to and including octane 2020.2.1 this works perfect, but in 2020.2.3 the focal length does not seem to get updated when skipping through the timeline.
Attached is an example orbx to showcase the issue. The scripted graph code can be read by opening the orbx in a text editor.

If you could post an example of this problem, that would be very helpful. Thanks.