Hey! Ive been dealing with some strange behavior over the last couple of days.
When trying to select objects in my Rhino 8 file, often times there seems to be an “invisible wall” that just blocks all selection. This has just gotten worse and worse, to the point that every command i have to do has to go through a hide then hideSwap to only see the object im trying to manipulate. This does not only apply to selecting items, but also snap points and such are often “blocked”. Again i have to hide almost every element but the one im working on. This is for object and points that are clearly visible, not clipping with anything.
I cant really add the file to the post as its for a client so sharing it would not work.
Sometimes trying to select the object from different angles, or zooming so far into it so you’re basically inside the object works. Uploaded is an example image. No matter what i do i cannot select this block from the front, but if i remove the roof and go behind the block, i can select it just fine. The roof has nothing to do with it, i just need to hide it to be able to see from the back. This problem gets workse and worse as the file gets bigger and bigger from my experience.
Its not really consistent with this i think, as i can select if from the front from very certain angles. Often only the top 10% of the object is selectable, other times only the right/left side. It seems like there is something in the way for the click almost. This also happens in Iso view, not only perspective.
Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 64GB)
.NET 7.0.20
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce GTX 1080 Ti (NVidia) Memory: 11GB, Driver date: 6-25-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 556.12
> Accelerated graphics device with 4 adapter port(s)
- Secondary monitor attached to adapter port #0
- Secondary monitor attached to adapter port #1
- Windows Main Display attached to adapter port #2
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: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 6-25-2024
Driver Version: 32.0.15.5612
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 11 GB
Rhino plugins that do not ship with Rhino
C:\Program Files\Enscape\Enscape.Rhino.Plugin-net48\Enscape.Rhino8.Plugin.dll “Enscape.Rhino8.Plugin” 4.2.0.1589
C:\Program Files\Chaos Group\V-Ray\V-Ray for Rhinoceros\V7\VRayForRhino.rhp “V-Ray for Rhino”
I run into this occasionally. When snaps fail it often has to do with…
A clipping plane is active and we might have forgotten it is on.
Or the display mode won’t allow it. (This I think is a long standing bug or bad behavior.)
Snap settings in settings might need tweaking like turning off or on snap to occluded or tweak the snap distance setting.
Lastly your display drivers might need updating.
In your image I see you’re in shaded mode, next time you run into this try switching to wireframe mode and see if the snaps work again. I have found that shaded mode and other viewmodes will not let one snap to interior areas even though the yellow highlight outline shows them.
I’ve complained about this but got no response since I don’t think snaps should be viewmode dependent.
RM
I wonder if there is some kind of object that is causing the view frustum to be too big/too small/in the wrong place. Maybe try turning on the camera (F6) to see where it is… Also viewports can get corrupted, you can do a reset by running the 4View command twice.
If you have any clipping planes in your scene, it’s possible that a current 8.17 fixes the issue that you are running into → RH-85940 Selection: Clipped objects incorrectly block mouse picking
Does the behavior change when you disconnect all but one of those screens?
You can send sensitive files to us from Rhino Accounts.
If you use that page, make sure to add a link to this thread in the comments field.
-wim
Switching to wireframe does indeed let me snap like i expect, so its a workaround for now. For info i had this exact problem with Rhino 7 for months now, so its not something new in Rhino 8
I was playing around with the camera a bit and it seems the i can now select stuff normally like im used to. Could it be the camera being to “big/small”? Would love to find exactly whats causing this so its easy to solve next time, but for now just fiddeling with the camera has seemed to solve it
Yes so please complain and let’s get rhino development to even acknowledge it or worse fix it.
Notice that throughout this whole thread the developers ignore that you can select it if you switch to wireframe. Do they even mention that selection is viewmode dependent? Do they try to fix it since one can see the wireframe in highlighted yellow?
As you can see you had this problem in V7 and it’s in still in V8.
RM
