You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
File spacenav_node.cpp contains FULL_SCALE definition (512) which is used for normalizing values for "joy" topic. Non-normalized values are available on "offset" topic and it seems that my device gives 350 as maximum instead of 512. If some devices really have 512 as the max. value I would propose to make FULL_SCALE configurable using parameter.
The text was updated successfully, but these errors were encountered:
Just recently, the changelog was also bumped which caused this change to finally make it into published .deb packages, dramatically changing spacenav_node message values.
To get the OLD behavior, one would need to set the "full_scale" parameter to "1" everywhere. To get PROPER new behavior, one would need to find your actual full_scale value and set that everywhere. Either way - MOST of the time, this will require an additional parameter.
Is "512" actually expected to work with some selection of the spacenav hardware? Would it not make sense to default to the old behavior (full_scale=1), or to a value that is common on more of the actual devices (full_scale=<???>) ?
File spacenav_node.cpp contains FULL_SCALE definition (512) which is used for normalizing values for "joy" topic. Non-normalized values are available on "offset" topic and it seems that my device gives 350 as maximum instead of 512. If some devices really have 512 as the max. value I would propose to make FULL_SCALE configurable using parameter.
The text was updated successfully, but these errors were encountered: