Arx Libertatis Bug Tracker
Please log in to bookmark issues
CLOSED  Bug report #413  -  Jumping range
Posted Oct 25, 2012 - updated Jul 14, 2013   Shortlink:
icon_info.png This issue has been closed with status "Fixed" and resolution "RESOLVED".
Issue details
  • Type of issue
    Bug report
  • 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
  • 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.1
Issue description
Greetings. I have a question. In far 2002 year, when i play in arx fatalis i have no problems with jumping moment in 8th lvl, dwarven lava pit. but now, with arx libertatis mod i'm definetly can not jump over lava pit from last platform to th edge of the "earth". Is it possible, that libertatis mod have some jumping issues that provides shorter range of jumping? Sorry for my english, im not an englishman. OS: win7 x64 arch arx libertatis 1.03 cpu: i5; vga: gForce 550ti; 8gb ram

Steps to reproduce this issue
Nothing entered.

Comment posted by
 Daniel Scharrer
Oct 30, 20:31
I compared a new character in AF and AL with the same stats and jumps are indeed slightly shorter in AL - we'll need to fix that. However, jumping in arx is kind of weir anyway, so we should try to improve it and not emulate the AF behavior exactly.
Comment posted by
 Daniel Scharrer
Jun 30, 10:29
A file was uploaded. Save files for some hard jumpsicon_open_new.png
Comment posted by
 Daniel Scharrer
Jul 06, 16:19
A fix for this is available in the git sources and will be part of the upcoming 1.1 release.

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