OctaneRender for Modo (Windows) 1.55 [OBSOLETE]

[heavypoly]

Hi Paul,

I checked,and redownloaded the live DB Contenet, and yes it does overlap items.

About the 1.53.1 there is a bug with modo 701. Directional light set as sun parameters has no effect over the direction of the octane sun.

Same thing happening here with 701 SP4. Any workarounds?

[face_off]

I checked,and redownloaded the live DB Contenet, and yes it does overlap items.

Can you post a screenshot of a material in the schematic pls, so I can compare against my version here? Let me know which LiveDb material you post.

About the 1.53.1 there is a bug with modo 701. Directional light set as sun parameters has no effect over the direction of the octane sun.

Fixed in the next release.

Paul

[v1adut]

I checked,and redownloaded the live DB Contenet, and yes it does overlap items.

Can you post a screenshot of a material in the schematic pls, so I can compare against my version here? Let me know which LiveDb material you post.

About the 1.53.1 there is a bug with modo 701. Directional light set as sun parameters has no effect over the direction of the octane sun.

Fixed in the next release.

Paul

Hi Paul,

The first 2 images, contain 2 random materials I choosed, the third image is my wish of the layout

[face_off]

The first 2 images, contain 2 random materials I choosed, the third image is my wish of the layout

I see the issue. The LiveDb materials are automatically formatted by the plugin - and the formatting you are seeing it the default automatic formatting. I have tried to use a few of the node layout "clean-up" functions in Modo, but they do not seem to work. So for the time being - that is the format you will get. Over time I will improve this layout, however unless the Modo Schematic functionality is enhanced, it's not possible to determine that one node is overlayed on another.

Paul

[v1adut]

Hi Paul,
I understand that there is some modo api limitation, but if we found a way to set a miminum distance between the nodes, and a rule to control the position by checking the parent position and set a vertical rule alignment... By the way I am far away from a developer, but this is my designer approach.

I also saw you somehow fixed the horizontal positioning.

Thank you fot the reply

[face_off]

I understand that there is some modo api limitation, but if we found a way to set a miminum distance between the nodes, and a rule to control the position by checking the parent position and set a vertical rule alignment... By the way I am far away from a developer, but this is my designer approach.

I also saw you somehow fixed the horizontal positioning.

Yes, with a lot of effort this could be improved, but ultimately it's a function that Modo needs to provide - anything I do in the plugin is a workaround, and whilst I will probably look at it in the future, it's hard to justify the time on this when cool new features like Viewport Navigation are awaiting...

Paul

[v1adut]

I understand that there is some modo api limitation, but if we found a way to set a miminum distance between the nodes, and a rule to control the position by checking the parent position and set a vertical rule alignment... By the way I am far away from a developer, but this is my designer approach.

I also saw you somehow fixed the horizontal positioning.

Yes, with a lot of effort this could be improved, but ultimately it's a function that Modo needs to provide - anything I do in the plugin is a workaround, and whilst I will probably look at it in the future, it's hard to justify the time on this when cool new features like Viewport Navigation are awaiting...

Paul

Thank you for considering it Paul.
I just want to share the frustration.

[face_off]

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

1.53.1.66
- Octane channels on the mesh for General Visibility, Camera Visibility and Shadow Visibility are now animate-able (if Load Animation Into Octane is UNTICKED)
- Fixed "Perspective Correction" label (which was showing as "Distortion")
- If Perspective Correction is on, the Octane Camera up vector will NOT track the Modo up vector and will instead be locked at a vector of 0, 1, 0
- If a mesh is "Live", enabling/disabling visibility will update the Viewport accordingly
- Added Viewport Navigation (Alt-LMB = rotate, Ctl-Alt LMB = zoom, Alt-Shift LMB = pan) - needs some fine-tuning
- Fixed problem where the materials in the Shader Tree which had an item tag which was the Group Locator rather than a Mesh Item were not being picked up correctly
- Fixed issue causing the Octane daylight to not track the Modo directional light

The second last and third last items required a significant amount of effort - so pls report any issue you encounter.

Paul

[funk]

Hey Paul, the icon is missing for the new navigation button. The config points to resrc/viewportnavigation_button.png, but the file doesnt exist

[funk]

Paul I'm noticing some problems with the viewport navigation:

1. It just acts too differently from modo's navigation
2. If you zoom out, the center of rotation changes and makes it very hard to keep your object centered.
3. When you pan left and right, it pans according to the viewport rotation (eg. If your cam is banked 45 degrees, your pan left pans diagonally)
4. If you navigate in the viewport, but dont like the new view, you have to close the viewport to cancel (otherwise modo's viewport will update).