Following is a pre-release of the next version of the plugin (for Windows).
3.6.1.120 pre-release
- Compiled with Octane 3.06.1
- Added official support for Modo11 and removed suppoert for Modo801
- Resolved issue where some Octane Proxy OCS/ORBX scene would not load correctly
- Fixed issue where parenting a mesh to an area, point or photometric light would stop the on-the-fly light conversion from working
- EXPERIMENTAL: Added preliminary support for Modo AlembicMesh items - which will be loaded into Octane as an Octane Scene node (meaning vertex motion blur support) is the Preferences->Use Modo Render Cache is disabled. It is assumed there is a single material for an AlembicMesh item
- Deleting an Octane Override not longer opens and immediately closes the Octane Setup window
- Added support for Modo11 and Modo801 no longer supported
- Added Sampling Rate, Light Pass ID and Cast Illumination to the Octane tab of Modo Area, Point and Photometry Lights to set the Octane Sampling Rate of the on-the-fly converted lights
- Resolved issue where rendering VDB files which have velocity data was crashing Modo
- Added W Coordinate node (for rendering strand hair)
- Fixed issue where octane.importLocalDb was not loading materials saved with octane.exportMaterial
- Re-wrote the VDB loader for Modo11 compatibility. In general, you are better off to load a VDB sequence into Octane Standalone and save as an ORBX and use that ORBX file as a proxy in Modo then to render the Modo Volume/VdbVoxel items
https://render.otoy.com/customerdownloads/plugins/fe/8b/1a/02/OctaneRender_for_Modo_3_6_1_120_64bit.exe
I have one more addition to make to the release and then I will do the final release.
Paul