Can't get driver to work on macos

[vpark915]

Followed the setup procedure to a T but my editor isn't detecting anything from the spacemouse. Tried on editor 2023.2.16f1 and 6000.0.32f1 on apple silicon. Using the bluetooth edition of the spacemouse. My mouse does work in Blender. I'm on the newest MacOS with up to date drivers for the spacemouse

[PatHightree]

I had a look and indeed, instead of data, I saw a HID error message on MacOS.
The driver relies on Unity's Input System to provide that data and apparently the system's OS cross-compatibility isn't what I had hoped it would be.
I recently had a look into supporting Linux and found a similar lack of HID support.
The Hidrogen package got me data, but performance was underwhelming.
Maybe that's needed for MacOS too.
Unfortunately my out of date Mac Mini choked on an update and doesn't boot anymore, so work on MacOS is blocked for now.

[PatHightree]

You can test for yourself.
Might be that just adding the the HIDrogen package to the project fixes the problem.

[chargedneuron]

I had a look and indeed, instead of data, I saw a HID error message on MacOS. The driver relies on Unity's Input System to provide that data and apparently the system's OS cross-compatibility isn't what I had hoped it would be. I recently had a look into supporting Linux and found a similar lack of HID support. The Hidrogen package got me data, but performance was underwhelming. Maybe that's needed for MacOS too. Unfortunately my out of date Mac Mini choked on an update and doesn't boot anymore, so work on MacOS is blocked for now.

Pat, you can recover your Mac Mini using the recovery or internet recovery modes. Command (⌘)-R: Start up from the built-in macOS Recovery system. Or use Option-Command-R or Shift-Option-Command-R to start up from macOS Recovery over the internet. https://support.apple.com/en-us/102603 - Let me know if you need more help with your Mac.

[PatHightree]

This is a 2011 mac mini that was workable through OpenCore patcher.
I can't get it into normal recovery anymore and internet recovery leads to a Lion reinstall screen. Bootable usb stick seems to be the only way forward.

[PatHightree]

Ok, I've finally got my mini mac going again.
My wired spacemouse pro works fine in Unity on MacOS (the mouse cursor is moving with it, but that's another issue #65).
@vpark915, I think your problem is more likely caused by the bluetooth connection.
Have you tried using it wired ?

[sordidlist]

I'm having a similar issue on Apple Silicon M4 Max, Unity 6000.0.33f1, wireless spacemouse.

I've tried connecting wired and wireless, no luck. I'll be away from my desk for a few days so I don't have many more useful details at the moment, unfortunately. I do remember also having some trouble with the 3DConnexion test viewer app; it would respond, but erratically. Unity wouldn't respond at all. I'll post more details when I get back

[PatHightree]

Wireless mice are just way more complex, the 3dconnexion driver used to abstract that complexity away from me.
Moving the driver to the input system revealed how much complexity :(
Also, I don't have any wireless mice, so making progress is challenging to say the least...

[sordidlist]

I have used your driver for several years and can't tell you how helpful it's been. My wired mouse eventually got so old the wire broke off, so I "upgraded", haha. I heard that the implementation was changed and that it was harder to support now... quite lame of them.

[AntoineFachez]

HI Pat,
Mac Mini Ventura with a SpaceNav Firmware 4.04, 3dxWare 10.8.7 here. My Untiy 6000.2.0a6 project is - except for the single "Try to Sync Device" call and the entry in the events list - falling to receive inputs too. Blender works perfect, so, its not the hardware.
Any ideas?
Would love to use it in Unity too and buy you a pint of 🍻 beer.
Cheers, Antoine

[PatHightree]

I suspect that it has to do with 3dxWare being installed. Without it, the mouse pointer is moved by SN input on MacOS, this is why you have to set up accessibility stuff during the 3dxWare installation procedure. They are intercepting the device data and maybe their fix for the mouse pointer issue stops the data from flowing to my driver.
Can you uninstall the 3dxWare and see if that makes a difference ?

[AntoineFachez]

Hey, thx for your immediate response ! Uninstalling worked for Unity, SpaceNavigator works in this case. But surly in Blender is only receiving scroll up & down. So, I guess I have to decide which app to use with SN or have two different machines running Blender and Unity…?

[PatHightree]

Thanks for confirming.
I specifically modified my driver to not use 3dconnexion's api, because they are soft-deprecating devices that work perfectly fine.
SpaceNav has been deprecated last september, so next software update it likely won't work with 3dconnexion's driver anymore.

I'm wondering if adding support for their api back in would be a good or bad idea.

Benefits:

• Ability to use SN with Unity and other applications
• Abstract away all device specific quirks and avoid the resulting bugs

Downsides:

• Another variant to complicate testing and debugging (besides platform, device type, wire(less), 3dconnexion driver installed y/n, driver version, unity version)
• Implementation work

Food for thought....

[AntoineFachez]

idk about the good or bad idea… I bought my SN in 2008 and it still works pretty good. That is awesome manufactoring. But maybe its time for an upgrade to SpaceMouse anyways.
Whats your future plan with the PlugIn for Unity?