OctaneRender for Rhino 1.55 [OBSOLETE]

[face_off]

This is the recommended thread for downloading, and posting any questions, suggestions or support queries for OctaneRender for Rhino 1.5 - TEST RELEASE.

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.50.0.17
- Added camera motion blur - assumes 24fps (if your fps is different, adjust the shutter speed accordingly). This is accessed through the Animation button on the Viewport. If you set a non-zero shutter speed in this panel, it will be saved in the Rhino file, and will also be used when rendering the animation via _RecordAnimation. When doing this, discard the FIRST frame, which will not have motion blur. The camera position will be one frame behind the actual frame being rendered - in order to calculate the motion blur.

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

[v-cube]

Hello Paul,

it seems like an old bug reappeared, when rotating the HDRI map, the light distribution is odd until you untick and retick "importance sampling"...
see here:

http://render.otoy.com/forum/viewtopic. ... ri#p169139


best regards

Andreas

[face_off]

I will do a test build of the plugin against Octane 1.52 in the next day or two - and if the problem persists, escalate to Otoy.

Paul

[face_off]

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

1.52.0.20
- Compiled against Octane 1.52
- EXR added to the Load Image dialog file types
- Internal plugin changes in preparation for Octane 2
- Fixed issue where Rhino render animations could not be cancelled by closing the render window. Clicking Cancel does not work due to an issue with Rhino which will be fixed in the next Rhino SR.
- Changing between image types (ie. RGB to Greyscale) no longer pops up the Select File dialog

Andreas, can you see if this version fixes your IBL issue pls.

Thanks

Paul

[v-cube]

Hello Paul,

HDRI rotation is working again, thanks!


Andreas

[face_off]

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

1.52.0.21
- Fixed bug preventing rendering of animations

Paul

[face_off]

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

1.53.1.22
- Built against Octane 1.53.1
- Fixed bug causing the load process to use more memory than required
- Fixed bug causing an Octane rendertarget to be set when changing views even when the Viewport is closed
- Fixed bug where a line item converted to a polygon would crash Octane

Paul

[kampfer10122]

Hello Paul:

I'm currently using the newest version of octane for rhino (1.53.1.22).

Everything was working well, even a bug i have encountered while using ver. 1.50 which pops up on every frame when I'm rendering a animation( Some thread in the forum has the same issue i suppose) is fixed. Yet today I have encountered a problem while rendering with OctaneRenderViewport. A box poped up saying there is a CUDA error 700 on device 1 and the core clock on my second graphic card(which is the so called device 1 I think) dropped down from 1200 to 549 MHz immediately and stucked there. I tried to restart rhino and OctaneViewPort again again but the card is still slowed down and can only be solved by rebooting my system(but the same thing happened again when i tried to render the scene). I'll try to find out if it's a hardware issue while waiting for your reply.

My gears are

I7-4930K @3.40GHz
32GB RAM
2* EVGA GTX780Ti OC@1200MHz w/ 3GB VRAM each
Driver version 337.50

Attached file is the error message. Let me know if you need other information.
Thank you for your time and sorry for my bad english.

Humphrey

[face_off]

Everything was working well, even a bug i have encountered while using ver. 1.50 which pops up on every frame when I'm rendering a animation( Some thread in the forum has the same issue i suppose) is fixed. Yet today I have encountered a problem while rendering with OctaneRenderViewport. A box poped up saying there is a CUDA error 700 on device 1 and the core clock on my second graphic card(which is the so called device 1 I think) dropped down from 1200 to 549 MHz immediately and stucked there. I tried to restart rhino and OctaneViewPort again again but the card is still slowed down and can only be solved by rebooting my system(but the same thing happened again when i tried to render the scene). I'll try to find out if it's a hardware issue while waiting for your reply.

I suspect there is a geometry structure in the which is triggering a fault in Octane. Would it be possible to send the scene to me pls? Then I can save as ORBX and submit it to Otoy for further analysis.

Paul

[face_off]

Hi Humphrey

I was able to load and render that scene without any Cuda errors. I think in this particular case, the scene is sufficiently "complex" that the level of overclocking you are using is too much. If you bring the clock speeds back to normal, then progressively increase the clock speeds when you open the Viewport on that scene, you should be able to find the right level of overclocking.

Paul