Minor-ish clipping plane bug with selective clipping

I’m seeing some weird behavior with the clipping plan in certain view modes if I use selection clipping.
Arctic mode:


Rendered mode (bolt is slightly X-Ray’d):
image
It might be material based? I slapped a custom material on the bolt:

Modes like pen/shaded look okay.

Looks like my crystal ball is completely broken…
Works fine here.

I tried it on a fresh file and it definitely still does it. It’s only happening in certain display modes (monochrome, arctic, rendered).

Issues encountered on my setup are usually indicative of issues other’s will encounter as well (I’ve been fairly lucky to be spared from the more rare and unusual bugs). At the moment, selection clipping isn’t really something I absolutely need, so posting this issue is more just an FYI more than anything else.

The setup in your image looks simple enough. Why not just post that 3dm??

I agree but the 3dm is so simple that it can be recreated in seconds. I’ve chased this for a while between updates and it’s persistent. Same goes with the file(s)/geometry. I’m also careful about posting bugs when my machine is ‘maxed out’ (lots more stuff goes wrong but it’s usually doing things I shouldn’t being doing or don’t need to do).

It might be better to wait and see if someone else has the same issue (90% sure someone will). As mentioned this isn’t critical (the printing issues were, it’s fixed, and prints look awesome now!!).

Here’s my system info:

Rhino 8 SR4 2024-1-11 (Rhino 8, 8.4.24011.01001, Git hash:master @ e10fc00b1217949781e60400f1920b7f9ad96acb)
License type: Evaluation, build 2024-01-11
License details: Cloud Zoo
Expires on: 2024-02-15

Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 15GB)
.NET 7.0.10

Computer platform: LAPTOP - Plugged in [100% battery remaining]

Hybrid graphics configuration.
Primary display: AMD Radeon™ Graphics (AMD) Memory: 1GB, Driver date: 6-22-2020 (M-D-Y).
> Integrated accelerated graphics device with 3 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA GeForce GTX 1650 Ti (NVidia) Memory: 4GB, Driver date: 10-26-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 546.01
> Integrated accelerated graphics device with 1 adapter port(s)
- Video pass-through to primary display device

Secondary graphics devices.
DisplayLink USB Device (DisplayLink) Memory: 0MB, Driver date: 4-16-2020 (M-D-Y).
> External USB display device with 1 adapter port(s)
- Secondary monitor attached to adapter port #0
DisplayLink USB Device (DisplayLink) Memory: 0MB, Driver date: 4-16-2020 (M-D-Y).
> External USB display device with 0 adapter port(s)
- There are no monitors attached to this device. Laptop lid is probably closed

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: 10-26-2023
Driver Version: 31.0.15.4601
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 4 GB

Rhino plugins that do not ship with Rhino
C:\ProgramData\McNeel\Rhinoceros\7.0\Plug-ins\Datasmith Rhino Exporter (d1fdc795-b334-4933-b680-088119cdc6bb)\DatasmithRhino7.rhp “Datasmith Exporter” 5.0.3.0

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.4.24011.1001
C:\Program Files\Rhino 8\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 8\Plug-ins\RhinoLabsTools.rhp “Rhino Labs Tools”
C:\Program Files\Rhino 8\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.4.24011.1001
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.4.24011.1001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.4.24011.1001
C:\Program Files\Rhino 8\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 8.4.24011.1001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.4.24011.1001
C:\Program Files\Rhino 8\Plug-ins\RhinoCode\RhinoCodePlugin.rhp “RhinoCodePlugin” 8.4.24011.1001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.4.24011.1001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”

If you post a 3dm file, then we can look at it and see if we get different results than you. Even pictures with boxes are surprisingly hard to accurately duplicated. For example, we don’t know if these are extrusions or polysurfaces.

clipping plane bug.3dm (186.0 KB)
Fair enough!!

1 Like

That may be so but sending the actual file you are testing with is far better if possible. There always the possibility - liklihood even - that some detail will be different when we try to reproduce.

Meantime, I think this may be the bug
RH-79291 Display: ClippingPlane display glitch

-Pascal

1 Like