OctaneRender for Modo (OS X) 1.55 [OBSOLETE]

[riggles]

So - are all OS X plugin users going to update to 2.0? Or are some planning on stay with 1.5?

I've already bought the upgrades as well. I would assume most are going to upgrade to 2.0. The only thing that may keep me on 1.5 for any length of time are any big MODO internal bugs that require 801 to get fixed (such as the closing crash or the export selected layer). I'm on 701 and don't have plans to pay $500 to upgrade to 801 yet, which means I don't get SP updates.

[face_off]

I've already bought the upgrades as well. I would assume most are going to upgrade to 2.0. The only thing that may keep me on 1.5 for any length of time are any big MODO internal bugs that require 801 to get fixed (such as the closing crash or the export selected layer). I'm on 701 and don't have plans to pay $500 to upgrade to 801 yet, which means I don't get SP updates.

The Octane 2 version of the plugin runs on Modo 701, so this shouldn't be a problem.

I have the Octane 2.0 version of the plugin ported to OSX, but it is waiting for an Octane API library before I can release it.

Paul

[riggles]

The Octane 2 version of the plugin runs on Modo 701, so this shouldn't be a problem.

I have the Octane 2.0 version of the plugin ported to OSX, but it is waiting for an Octane API library before I can release it.

Paul

Thanks Paul. How many 701-specific bugs are there? Bugs in MODO that are uncovered by Octane but are only fixed in 801, or are yet to be resolved?

Also, I'm a little worried by the performance hit I'm reading about in the Max thread. Some people are seeing almost 50% longer render times just by using 2.0, even if they aren't using the new features directly. Now that would keep me using 1.5 longer than anything. Eek.

[face_off]

Thanks Paul. How many 701-specific bugs are there? Bugs in MODO that are uncovered by Octane but are only fixed in 801, or are yet to be resolved?

There are some 701 bugs fixed in 801, and some new bugs in 801. See http://render.otoy.com/manuals/Modo/?page_id=959 for details.

Also, I'm a little worried by the performance hit I'm reading about in the Max thread. Some people are seeing almost 50% longer render times just by using 2.0, even if they aren't using the new features directly. Now that would keep me using 1.5 longer than anything. Eek.

As I said elsewhere, I would be staggered if you notice a performance hit. For every 1 person saying 2.0 is slower, there are 5 saying it's faster. Render Region will make up for any performance hit if there is actual one.

Paul

[face_off]

I have refreshed the installer at the top of this thread with:

1.55.0.72
- Added NoLiveGeometryUpdate button to the Viewport toolbar
- If enabling Viewport Navigation with Load All Frames Into Octane enabled, a Y/N dialog is presented to allow the auto-disabling of that property
- Additional fix to the issue where adding Octane Overrides to Shader Tree Library materials was not working correctly
- Added checkbox to set the Octane Len Shift to the Modo Film Offset
- Meshes with Bounding Box ticked can now be rendered if you tick Load Cage
- Fixed issue where a node linked to two pins would only update the first pin when the node value was changed
- Fixed issue where adding Octane Overrides to Shader Tree Library materials was not working correctly

Paul

[rojharris]

Just like to say that I'm using 801 with the plugin and so far everything is working really well. I don't even have a super duper video card, just the 680MX 2048 MB that came with the imac, but its lightning fast for me, much better than the 580 I had on my crusty old PC

Cheers
Roger

[face_off]

Pls see http://render.otoy.com/forum/viewtopic. ... 28#p189528 for an initial OSX build of version 2.0 of the plugin.

Paul

[riggles]

So is 1.55.0.72 the last 1.5 plugin build? If so, I'm keeping a copy in a safe place, just in case

[face_off]

So is 1.55.0.72 the last 1.5 plugin build?

That would be my preference, but if people really need an updated 1.5 build, it's only 30 mins to roll the version 2.0 code out, do the 1.5 build, then roll 2.0 back in. My reluctance for doing this is that whilst on Windows this is automatic, on OSX it has to be done manually, so there is the possibility of human error.

Paul