![]() ![]() Switches -w, -direct -txt, & -3dfx don't change the issue whatsoever for the moment. Thanks.Įdit: Video is set to Direct3D since DirectDraw & Glide (through the nGlide wrapper) don't work with MultiRes. ![]() I wouldn't mind getting it work, since when it did work, it looked great.ĭoes anyone have any idea why it might be occuring? All mods are the newest versions (D2MultiRes is stuck at v1.02) & Diablo 2 is set to 1.12a for MultiRes to work. W/O MultiRes, the game loads fine but no widescreen resolution settings. I was quite sure I was about to enjoy a long gaming session when all of them initially worked but now I'm unsure. I elminated Plug Y & it still had issues. I initially had it working at 1920x1080 but after a few launches it went to crap. When I launch Diablo 2 w/ Median XL & Plug Y, it starts up fine but when I add in MultiRes, it crashes with an "Unhandled Exception: access_violation (c000005)" error after loading a saved game. I have tested the game thoroughly with & without the MultiRes patch. Error: UNHANDLED EXCEPTION ACCESS VIOLATION (cx0000005) on booting game FIX: Check DEP is disabled Control Panel>System>Advanced System Settings>Performance>Settings>Data Execution Prevention Check the turn on DEP for essential windows programs and services only setting Then RESTART YOUR PC. It was solved using a combination of this fix (be sure to reboot each time) and changing the video mode in the MXL Launcher settings to 3DFX Glide.I currently have Diablo 2 with Median XL, Plug Y, & MultiRes mods installed. I have reinstalled both the base game and Median XL 4 times, 3 to the same location - once to another location just to rule that out.Įdit for anyone else who stumbles across this thread. I have tried running the game and Median XL in compatibility mode. I have tried running the game, and Median XL as an administrator. Error: Command failed: "C:\Games\Diablo II\Game.exe"Īt ChildProcess.exithandler (child_process.js:282:12)Īt maybeClose (internal/child_process.js:921:16)Īt Process.ChildProcess._handle.onexit (internal/child_process.js:211:5) I googled this error assuming that it would be an easy fix, and was informed that this is a generic Diablo II error and I won't know what's actually happening until I look into the crash log. Upon clicking 'play' I get an error 'UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005). I installed Median XL to the same location. The base game, and LoD run without issue until Median XL has been installed. ![]() I just installed a fresh copy of Diablo II and LoD ver 1.14b to C:/Games/Diablo II. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |