Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report #1042  -  Entity vs. world colission regression with non-colliding polygons
Posted Jul 14, 2017 - updated Sep 14, 2017   Shortlink: http://arx.vg/1042
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
     Daniel Scharrer
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Gameplay
  • Resolution
    RESOLVED
  • Priority
    Regression
  • Reproducability
    Can't reproduce
  • 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 Not determined
Issue description
In the current development code falling entity touching world polygons that are non-colliding falls through not only those polygons but also all other surfaces. This is not the case in AL 1.1.2.
Steps to reproduce this issue
Nothing entered.

#3
icon_reply.pngReply
Comment posted by
 Daniel Scharrer
Jul 14, 01:05
A file was uploaded. Save file to reproduce the issueicon_open_new.png This comment was attached:

Try putting an item on the small table in front of the player in this save. In 1.1.2 it will fall through the table (which is expected, the player can also walk through the table). In git master the item will also fall through the floor.

This can also be reproduced with the small wall shelf to the left.
#6
icon_reply.pngReply
Comment posted by
 Daniel Scharrer
Sep 14, 16:55
The regression is fixed, but collisions could still be improved.

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