OctaneRender 2021 for Modo [OBSOLETE]

[jwfvr]

hi - if I were to open a scene (previously set up in modo 14.2 with octane 169) in modo 15 with octane 172, then opened the same scene again in modo 14.2, could that potentially cause render settings to get scrambled? I ask because I can't find any other cause - I have a file with about 20 render passes, all unique lighting/material tweaks and its now, inside the render passes, the geo is unchanged, but the light settings are randomly different in every pass. I have everything corrected now, I just wanted to confirm whether my suspicions are true.

[funk]

jwfvr absolutely. Files will not be backward compatible. The render pass system has had some major changes in the 2021 core.

Always keep a back up of the original 2020.x files created in previous versions of the plugin, and save to a NEW file when working with newer builds.

Since 2021 standalone is still an experimental build, more changes are expected before the final release. Files created with this test build may not work with future 2021.1 XB builds either.

[jwfvr]

ok got it - thank you!

[jwfvr]

follow up question! - are the plugins for modo 14 and 15 completely separate from each other? meaning does the act of installing the newer plugin for 15 have any effect on 14? I assume I can have both installed at the same time, or maybe that's a bad idea?

[funk]

The 14 and 15 plugins do not affect eachother. Just make sure you arent installing both to the same directory by accident.

EDIT: Also make sure you are using the latest build for each version (so the latest build of the modo 14 2020.x plugin, and the latest build of the modo 15 2021.x plugin)

[jwfvr]

ok thank you!

[face_off]

I have updated the installers at the top of this thread with:

2021.1.0.174
- Compiled with Octane 2021.1 XB3
- Resolved a number of issues with the octane.renderAndSave command introduced in release 2020.2.0.165. VERY IMPORTANT: the octane.renderAndSave command will now save to the format set in the Image Save panel. This means you will have to have opened the Save Image panel on that scene at some point prior to using the octane.renderAndSave command.
- Fixed issue with the Layered Material was causing an Octane Log error
- Added new Octane 2021.1 XB2 texture nodes (see viewtopic.php?f=33&t=77996 for details)
- Added new Value->Float Color Value node to the schematic, for pluggin into Octane Float pins that are a color (the Compositor->Light Mixer AOV Output->Tint pins for example)
- Added support for vertex maps for curves. One RGB/RGBA and one Weight Map is supported per curve Mesh item

Thanks

Paul

[funk]

Thanks Paul

[yoshikai]

Hi Paul
Thanks so much for the update!
I'm so, so happy about the curve weighting update!
Thanks.
BTW, I'd like to report something I noticed in my experiments.
I set weights for the polygon object and the curve object with set weight MOP. This works perfectly for both objects. Thanks!
Next I used Remap to animate the Wightmap. The name of the weights is changed from the name of the weights set in Set Wight MOP to another name.
And when animated, the polygon mesh works perfectly with the changed weight name.
The curve object does not animate with the changed weight name, but it does animate with the name set in set weight MOP.
It seems that the changed weight name is not being recognized. (But it still animates with the name set in Set Weight MOP.
I have reported this just in case.

[face_off]

BTW, I'd like to report something I noticed in my experiments.
I set weights for the polygon object and the curve object with set weight MOP. This works perfectly for both objects. Thanks!
Next I used Remap to animate the Wightmap. The name of the weights is changed from the name of the weights set in Set Wight MOP to another name.
And when animated, the polygon mesh works perfectly with the changed weight name.
The curve object does not animate with the changed weight name, but it does animate with the name set in set weight MOP.
It seems that the changed weight name is not being recognized. (But it still animates with the name set in Set Weight MOP.
I have reported this just in case.

The curve weight only supports one weight map name (potentially the last in the list). So you will see some odd behavior like this with you have multiple maps for a curve.

Paul