OctaneRender® 2022.1 XB 1

[SSmolak]

There is huge OSL problem with this version. Some OSL code that works fine with latest 2021 version here completely doesn't work and even cause black screen - no render.

To make them works there is need to create new scene and copy objects with materials from old. Old scene with custom OSL code completely doesn't work.

[Meet]

Does the standard volume medium support color(Cd) channel of the VDB to color the VDB using scatter color channel?
Imported a vdb having Cd channel from houdini, doesn't seem to be reading the channel in either standard volume medium node or volume to texture node

Edit - I merged all scalar Cd values to one Vector Cd value and still no color

Cd single.PNG (11.27 KiB) Viewed 2975 times

[Meet]

Another question, is it possible for mesh to fog node to have some sort of volume padding like in arnold?

mesh to volume.PNG (23.72 KiB) Viewed 2991 times

[aoktar]

There is huge OSL problem with this version. Some OSL code that works fine with latest 2021 version here completely doesn't work and even cause black screen - no render.

To make them works there is need to create new scene and copy objects with materials from old. Old scene with custom OSL code completely doesn't work.

Share some screen capture and scenes to show what are you saying.

[galleon27]

Does the standard volume medium support color(Cd) channel of the VDB to color the VDB using scatter color channel?
Imported a vdb having Cd channel from houdini, doesn't seem to be reading the channel in either standard volume medium node or volume to texture node

The attachment vdb color.PNG is no longer available

Edit - I merged all scalar Cd values to one Vector Cd value and still no color

The attachment Cd single.PNG is no longer available

Yes, it does support it. I've attached the scene file for both Houdini and Standalone.

[Meet]

Yes, it does support it. I've attached the scene file for both Houdini and Standalone.

Thank you for the files, helped with troubleshooting.
I understood why it wasn't working, I had to toggle on the "Cd" option in the import settings

Seems to be working fine in standalone, doesn't work in C4d, maybe Aoktar can shed some light on that. I will post it in the C4D section.

[john_otoy]

There is huge OSL problem with this version. Some OSL code that works fine with latest 2021 version here completely doesn't work and even cause black screen - no render.

To make them works there is need to create new scene and copy objects with materials from old. Old scene with custom OSL code completely doesn't work.

I have sent you a PM. Can you please provide an ORBX that works in 2021.1.5 but not in 2022.1 XB1? Thanks

Can you also open a log window to check for any errors? A black screen may mean you haven't set an OCIO config path in your Standalone preferences.

[GXGsynth]

What is the correct protocol to utilize the new 'ACES tone mapping' feature in regards to OCIO view/Force tone mapping/response curve/gamma/save format?

I'm having trouble getting exported images to look exactly as they do within the Live Viewer window

[haze]

Another question, is it possible for mesh to fog node to have some sort of volume padding like in arnold?

mesh to volume.PNG

Thank you for your suggestion, I think it makes sense and will add it to our list.

[karl]

What is the correct protocol to utilize the new 'ACES tone mapping' feature in regards to OCIO view/Force tone mapping/response curve/gamma/save format?

I'm having trouble getting exported images to look exactly as they do within the Live Viewer window

Those settings should result in the exported image being identical to what you see in the render viewport, except in two cases(1)(2). That matches the behavior I see when using those same settings. Because the OCIO view is set to None (sRGB) and the save color space is set to sRGB, both should use the tone mapping to sRGB as set up in the imager, which in this case says to use ACES sRGB output and ignore all the other pins (as explained by the tooltips for the relevant pins).

(1) If display color management is set up differently between Octane standalone and the viewer you're using to view the exported image, the two applications will be applying different color transforms to the image when displaying it. In Octane standalone, check Preferences > Color management > Display color profile to see if a color profile is being used ("sRGB (default)" means no additional color transform will be applied, so the viewport should match any non-color-managed image viewer).

(2) If you're on macOS and are using the HDR viewport (see Preferences > Color management > HDR viewport), the tone mapping settings in the camera imager node are bypassed for the render viewport because the OS does the tone mapping.

If neither of those cases apply and you still see a difference, please attach a scene or some screenshots demonstrating the difference because some further investigation is needed.