OTOY Forums

Hi Paul,

Quick Question -- I think I remember some discussion a while back with the possibility of implementing the Rhino command "Clipping Plane", so that Octane will render the clipped items, like they are shown in the Rhino viewport. Is this still possible, and if so, is it somewhere on the long term list of features to be added at some point?

Thanks,
Ryan

Quick Question -- I think I remember some discussion a while back with the possibility of implementing the Rhino command "Clipping Plane", so that Octane will render the clipped items, like they are shown in the Rhino viewport. Is this still possible, and if so, is it somewhere on the long term list of features to be added at some point?

I will put that question to the McNeel devs.

Paul

Thank you Paul. They are usefull for still shots of buildings to show a "floor by floor" arrangement. And, another nice feature about the clipping planes is that you can animate them in Bongo, so they can be powerful for architectural animations to "pull back" a floor to reveal the interior.

Bendbox wrote:Thank you Paul. They are usefull for still shots of buildings to show a "floor by floor" arrangement. And, another nice feature about the clipping planes is that you can animate them in Bongo, so they can be powerful for architectural animations to "pull back" a floor to reveal the interior.

yes clipping planes !! me too

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

2.21.1.32
- Compiled with Octane 2.21.1
- Added Light Passes (you can now assign a Light Pass to each Emitter, and then view each light pass as a Render Pass).
- Added Out-of-Core Textures to the Devices tab - where texturemaps can now be stored in CPU/Motherboard RAM if graphic card VRAM is full. Enabling this sets the RAM limit to your total RAM amount.
- Added "Cube Map" project type to the Spherical Camera
- You can now adjust the new Focal Length slider in the Thinlens Camera to adjust the Aperture

Paul

Regarding clipping planes - McNeel have stated (as at mid-last year) it was not possible. http://discourse.mcneel.com/t/neon-clip ... nes/8903/4. Suggest if you want this, put in a feature request for Rhino6 for clipping support for renderer plugins.

Paul

face_off wrote:Regarding clipping planes - McNeel have stated (as at mid-last year) it was not possible. http://discourse.mcneel.com/t/neon-clip ... nes/8903/4. Suggest if you want this, put in a feature request for Rhino6 for clipping support for renderer plugins.

Paul

Will do. Thanks for checking into this Paul.

face_off wrote:Regarding clipping planes - McNeel have stated (as at mid-last year) it was not possible. http://discourse.mcneel.com/t/neon-clip ... nes/8903/4. Suggest if you want this, put in a feature request for Rhino6 for clipping support for renderer plugins.

Paul

Hi Paul,

I posted the request to make clipping planes available to render engines to the Rhino devs, and they have a public SDK for adding clipping planes to render plug in's. Is this what you'd need to allow this feature to work in Octane for Rhino?

Here's the discussion link: http://discourse.mcneel.com/t/render-su ... anes/16775

Thanks,
Ryan

Hi Ryan. I think Andy and Steve are saying that they think that clipping planes are a renderer function rather than something the RDK needs to support. In this case, Octane would need to support clipping planes in order to support clipping planes in the Rhino plugin. At a guess, I would think building clipping plane support into a GPU renderer like Octane would kill performance, because Octane would need to be always accessing if a vertex was visible or not. To me it makes more sense to only load polygons into Octane which are visible - so a RhinoCommon function to provide this would be great.

Paul

face_off wrote:Hi Ryan. I think Andy and Steve are saying that they think that clipping planes are a renderer function rather than something the RDK needs to support. In this case, Octane would need to support clipping planes in order to support clipping planes in the Rhino plugin. At a guess, I would think building clipping plane support into a GPU renderer like Octane would kill performance, because Octane would need to be always accessing if a vertex was visible or not. To me it makes more sense to only load polygons into Octane which are visible - so a RhinoCommon function to provide this would be great.

Paul

Thanks Paul. So, I need to request a "RhinoCommon" function? Is this the correct terminology to ask for?

Also, I might try the Rhino Section tools and see if they actually load polygons instead of use a trick. They are definitely doing something in a different way, because Rhino's standard clipping plane clips everything, and with the section tools, you can specify "per geometry" clipping. Which is really more useful anyway. I doubt it will work, but they are free, so it can't hurt to try!

*edit* Ok, I just went back to the Rhino forum and saw that you had responded (THANK YOU!). Maybe the developers will respond with a RhinoCommon function solution.