Where is the "Affect alpha" option in the Modo plugin?

[studio3lhd]

The "affect alpha" is pretty important, but it simply doesn't exist in the Modo plugin?!

We've just recently switched from using Octane Standalone to the Modo plugin.
Exporting .orbx to standalone solves the problem, but it doesn't make much sense for it to be missing.

I hope I'm not missing something obvious..

Also, how is the proxy support going? The best thing about not using standalone is not having to manually create and edit placement nodes. No luck with that so far..

Jan

[face_off]

The "affect alpha" is pretty important, but it simply doesn't exist in the Modo plugin?!

It's in the version I am using (2.22.2.68).

Also, how is the proxy support going? The best thing about not using standalone is not having to manually create and edit placement nodes. No luck with that so far..

The render cache API introduced in the latest 801 SR provides proxy support - and it works well. However there are some crash situations, so I am holding off releasing a version of the plugin which uses this new API until TF address those issues. I'm sure you already know, but if you tick Live Geometry Update on mesh, that mesh gets a Placement node (or scatter node if it's also used as an instance source).

Paul

[studio3lhd]

Thanks Paul!

I try to keep us up-to-date on the plugins, and I believe we're currently in the 2.22ish. Is there somewhere I can check the exact build number/version of the plugin? The about section isn't very helpful.
I wasn't aware of the placement node being generated, sorry. I've taken up Modo just days ago, so it's still a struggle with the shader tree etc., not to mention interoperability with Octane.

Since you've mentioned APIs and stuff... What's the take on Modos procedurals? How's that coming along? There's some sweeeeet texturing going on in there (coming from 3ds Max, I was sold at the cellular map, didn't even try the others yet..)

Jan

[face_off]

Hi Jan

I try to keep us up-to-date on the plugins, and I believe we're currently in the 2.22ish. Is there somewhere I can check the exact build number/version of the plugin? The about section isn't very helpful.

I have been posting build notes at the top post at http://render.otoy.com/forum/viewtopic.php?f=34&t=42581 (although it doesn't go back far). My own notes indicate Effect Alpha was added in 2.20.0.49. If you are on a later version and it is not there, delete your Modo801.cfg.

Since you've mentioned APIs and stuff... What's the take on Modos procedurals? How's that coming along? There's some sweeeeet texturing going on in there (coming from 3ds Max, I was sold at the cellular map, didn't even try the others yet..)

I have done a lot of work trying to build in support for procedural textures - but the challenges presented by the Modo API are substantial. Some Modo devs say it's not possible, others say it is, but following their suggestions lead to undocumented territory and some stability issues. So all I can say is "maybe". However I suspect the Octane 3 OSL (Open Shader Language) feature may remove the need for Modo procedural texture support - since you will be able to write your own shaders.

Paul

[studio3lhd]

The plugin was surely later than 2.21, since its been installed for only about two weeks now.
However, I've done exactly as you've instructed and the "affect alpha" is now present in the specular material! Thanks a ton!
My precious beautiful custom layouts are now gone, though... (thankfully they weren't actually "beautiful" or useful so I won't be bothering with that, lol)

Jan

[face_off]

Jan - that is one of the gripes ppl have with Modo - when you delete Modo801.cfg (which is required on a regular basis), you loose you custom layouts etc. However you can store your Octane custom forms, layout, etc in a separate Kit - http://render.otoy.com/manuals/Modo/?page_id=1091 explains how (although you'll need some tech skills to work out how to transfers custom forms/layouts from your Modo801.cfg into the index.cfg of the new Kit).

Paul