Could it be that latest 3DConnexion Driver for Mac is completely broken after 15.2 update ?
Cad Mouse and original Space Navigator worked well for a few minutes before the macOS update.
(Well, as far as they do on Mac ...)
I mean, after macOS update, it did things like left click (!) is not working, even worse, in this case it prevents left click working for my Logitech MX for Mac - until I unplug my CADMouse. Or Scroll Wheel was dysfunctional. Blender assignments did no more work.
So I reinstalled the driver and some security questions allowed by password won't succeed. Same result after a few reboots.
After unplugging for an hour I tried again, Scroll Wheel (more or less) and LMB works again, but now MMB/Button3 is dysfunctional ....
Am I the only one ?
macOS 15.2 update - 3DConnexion driver broken .....
Moderator: Moderators
Re: macOS 15.2 update - 3DConnexion driver broken .....
BTW, Space Navigator is completely dead now ....
Re: macOS 15.2 update - 3DConnexion driver broken .....
You may want to get in touch with our Technical Support Team. Please visit https://3dconnexion.com/support/
Re: macOS 15.2 update - 3DConnexion driver broken .....
Tried again.
- Installed 3DCon driver over another time
- restarted
- immediately switched off M1 Mini completely
- rebooted
- went to macOS settings > General > Startup Items
This time I was able to activate 3DConnexionHelper.app (Object from unknown Developer)
without error warnings.
So the driver works again,
with original Space Navigator, CADMouse and Enterprise.
- Installed 3DCon driver over another time
- restarted
- immediately switched off M1 Mini completely
- rebooted
- went to macOS settings > General > Startup Items
This time I was able to activate 3DConnexionHelper.app (Object from unknown Developer)
without error warnings.
So the driver works again,
with original Space Navigator, CADMouse and Enterprise.
Re: macOS 15.2 update - 3DConnexion driver broken .....
For the love of Steve Jobs, can't somebody at your company post in official solution to this problem. I see many reports of these driver issues since Sonoma 14.4 and crickets when it comes to a solution. If you're not going to post solutions to this Mac problem, perhaps you should just stop developing drivers for Mac and spare us the headaches.
