OctaneRender for Rhino 1.50 [OBSOLETE] Tweet

[face_off]

This is the recommended thread for downloading, and posting any questions, suggestions or support queries for OctaneRender for Rhino, build 1.50.0.15 onwards (STABLE RELEASE). This version is compiled against Octane 1.50, so see the requirements for that build regarding compatibility with your video card.

This version requires Rhino5, SR8 - build 40305 or later. Pls check your Rhino version prior to installing this version of the plugin.

Scenes saved with this build cannot be loaded with the 1.20 build, so make sure you keep a backup of the 1.20 scenes

If you have a support issue, pls provide the following information:
- Operating System (ie. Win XP, Vista, 7, 8)
- 32 or 64 bit
- Amount of RAM
- Graphics Card(s) - model (ie. GTX 580, 3GB)
- Nvidia driver version
- Rhino version and build number
- OctaneRender for Rhino version (ie. 1.20.1.13)

Change Log from release 1.32.0.15
- Compiled against Octane 1.50

For more information...
- Watch Iceglance's quickstart tutorial http://render.otoy.com/forum/viewtopic.php?f=51&t=36299
- Read the on-line manual
- Watch the "Getting Started" video http://vimeo.com/73202740
- Read the FAQ
- Post your question on this forum thread

Limitations
Refer to the on-line manual

Download Links
Download the plugin from the following links:
- OctaneRender for Rhino5 1.55.0.24 (64 bit)
- OctaneRender for Rhino5 1.55.0.24 (32 bit)

Paul

[Bendbox]

Hi Paul,

For the limitation you mentioned, do you mean that when performing an animated sun study, the correct sun position is not being pick up, or do you mean that Octane will not pick up an accurate sun position at all, not even for still images? If the later, did McNeal say when this might be fixed, it's really important to determine sun angle when designing building interior elements near windows. Thanks!

[Bendbox]

Also, two other quick questions --

1) is the viewport texture map bug ironed out with this release? (I think however, this may have had to do with McNeal though and not Octane)
2) I'm assuming that files created with the 1.32 version won't have any issues when installing 1.5 -- is this correct? I ask because I have many ongoing projects that I created using 1.32, that I'm still working on. If installing 1.5 will cause any issues, I'll hold off for now.

Thanks.

[face_off]

For the limitation you mentioned, do you mean that when performing an animated sun study, the correct sun position is not being pick up, or do you mean that Octane will not pick up an accurate sun position at all, not even for still images? If the later, did McNeal say when this might be fixed, it's really important to determine sun angle when designing building interior elements near windows. Thanks!

Sun position when rendering to the Octane Viewport is fine. When rendering to the Rhino renderer panel (incl animations) where was an issue picking up the Rhino sun position for Octane to use. McNeel said it could be done, but it's one of those things people haven't needed to date, so had a low priority and not been fixed yet.

1) is the viewport texture map bug ironed out with this release? (I think however, this may have had to do with McNeal though and not Octane)

I have been in daily communication with McNeel on this, but there is no solution yet - sorry.

2) I'm assuming that files created with the 1.32 version won't have any issues when installing 1.5 -- is this correct? I ask because I have many ongoing projects that I created using 1.32, that I'm still working on. If installing 1.5 will cause any issues, I'll hold off for now.

It's only 1.21 onwards scene that will not load in 1.20. Going the other direction is fine. If exporting to Standalone, make sure you have the same version of Standalone as the plugin (ie. 1.50).

Paul

[Bendbox]

Thanks for the good info Paul. That's really good to know that Octane is picking up the correct sun position. If it helps with McNeel, as far as people needing it, I'm sure there are many who use some type of batch rendering, which would of course render to the Rhino panel instead of Octane's. I see this being pretty important, as interior architecture renderings can take quite a while, and I'd love to run a batch render while I sleep overnight and not worry about the correct sun position! Thanks again!

[face_off]

The interim version at http://render.otoy.com/customerdownloads/plugins/OctaneRender_for_Rhino5_1_50_0_16_64bit.exe should pick up the sun position whilst rendering Sun Studies. Refer to the instruction at http://render.otoy.com/manuals/Rhino/?page_id=388 for details.

1.50.0.16
- Increased the height of the material tree in the Material panel by 20%. Can go bigger if needed.
- Implemented automatic sun positioning when rendering Sun Studies. To do this, turn the Rhino Sun OFF, then the Rhino render will provide the Octane sun position from the Sun Study sun direction
- Added support for Worksessions. Attached scenes will need their Octane materials already defined (ie. you cannot edit the Octane material of an attached scene object in the worksession).

Paul

[Bendbox]

Awesome, thank you!

[eric_clough]

Hi Paul ...

1.50 plug-in for Rhino is working beautifully and I get the impression that it is faster and smoother on my system than previous versions. I am updating my system in the next couple of days so I may have some more input for you then.

When I used the Octane window with wireframe in the the Rhino display the response was almost instantaneous ... also very responsive with the render view in the Rhino window. However, when I turned the display on to Neon it was fast, too, but Rhino crashed in a few minutes of perspective angle changing. I restarted Rhino and used 'wireframe' display and could not get a crash.

This is not a really big file.

cheers,
eric

[face_off]

When I used the Octane window with wireframe in the the Rhino display the response was almost instantaneous ... also very responsive with the render view in the Rhino window. However, when I turned the display on to Neon it was fast, too, but Rhino crashed in a few minutes of perspective angle changing. I restarted Rhino and used 'wireframe' display and could not get a crash.

Hi Eric. Is this reproduceable (ie. can you make it happen every time?).

EDIT: I installed Neon and tried some scenes, but couldn't get a crash. Would be good to know your OpenGl settings in Rhino, and Neon settings.

Paul

[eric_clough]

Hi Paul ...

No, I could not recreate the crash ... and this time I was using a much larger drawing file.

It's pretty jumpy but workable. I'm pushing the limits of my present system.

cheers,
eric