At the moment, all these changes impact the RhinoWIP for Mac (hence the title of the topic). We will let you know when the Windows integration changes.
Please remind me of the exact device you are testing with @Akash
Thanks. I don’t have that device on me right now, but I do have access to it. I’ll see if I can reproduce what you’re reporting next week.
Hi @dan
The problem here is likely not related to that specific device!
I tested also with my little SpaceNavigator and it too does not work [it works fine with the legacy settings]
Yep, that’s the one I have and it’s working fine here. We need to figure out what we’re doing differently.
Can you please send me your SystemInfo when you have UseLegacy disabled?
Does it change anything if you switch the Application that the 3DConnexion device is set to?
When you do get it working, the tell-tale sign is the little target:
akashSysInfo29-01-26.txt (5.0 KB)
no
the Knob is not working at all. but all the buttons do! and [to my surprise] the legacy False setting in the WIP also disable the device in R8 …. ?
it is working in other applications. so it’s not a device issue.
Thanks for the SystemInfo. I can see from that info that the 3DxRhino.rhp isn’t loading at all. From Terminal, can you please run:
ls -al /Applications/RhinoWIP.app/Contents/PlugIns/ | grep 3Dx
and send the output? I just want to verify that the rhp is there at all.
This should have no impact whatsoever on Rhino 8. Rhino 8 doesn’t even have that setting.
drwxr-xr-x@ 3 akash admin 96 Sep 30 22:50 3DxRhino.rhp
I know it doesn’t have the setting for it [ I checked to make sure] but it still disable the Knob in R8 . they seemed to somehow share these settings in an unexposed way [at least here]
Good, we know the plugin is there. What I suspect is happening is that, since you previously tried this in previous WIPs, an old path to the plugin is cached somewhere. I suspect that it would work if you ran Reset and went back to factory-settings for Rhino 9.
I have no clue what could be going on in Rhino 8. The settings ought to be completely version-specific. There is no code in Rhino 8 that pays attention to the UseLegacy setting.
Just wanted to say the mouse is working flawlessly in recent WIP versions! With two minor exceptions:
-
I have a custom axis assignment different from the default. On a fresh start of RhinoWIP, to get that picked up, I need to open 3Dconnexion pref pane on macOS, select Rhino, click in the Axis list, and then the settings take effect. It’s as if selection in the pref pane triggers some kind of update or plist to be written out. Moving back to RhinoWIP after doing that, the axis assignment is correct. I can gather more details here if this is not a known issue.
-
I haven’t figured out any way to use the auxiliary buttons like F, R, T, “Fit”, etc. In the pref pane it lists one application command “Fit”, but using that has no effect. I can obviously have these buttons do hot keys or keyboard inputs or some such as a workaround, but it would be nice if either Rhino could treat these buttons as keyboard inputs (thus allowing the keyboard preferences to be used for assignment) or allow for aliases to be exported and to show up in the 3dconnexion pref pane.
I don’t see a particularly elegant solution here, but given that the new plugin pushes responsibility for button assignments into the 3dconnexion pref pane, that kinda implies to me that Rhino needs some way to expose button-assignable operations such that they’re picked up by the pref pane.
One other weird thing in case this trips anyone: if I assigned Button T to Command-F1 which is '_SetMaximizedViewport Top it popped a whole duplicate Rhino window onto my second display! Hitting the key again dismissed it. This had to be corrected by changing the macOS keyboard preference “Use F1, F2, etc. keys as standard function keys”
Hi Luke!
Thank you so much for testing the new integration and providing the feedback. I think I need to reach out to the 3Dconnexion developers and see what our options are with regard to these issues.
Stay tuned,
-Dan
Hi @dan
Do you possibly have any update on this subject…? Is there still an intention to get the 3DConnexion plug-in to work correctly before 9 is shipped? Or do we stay with Legacy until 3DConnexion fix the plugin on there’s side…?
I just tested it now [after a few months away from the forum] and it is still set with wrong axis and within a minute of testing the grid disappears into deep space with no way of find the way back to a visible zoom with the device. [having to use zoom extent to be back on Rhino’s earth]
thanks a lot
Hi Akash-
I had hoped to come to this thread and others with some good news this week but there have been a couple regressions that prevented it. This is still getting attention.
As always, you’ll be free to stay with the legacy for as long as you like. That said, when we have something better to test - and likely better to report to 3Dconnexion (because some of the change might be on their end - I will appreciate your help.
-Dan