OctaneRender 3 for Modo [OBSOLETE]

[funk]

Thank you Paul for this awesome pre-release! Lots of good stuff here

[Hesekiel2517]

Thank you very much!!

Edit: The new arealight-feature is really really usefull! Great work! I'm sure it's on the roadmap but would it be possible to texture the Arealight aswell?

Edit2: I think the new TriplanarProjectionNode doesn't work. There aren't any options available too.

[face_off]

Im looking forward to this test release for OS X paul. when will it be gracing us

3.06 TEST 3 (and the Modo plugin for that release) are starting to look pretty stable - so my preference would be to do a full Windows/OSX/Linux release on the next 3.06 Octane release (assuming it is not tagged as "TEST").

Paul

[Greggers]

Brilliant all cheers, any idea on a time reference?

[face_off]

any idea on a time reference?

I would be guessing - but maybe in the next 1-2 weeks? If nothing has been released within two weeks - msg me and I will do an OSX release.

Paul

[Greggers]

Thank you

[face_off]

Will you be adding these changes over to Photometric and Point?

I'm not sure yet. Area Lights work nicely because the light emitted from the Octane emitter is exactly the same as that from the Modo area light - so there is no need to tweak the Octane Material, means it can do the conversion on-the-fly. I doubt Point Lights will match (since in Octane then need to be converted to an actual geometry emitter). I need to re-visit Photometric lights to see what potential there is for improvements there.

Also - a big thanks to Funk who worked out the on-the-fly conversion formula's for area lights. Without his input, I doubt I could have done it.

Paul

[MildMustard]

Also - a big thanks to Funk who worked out the on-the-fly conversion formula's for area lights. Without his input, I doubt I could have done it.

Thanks Funk, appreciated !!!

I doubt Point Lights will match (since in Octane then need to be converted to an actual geometry emitter). I need to re-visit Photometric lights to see what potential there is for improvements there.

I could probably live without the point light conversion, I think the Photometric one is probably more important of the 2 (in my workflow at least). I hope you can find a way for it! Thanks again for the ongoing improvements and updates Paul, it really makes working with Octane in Modo more and more a pleasure.

[face_off]

Another pre-release - this version fixes a number of issues with the on-the-fly area light conversion introduced in the previous pre-release.

3.6.2.117 PRE-RELEASE
- Compiled with Octane 3.06 TEST 3 (includes Adaptive Sampling, new Bokeh pins, new Pano Camera DOF pins, new Add/Subtract/Comparison/Triplanar texture nodes, and Normal and Displacement mapping enhancements, new Triplanar projection node)
- Resolved issue with some non-Mesh item geometry meshes loading twice
- Modo Render Region channel modifiers are now evaluated when setting the Octane render region
- The following Imager defaults have changed to better match Modo - Response now defaults to Linear, Gamma now defaults to 2.2 and Vignetting now defaults to 0
- VERY IMPORTANT: The plugin will now correctly convert the Modo scene and image ocio colorspace settings to the Octane Image Gamma values. This means if you have saved scenes with the 8 and 16 bit colorspace at a setting other than Linear (as per the manual), then Image gamma values will change when you render with this release of the plugin. At this stage sRGB, sRGBf, rec709, gamma2.2 are converted to a 2.2 gamma, gamma1.8 is converted to a 1.8 gamma and everything else remains linear/no correction (1.0 gamma). The Octane Environment IBL does NOT take into account the Modo ocio settings.
- Changed the default values for the Camera settings Use Modo Film Offset, Use Modo Clipping Distance, Use Modo Focus Distance and Use Modo F-Stop for Aperture to ON
- The default Environment is now the Texture Environment, rather than Daylight Environment, and Use Modo Environment Power and Rotation properties are now defaulted to ON
- Fixed issue where the octane.saveAnimation command was not exporting animated Environment channels
- Modo Area Lights when do NOT have a mesh item (ie. Octane emitter) attached to them will now convert to an Octane emitter automatically. The emitter geometry will automatically be created, and the Octane material will be created from the Modo area light material. You can still use the Create Octane Emitter function to override this default behavior
- Revamped the proxy system so animations inside ABC nodes in an OCS/ORBX will render correctly.
- Fixed error when exiting Viewport Navigation mode and transferring the Octane camera back to the Modo camera

LINK REMOVED - New test release available below.

Paul

[Greggers]

Paul,

It would be great if you could include the correct mapped keys in the latest build of octane. We discussed this earlier in this post regarding the zoom keys on a mac in the octane viewport. Just thought I would throw it in there. Looking forward to testing the new test build when you release it for us