Strange rotation values of Space Navigator PE

[slompf]

Hallo,

I have implemented access to 3dx devices in my application. I'm testing it with a space navigator pe. This works fine so far, but Im wondering why the translation values are force dependent and the rotation values are not. The rotation values are in axis domination mode either -1, 0 or 1. Is this a limitation to space navigator pe or maybe a matter of preferences?


Regards,
Torsten Goroll

[ngomes]

Hi slompf,

The rotation values are in axis domination mode either -1, 0 or 1.

This is not the normal range of values.

Is this a limitation to space navigator pe or maybe a matter of preferences?

The PE hardware is not limited in any way compared to the SE. The difference (level of support) is explained here.

Using one of the demo applications (Start menu, Applications, 3Dconnexion, 3Dconnexion 3DxWare, demos), see if you can rotate the model and that you are able to change the rotation speed by applying more or less pressure to the sensor cap.

I'm assuming you've implemented support for 3DxInput (COM interface). If that is indeed the case, and all is well with the demo, then start your app and open the "3Dconnexion Control Panel". There's a tab that has sliders to control the speed of individual axes and check boxes to disable/enable them.

[slompf]

Thank you for your reply.

I have seen how it works. One has to work with the sensor.rotation.angle property, which seems to hold the overall angle and the rotation values are only the direction vector where this angle starts.


Thanks,
Torsten

[ngomes]

Hi slompf,

Good news. You are correct: the "rotation" vector is a unit-length direction vector. The vector components vary in the range [-1..+1] but the values are not discrete (integers) but scalars (floats).