OctaneRender 2020.1 for Houdini Beta build 2020.1.0.0 XB1

[juanjgon]

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

[snakeboxmedia]

Perhaps your best chance to check if the RTX feature is working fine in the Houdini plugin is to export the scene to the 2020.1 Standalone and check there is the RTX is improving the rendering performance. Remember that you can export the current scene to the Standalone directly from the OpenGL IPR window right-click menu, but only if you have a full Houdini license because Indie can't export Octane scenes.

To be honest, here I've only seen minor differences, but probably because I only have very simple unit test scenes. Of course, something can be broken on the plugin side, so checking the RTX feature using production scenes exported to the Standalone could be great!

Thanks,
-Juanjo

Unfortunately I do have an indie license and so far I have not been able to force octane to give me any difference... down to the second when switching Rtx on or off, not it could be the scenes im testing but if it really is... it's really strange and somewhat disappointing if it's that sensitive, and yes I know how it doesn't work on everything and so on, these are fairly large project scenes with everything in there.

If anyone else here on the forum has an FX license could you please try and export a scene to the stand alone and check RTX is actually working? thanks

[tobywe]

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

Thanks Juanjo! I'll ask in the general forum as you suggest.

[motionskill]

I guess, this version has no Solaris support? Because I can't see Octane in list of Renders in Solaris

[juanjgon]

I guess, this version has no Solaris support? Because I can't see Octane in list of Renders in Solaris

Hi,

Nope, the Octane Hydra delegate plugin is another project not related to this main Octane for Houdini plugin that probably will be released in its own forum when available.

Thanks,
-Juanjo

[blobbybarack]

his feature is not available in the current XB1 core yet, but supporting point attributes in the curve primitives is a planned feature for this 2020.1 Octane release.

warm my heart

[seriawp]

Where i can find Octane Variables List?
$OCTANE_PASS...

[caseyhupke]

Will the XB2 plugin have point attributes for curves and maxon noises?

[juanjgon]

Where i can find Octane Variables List?
$OCTANE_PASS...

Currently, there are two variables that can be used to format the output file name/path: $OCTANE_PASS and $OCTANE_LAYER
https://docs.otoy.com/HoudiniH/HoudiniP ... gsOutp.htm

Thanks,
-Juanjo

[juanjgon]

Will the XB2 plugin have point attributes for curves and maxon noises?

Nope, not yet. The point attributes for curves is not available in the XB2 core yet, and the maxon noises can't be used outside the C4D currently.

Thanks,
-Juanjo