I thought this initially was because I’m using the rendered mode a lot in this project (my first V8 project), but I just had this happen using the shaded mode too!
When it happens, I need to alter the camera angle and click on my surfaces again to actually get a selection (and so far, it’s only surfaces).
Maybe it’s not just the camera, but something with adding to an existing selection?
I managed to capture this, which is me shift clicking around a surface I’m not able to select, until I accidentally select the background have to de-select everything and then I’m allowed to add it to the selection…
Yes, I also get the following problems:
Thank you for confirming!
Now that I look at the video I posted, it does appear as if the click which causes everything in the background to get selected is a correct click on that surface, so maybe I actually managed to capture that happening as well!
I just had another instance of this happen where a leader absolutely refused to get selected until I hit esc (but no tool/command was active)…
Pls post a model in the position that you see this issue happening in, and, as always _SystemInfo,
Thanks.
It will be very helpful if you can send the model in the exact camera position when this happens again, thanks
I have also noticed this, especially when shift-selecting multiple objects.
Selection Bug.3dm (429.3 KB)
In this file in current camera view.
Click the red object (selects normally).
Click it again in the same place (deselects the object as though I clicked the background).
Rhino 8 SR15 2024-12-3 (Rhino 8, 8.15.24338.10001, Git hash:master @ 1c140c6af196d6cc0dc11d8f781198912e87de59)
License type: Commercial, build 2024-12-03
License details: LAN Zoo Network Node
Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 112GB)
.NET 7.0.16
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA Quadro K5000 (NVidia) Memory: 4GB, Driver date: 6-10-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 475.14
> 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
GPU Tessellation is: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU's maximum)
Anti-alias mode: 2x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 6-10-2024
Driver Version: 30.0.14.7514
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 4 GB
Rhino plugins that do not ship with Rhino
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp "Commands" 8.15.24338.10001
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\IdleProcessor.rhp "IdleProcessor"
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp "Rhino Render" 8.15.24338.10001
C:\Program Files\Rhino 8\Plug-ins\RhinoRender.rhp "Legacy Rhino Render"
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp "RDK_EtoUI" 8.15.24338.10001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp "Snapshots"
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp "MeshCommands" 8.15.24338.10001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp "RhinoCycles" 8.15.24338.10001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp "Toolbars" 8.15.24338.10001
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"
I cannot reproduce that behavior here. I tried on both Mac and Windows. Does it matter for you where on the object you click?
Basically anywhere in the faces. Clicking the edges behaves normally.
@Measure we can’t seem to reproduce that here. Can you run _Reset, hit the “save settings for support” and send over the resulting zip? Maybe that reveals something.
RhinoSettingsForSupport.zip (540.6 KB)
@Measure that didn’t reveal anything unfortunately.
Here’s mine:
RhinoSettingsForSupport.zip (1.4 MB)
Also, this just happened:
I can’t share the file, but what’s happening is this:
So, unfortunately, while it’s random that this happens, when it happens the behavior is very consistent until you change the camera angle.
With clipping views enabled, adjusting dimensions is equally unreliable (again depending on zoom).
@eobet Mikko generally fixes selection issues quite quickly if you can share a repeatable example. I could not reproduce this by simply making an object with a dimension and a clipping plane.
If this happens again, pls send the model in the exact camera position, thanks!
Huh… managed to end up in a situation where missed selections were reproducible so often that I managed to take another video of it:
But then, after I switched off my clipping planes, the problem went away, and now I even have pre-selection highlights back which you’ll notice is missing from the video…
EDIT: Oh, those pre-selection highlights do disappear quite often for me depending on camera angle I see now… I was even so surprised to see them that I think I’m more used to actually not seeing them (and that’s with the default shaded view mode as you can see).
EDIT: Ah, clipping planes is the culprit with the pre-selection highlights as well, it seems. I do like my clipping planes. 
Hi Robert -
…
-wim
Unfortunately, I tried to export just the affected objects (and even some surrounding ones on affected layers, including the clip planes) but that wasn’t enough.
I can’t send the entire file because that’s just too sensitive (new client).
But I can 100% reproduce it in this file.
EDIT: No wait, I think I figured it out… objects clipped by the clipping planes block selection! Sending reproducable example now.