axis_x snaps to 0 if nun_x is out of bounds

[GoogleCodeExporter]

This is an enhancement request. When nun_x is out of bounds, axis_x is set
to 0. The practical consequence of this is that there is a very fine line
between the maximum extent to which one may sway the wiimote left/right and
the point at which it oversteps the mark, at which point the turning comes
to a sudden halt. Perhaps this is more of a problem for those who live in
small living quarters and must sit relatively close to the sensor bar, such
as myself.

In any case, while the controls are already very good as they stand, I
believe that it would feel more natural and facilitate more enjoyable
gameplay if the last known value of nun_x was stored. Should the next
reading then be out of bounds (or unavailable) and if the last reading was
within a particular threshold of the maximum bound then the program could
set axis_x to be equal to the maximum bound (in whichever applicable
direction along the axis), rather than 0.

Assuming that there is nothing that prevents this scheme from being
feasible, it would allow the player to overstep the mark somewhat with the
wiimote without being 'punished' for it.

Original issue reported on code.google.com by kerfra...@gmail.com on 26 Sep 2008 at 3:24

[GoogleCodeExporter]

Will be fixed in next release

Original comment by lnux...@gmail.com on 26 Sep 2008 at 11:58

• Changed state: Accepted

[GoogleCodeExporter]

Thanks. I very much look forward to seeing the nature of its implementation in 
the
source :)

Original comment by kerfra...@gmail.com on 26 Sep 2008 at 12:02

[GoogleCodeExporter]

This appears to be fixed for awhile now. Closing the issue. If there are any 
more problems regarding this, please speak up.

Original comment by castleva...@yahoo.com on 29 Aug 2010 at 7:36

• Changed state: Fixed