[FIXED] 3DConnexion Space Mouse S3DV5

[asoderberg]

S3D V5 does not respond to my 3DConnexion Space Mouse. I have added S3D V5 to the space mouse control panel. What must be set in S3D to recognize the space mouse. If the 3DConnexion needs to be configured to specific S3D mappings, where can those be found. My space mouse works with all my other 3D apps (Fusion 360, FreeCAD, etc.).

[S3D-Jason]

We have a bunch of 3Dconnexion space mice here, and usually the only step required was to install the 3Dconnexion drivers. If the mouse is already working in Fusion 360 and FreeCAD then I'm guessing you already did that.

Can you clarify what exact operating system you are using?

[mikeysmailbox]

Hi Jason

I am having the same issue with the Space Mouse. It works every where except in V5.

Running on MacOS 13.0.1.

I added the S3DV5 to the 3Dconnexion in the System Settings like the others (Fusion360,etc.)

Not working.

Thanks

Mike

[dibor]

Have same MacOS and same problem.
Space mouse works in the Fusion 360 but do not in the S3DV5

[asoderberg]

I am running MacOS 13.1 (GM) Ventura on a MacBook Pro (2021 with M1 CPU).

[asoderberg]

@S3D-Jason
Can you export a 3DConnexion configuration file (3Dconnexion Config.3dc) for S3C from a working setup with S3D and share that here so we can test to see if that is it?
See attached screen shot for reference.

screen shot

[zemlin]

I have the SpacePilot Pro - been working for me in V5.

[dibor]

I have the SpacePilot Pro - been working for me in V5.

Hello.
What your MacOS version and Mac model?

[zemlin]

Hello.
What your MacOS version and Mac model?

Didn't realize this was a mac-specific thread. Lenovo P16, Windows 11. I need a computer that works.

[S3D-Jason]

@S3D-Jason
Can you export a 3DConnexion configuration file (3Dconnexion Config.3dc) for S3C from a working setup with S3D and share that here so we can test to see if that is it?

It doesn't require a special config file. We've tested this on a completely fresh Mac with nothing installed but S3D and the 3Dconnexion drivers and it worked fine. I'm beginning to think the 3Dconnexion driver may have a bug in certain versions of MacOS based on some of the responses here.