Buttons mapping doesn't work after updating to Sequoia 15.1

[Stecu]

Hi, none of the buttons mapping work for any app after updating to Sequoia (image). Even after reinstalling driver from the website.

How do I fix this?

[neil2212]

While this post appears to be relative to the CadMouse, I have the same issue with the buttons on my SME. Any resolution that someone has identified?

[ngomes]

Have a look at this post. You may have a corrupted system extension installation. If the system extension is not installed correctly, button assigned to keyboard shortcuts will not work.

If the system extension is installed incorrectly, you will see a warning in the "3Dconnexion Home" application.

[zoomer]

Have a look at this post. You may have a corrupted system extension installation. If the system extension is not installed correctly, button assigned to keyboard shortcuts will not work.

If the system extension is installed incorrectly, you will see a warning in the "3Dconnexion Home" application.

Is this (1.3.6) a correct and current system extension ?

SCREENSHOT_2024-12-17_09.52.47.jpg (187.45 KiB) Viewed 28132 times

SCREENSHOT_2024-12-17_09.55.08.jpg (95.65 KiB) Viewed 28132 times

SCREENSHOT_2024-12-17_09.56.46.jpg (48.43 KiB) Viewed 28132 times

[zoomer]

BTW,
where can I find a list where I can check if I have latest Firmware ?

original Space Navigator FW 3.18
CADMouse USB FW 1.06
Enterprise FW 4.42

if these are old - would they update when I attach them to a PC ?
(and if - only while updating the Driver ?)

[zoomer]

Sorry,
not 3D Helper ....
this is my DEXT : Version 1.3.516

SCREENSHOT_2024-12-17_10.08.19.jpg (177.98 KiB) Viewed 28129 times

[zoomer]

And yes, I also suffer from dysfunctional Button Mappings ....

But my 3D Connexion DEXT is activated.

Finally, as when I installed the driver again/over, after it did no more work after I upgraded to macOS 15.2,
it threw an error messages while asking for permissions while installing.
After some reboot cycles + second driver installation I was able to activate the DEXT in macOS Settings manually.

SCREENSHOT_2024-12-17_10.15.45.jpg (60.37 KiB) Viewed 28128 times

[zoomer]

BTW,
why is 3DConnexionHelper.app .... an "Object from unknown Developer" ?

SCREENSHOT_2024-12-17_10.21.45.jpg (51.23 KiB) Viewed 28127 times

[ngomes]

All looks good. The build number ("516" in your case) of the system extension matches the installed version of 3DxWare 10.

That "unknown" is remark is a concern. All our software does through Apple's notarization process. 3Dconnexion has the required developer credentials as issued by Apple and they are valid.

[zoomer]

Thank you very much @ngomes.

I do not see problems with my 3DConnexion driver now (beside in Blender) but it is good to know that do not have any corrupt or old DEXTs and such things .....

That "unknown" is remark is a concern. All our software does through Apple's notarization process. 3Dconnexion has the required developer credentials as issued by Apple and they are valid.

I am not sure but I also think I see that for the first time and also expected that 3DConnexion has developer credentials. I think that was the problem when I first (re-)installed the driver and Apple rejected my security confirmation.
(But I also read of other App's Installation problems, as Sequoia sabotaged Installer Files by deleting parts inside Zip Archives)

[ngomes]

I do not see problems with my 3DConnexion driver now (beside in Blender) but it is good to know that do not have any corrupt or old DEXTs and such things .....

Well, I'm not sure if there is a problem or otherwise. That "unknown developer" issue is definitely a concern (we we don't see it on our systems). We're discussing this internally.

For Blender, perhaps you're looking at an issue that we are trying to resolve in the application (see here). It will require an updated driver to fully fix it. GitHub user "kgalik" is one of our SW Engineering team members.

[zoomer]

Thanks @ngomes,

Meanwhile I also noticed that it is (at least also) a Blender thing. I notice that a few Enterprise buttons do something in Blender 4.2, opposed to 4.3 or 4.4. Nothing useful but they do something in 4.2. (looks like the 1-12 buttons aren't recognized so some other buttons default assignments shifted to them or flew in).

This link gave some insight.
Did not fully understand if Blender Enterprise Setup was finally meant to be controlled from Driver or from Blender but I will see. Looks like a driver update is already in the works and could be released in the not too far future.

[liyanage]

Have a look at this post. You may have a corrupted system extension installation. If the system extension is not installed correctly, button assigned to keyboard shortcuts will not work.

If the system extension is installed incorrectly, you will see a warning in the "3Dconnexion Home" application.

Thanks a lot for this pointer, it solved my problem that I came here to research.

I just got a new SpaceMouse Enterprise as an upgrade from my SpaceMouse Wireless. When I switched from the old to the new SpaceMouse, the puck was working in Fusion 360 but the buttons weren't and I was confused.

Based on the referenced thread I checked the 3Dconnexion Home app and indeed it showed that the system extension was not active. I was completely unaware of this problem because I never use this app. I only ever use the 3Dconnexion pane in System Settings, and I really think that this extension check should be performed there too and the warning should show up there.

Oddly, when I then went to System Settings > General > Login Items & Extensions > Driver Extensions, the 3DconnexionHelper.app entry was properly enabled. So there is a mismatch between what System Setting says and what 3dconnexion Home sees, which is very confusing.

I then tried to toggle the extension off and back on, but that led to an error message about an invalid state when re-enabling. I then rebooted the system, and that finally made the system extension load in a way that showed it enabled both in System Settings as well as in 3dconnexion Home. At this point, the buttons started working as expected in Fusion 360 as well.