OTOY Forums

Very sorry for the long delay with this. Quick rundown,

*RenderOctane will now ask you where you want to save the obj
*RenderOctaneQuiet will behave like the old version where it just creates OctaneExport.obj on its own
*OctaneOptions now includes a RenderOnStart option which will let you choose if you want to link the mesh node for immediate rendering when Octane opens, or for Octane to just load the mesh node but not start rendering. There were some users with smaller amounts of RAM on their cards for whom Octane would bomb out if Rhino and Octane where trying use the video RAM at the same time. This should help those affected to work around the issue.

There are a few other behind the scenes changes which should hopefully make it a bit more bullet proof, and it should now recognize and export the new Lightweight Extrusion Objects. Let me know if you have issues,
Sam

-----OK------
The following seems to be behaving better over here: Let me know if you have problems,
Sam

You are a wonderful soul Sam!

Any Idea what this could mean (when I try to load the Plug-in in v4)?

I don't see it in the plugin list, so I'm somewhat sure it's not conflicting with a prior install. No?

I just found a annoying little bug in this version, so I will recompile it in a second. Perhaps that will take care of things. I will also ask the Seattle guys. It seems unlikely that it would be conflicting with another plug-in ID, but I guess possible.

I might try with all Rhinos closed, deleting all instances of RenderOctane.rhp. Once you are sure you got any / all of them, fire up Rhino. You shouldn't see the error because there isn't any RenderOctanes to load. Now check Rhino Options -> Plug-ins just to be sure a rouge version isn't still loading from somewhere (if it is, down toward the bottom of the window that comes up when you click Properties for the plug-in, it will give the file name including the path in case it is someplace odd).

Give me a second to work out the above mentioned bug.
Sam

OK, attached a new version in the first post. It fixes a bug in getting the options to stick.

Let me know if you have problems,
Sam

Thanks again Sam! Your making rendering from Rhino a joy, in Octane that is... I've done some comparisons on the same project in Brazil vs Rhino and will post them on my Gallery soon. I thought I was getting pretty good with Rhino/Brazil but Octane has changed all that. Keep up the good work on the plugin and I'll see you on the Rhino group. Funny how I don't see much there on Octane, maybe I should give them another poke... Jody

The new version (like previous versions) can't find the path to Octane. What do I need to do?

Thanks,
tim

timbarnes wrote:The new version (like previous versions) can't find the path to Octane. What do I need to do?

OctaneOptions will let you browse for the path. If you are still having problems, make sure you have actually deleted the old exportOptions.ini, it sounded like your old version had some permission issues which I'm not sure where ever resolved.

Sam

Thank you Sam!

No more Error!

Whoohooo!


Oooop!

One thing, though:

when it opens in Octane, the navigation is a little 'funky' and orbits spherical radially instead of flat radially. Is there an on/off setting for that in Octane? I recall that happening even before you started working on a plugin.

8Eggar8 wrote:when it opens in Octane, the navigation is a little 'funky' and orbits spherical radially instead of flat radially. Is there an on/off setting for that in Octane? I recall that happening even before you started working on a plugin.

I will have a more in depth look when I get a chance (I have to get out to the polls this evening), but it should be rotating about the target point, which should be the same as the target point in Rhino in the active viewport you exported from. So the orbiting in Octane should be similar to the orbiting in Rhino.

The one inconsistency that I know about is that the camera up vector gets a little funky in Octane. So while if you didn't purposely roll your camera in Rhino, the camera will stay level as you orbit about. In Octane, the camera will come in with no apparent roll, but as you orbit about you will start to see roll introduced. This is something that was a byproduct of me wanting to include purposeful camera roll in Rhino, but it needs to be cleaned up in my plug-in.

Sam

SamPage wrote: OctaneOptions will let you browse for the path...
Sam

Thanks, Sam. I have it working now. My next problem is to get Rhino to read the materials in a Revit .fbx file...I can load my model, but it comes in white. Loaded into 3dsMax it comes in with materials (when it doesn't crash). But that's not a plugin problem.