OctaneRender for Modo (Windows) 1.52 [STABLE]

[Talleman]

I notice this when the render has reached the max sample limit, the controls look like it's paused, but when you make a change to a scene, it restarts. Maybe that's what he was referring too?

That is correct... and the fact that it was finished made it a little worse



Regarding the Bump intensity... I use a combination of 2 values, Bump amplitude and opacity on the material slot.

So I was thinking that Octane bump power = bump amplitude x (opacity/100)

[cakeller98]

I notice this when the render has reached the max sample limit, the controls look like it's paused, but when you make a change to a scene, it restarts. Maybe that's what he was referring too?

That is correct... and the fact that it was finished made it a little worse

Set up the periodic save in prefs and at least then (I think) you can at least retrieve the latest auto-save.

[sjogren]

Hi, I may have found a bug...
Export Selected Layers to .obj crashes Modo, I noticed this behavior with:
701_1_52_0_58_beta_64bit, I uninstalled the plugin and everything Worked fine, no crash!
Installed 701_1_52_0_57_beta_64bit and got the same crash again!
just me and my computer or can anyone confirm?
Is there anything else I can check, obtain to help?

/Niklas

[face_off]

Export Selected Layers to .obj crashes Modo, I noticed this behavior with:
701_1_52_0_58_beta_64bit, I uninstalled the plugin and everything Worked fine, no crash!
Installed 701_1_52_0_57_beta_64bit and got the same crash again!
just me and my computer or can anyone confirm?
Is there anything else I can check, obtain to help?

I wasn't able to reproduce this issue. Are you able to send me a very simple scene with exact instructions as to how to reproduce the problem pls?

Paul

[lightboy]

Hi Paul
This is how modo imports an objects materials.
It puts it in an item mask and adds another base shader into the item mask then it places it above the default base shader.
When you render in Modo everything is fine. When you transfer it over to Octane and create emitter overrides for the area lights you won't see any light in the scene.
To get the Octane lights to light the scene you have to move the imported item down the shader tree under the Octane created area light emitters, then the lights will work.
I don't know if there is an automated away around this?

Here's a couple of pics to show what I mean.

Modo default import

Octane lights friendly

[lightboy]

I should of done some more checking.
You have to move the the imported item with the material mask to the bottom of the shader tree so as to not affect any other materials in Octane.

Octane_below other materials

[sjogren]

Export Selected Layers to .obj crashes Modo, I noticed this behavior with:
701_1_52_0_58_beta_64bit, I uninstalled the plugin and everything Worked fine, no crash!
Installed 701_1_52_0_57_beta_64bit and got the same crash again!
just me and my computer or can anyone confirm?
Is there anything else I can check, obtain to help?

I wasn't able to reproduce this issue. Are you able to send me a very simple scene with exact instructions as to how to reproduce the problem pls?

Paul

Strange, I get this behavior every time if I have Octane for Modo installed!
If I make 2 cubes and try to export one as .obj with "Export Selected Layers" Modo crash!
If I copy one cube to a new scene and export that scene as .obj with "File - Export as..." everything works!
2 Cubes scene(.LXO)
Video(youtube) about this problem
/Niklas

[face_off]

Strange, I get this behavior every time if I have Octane for Modo installed!
If I make 2 cubes and try to export one as .obj with "Export Selected Layers" Modo crash!
If I copy one cube to a new scene and export that scene as .obj with "File - Export as..." everything works!
2 Cubes scene(.LXO)
Video(youtube) about this problem

Thank you - I can now reproduce this issue. The crash is happening inside the Modo python interpreter (and the Octane plugin does not have any python code), so this might take so time to resolve.

This is how modo imports an objects materials.
It puts it in an item mask and adds another base shader into the item mask then it places it above the default base shader.
When you render in Modo everything is fine. When you transfer it over to Octane and create emitter overrides for the area lights you won't see any light in the scene.
To get the Octane lights to light the scene you have to move the imported item down the shader tree under the Octane created area light emitters, then the lights will work.
I don't know if there is an automated away around this?

This looks like a bug in the plugin. Would it be possible to send me the object you are importing pls? That way I can reproduce the exact situation you have to more rapidly fix the problem.

Paul

[face_off]

Strange, I get this behavior every time if I have Octane for Modo installed!
If I make 2 cubes and try to export one as .obj with "Export Selected Layers" Modo crash!
If I copy one cube to a new scene and export that scene as .obj with "File - Export as..." everything works!
2 Cubes scene(.LXO)
Video(youtube) about this problem
/Niklas

Modo is crashing for me even with the plugin disabled. I am on SP5, deleted my Config.CFG, and it still crashes - so it look like a Modo bug to me. Is anyone else able to reproduce this crash pls?

Paul

[face_off]

This is how modo imports an objects materials.
It puts it in an item mask and adds another base shader into the item mask then it places it above the default base shader.
When you render in Modo everything is fine. When you transfer it over to Octane and create emitter overrides for the area lights you won't see any light in the scene.
To get the Octane lights to light the scene you have to move the imported item down the shader tree under the Octane created area light emitters, then the lights will work.
I don't know if there is an automated away around this?

I have investigated this further, and cannot reproduce the issue. Can you pls send me a scene which demonstrates this problem.

Thanks