Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report #269  -  not calibrated tablet-input
Posted May 29, 2012 - updated Jul 05, 2013   Shortlink: http://arx.vg/269
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Fixed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • Status
     
    		 Fixed
  • Assigned to
    Not assigned to anyone
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    Guest user
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Not determined
  • Resolution
    RESOLVED
  • Priority
    Not determined
  • Reproducability
    Not determined
  • Severity
    Not determined
  • Targetted for
    icon_milestones.png Not determined
  • OS
    icon_customdatatype.png Not determined
  • Architecture
    icon_customdatatype.png Not determined
  • Fixed in
    icon_customdatatype.png Arx Libertatis 1.0.2
Issue description
I thought it is nice to play this game on my convertible (toshiba m7). But in the menus and during gameplay the movement of my pen isn't syncron with my touchpanel / mouse. An example: if i move the pen one cm to the left the cursor moves 2 cm left. Moving the pen another cm leftwards let the cursor moves 3 cm. Also there is not a stable "fixpoint", where mouse and pen are the same. The location of the "fixpoint" moves in directions where the cursor reaches the borders. I don't know if this is a problem within sdl-input or in the game itself. But I didn't have this problem in other games.

Steps to reproduce this issue
Installed the game Played the game without changing any options


#2
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Jun 14, 14:12
We changed the input code so that absolute cursor positions always align with the positions provided by the underlying input system. This fix will be part of the next release (1.0.2).

If the problem remains, it's a bug in SDL and we cannot do anything about it - we may switch away from SDL at some point though.

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from Confirmed to Fixed.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.