OCIO Issues

Forums: OCIO Issues
Sub forum for bug reports

Moderator: juanjgon

Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.


All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)

OCIO Issues

Postby HandcraftedMedia » Sat Sep 10, 2022 4:46 pm

HandcraftedMedia Sat Sep 10, 2022 4:46 pm
I am having a bunch of issues with OCIO in octane (and octane only). I figured it would be better if I outlined everything here. These are all issues that I did not have a few months ago.

First things first I'm on Houdini 19.5.303 and Octane 2021.1.1.5.0 on Windows 10. My OCIO config file is declared in the houdini.env file and I am using aces_1.2.

Issue 1:
The ipr on everything but srgb is way off. And when I set it to OCIO the screen goes completely black.

Screenshot_1507.png
sRGB Setting

Screenshot_1508.png
Aces Setting

Screenshot_1510.png
OCIO Setting


I figured out that the issue stems from the ocio_view node that comes in the render target by default does not show any available views. If I drop down a fresh one from the tab menu or reset the one that comes with it to defaults on the other hand all the views show.

Screenshot_1511.png
OCIO view node that comes in render target

Screenshot_1512.png
Fresh OCIO view node that I dropped down


Once I plugin my custom ocio view node the ipr now looks correct. I do not know why this is happening but it's very frustrating.
Here the project file that includes the original view node that comes in the rop node and then the one I dropped down! https://www.dropbox.com/sh/yypdmdv9stw0 ... kmFwa?dl=0
HandcraftedMedia
Licensed Customer
Licensed Customer
 
Posts: 67
Joined: Thu Jan 10, 2019 12:15 am

Re: OCIO Issues

Postby elsksa » Sun Sep 11, 2022 9:51 am

elsksa Sun Sep 11, 2022 9:51 am
elsksa
Licensed Customer
Licensed Customer
 
Posts: 784
Joined: Sat Jul 24, 2021 1:06 am

Re: OCIO Issues

Postby juanjgon » Mon Sep 12, 2022 9:46 pm

juanjgon Mon Sep 12, 2022 9:46 pm
Hi,

You probably have the answer to the OCIO issue in the last topic you have attached: The OCIO settings for the IPR are available in the RenderTarget /mat HDA, in the Imager tab. Be aware that you need to select the ocio display name (for example "ACES") even if it is the default option to let the HDA populate the views drop-down menu.

I know that this is a weird behavior, but I've not found how to auto-populate the views menu without selecting any display first. I'm still investigating how to build a startup script to do that.

Hope it helps,
-Juanjo
User avatar
juanjgon
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Re: OCIO Issues

Postby HandcraftedMedia » Thu Sep 15, 2022 3:52 pm

HandcraftedMedia Thu Sep 15, 2022 3:52 pm
Yeah that fixed it.
Could a simple python onCreated script fix the issue maybe?
With this it's working:
Code: Select all
node = kwargs
thisnode = node['node']
thisnode.parm("A_OCIO_DISPLAY_NAME").set("ACES")


Is there any scenario where the display name should not be ACES or at least by default?
HandcraftedMedia
Licensed Customer
Licensed Customer
 
Posts: 67
Joined: Thu Jan 10, 2019 12:15 am

Re: OCIO Issues

Postby juanjgon » Thu Sep 15, 2022 5:28 pm

juanjgon Thu Sep 15, 2022 5:28 pm
Yeah, this is why had not added this script as default, but you can be right, probably ACES by default can be a good option in any case. Let's try that for the next build ;)

Thanks,
-Juanjo
User avatar
juanjgon
Octane Plugin Developer
Octane Plugin Developer
 
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Re: OCIO Issues

Postby HandcraftedMedia » Thu Sep 15, 2022 11:49 pm

HandcraftedMedia Thu Sep 15, 2022 11:49 pm
Sweet.
I noticed for it to work it also needs to include the view name as well so:
Code: Select all
node = kwargs
thisnode = node['node']
thisnode.parm("A_OCIO_DISPLAY_NAME").set("ACES")
thisnode.parm("A_OCIO_VIEW_NAME").set("sRGB")
HandcraftedMedia
Licensed Customer
Licensed Customer
 
Posts: 67
Joined: Thu Jan 10, 2019 12:15 am

Return to Bug Reports


Who is online

Users browsing this forum: No registered users and 2 guests

Sat Apr 27, 2024 9:03 pm [ UTC ]