3D connexion spacemouse – Remote forwarding from Mac to Windows not working

Forums / NoMachine for Windows / 3D connexion spacemouse – Remote forwarding from Mac to Windows not working

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #36000
    CadderK
    Participant

    Hey all,

    Ever since the Big Sur update, I’ve not been able to use my 3Dconnexion Spacemouse Pro through NoMachine.

    I’m using a Mac running Big Sur 11.4 and connecting remotely to a Windows machine running Windows 10 Pro.  I’ve updated NoMachine on both machines and restarted both.  The Spacemouse is available under local devices but it always fails to connect remotely (little red exclamation point pops up next to the connection instead of the green dot).  I’ve checked to make sure that the system extensions on the Mac side are allowed according to this page but still no luck.

    I’m running 3D connexion 3DxWare 10 (10.7.4.3350) on the Windows machine and 10.7.0.3386 on the Mac if that’s relevant, and NoMachine version 7.7.4 both computers.

    I can use the mouse on my Mac without issues, but I need to connect to a machine running Solidworks and running that locally is not viable.  It’s not preventing me from getting work done but is slowing me down significantly as I’ve come to rely on the 3d mouse for navigating 3d models.

    I’m not a super computer-savvy person so any tips would be very helpful here.  Thanks a ton in advance!

    #36027
    Giorgi-G.
    Contributor

    Hi,

    Can you please post a screenshot of the Devices -> Connect a USB device tab?

    Also if there is any chance, please try to forward any other USB device (i.e. flash drive, or mouse), so we can find out if it’s a device-specific issue or not.

    #36126
    CadderK
    Participant

    For sure – here is a screenshot.  Both the 3d mouse and the USB receiver for my regular mouse show up as connected in the local devices but neither functions, so it might not be a spacemouse specific issue.

    #36429
    Giorgi-G.
    Contributor

    Hi,

    It seems to me that the issue is on the macOS side. Please take a look at this article to accept all required drivers’ permissions.

    To check if all required permissions are provided, you can run in terminal this command:

    sudo kextload /Library/Application\ Support/NoMachine/Extensions/nxusbvhci_11.0.kext/

    If there is empty output or error indicating that the driver is already loaded – permissions are set properly.

     

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.