Hi everyone! I’ve really been excited about the new clipping plane features in Rhino 8 but I’ve been frustrated by the bugginess. Hopefully this is just user error and I’m failing to adjust a certain setting!
In my layouts (and in the final exported drawings), I’ve been experiencing some bugs where the sections are incomplete.
Hi Japhy, tank you so much for your fast response.
This is a problem that I’ve have had frequently while using clipping plane with complex structures.
Please see attached a sample of the model.
Also, system info:
Rhino 8 SR11 2024-9-10 (Rhino 8, 8.11.24254.15001, Git hash:master @ d3c11108eae09fadc146928ba51b9b182a05303f)
License type: Educational, build 2024-09-10
License details: Cloud Zoo
Windows 11 (10.0.22631 SR0.0) or greater (Physical RAM: 32GB)
.NET 7.0.0
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 2080 SUPER (NVidia) Memory: 8GB, Driver date: 3-12-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 551.86
> Accelerated graphics device with 4 adapter port(s)
- Secondary monitor attached to adapter port #0
- Windows Main Display attached to adapter port #1
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 3-12-2024
Driver Version: 31.0.15.5186
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8 GB
Rhino plugins that do not ship with Rhino
C:\Program Files\Chaos Group\V-Ray\V-Ray for Rhinoceros\V8\VRayForRhino.rhp “V-Ray for Rhino”
C:\Users\thier\AppData\Roaming\McNeel\Rhinoceros\7.0\Plug-ins\D5Conv (e0d5e210-02f6-4ee9-a2b0-1675e225d958)\0.10.1.0001\Rhino 7\D5Conv.rhp “D5Converter for Rhino”
C:\ProgramData\McNeel\Rhinoceros\7.0\Plug-ins\Datasmith Rhino Exporter (d1fdc795-b334-4933-b680-088119cdc6bb)\DatasmithRhino7.rhp “Datasmith Exporter” 5.3.0.0
C:\Users\thier\AppData\Roaming\McNeel\Rhinoceros\7.0\Plug-ins\Lumion LiveSync for Rhino (839d6175-32d1-4ffe-a0a4-b7fb43cf0ff5)\2021.3.25.899\Lumion\Rhino 7.0\LumionPlugin.rhp “Lumion LiveSync for Rhino”
C:\Users\thier\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\EleFront\4.2.2\ElefrontProperties.rhp “ElefrontProperties” 1.0.0.0
C:\Users\thier\AppData\Roaming\bf7_plugins\LayoutManager\0.1\LayoutManager.rhp “LayoutManager” 0.2.6.0
C:\Users\thier\AppData\Roaming\McNeel\Rhinoceros\packages\8.0\AdaptivePartsEnvironment\1.0.65.3\Rhenso.Ape.rhp “Adaptive Parts Environment” 1.0.0.0
C:\ProgramData\McNeel\Rhinoceros\packages\8.0\LadybugTools\1.38.188\Ladybug.RH.Loader.rhp “Ladybug.RH.Loader” 1.38.188.0
C:\ProgramData\McNeel\Rhinoceros\packages\8.0\Pollination\1.48.9\Pollination.RH.Loader.rhp “Pollination.RH.Loader” 1.48.9.0
Thanks for sharing this link Japhy, I’ve posted on this forum a number of times without all these details and now I know how to include them when posting in the future!
Your file is in meters and the tolerance is larger then or equal to the length of some of the features in that model. This is a recipe for problems. Change your units to centimeters using the “Change unit system and maintain object sizes” option.
-wim
Sorry, ill try do explain clearly and also am attaching the complete version.
I’m developing a bamboo structure and need to extract the technical drawings.
The overall model seem to work ok, extracting the perspectives and views.
However, when I started trying to extract the sections, thats when the problems started.
The clipping planes are bugging with the geometry, I want for the area where the clipping plane intersects with the geometry have a solid black hatch. I was expecting to have this kind of result:
Hi Wim, sorry, was responding to Japhy while you responded.
I did as you said and it definitely improved the model.
However, there was still with some bugs on the hatches:
What I did to solve the issue was to create a new model in millimeters and pasting the geometry into it, it created a much cleaner model. However, that means that I’ll have to recreate the whole set.
Thanks, I’ve put this on the list as RH-84041 Display: Monochrome Silhouettes ‘Mix’ with Edges
For the time being, you could change the settings so that the edges are drawn in the same color as the silhouettes.
FWIW, Note that when you print these drawings to a vector PDF, the shaded features of the Monochrome display mode will be discarded, and I’d probably just use the Technical display mode for this type of production documentation anyway.
-wim
This is a problem with how and where silhouettes are calculated.
Edges are mathematically defined curves with infinite precision… Silhouettes are made up entities based on camera viewing angle, and stem from the render mesh’s back faces that share an edge with a front face.
This means that if/when the render mesh is not optimum, it’s edges will not follow the same path as the infinitely precise curve/edge.
The only way to get things to work better (other than what @wim suggested), is to increase the meshing quality…either on an individual object basis, or at the document level. If I set all of the meshing settings to 0.0, except for “Maximum edge to surface distance” I set that to 0.001 or 0.0001… Then most of the issues go away because the mesh edges now follow much more closely to the actual edges.
Note: However, in parallel views you still may encounter z-fighting between mesh edges and curves because camera view angle is non-existent…but I may be able to tune that up…won’t know until I try.
When I applied the first fix, which was changing the model units and scaling, the model the model worked.
So what I did next was to start a new model in millimeter, change the whole grasshopper unit sliders to also be millimeters. After I did that, when I tested the sections I had the exact same problem as before. What do you think is causing it now? I attached the rhino file and also the grasshopper model.
As for the silhouettes in monochrome, I tested increasing the mesh quality, but for me it didn’t work and made the model super slow. So I just changed the displays to technical an it gave me a better result.
If you’re going to just do that, and you prefer Monochrome mode, then I would just go into the Monochrome display mode settings and change the “Edge Color” to match the “Silhouette Color”, or vice versa… The reason “Technical” gives a better result, is because all “Line Color” settings are exactly the same (i.e. they’re all set to use “Object color”).
Not sure why increasing the mesh quality didn’t solve the issue for you…but I do understand that it can make the model/display pretty heavy, depending on the setting you use.
The problem that I had on my last comment is that I’m having the same issue I had in the beginning of this thread, but with the model in millimeters.
I started a new model with the units set to millimeter and also set my whole grasshopper script to also be in millimeters. However, I’m having the same problem I had when when I modelled everything in meters.
I attached the files in the previews comment.
I really have no idea what is causing this.
If you think I can try a different approach…
