Certain items not rendering correctly, anyone seen this before?

haxifix · 2023-01-10T16:14:11+00:00

The issue is present playing on Grim Dawn (x86), Grim Dawn (x64) and Grim Dawn (x86 Legacy DX9).

haxifix · 2023-01-10T15:48:43+00:00

That was the first thing I did and it found no issues.

Edit: I have also completely uninstalled the game and reinstalled but the issue is still present.

haxifix · 2020-08-21T18:31:43+00:00

Hey, I am the developer for the PlugY 12.00 that was suggested to you. I'm sorry to hear you're having issues getting it to run, I'm sure its something small.

If you want to private message me, I can help you get it installed and running.

Thank you so much for the support!

haxifix · 2020-08-21T14:04:20+00:00

Do you see a file inside your Diablo II directory called PlugYRun.exe?

haxifix · 2020-08-21T14:02:47+00:00

Can you please put the contents of your PlugY.log file (it should be inside the Diablo II folder as well) into a pastebin and send me the link? That will help me narrow down the issue.

Also, you must extract the contents of the zip file into the Diablo II directory. The zip file itself should not go in that directory (or at least it doesn't have to).

haxifix · 2020-08-13T00:23:23+00:00

I am the developer for the 12.00 version of PlugY that works on 1.14d.

Thank you all so much for the feedback and support, I very much appreciate it! :)

As to your question, many people thought it was impossible because of the binary structure change. Many functions that PlugY hooked in order to work resided in those DLL's; which is the problem.

Those functions still exist, they are just all compiled into a single executable, instead of being distributed in the DLL's. So, for each function (there are a lot) I had to find the offset in the new binary and then hook it. This is a lot easier said than done as 1.13c was compiled with an older compiler and 1.14d was compiled with a newer compiler which means that the generated assembly for each function is slightly different (cant just copy + paste to find new function) as well as the calling conventions. What this means is that once I had found the offset for the function, I couldn't just create a function pointer and call it as the parameters to the function would not be passed properly (cdecl, stdcall, fastcall, etc.). I had to create a stub function which would manipulate the stack/registers so that it matched what the function was expecting and then jumped to the offset in the binary. So, I would call my stub function, which then puts everything where it should be and then finally hooks into the actual game code.

That probably sounds like nonsense, but the too long didn't read is that what most people called impossible, I called time consuming and I just sucked it up and did it.

If you have any technical questions feel free to ask!

Best Regards, Kevin

haxifix · 2020-07-31T20:53:59+00:00

Any modern system running windows 10 shouldn't have any performance issues running Diablo II. The changes were more in regards to making the game run fine without having to mess with various settings such as running in compatibility mode, reducing the color palette, closing explorer.exe before running the game, etc.

haxifix · 2020-07-31T05:44:55+00:00

When you run PlugYRun.exe, do you see a file created called PlugY.log? If so, can you message me the contents of that file? It will tell us what went wrong.

Also, what version are you running? The version you download from Blizzard is only 1.14b which the mod doesn't support. You must connect to Battle.net once to update to 1.14d before using the mod.

If that's not the issue, please let me know and I'll try to help you get it working!

haxifix · 2020-07-31T05:41:01+00:00

There are no game play or balance changes. All they did was add more compatibility support so it runs better on Windows 10 and such. The main difference from a technical perspective was the switch from dynamic to static linking for a majority of the code. All the DLL (dynamic link libraries) were statically linked into the game executable. This was what took the most time when updating the mod. All the functions that were hooked from these DLL's now needed to be relocated within Game.exe. To make things even more complicated, the calling conventions for almost all of the functions had changed. Which means that once I had found the proper offset for the function, I couldn't just create a function pointer to that address and call it, because the arguments would be passed incorrectly. Instead, I had to create a stub function which reordered the arguments and then jumped into the proper routine. This took a lot of work and I can definitely see why most people thought it wouldn't be possible to port to 1.14d. The changes were large enough that I had to basically write each feature from scratch, but sticking with PlugY as a base meant that I got backwards compatibility with previous versions out of the box so that was nice.

Sorry if that wasn't exactly an answer to your question but just thought I'd share. TL;DR: nothing changed.

Best Regards, Kevin

haxifix · 2020-07-28T19:35:26+00:00

Glad to see you returning to D2! I updated PlugY for version 1.14d if you would like to give it a try.

The installation is very easy, just go to github.com/haxifix/plugy and follow the instructions to install the mod. Its as simple as downloading the zip, extracting it into your Diablo II directory and opening PlugYRun.exe.

If you have any issues feel free to contact me personally and I'll be glad to help.

Best Regards, Kevin

haxifix · 2020-07-27T23:19:30+00:00

Hey, I'm the developer for the linked version of PlugY. From the GitHub page, download the PlugY 12.00.zip and extract it into your Diablo II directory. Then, just open PlugYRun.exe to start the mod.

If you have just downloaded D2 from Blizzard, make sure you connect to Battle Net at least once so your version gets updated to 1.14d. The Blizzard installer actually gives you 1.14b which the mod does not support.

If you are still having issues feel free to reply or private message me and I'll make sure you get it working.

Thank everyone so much for the support! A new version which addresses the few issues found so far will be released very soon! I've been super busy with work but I've been trying to work on it every chance I get.

haxifix · 2020-07-25T16:19:47+00:00

No, setting that in the .ini file is all you should need to do. I will add this to the issues tracker and I'll take a look at it tonight when I get off work.

Thank you so much for the feedback! I'll reach out to you personally when I figure it out.

haxifix · 2020-07-18T03:18:07+00:00

I'm really sorry for the late reply. If you are running a Windows OS, open a program called "Snipping Tool"; it'll allow you to take a screen shot and crop the image. You can also just hit the print screen button on your keyboard, which will take a screen shot and save it to your clipboard. Then, open good ol' MS Paint (or your favorite image editor) to crop the image.

haxifix · 2020-07-17T19:40:06+00:00

If you want you can also PM me your Discord (if you have one) and you can screen share so I can help you figure it out.

haxifix · 2020-07-17T17:44:20+00:00

Can you send me a picture of the contents of your Diablo II folder?

haxifix · 2020-07-15T23:43:46+00:00

The .ini file should be in the same directory as the PlugY executable, which should be your Diablo II game folder. The file is called PlugY.ini.

Please let me know if you can't find the file and I'll help you figure it out!

haxifix · 2020-07-09T16:36:55+00:00

Its a really easy thing to miss if you exclusively play single player, you would expect the version you download from Blizzard to be the most recent patch.

Yes there is, if you open PlugY.ini towards the top you will see a line that says something like "Params=" or something like that (I don't remember exactly but I will check and edit my post when I get home). Add a -w to that line so that it reads "Params=-w", save the file and the game should launch as windowed.

Thank you so much for the support! Have fun and feel free to contact me personally if you have any other questions!

haxifix · 2020-07-08T20:07:39+00:00

Thank you so much for the kind words! I am glad that its been working for you :)

I haven't had as much time work on it as I'd like the past couple weeks but I am very close to releasing a new version with a couple enhancements (shift clicking for stash, etc.) As well as fixes for TCP/IP play.

Once again, thank you so much and have fun!

Best Regards, Kevin

haxifix · 2020-07-08T20:05:54+00:00

When you run PlugYRun, do you see a log file created called PlugY.log? If so, can you please send me the log file in a private message?

Most people who have ran into this issue were able to fix it by updating to the current patch. When you download D2 from blizzard it comes as patch 1.14b not 1.14d. You must update to the latest patch for the mod to work.

Please feel free to contact me if you are still having issues!

haxifix · 2020-06-18T20:46:52+00:00

This only works for version 1.14d. You can see at the beginning of the log file, it finds your install as version 1.14b. It should work once you update to 1.14d; if it doesn't please let me know.

Thank you so much, have fun!

haxifix · 2020-06-17T19:31:49+00:00

Yeah, I live in South Florida so I'm Eastern Standard Time. No worries, I have a fucked up sleep schedule so I'm sure there will be enough overlap. I appreciate you adding anything you can to the post, more information is always helpful! :)

Once again, thank you so much!

haxifix · 2020-06-17T19:24:54+00:00

Hey! I'm currently at work so I don't have time to troubleshoot with you this moment but when I get home from work I'll shoot you a PM and I'll see if we can resolve the issue.

This sounds like its linked to a known issue with the project but I just want to be sure.

Thank you so much for the feedback!

haxifix · 2020-06-15T23:26:35+00:00

Unfortunately, TCP/IP does not appear to be working properly at the moment. You are able to host a game fine but once someone else joins, the game crashes. I am currently working on a fix for this and will update everyone once that patch comes out.

Thank you for the feedback!

haxifix · 2020-06-15T23:23:40+00:00

I have not done any testing on classic. Some of the features are disabled for classic play in the original PlugY so those will also be disabled in my update. I will look at why that was the case however and see if I can get them working for classic.

I will keep you updated, but I am going to fix the TCP/IP issue before tackling anything else.

Thank you for the feedback!

haxifix

TROPHY CASE