Only difference is that your Use Advanced GPU Lighting is checked. Changing this hasn’t affected selection as of yet. I’ll keep poking at it.
Can you repeat behavior while in Safe mode?
But Viewport shading in safe mode is disabled…
My bad, I thought that could be made available.
Here are a few observations.
These display modes DO work:
Wireframe, Technical, Artistic, Pen & Monochrome.
Here are display modes that DO NOT work:
Shaded, Rendered, Ghosted, X-Ray, Acrtic, Raytraced.
Exporting geometry out to IGES and importing back in made no difference.
The GPU is disabled in safe mode, so those aren’t available for testing. I was concerned with Jeremy’s plugins and that is a quick way to test… if shading was available.
Also, setting Antialiasing to None and unchecking GPU Tessellation made no difference either.
Hi @Japhy,
I’ve disabled plugins that do not ship with Rhino, restarted and the problem still occurs, so they are not the problem.
But - I also tried disabling the 3Dconnexion 3D Mouse plugin and restarting and the problem went away. However on another computer with the plugin enabled, but no SpaceMouse attached I don’t get the problem. So on the problematic pc I reenabled the plugin and turned off my SpaceMouse Wireless then restarted Rhino but the problem persisted.
Next I removed the 3Dconnexion transceiver from the PC and restarted Rhino and this time the problem went away. So I think that the problem is related to the transceiver (although it is also possible that without a Spacemouse connected the 3Dconnexion plugin doesn’t load - one for a dev to advise on).
This is further borne out by the discovery of another symptom. With the transceiver in situ and the 3Dconnexion plugin disabled, I sometimes notice a small hesitation before the system reacts to the mouse click on the second panel. Further, if I select the first panel without shift and then press shift before quickly clicking on the second panel I sometimes get the second panel selected but the first deselected (ie. as though using an unshifted click). If I move more slowly this does not happen. This suggests that the transceiver is interacting/interfering with my Logi wireless keyboard and mouse (which have their own transceiver) or the software which responds to them.
I’m not sure how far this takes us. @mht.jeff do you have a Spacemouse connected to your system?
Addendum: Just discovered that in the problem scenario where if I click at top or bottom of the leftmost panel I cannot select the others; if I select the first panel in the same position but via another viewport I can select the other panels fine in the perspective viewport. Curiouser and curiouser.
I believe we have found our culprit. Let me see what i can find that might be related.
MorningJaphy,
I followed those instuctions to the letter and still no bueno here.
I had high hopes you had fixed things. It made some sense because it will always work WHILE rotating the geometry with the 3DConnexion device.
Additional information in case it helps.
I have an another almost identical ThinkPad machine with the same video card but running windows 11. When that machine is plugged into the same docking station it does work. It seemed like it didn’t work once, but I just repeatedly tried opening and filleting and it works.
I have a docking station upstairs and downstairs, both with different types of 3DConnexion devices, my primary machine will not work either location.
Hi @Japhy,
I’ve tried updating to the latest driver (10.9.4) and to a driver from 2023 (10.8.16) and neither has cured the problem.
But here is another clue: When I have the first panel selected and cannot select the next, if I resize the viewport (e.g. by double clicking the viewport name to maximise it or by dragging the border) the remaining panels become selectable. Note: if I resize before selecting the first panel, the problem still occurs.
Hi Japhy,
Do you have any other suggestions we might try or are we stuck here?
Thanks!
Japhy,
I sure hope we’re not out of luck on a fix for this problem.
Is there a Rhino 9 WIP, or is that still on hold?
Let me know and thanks!
Ok, the problem exists in Rhino 9 WIP also. Ugh..
Mht Jeff,
Per Jeremy’s post it looks like a regression (Selection is OK with Spacemouse in Rhino 7)
If this is something on our side or the hardware side we will have to wait and see the results of the investigation by the developers.
Hey Japhy,
I want to make sure I understand you correctly, you’re recommending I switch back to Rhino 7 instead of using my shiny new Rhino 8 program?
And, are you saying that developers ARE working on this issue currently?
Thanks!
The spacemouse plugin had a bug, there is a fix and will send it to you for testing as soon as there is a build to share.
Perfect. Thanks, Japhy!