tobywe wrote:It's great to see that ACES workflow has been introduced. I'm still a bit hazy on how to set it up. Am I right in thinking that to set it up correctly, it would be a matter of :
1. Bringing in the textures in pre-converted to AcesCG, ideally.
2. Setting the response curve to 'linear/off' in the imager tab.
3. Configuring the OCIO path variable in the Houdini env.
3. Setting the IPR to render in Mplay (as the Custom OpenGL doesn't seem to have an Aces Cofiguration).
4. Setting the rop to render to ACES exr.
In my test, I'm finding that a texture that's converted to AcesCG is still lookng too dark. I'm sure I've got one (or more) steps wrong in this process, but was hoping you might be able to give some direction on this.
As far as I know ACES is only available while exporting EXR files using the new file format option. The IPR data is always exported as it is available from the imager node, so unless the ACES correction is also available in this node, I suppose that you should try to configure the ACES options in MPlay, if possible.
Sorry, I'm not even sure how this works in the Standalone, but you could try to ask this question in the general forum or in the Standalone 2020.1 XB1 topic to see if someone else can help you.
Thanks,
-Juanjo