Thread: SpaceNavigator huge price drop

that's exactly what i did. I also disabled every other plugin, so only the HID was active.

you're right on the money cherry bomb.

I'm getting a huge amount of data coming in when I barely touch the thing, but that's 'cos the stream is not being filtered.

I guess now I have to mess with that code to filter the data and make it a little more effective.

fantasticles... this is very exciting

looks like I'll have to learn lua to create a definition for this device.

In Girder, I can see that manipulating the device, the following is displayed:

00 00 00 00 00 00

pressing buttons 1 or 2, give definitive values, but things move way too fast to be able to determine how the different axis affect the numbers. I can already see though that moving one axis, sets one of those to FF, and others start playing.

I'll play some more and let you guys know soon.

I just ordered my SpaceNavigator and it should arrive in the next week or so.

I'll be more than happy to work with you on whatever LUA code and Girder files you may have created by then. Probably be able to turn these into window messages sent to RR, which would allow you to map those messages to commands depending on the skin.

I'm planning to use RR, though I'm sure the HID messages could be translated into something a little more generic in Girder for use with other front ends.

Originally Posted by sama

looks like I'll have to learn lua to create a definition for this device.

In Girder, I can see that manipulating the device, the following is displayed:

00 00 00 00 00 00

pressing buttons 1 or 2, give definitive values, but things move way too fast to be able to determine how the different axis affect the numbers. I can already see though that moving one axis, sets one of those to FF, and others start playing.

I'll play some more and let you guys know soon.

You'll want to use the "print" function of LUA to print the data string to the console, this should hopefully allow you to identify some sort of pattern. I suspect this device will spew TONS of input since it's analog in nearly every direction.

We might need to "dumb it down" a bit, and make it behave a bit more like a digital device. If I understand correctly, none of the motion directions have detents, it's just a fluid analog motion?

that's correct. It's like a hat on a stick, that returns to center with little resistance.

You can tilt the hat lef/right or up/down, you can pan or strafe the hat forward or sideways, you can twist, and you can pull/push. There are also two buttons.

dumbing it down is exactly what I was thinking. Perhaps translate the analogue to steps. For twisting for example, you want slow repeat rate when barely twistsed, and perhaps 3 levels of speed for that.

well, it is

it's just that so much data comes back, that if you map anything (except the two buttons, whcih work fine with anything you like), you'll get a billion events being fired!

just needs a little work, but it's not (EDIT: oops!) doable for sure.

I think we should probably start a new thread for this.