Ocatne with MODO 801

[jbavar]

Is it possible to deactivate octane for 701 and reactivate it in 801 and has there been any testing with 801 yet?

[Battery555]

I would like to know as well

[face_off]

I'm only done very limited testing, but so far, the plugin seems to work with Modo801. The is a warning with pops when opening the Viewport, which I will fix.

If you are running Modo801 on the same PC as your Modo701 installation, you can activate the 801 plugin with the same username/password that you are using with Modo701.

Paul

[face_off]

Edit to the above - looks like the color model in Modo801 has changed - so I will need to make some changes to the plugin to cater for this.

Paul

[face_off]

I have updated the TEST release to now work correctly with Modo801. Pls refer to release 1.52.0.64.

Paul

[padwick269]

I'm only done very limited testing, but so far, the plugin seems to work with Modo801. The is a warning with pops when opening the Viewport, which I will fix.

If you are running Modo801 on the same PC as your Modo701 installation, you can activate the 801 plugin with the same username/password that you are using with Modo701.

Paul

I can confirm 1.52.0.64 work fine in modo 801. Just upgraded and installed.

Thanks Paul for making this plugin happen I know it can't have been easy.

Pat Doyle

[padwick269]

Is it possible to deactivate octane for 701 and reactivate it in 801 and has there been any testing with 801 yet?

I'd take Pauls advice and just use same user name and pass to activate in modo 801. I'd keep 701 until at least 801 SP1, I've learnt that initial realeases of modo always seem to be let's say temperamental unitl then. That's not a slate, I've never complained as I understand when your constantly pushing the envelope its hard to ensure stability.

I'd accept slight instability over stiffled innovation any day of the week myself. The modo team always fix the problems anyway. That's why I love Modo.

Good luck,

Pat Doyle

[riggles]

Has 801 included any API updates that allow for the things we couldn't have in Octane with 701? Like preview window docking, adding control toolbar inside the preview viewport, and access to hair/fur vertex data for use with Octane 2.0 hair/fur?

[face_off]

Has 801 included any API updates that allow for the things we couldn't have in Octane with 701? Like preview window docking, adding control toolbar inside the preview viewport, and access to hair/fur vertex data for use with Octane 2.0 hair/fur?

The Modo801 API includes some new functions to trap the animation slider status, which might lead so new plugin functionality so that it knows when you have released the button on the Modo animation slider and it reloads the vertices data if you are using vertex motion blur in the plugin.

The Fur Material shader vertices are still not exposed by the Modo API, however the new 801 hair tools (which I have not used yet) work on strand hair which the latest version of the plugin does pick up.

UI : My understanding is that docking /might/ now be possible....on the Linux version of Modo. The Modo API for the Linux version allows QT windows to be created which is a huge bonus, but TheFoundry have stated that they are unsure if this feature will be migrated to the Windows and OS X Modo versions yet. If it is - it will be fantastic. Regardless, I will do a Linux version of the plugin in a month or two to at least explore the possibilities.

Also, 801 fixes the Modo scene close create after you've added a workspace, so that alone is a big plus for the plugin.

Paul

[face_off]

I have added some Modo801 specific info to the manual. http://render.otoy.com/manuals/Modo/?page_id=959. Thanks to Funk for the content.

Paul