Gecko94
commented
2 years ago setting noresmod=true in d2dx.cfg allows me to skip past that error message. The next test I copy the d2dx.cfg and Glide3x.dll into different D2SE MOD folders, and also test inside the D2SE\CORES\1.13c folder.
Typical Error Message I get from debuglog.txt is
19:56:31.851 PROGRAM: Diablo II D2SE Core 1.13c 19:56:31.851 TIME: 2022-02-03 19:56:31.851 19:56:31.851
19:56:31.851 ***** UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005) 19:56:31.851 Fault address: 734506AE 01:0000F6AE C:\Program Files\Diablo II\D2SE\CORES\1.13c\glide3x.dll 19:56:31.851 eax:000000ff ebx:04206548 ecx:00000000 edx:0018f92c esi:00ffffff 19:56:31.851 edi:00000100 ebp:0018fd30 esp:0018f918 eip:734506ae flg:00210246 19:56:31.851 cs:0023 ds:002b es:002b ss:002b fs:0053 gs:002b 19:56:31.851 --------------------------------------
d2dx_log.txt
Game version: 1.0.13.60 (supported) Apparent Windows version: 5.1 (build 2600). Actual Windows version: 0.0 (build 0).
D2SE.exe is set to run with XP_SP3 compatibility mode, because D2SE exits without any error when compatibility mode is disabled in Win8.1.
Hi,
Thank you for your work on this project, the improvements are amazing!
I am getting an error with a D2DX standalone installation in a D2SE Mod.
I removed SGD2FreeRes from the installation, and I'm still get the same error from D2DX. It looks like the error is coming from an older version of SlashGaming-Diablo-II-API included in D2DX. The D2SE string mismatch error was already fixed in SlashGaming-Diablo-II-API, some time ago.
This was the bug report from SlashGaming-Diablo-II-API, please update the library for D2DX to work with D2SE. https://github.com/mir-diablo-ii-tools/SlashGaming-Diablo-II-API/issues/280
Thanks!