Hi there!

I'm struggling with backward compatibility when opening older Octane files.
As a solution, could we have the option to 'pin' specific Octane versions to different Rhino installations?
For instance, using an older build for Rhino 7 and the latest one for Rhino 8.

Adding a simple ...

OTOY team,
Please add to Octane 2027:

One-click AI face fix for all people (same as V-Ray 7 Neural Face Restoration).
Let me load my own face photos and turn on replacement: Octane detects heads and swaps in my photos, keeping angle, lighting and shadows.

Everything must run fully locally on the ...

Thank you so much for the effort Paul.

I will test it as soon a s possible.

Wow - that was fast , thank you so much for looking into this!


Is there any chance to make the process of editing the config.xml a bit more user friendly?

Since you can have user defined standard search paths somewhere in the Rhino settings (I am travelling right now so I cannot lookup the exact ...

Hallo Paul

Yesterday, I tried to open a library item however the assigned texture was not showing up.

It is possible that the location of the missing texture was moved so that the original path is no longer valid.
However, when looking at the obtained material in the rhino material editor, the ...

Are you able to try this version please a tell me if it fixes your issue?

will do.

I suppose you want me to choose octane as the "current render engine" then, correct?

Hi Paul, thanks for looking into this,

as for your questions:

1. I am using normally using Rhino 8 , this is where the crashed occurred. this actually brings me to an idea: is it maybe possible to have different octane versions installed for R8 and R7 (or maybe even R9 WIP)?
While this would of ...

here is the file

Hello Paul,

Unfortunately, I’ve been experiencing frequent crashes with the latest version of the Rhino plugin.
Since I hadn’t used Octane for at least eight months prior, I can’t say with certainty whether this instability began with the latest version or if it was already present before.

I haven ...

just for clarification:

Default appearance: 5 dots instead of 10
Appearance after manual user intervention (scale 0.5, translation 0.5)

-> Correct representation