![]() ![]() Such as a joint storage - we mule so its ok. I think the devs have been pretty clear they want to keep things as close to d2 as possible unless they can justify the changes, as something players have found a loophole around, so requests of personal loot wont happen or 42x mob densityĪll changes devs have made have been QOL, and justifiable by player actions Switches -w, -direct -txt, & -3dfx don't change the issue whatsoever for the moment.A blanket statement of dont ask for changes, wont actually help you stop changes, surprisingly if you want to fight something you actually have to put effort inĭo you actually feel like you are influencing the devs with this post? ![]() 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. I currently have Diablo 2 with Median XL, Plug Y, & MultiRes mods installed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |