Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Crash report #1733  -  Reshade opengl32.dll causes fatal error on launch
Posted Oct 31, 2023 - updated Nov 24, 2023   Shortlink: http://arx.vg/1733
action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Upstream" and resolution "Not determined".
Issue details
  • Type of issue
    Crash report
  • Status
     
    Upstream
  • Assigned to
    Not assigned to anyone
  • 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
    Not determined
  • 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 Not determined
Issue description
When installing reshade on arx.exe (x64), the game fails to launch and gives fatal error.

Here is crash report:

Unhandled exception

Exception code: ACCESS_VIOLATION

 Instruction address: 0x7fff0dd7c6d5
 Memory accessed: 0x238
 Stack pointer: 0x1aac6ff0a0


Callstack:
 atio6axx.dll!DrvSetCallbackProcs()
 atio6axx.dll!DrvSetCallbackProcs()
 atio6axx.dll!DrvSetCallbackProcs()
 atio6axx.dll!DrvSetCallbackProcs()
 atio6axx.dll!DllMain()
 atio6axx.dll!DllMain()
 atio6axx.dll!DllMain()
 atio6axx.dll!DllMain()
 atio6axx.dll!DllMain()
 atio6axx.dll!DllMain()
 atio6axx.dll!DllMain()
 atio6axx.dll!eglGetProcAddress()
 KERNEL32.DLL!BaseThreadInitThunk()
 ntdll.dll!RtlUserThreadStart()


Steps to reproduce this issue
Nothing entered.

#1
icon_reply.pngReply
Comment posted by
 Daniel Scharrer
Nov 24, 22:12
We can't support third-party injectors, please take issues you experience when using them up with the developers of those injectors.

The issue was updated with the following change(s):
  • The status has been updated, from New to Upstream.
  • This issue has been closed