OctaneRender for Rhino 3.03.2 [OBSOLETE]

[face_off]

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

2.10.0.17
- Fixed issue where rendering in the Rhino render panel with the OctaneRenderer was not working

Sorry - the ortho view is not fixed in this release - it will be in the next one.

Getting an error using the 'Render' command (as opposed to opening the OctaneRender viewport) - see attached image. It instead causes the viewport to stop responding (I assume related issue). Thus !_RecordAnimation doesn't currently work unless using viewport geometry (ie. no scripted or bongo animations) amongst other things.

Fixed in 2.10.0.17.

I attached screenshots demonstrating this - the 'expected' result (500ms shutter speed) and the rendered outcome. Note that due to the issue listed above this is 'using render viewport geometry' to record the animation.

Your workflow is correct - and I just tested the same workflow and it worked (on 2.10.0.17). Keep in mind that if the entire animation is a shorter length than the shutter speed, you won't get any motion blur. Perhaps try again on the latest version. I closed the viewport down prior to _RecordAnimation. I will add a tutorial for this to the manual in the next week or two.

And lastly, just wondering if there's any way camera motion blur can respond to the camera motion paths of Bongo, and also (less importantly) whether there was any news on the front of object motion blur with Bongo, as IIRC it was discussed a little while ago.

Can you import the bongo camera path to the Rhino fly-thru path? If so, the current version should do this. For object motion blur, the intent is to provide a facility to export the entire scene's (Bongo) animation (ie. vertex positions each frame) to ORBX, so you can render in Octane Standalone. I have posted elsewhere that I will look at this once someone sends be a Bongo scene with both camera and object movement animation.

Paul

[newske]

Thanks for the swift response/fix as usual Paul. The render window appears fixed.

However, still having a couple of issues:

Rendering from Bongo (!_BongoRenderAnimation) freezes (see attached image). Tested with Rhino Render and all appears fine - very simple scene (as pictured) and only settings in Octane changed were to reduced the max samples to 160 from 16000.

Still having issues with camera motion blur - it does show some motion blur, but certainly not the same as pictured in the OctaneRender window when setting the shutter speed. ie. When setting it to 500ms for example it will show correctly in the OctaneRender window, but appears to only render it at around 24ms, as if the setting was forgotten (something around that is default?)

Also, in a related matter - there's a convenient (maybe accidental?) feature, which is after setting a shutter speed, you can render from a location, move the camera slightly and render from a different location and have camera motion blur between the two. Rendering twice in the same spot essentially makes for no motion blur. As such - I was wondering if it would be possible to have this 'always on' but defaulted to 0ms shutter speed, and include it in the camera module of a rendertarget? I assume this would make cmb work with Bongo (given it happens just by rendering 2 locations after turning it on) and would also make it easier to have cmb for 'single' images.

Minor note: spelling of "All Mehses Live" under Live Updating, under settings.

Cam

[face_off]

Hi Cam - would it be possible to email be the bongo scene, and the scene demonstrating the motion blur problem pls? Then aI can take a closer look.

Also, in a related matter - there's a convenient (maybe accidental?) feature, which is after setting a shutter speed, you can render from a location, move the camera slightly and render from a different location and have camera motion blur between the two

This looks like a plugin bug Sorry.

Paul

[v-cube]

-OK I think I missed this one...

Is Bongo (with motion blur) supported now?!

I always thought MB was only working for native rhino animations...

please enlight me

Andreas

EDIT : OK should have read the entire postings before getting exited.... anyway I am looking forward to this !

[face_off]

Hi Andreas - pls see the message from the 2.06 thread.....I have not yet received any test bongo files to continue this work - so figured no one was interested

2.6.0.12
- Compiled against Octane 2.06
- Added fix to stop the Octane tree control from frashing while rendering
- Color picker dialog now remembers it's last position
- Added Rhino commands "OctaneRenderOpenViewport" and "OctaneRenderCloseViewport" to open and close the viewport

I need to also do some work on the "Sync Octane to Rhino Environment". At the moment this mode is not saved in the Rhino scene - and there are some other complexities which need to be addressed. So you will see some changes with this in the next few weeks.

I have also done some work on exporting a full Bongo animation to OCS/ORBX for rendering with Vertex Motion Blur in Octane Standalone. I am looking for a Bongo test scene, which has both object and camera movement - so if you have something like this, pls send it to me.

Paul

[v-cube]

Sorry Paul , must have forgotten about it. ...
I was burrowed in work for the last 10 days and now I will be on vacation for 14 days...

But I am really, really interested, and the first thing when I come back will be providing you a bongo file

Best

Andreas

[newske]

Hi Paul,
It seems that curves might be filling up GPU ram even when curve piping is not enabled - ie. I am currently rendering a scene on my 1GB cards, and with no curves the total is ~200mb, but with 4000 curves visible (with no piping) it tops out the card and won't render.

Cam

[eric_clough]

Hi Paul

I am using the latest beta and it seemed to be working well ... then I added windows to a building I am designing and the back wall became transparent when looking through the interior of the building. I tried building a new wall and placing it where the existing wall was and when that had no effect I built a wall just outside ... it was transparent also.

Then I got a message that there was an exception (having to do with Octane). Then Octane quit working altogether. I reloaded it from your current download page and it is now functioning but still produces a transparent wall. And there are some decks on the building with extruded single planks set next to each other. Many of the planks now have chunks missing.

I really don't know if I am having Rhino problems or Octane problems.

In either case it is frustrating.

cheers,
eric

[face_off]

Eric - could you provide a screenshot and/or sample scene which produces this issue pls?

Paul

[eric_clough]

Hi Paul ...

Now I feel just a bit foolish. The seemingly transparent wall was simply reflective glass and the angle of view ... the reflection lined up exactly with the base angle of the ground. It is the first time I have used highly reflective architectural glass.

And the missing pieces of the decking is an artifact of Neon for Rhino.

So, except for the crash and needing to reinstall Octane all seems to be OK.

I was rushing to finish a render to meet with a client so I could not tell a reflection from a hallucination.

thanks,
eric