OctaneRender 3 for Modo [OBSOLETE]

[MrFurious]

Also I like the way it works how the Octane Camera panel automatically pops up when a camera is clicked, and disappears when something other than a camera is clicked. This works the same (almost) for the Octane Environment tab when the modo 'environment' is selected, but in the case of the octane environment tab it does not completely vanished when un-selecting the modo environment, rather it kindof minimises and looks like this:

How are you unselected the Octane Environment? If you press <esc> (to unselect all) the Octane Environment should disappear

Thanks Paul, I'm un-selecting the Octane environment by selecting something else and also tried pressing escape once or twice. The Octane Environment panel still minimizes rather than vanishing as in my previous screenshot.

[face_off]

The Octane Environment panel still minimizes rather than vanishing as in my previous screenshot.

I cannot reproduce this issue Dino. May I suggest deleting your Modo cfg file - perhaps it contains something which is causing the problem.

Paul

[MrFurious]

The Octane Environment panel still minimizes rather than vanishing as in my previous screenshot.

I cannot reproduce this issue Dino. May I suggest deleting your Modo cfg file - perhaps it contains something which is causing the problem.

Paul

Thanks Paul I'll give it a try. did you see my other feedback on the clay mode buttons in the toolbar?

cheers,
Dino.

[funk]

I'm seeing the same thing with the environment panel here too, so its not bad configs

[face_off]

G'day Paul just a quick one... wonder if it's not too difficult to add an icon button or button(s) to the octane toolbar which will switch to clay/colour clay mode? Would be handy to have one click access to this rather than having to open the kernel-->settings first.

Hi Dino - I have enough high priority issues to manage at the moment (render cache issues, mesh lights, etc) that I would prefer to not divert time to more cosmetic issues such as this at the moment. And it's something you can implement yourself by tweaking the XML code.

Paul

[smicha]

Paul,

Not rushing you at all but I am still having issues on .ocs proxies even with the render target node is pinned in the .ocs file - I get still same error in the log that octane for modo cannot detect output... and there is a blank viewport. Any progress in solving this issue?

[face_off]

I'm seeing the same thing with the environment panel here too, so its not bad configs

Yes, I can reproduce it too. I cannot see any issue within the plugin which would cause this behavior, so it is potentially a Modo UI issue.

Not rushing you at all but I am still having issues on .ocs proxies even with the render target node is pinned in the .ocs file - I get still same error in the log that octane for modo cannot detect output... and there is a blank viewport. Any progress in solving this issue?

Below is a link to a pre-release of the next version of the plugin.

3.4.4.114
- Compiled with Octane 3.04.4
- Fixed issue where setting the Border Mode with Black Color or Clamp Value was not working after a scene refresh
- octane.SaveAnimation now uses a new Octane API library to export the scene, which should work quicker, and also support strand hair and volumes
- Added Direct Lighting Kernel AO Texture as per Octane 3.04. Drag the property name onto the schematic and attach an RGB Color node to use this
- Added Render Layer Mode combobox to the Render Layer tab as per Octane 3.04
- Added additional Falloff Texture node pins as per Octane 3.04
- Enabling/Disabling render passes now no longer restart the render when viewing the beauty pass
- Resolved issue where vertex motion blur was not working when using the octane.saveAnimation command
- Fixed issue where the User For Tonemap setting was not being set in certain situations
- Removed Render Cache UPDATES. Due to breaking changes in the Modo10.2v1 render cache, mesh update events from the render cache are now ignored. If the Render Cache is enabled, Meshes with Live Geometry Update enabled are still "live", but morphs/vetice changes are not detected (which is the same as when Use Modo Render Cache is OFF)
- Increased the size of the Cuba Devices panel
- Added support for Modo 10.2v1 Mesh Lights. These are automatically converted to Octane emitter meshes. The Mesh Light "Radiance" and "Light Color" are the only properties taken into account when building the Octane diffuse emitter material for the emitter mesh
- Meshops changes now update Mesh Items which have Live Geometry Update enabled
- Fixed error when using a Geometry Out node in a proxy ORBX or OCS file
- Changed the beauty pass layer name to "RGBA" when saving multi-layer EXR's

https://render.otoy.com/customerdownloa ... _64bit.exe

Paul

[MrFurious]

G'day Paul just a quick one... wonder if it's not too difficult to add an icon button or button(s) to the octane toolbar which will switch to clay/colour clay mode? Would be handy to have one click access to this rather than having to open the kernel-->settings first.

Hi Dino - I have enough high priority issues to manage at the moment (render cache issues, mesh lights, etc) that I would prefer to not divert time to more cosmetic issues such as this at the moment. And it's something you can implement yourself by tweaking the XML code.

Paul

Ok no problem. I don't know the first thing about XML Code but maybe this can be done with the Form Editor in Modo?..

[smicha]

Paul,

OCS is fixed, thank you! But there is one detail I am not sure it shall work like it is now: namely, when I have a simple cube to which a very complex ocs is connected as a proxy and I want to replicate it (the proxy) by replicating the cube as a modo instance - proxy is gone and I can only see cubes in octane viewport. To get a copy of proxy I cannot use an instance of a cube but a regular copy of a cube. Is it clear what I am saying?

[smicha]

Paul,

I hope the screenshot will make it clear.