Arx Libertatis Bug Tracker
Please log in to bookmark issues
CLOSED  Feature request #653  -  Enhance rune draw detection: Taar vs. Movis
Posted Aug 20, 2014 - updated Dec 25, 2016   Shortlink:
icon_info.png This issue has been closed with status "Done" and resolution "RESOLVED".
Issue details
  • Type of issue
    Feature request
  • Status
  • 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
  • Priority
    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.2-dev
Issue description
Overall the gesture recognition could use a lot of improvement, however a relatively concrete (and annoying) issue is the confusing between the runes " movis" and " taar".

Given a three-segment rune whose first and last segments are horizontal lines, connected by a middle segment:

  1. (OK) middle segment has positive slope -> "movis"
  2. (OK) middle segment is vertical -> "taar"
  3. (NK) middle segment has negative slope -> "movis"

As it stands right now, the middle segment has to be near-perfectly vertical for the rune to be recognized as "taar". At the very least, negative slope should be recognized as an incorrect rune. Ideally, there would be a bit more leeway towards the negative side.

Comment posted by
 Daniel Scharrer
Aug 20, 15:11
I agree that the recognition for middle segment of Taar is a quite picky, but cannot reproduce getting Movis whith a \ slope in AL 1.1.2 or the current dev code - that would be a bug.

What OS and version of AL are you using?
Comment posted by
icon_reply.pngAug 21, 04:19, in reply to comment #1
Hmm, I can no longer reproduce this either - in fact, a very gentle slope of \ is now recognized as Taar. Strange.
Comment posted by
 Daniel Scharrer
Dec 25, 03:24
The new rune recognition algorithm introduced in commit 4e484eb solves this.

The issue was updated with the following change(s):
  • The custom field Fixed in has been updated, from Unknown to Arx Libertatis Git.
  • This issue has been closed
  • The status has been updated, from New to Done.
  • The resolution has been updated, from Not determined to RESOLVED.
  • This issue's progression has been updated to 100 percent completed.