6 DOF device [3Dconnexion space navigator as example]

[reptor]

Thanks for the patch.

In the name of preserving information, I submitted the patch to the sourceforge wgois patch tracker at:

http://sourceforge.net/tracker/index.php?func=detail&aid=1821175&group_id=149835&atid=775955



Just for reference, other threads here at the Wrecked Games OIS forum relating to this subject:

Support request for 3D navigation devices, examples: http://www.3dconnexion.com/
http://www.wreckedgames.com/forum/index.php/topic,920.0.html

3DxWare support
http://www.wreckedgames.com/forum/index.php/topic,800.0.html

[Absum]

hi Absum -  the patch (and the replacement driver) is for linux support only isn't it? Did you by any chance look at adding stuff for DI / win32?

Yeah the replacement driver is linux only and not very portable I guess. The patch is linux only simply cause I don't really have had any reason to port it to win32 and have no idea how to do it since everything I know about USB devices and such mainly apply to linux. But if I should guess I would say that the same technique could be used in a win32 implementation.

[Absum]

Has anyone modified my diff to work with current OIS version?

Edit:
No major modifications needed apparently but cleaned up the old one quite a bit and removed all led references:
http://sourceforge.net/tracker/index.php?func=detail&aid=1837755&group_id=149835&atid=775955

[xabila]

Nice i love the 3Dconnection space mouse.
Is it working and patching on the OIS 1.2?
And do we need to install the driver or not ?
Thanks

[xabila]

Ok i add you patch on my ois 1.2.
Thanks it works well.

[mr e]

Hi,

I wrote a quick patch to use my SpaceNavigator with OIS 1.2.0 on OS X.
It's rather basic but if it can be of any help to someone else here is the link to the patch tracker entry:

http://sourceforge.net/tracker/?func=detail&aid=2965660&group_id=149835&atid=775955

It will simply register a joystick with 6 axes and 2 buttons. Notice that if you give it a try with the console test application you probably won't see the axes moving as the values returned by the 3Dconnexion client will most likely be inside the little "dead zone" defined in the test app (depending on the speed settings).