I have been able to get the service running on my workstation, the client sees the server and the USB device shows up but it seems to be shared only as a mouse. So, on the workstation the spacemouse only works to zoom in and out. I do have the 3DConnexion driver installed on the server machine, but it doesn't see a device so I can't change settings for instance to enable any of the other axes. Any idea what the issue might be?
Thanks
Gary
.
You (only) need the 3dconnexion driver installed on the client machine (where you want to remotely access the mouse, where the virtualhere client runs)
Thanks, I only had the…
Thanks, I only had the driver there from when I was using that machine at my desk. Do I need to uninstall it? I have tried everything I can think of, for instance in settings on the client machine I have enabled every axis on the spacemouse and I have done this for the remote desktop app. Still, on the server machine it is only getting the zoom in/out command no matter how I move the puck.
.
I think its something related to RDP probably. A quick check of google AI (https://www.google.com.au/search?q=using+spacemouse+rdp+conflict) mentions trying virtualhere first :) but before that it also suggests
If movement works but buttons do not, you need to fix how the RDP session handles inputs.
%appdata%\3Dconnexion\3DxWare\cfg\and openGlobal.xml(or your application-specific config file). Add<KMJMechanism>SendInput</KMJMechanism>within the<Settings>region.Well, this did something,…
Well, this did something, because now there is no lag on the zoom and the parts move from tiny to massive in an instant. But, I still only have zoom and not the full 3D functionality. I'll keep searching for a solution because I really want this to work.