OTOY Forums

Hey Paul,

sorry about the long wait to my reply.
I often duplicate an override and assign it to another material that is similar and tweak it from there...when moving the override into the new material group it received that materials groups name by default.

Gutmann wrote:Hey Paul,

sorry about the long wait to my reply.
I often duplicate an override and assign it to another material that is similar and tweak it from there...when moving the override into the new material group it received that materials groups name by default.

I think the functionality you are asking for is in the latest version of the plugin at the top of this thread.

Thanks

Paul

- Moving Octane Overrides between Material Masks no longer causes them to be renamed

To be clear - this happens whenever Octane Overrides are moved between Material Masks. This behavior cannot be changed via the Preferences.

Thanks

Paul

Hello,
I'm having issues with references and shader overrides (tested in both 184 and 186 builds). I'd like to try to understand more about the issue, but the fact is I can't open overrides in the schematic, they simply aren't listed between workspaces.
Attached is a very simple scene that shows the issue: cube is in the scene as a classic mesh, spheres are referenced. If you open Octane, you can see that spheres color doesn't match OGL (that's because of the overrides), so they work but aren't listed in schematic (only one is).
In a more complex scene where I discovered the issue, I have several problems with shading too, but I'd like to start with the schematic bug so I can investigate more.

Thanks.

G

Hi

I don't think the plugin is going to handle the situation with Reference Octane Overrides well. From your scene, I found 2 workarounds:

1) Edit the Octane Override in the Reference file (ie. Sphere1.lxo). I understand this is going to be an ugly solution. Or,

2) Create a new Octane Override in the Sphere1 item mask - then it will shade the Sphere1 mesh. It means the Octane Overrides in the reference .lxo's will be ignored.

Sorry I don't have a better solution.

Paul

Thanks Paul for trying.
The first solution would be fine, but I have shading issues as well of referenced files with more complicated setups than the one I attached and I can't investigate the source of issues because I can't see their workspaces.
The only solution now is to get rid of references in the project.

G

Hello,
.VDB's disappear when placed onto a placement node or group node through Octane Standalone when imported into MODO as a proxy.
Connecting a single .VDB directly onto the Render Target appears though.
Windows 10. Octane 2021.1.5.186 & 2021.1.3.184.

Any thoughts appreciated.

leblanc980 wrote:Hello,
.VDB's disappear when placed onto a placement node or group node through Octane Standalone when imported into MODO as a proxy.
Connecting a single .VDB directly onto the Render Target appears though.
Windows 10. Octane 2021.1.5.186 & 2021.1.3.184.

Any thoughts appreciated.

Yes, this is a known issue with Octane which I have discussed with OTOY. I suggest you raise it with them too, so they are aware of the problems this is causing. It means you cannot put a Placement node in the ORBX that you are loading as a Mesh Proxy. Instead, connect the Mesh or VDB to a Geometry Out node in the ORBX file used as the proxy, and this Geometry Out node will be connected to the Placement Node used by the plugin.

I hope that helps.

Thanks

Paul

Hi

I have added a note to the 2021.1.5.186 release as follows:

IMPORTANT: With release 2021.1.5.176, when exporting an animation to ORBX, make sure you UNTICK Kernel->Animation->Camera and Object Motion Blur to ensure object transformations are correctly exported. This issue will be fixed in the next release.

The next release of the plugin will built with Octane 2022.1 (and will be in a new thread in this forum).

Thanks

Paul

I have posted an Octane 2022.1 build of the plugin at https://render.otoy.com/forum/viewtopic.php?f=34&t=80262 (including a macOS build). I am not anticipating any further Octane 2021.1 plugin builds, so that thread is now the active thread for new releases.

Thanks

Paul