Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Crash report #1518  -  [7543C7BB] arx.exe!ARX_DAMAGES_DealDamages() [Damage.cpp:730]
Posted Jan 08, 2021 - updated Jan 14, 2021   Shortlink: http://arx.vg/1518
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
icon_info.png This issue is a duplicate of issue #1388 - "[3AA19401] arx.exe!ARX_DAMAGES_DealDamages() [Damage.cpp:722]"
icon_info.png This issue has been closed with status "Not a bug" and resolution "DUPLICATE".
Issue details
  • Type of issue
    Crash report
  • Status
     
    Not a bug
  • Assigned to
    Not assigned to anyone
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
     CrashBot
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Not determined
  • Resolution
    DUPLICATE
  • Priority
    Not determined
  • Reproducability
    Not determined
  • Severity
    Not determined
  • Targetted for
    icon_milestones.png Not determined
  • OS
    icon_customdatatype.png Windows
  • Architecture
    icon_customdatatype.png amd64
  • Fixed in
    icon_customdatatype.png Not determined
Issue description
Assertion Failed at Damage.cpp:642: isallfinite(vect)

Unhandled exception

Exception code: BREAKPOINT

 Instruction address: 0x7ff76429d243
 Stack pointer: 0x767617e880


Callstack:
 arx.exe!0x7ff76429d243
 arx.exe!0x7ff764384026
 arx.exe!0x7ff764384f86
 arx.exe!0x7ff764386602
 arx.exe!0x7ff764386c3a
 arx.exe!0x7ff7642ae370
 arx.exe!0x7ff7642aedcc
 arx.exe!0x7ff7642ab1e9
 arx.exe!0x7ff764287bbb
 arx.exe!0x7ff764289141
 arx.exe!0x7ff7642858c2
 arx.exe!0x7ff76429a13e
 arx.exe!0x7ff76439418a
 arx.exe!0x7ff76450e05a
 KERNEL32.DLL!BaseThreadInitThunk()
 ntdll.dll!RtlUserThreadStart()
Symbols:
  0  arx.exe!ARX_DAMAGES_DealDamages(HandleType<EntityHandleTag,long,-1>,float,HandleType<EntityHandleTag,long,-1>,Flags<DamageTypeFlag>,glm::vec<3,float,0> *) [Damage.cpp : 730 + 0x3c]
  1  arx.exe!CheckAnythingInCylinder_Inner [Collisions.cpp : 527 + 0x0]
  2  arx.exe!CheckAnythingInCylinder(Cylinder const &,Entity *,long) [Collisions.cpp : 739 + 0x20]
  3  arx.exe!AttemptValidCylinderPos(Cylinder &,Entity *,Flags<CollisionFlag>) [Collisions.cpp : 1151 + 0x5]
  4  arx.exe!ARX_COLLISION_Move_Cylinder(IO_PHYSICS *,Entity *,float,Flags<CollisionFlag>) [Collisions.cpp : 1308 + 0x5]
  5  arx.exe!ManageNPCMovement_End [NPC.cpp : 2093 + 0x33]
  6  arx.exe!ManageNPCMovement [NPC.cpp : 2367 + 0x8]
  7  arx.exe!ARX_PHYSICS_Apply() [NPC.cpp : 992 + 0x0]
  8  arx.exe!ArxGame::updateLevel() [ArxGame.cpp : 1800 + 0x0]
  9  arx.exe!ArxGame::render() [ArxGame.cpp : 2045 + 0x0]
 10  arx.exe!ArxGame::doFrame() [ArxGame.cpp : 1269 + 0x0]
 11  arx.exe!utf8_main(int,char * * const) [Startup.cpp : 164 + 0xa5]
 12  arx.exe!WinMain [WindowsMainGUI.cpp : 48 + 0xe]
 13  arx.exe!__scrt_common_main_seh [exe_common.inl : 288 + 0x21]
Steps to reproduce this issue
I have found the final boss Akbaa, due him doing a lightning damage on me I started to retreating from him. Suddenly, a screen went white and then a demon appeared on my position (probably Akbaa casted a "Summon demon" spell). Which made me stuck inside the demon and the demon stuck in place, not attacking me (its AI was probably confused). Akbaa continued attacking me and then the game crashed.

#1
icon_reply.pngReply
Comment posted by
 CrashBot
Jan 08, 22:12
A file was uploaded. arx.logicon_open_new.png This comment was attached:

arxcrash-5492-2328717916
#3
icon_reply.pngReply
Comment posted by
 CrashBot
Jan 08, 22:12
A file was uploaded. cfg.iniicon_open_new.png This comment was attached:

arxcrash-5492-2328717916
#4
icon_reply.pngReply
Comment posted by
 CrashBot
Jan 08, 22:12
A file was uploaded. crash.dmpicon_open_new.png This comment was attached:

arxcrash-5492-2328717916
#5
icon_reply.pngReply
Comment posted by
 CrashBot
Jan 08, 22:12
A file was uploaded. crash.txticon_open_new.png This comment was attached:

arxcrash-5492-2328717916
#6
icon_reply.pngReply
Comment posted by
 Daniel Scharrer
Jan 14, 03:25
Looks like this happens sometimes but only rarely.

The issue was updated with the following change(s):
  • This issue's description has been changed
  • The status has been updated, from New to Not a bug.
  • This issue has been closed
  • The resolution has been updated, from Not determined to DUPLICATE.