Closed icex2 closed 1 year ago
Thanks for the detailed report and using the template. That saved us requesting a lot of the fundamental info you already provided and speeds up the troubleshooting process.
Grab X3 data - I'm using KDX:J:A:A:2012050800, but I assume most versions will be affected.
BT5 requires stock/clean data and executables/dll files that are not htpec protected. Is that the re-release that is available in the "pig stall"?
The instruction at 0x004d69c0 referenced memory at 0x00000001
That might indicate that you are trying to run the game with the htpac'd or a corrupted executable/dll files.
This happens both with ddrhook2 and without.
That makes it sound even more likely that your data setup/integrity is not ok. The game should at least run/open a render window if you have a stock drive setup on your dragon with D:, E: and F: partitions (because that makes the game crash before even showing the render window if not present).
Can you check the points regarding htpec'd exec and potentially corrupted files?
Everything else is looking fine as far as I can tell so far.
In GitLab by @fartballs999 on Jul 5, 2022, 08:38
X3 J region is eapki. The only change potentially done if it were the sows version would be a coin strip or game data modifications, but it seems to be crashing before it even loads the main module. ddr-13.zip has the AVS 2.13.x launcher so it's not an issue with that.
Fault Module Name: libavs-win32.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4e7148eb
In GitLab by @fungah on Jul 6, 2022, 01:10
I think something was corrupted in the original data I downloaded - I re-downloaded it and am able to successfully launch X3. Sorry for the noise! And thanks for the prompt responses.
In GitLab by @fungah on Jul 2, 2022, 03:28
Summary
Attempting to launch DDR X3 using BT v5.42 results in a crash.
Expected behavior
DDR X3 is able to launch.
Current behavior
The game crashes instead.
Detailed Description
DDR X3 crashes launcher. This occurs both on real hardware (a Dragon in this case) and on my Windows 7 PC, both of which are able to run X-X2 and 2013-A20+ via BT without issues. So this is some sort of X3-specific bug. I've included logs for both environments below.
Steps to reproduce
ddr-13.zip
into thecontents
directory.gamestart-13.bat
.Possible solution
I saw there was an AVS version mismatch that caused https://dev.s-ul.net/djhackers/bemanitools/-/issues/83 - since X2 started working but X3 is still crashing, perhaps the version for X3 is still incorrect?
Context (Environment)
Bemanitools version(s) affected
Game(s) and version(s) affected
Log output
Here's the log from my Dragon (stock hardware, Windows XP) attempting to boot X3: log.txt
The crash on the Dragon says something to the effect of: "The instruction at 0x004d69c0 referenced memory at 0x00000001. The memory could not be read. Click OK to terminate the program."
The crash output from my Windows 7 box is here: win7log.txt
Configuration files
The issue can be seen with the default
gamestart-13.bat
script included in BT.APIs used
This happens both with ddrhook2 and without.
OS version
Windows XP / Windows 7 Ultimate
Hardware specs