So, this is kinda a niche bug, but I'd be totally psyched if it was fixed.

I decided to try a 6 axis mouse for fun, and amazingly it actually works (really nicely)... to a point.

One one direction of every axis, the value seems to overflow and move to the other side of the controls, so if I am pushing hard right on the stick, it thinks I am pushing left, but lightly right goes right: (Video shows X axis, but it does the same thing on any axis) https://youtu.be/SVEUtl8_t4I

While I don't exactly expect many people at all have even tried using one of these, it actually allows for full control of a ship with one hand, and the other can rest on the keyboard (It's even got two buttons for primary and alt fire!), so having it work properly would be awesome.

I'm not sure if there are any logs, or custom values I can show, but honestly I bet it's just that this mouse can report more values than the integer for position can handle, so it overflows and goes ~boom~. I may be wrong, but hey, worth mentioning the idea!

Huh, weird.

Yeah, that was pretty much my thoughts on it when it happened as well.

Have there been any updates on this bug? I just tested it and I'm still having the same issue.

Just a hunch, but have to tried to hit the "set center" button, for each axis when the "mouse" in in the center?

Without hardware to test in-house, I'm not sure how much progress we'll make on this. I'm not inclined to go on a 3DConnexion buying spree, either, we aren't really the most common use case. But, I'll reach out to 3DConnexion and see if they respond.

Ironically, we used to support the old (joystick-port-era) "Logitech Cyberman II", which was the original predecessor to the Space Navigator. Unfortunately, I think we were the only ones who did..

This has always been the thing I wanted to use for VO. As far as strafing, to me, this thing seems most intuitive. However, I tried like the dickens to get this to work in VO by ALL KINDS of methods. I failed, regretfully, and do not look back fondly on trying to make it work.

Please keep us posted on your journey cause I'd gladly buy another one if it was known to work.

I'm not sure how complex the code is for reading mouse values, but since it reads fine in one direction, and overflows on the other, I'm wondering if stetting the range available to a larger amount might work?

Really not sure how the code functions, my development experience is limited to threatening JavaScript with a sledgehammer.

Really, the mouse works "fine" as long as you don't press it too hard. Even fixing it so that it just couldn't overflow the position data anymore would make it workable well enough.

"mouse" is the wrong word, as it is not a mouse and does not send regular mouse inputs, as that would make using it along side a mouse errm awkward. It is a controller, before they go looking to change the wrong bit of code ;)

...Point taken; I forgot that it's technically a really intense joystick, as they are called 3d mice by the manufacturer.