3Dconnexion Forum

You're right, it is the battery packet. I have implemented simple filtering with a timer to ignore any suspicious jumps.
Is this the right approach you think?

Thank you
Jay

It basically looks like this: SpaceMouse comes to a standstill (centred position). Raw Values: Tx= 0 Ty= 0 Tz= 0 Rx= 0 Ry= 0 Rz= 0 Normalized: [0]=0.0000 [1]=0.0000 [2]=0.0000 [3]=0.0000 [4]=0.0000 [5]=0.0000 Three seconds later, the raw value on Tx axis spontaneously jumps to 62. Raw Values: Tx= 62...

Hi I'm facing the same issue as described above. I'm literally stuck and need to find a workaround. Basically, I used an "AI programmer" to write a SpaceMouse Bridge program. This Bridge will capture, normalise and store SpaceMouse axes values. The destination app then uses a custom plugin...