I've been using the VRPN Wrapper with the 3DConnexion Navigator on OSX - and it works great.
But I had to make a few minor changes to the VRPNWrapper Unity3D Code:
1) In VRPN Analog, I had to add vrpn_3DConnexion_Navigator to the enum for Analog Type
2) I am just using the basic vrpn_server app, as compiled directly from the VRPN webpage - you need a vrpn.cfg file with the line 'vrpn_3DConnexion_Navigator device0' in it and away it goes (I did have to put the vrpn_server and vrpn.cfg files in my home directory root (/users/<you name>) due to a little quirk with OSX in the difference between running a file with double-click, in which case the home directory is your home directory, and running a program from the shell, in which case the home directory is the directory the executable file is in). Of course, you could make your own dedicated navigator server and not have to read the vrpn.cfg file and thus avoid that problem.
3) When building this in Unity3D to an OSX runtime, I had to shift the vrpnwrapper bundle into the plugins folder (rather than the plugins/vrpnwrapper folder), otherwise it didn't come over into the App. I also had to change the code where it refers to the plugin from vrpnwrapper/vrpnwrapper to just vrpnwrapper…
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been using the VRPN Wrapper with the 3DConnexion Navigator on OSX - and it works great.
But I had to make a few minor changes to the VRPNWrapper Unity3D Code:
1) In VRPN Analog, I had to add vrpn_3DConnexion_Navigator to the enum for Analog Type
2) I am just using the basic vrpn_server app, as compiled directly from the VRPN webpage - you need a vrpn.cfg file with the line 'vrpn_3DConnexion_Navigator device0' in it and away it goes (I did have to put the vrpn_server and vrpn.cfg files in my home directory root (/users/<you name>) due to a little quirk with OSX in the difference between running a file with double-click, in which case the home directory is your home directory, and running a program from the shell, in which case the home directory is the directory the executable file is in). Of course, you could make your own dedicated navigator server and not have to read the vrpn.cfg file and thus avoid that problem.
3) When building this in Unity3D to an OSX runtime, I had to shift the vrpnwrapper bundle into the plugins folder (rather than the plugins/vrpnwrapper folder), otherwise it didn't come over into the App. I also had to change the code where it refers to the plugin from vrpnwrapper/vrpnwrapper to just vrpnwrapper…