OctaneRender for Modo (OS X) 2.24.2 [STABLE]

[rrbarb]

Yes, I am getting this. However, I have two machines that have same loads of os and software- one of them 801 crashes on close, the other does not.
I have removed all configs, scripts, kits, ect. and still get the crash. On the other, no crash.
When time permits I am going to wipe and reload.

At this point I cannot say just exactly what the cause may be. I don't think it is Octane

./rrb

[rojharris]

Hi Paul,

I'm using the latest build downloaded yesterday from this thread. Latest modo too.

Thanks
Roger

rrb, when I move Octane from the kit folder the crash goes away.

[face_off]

Yes, I am getting this. However, I have two machines that have same loads of os and software- one of them 801 crashes on close, the other does not.
I have removed all configs, scripts, kits, ect. and still get the crash. On the other, no crash.
When time permits I am going to wipe and reload.

I suggest if the crash is causing an issue - roll back to the previous version. In the meantime I will investigate some more. I am without an OSX system for the next week or so, so unfortunately it will take a couple of weeks to get to the bottom of this.

Paul

[face_off]

Yes, I am getting this. However, I have two machines that have same loads of os and software- one of them 801 crashes on close, the other does not.
I have removed all configs, scripts, kits, ect. and still get the crash. On the other, no crash.
When time permits I am going to wipe and reload.

I have looked into this - but been unable to reproduce the problem. If you have any more info, pls send it through and I can investigate further.

Paul

[face_off]

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

2.3.0.22
- Compiled against Octane 2.03, which resolves a number of displacement mapping issues
- When Modo reloads a texturemap (if it has been edited outside Modo and saved), the plugin will also reload the texturemap if the Viewport is open
- Added "Reload Texturemaps" button to the OctaneRender Setup panel toolbar
- Improved Viewport Navigation rotation (removed gimbal lock issue)
- The calculated Field of View, and the Modo Focus Distance are now feed into the camera animation track when "Load All Frames Into Octane" is enabled.
- Bezier curves (ie. imported from Illustrator) are now supported

2.2.0.21
- Fixed issue where the Viewport Refresh command was sometimes locking Octane
- Fixed issue where checking material checkbox properties would not refresh the material in the Viewport if the material was in the Shader Tree Library
- Added support for Image Sequences. End Behavior "Mirror" is not supported (and is treated as "Hold"). There is very little support provided in the Modo API for image sequences, so you may find some issues!
- Fixed issue where changing a material's Texture Layer Polygon Tag Type or Polygon Tag was not refreshing all materials. In some case, you will need to refresh the scene (if the Octane material names associated with polygons has changed)
- Changing a material's Texture Layer Item tag now issues a "You will need to refresh the scene for this to take effect" message
- Octane Specular and Glossy Material "roughness" is now the Modo Material roughness * 0.6

Paul

[face_off]

Just a quick note to say that I have had a minor issue with the 2.06 API for OSX, so holding off on releasing an update until I am comfortable all is ok.

Paul

[riggles]

I was wondering about the OSX status. Ok, thanks for the update~

[riggles]

I upgraded to MODO 801 and I'm getting some errors. When I quit MODO, I get an error that MODO quit unexpectedly. I disabled my other plugins, but it doesn't stop until I disable the Octane plugin.

Also, a scene that I setup in Windows using the 2.06 plugin doesn't render correctly in OSX using the 2.03 plugin. No shadows from mesh emitters and the materials are weird, too. Diffuse still has reflections and specular isn't transparent. Weird.

[face_off]

I upgraded to MODO 801 and I'm getting some errors. When I quit MODO, I get an error that MODO quit unexpectedly. I disabled my other plugins, but it doesn't stop until I disable the Octane plugin.

Does the quit happen if you run Modo then exit? Or do you need to open the viewport first?

Also, a scene that I setup in Windows using the 2.06 plugin doesn't render correctly in OSX using the 2.03 plugin. No shadows from mesh emitters and the materials are weird, too. Diffuse still has reflections and specular isn't transparent. Weird.

I wonder if the OXS installer is not replacing certain files due to them having an earlier timestamp? Try removing all the 2.06 files, then installing 2.03.

Paul

[riggles]

I upgraded to MODO 801 and I'm getting some errors. When I quit MODO, I get an error that MODO quit unexpectedly. I disabled my other plugins, but it doesn't stop until I disable the Octane plugin.

Does the quit happen if you run Modo then exit? Or do you need to open the viewport first?

I just open MODO then immediately Cmd+Q to quit. MODO closes and then I get the error message.

Also, a scene that I setup in Windows using the 2.06 plugin doesn't render correctly in OSX using the 2.03 plugin. No shadows from mesh emitters and the materials are weird, too. Diffuse still has reflections and specular isn't transparent. Weird.

I wonder if the OXS installer is not replacing certain files due to them having an earlier timestamp? Try removing all the 2.06 files, then installing 2.03.

I have Windows installed on a separate partition, so the older OSX plugin doesn't see any newer plugin files. I created the file in Windows, copied it to Dropbox, restarted in OSX, downloaded the file, and hit render.