TPB... cover your ears, you already heard this in a PM. 
So far, it has not gotten to work with any MAME products. The products has very strict drivers and work only with specific applications supported. I would have to decompile the drivers in order to have any hope of making it work. However, am no programmer, so basically I wasted my money.
As I mentioned above, all we need to do is hack mame's code a little. In fact, 3dconnexion has samples that use directX DirectInput, and
they explicitly say the drivers are ignored.
To quote one of their sample's text file:
Since the 3DxWare driver is not used for DI [DirectInput] applications, you don't get the
advantages the driver provides. In particular, you get raw data from the device.
A) The data is completely linear, the driver makes it slightly non-linear.
B) The driver implements a small region around the rest position that prevents
the application from getting data while the device cap bounces back and forth,
or emits a small vector if it isn't centered accurately.
If you want these effects, you must implement them yourself.
Point B is already implemented with mame's deadzone, and the first, well, not sure how much that will effect mame.
I tried looking for the code I've already played with, but couldn't find it. I'll see if I can patch something up this weekend.
It does work great with Google Earth though. But I may still return it as I can't find any other use for it. I was hoping it would work with my editing software.
Well, if it doesn't work with your software (or might be better phrased "if your software doesn't work with the hardware" depending on POV), and you don't want to hack mame, yeah, google earth and (if you use it) google sketchup aren't much reason to keep it. I've keep mine, though. Up 2 you.