Windowed Diablo 3.
No effect :S
https://i.imgur.com/25PSJ1R.jpg
I will try to reinstall .net 4.6
Yes
Yes, but need to restart MapHack sometimes
Yes, but need to restart D3 sometimes
No, says it's attached but nothing is visible in game
No, stuck on waiting for process
Windowed Diablo 3.
No effect :S
https://i.imgur.com/25PSJ1R.jpg
I will try to reinstall .net 4.6
I have 4.6.2, no effect, still does not work.
The procedure is:
Launch Diablo 3 64bit in window mode.
Launch your mod which shows green state.
No clue then, sorry
I'll add error tracing to next version (no ETA). It could be a rendering issue, but it could also be that a memory read constantly fails (DebugView would spam messages if that's the case, but they do not contain enough info for me to fix).
Hi,
i tried it on Win8.1 64bit i have the same issue like jack3dm.
%windir%\system32\D3DCompiler_47.dll
D3DCompiler_43.dll 2.526.056 26.05.2010 12:41 -a--
Looks old :/
Can i use the win7 update, if needed?
Last edited by enigma32; 07-01-2017 at 03:25 PM.
Thanks to you I can play this game again. Where can I donate?
Glad to hear
I've added a donate button to the github readme for you!
this tool is so amazing, all i have to say... I use it daily when i play, and it truly makes the game more fun. Thank you so much Enigma32... I will donate when i can buddy. Thanks!
enigma32 Thanks for the free software, good luck!
Okay guys here is my answer to those folks who didn't get to make it work properly, like me before.
So you need .net framework version 4.6.0 installed, no more, no less, just 4.6.0
I had different versions of .net and enigmas hack was not working, only on 4.6.0
How to: Determine which .NET Framework versions are installed | Microsoft Docs
Here you go folks.
waiting for a d3 process..
how to fix this?:S
My best guess is that it has something to do with DPI, perhaps you have a 4K screen. I'll do some tests at some point...
Really weird, but glad it worked out for you I suspect it might've executed some repair operation.
Start D3? The name of the process is "Diablo III.exe" or "Diablo III64.exe" right? Does D3 run as a different user perhaps, so the program can't find the process?