The Space Mouse Rotates opposite to how it works in V8. Unusable.
I rely on this device in Rhino, please see what you can do.
Are you aware of the _Spacemouse command?
1 Like
that’s a Windows only command
1 Like
Ah ok, I didn’t know that…
@Udo_Kolter Unfortunately, the only [known] solution ATM is to wait and hope
I didnt know that one, Thanks Martin !
1 Like
Hi All-
We’re aware the the 3DConnexion support in the RhinoWIP on Mac is broken at the moment. We had intended to work on this over the past few weeks, but unrelated regressions on macOS Tahoe have taken priority. We hope to get back to this soon.
Apologies for leaving this in a broken state.
-Dan
1 Like
@Udo_Kolter looks like a known issue and we are working on it… sorry there is no eta for fix
1 Like
Thank you Dan, il be waiting for that.
How can I get 3dconnexion Space Mouse to work on the present V8?
It was working last week.
It now also dos Not work. I get Error Messages. When reinstalling its driver.
Failed see support. Can you help?
Udo Kolter
Cross-posting here, just in case:
Thank you Dan, I was finally able to install 3dconnexsion’s latest driver off there web sight. It seems to work well in Rhino3d V8. However in the prototype Wip V9 it rotates on wrong axis. Wen I twist to rotate horizontally, it tilts vertically. Can you work with the developer at Rhino to help them correct this? In the driver app the option ( Rhinoceros ) dos not work. I’m on Mac Tahoe.
We are actively engaged with the developers at 3DConnexion and working on the improved integration for Rhino 9 for Mac (RhinoWIP currently). We have a ways to go.
It’s possible in the latest RhinoWIP, it’s possible the newer plugin and the legacy integration are currently interfering with each other. I’m looking into that. In the meantime, please give this a try: RhinoWIP for Mac: Updated 3DConnexion library - #27 by dan
You might have to restart your Mac to get this all working as well.
In the latest update to V9 Wip My 3dconnection Space Mouse is again Rotating the wrong way as discussed last time as below. Could you please fix this?
Thank You
Hi Udo-
Can you please navigate to RhinoWIP > Settings… > Advanced and search for SpaceBall.UseLegacy…
Is it set to True 
or False?
-Dan
Just dropping a note here: I noticed extremely jittery movement with the spacemouse on RhinoWIP but not in Rhino8 … however I just went in and disabled UseLegacy in RhinoWIP and it is working smoothly again!
This is interesting because I guess UseLegacy is currently default on? I for sure didn’t know about this setting until today.
It is interesting to hear this. Yes, at the moment, it defaults to UseLegacy = enabled, but probably not for long. We recently added this setting because users were seeing poor behavior (understandably so) with the recent state of the updated implementation and wanted a way to get the legacy behavior back. As our collective work on the updated version progresses, we hope users will opt to use the newer version because it ought to provide better support for a wider variety modern of 3DConnexion devices and be more fully-featured.
Thank you Dan for your reply.
However changing UseLegacy To False Had No Effect even after exiting Rhino.
What els can I try?
Hi Udo-
Well that’s confounding. Can you please attach your 3DConnexion device, start up the RhinoWIP, run the SystemInfo command and attach that here?
-Dan
Space mouse still dose not work properly in V9. System test results .
Spase Mouse test info.txt (13.2 KB)
Sorry for the slow uptake. Thanks for providing the SystemInfo. I can see from that info that the WIP version of the plugin is still loading:
Rhino plugins that do not ship with Rhino
/Applications/RhinoWIP.app/Contents/PlugIns/3DxRhino.rhp "3DxRhino.9" 9.0.25329.1002
and, upon futher testing, it looks like the system for switching between legacy and the newer version is broken as well. You likely have RhinoWIP > Advanced > Rhino.Options.SpaceBall.UseLegacy set to true …and yet it’s still trying to load the newer version. That’s a bug. (I think this is because the plugin loading cache is overriding our plugin load order.)
As a temporary workaround, you should be able to get back to the legacy behavior if you run the Reset command (provided you’re willing to reset the WIP to factory defaults). After doing that, restart Rhino. Check in Advanced settings to make sure UseLegacy is still true. Now, if you run SystemInfo that plugin should NOT be loading.
Regardless, this is something we need to fix up as soon as we can so you can easily switch between the Legacy integration and the newer WIP version.