OK, thank you. I've added this into our tracking system. It is not currently planned.

Cheers,
Toby.

Hi. Can you elaborate on what you mean by viewing a texture map in the viewport? How would it be different to what you can see in the Octane IPR?

Hey, sorry I didn't get back to you. Some higher priority stuff has come up so this will remain in the queue for a while longer. Rest assured that it is in our internal issue tracker and won't be forgotten

Oh, I didn't notice that Beppe was helping you in a different topic. Please continue in the other topic rather than splitting the conversation.

Cheers,
Toby.

Hi, looks like your screenshot didn't attach properly.

The path to put in houdini.env is the name of the directory that was extracted from the downloaded zip file - it should be the directory containing the MainMenuCommon.xml file.

Thanks, that is useful information. The only difference between plugin builds 211 and 212 is the Octane core version change from 2022.1 to 2022.1.1, so it's most likely something changed there.

I will look into it.

Hi, thank you for reporting!

This is a new one to me, so it will take a little bit of time to investigate.

Which version or versions are working correctly on the Win10 machine?

Cheers,
Toby.

Thanks for the report! Issues with changing the layer count and loading messing up the connections are known and will be fixed.

In terms of the order the order of layers, doesn't it make sense for layers that are composed on top of other layers to appear on top in the UI? I agree that it can be ...

lavrenovlad wrote:Thanks for the release! Full-Reload Multi-Threaded scene extraction crashes aren't a pain anymore hopefully

Fingers crossed!

Hi, thanks for the scene. Just so I'm clear on what's missing - the problem is that you can't create the "Mesh Volume SDF" node (or the "Placement" node for that matter) in the material network?