Loading...

Diablo II CPU Bug Fix

Discussion in 'General Discussions' started by Gix, Mar 12, 2017.

Thread Status:
Not open for further replies.
  1. Gix

    Gix Founder

    Joined:
    Jan 1, 2005
    Messages:
    54,504
    Likes Received:
    5,070
    Trophy Points:
    113

    The infinite loop cpu bug has been present for years but even at this point it hasn't been fixed by the game developers. The bug causes Diablo II to always use 100% of a single core on any computer, 50% for dual cores and about 25% for quad cores computer. Most players probably never noticed the glitch but our custom patch has been optimized a long time ago to reduce the effect of this bug and now we are able to offer you a permanent fix that shouldn't produce any drop in game performance. Shoutout to those who shared their knowledge.

    Open your Diablo II game folder and replace the old D2Client.dll file with the one you just downloaded.
    The original D2Client.dll is included inside of the archive in case you experience any issues and need to revert.

    Before
    After

    Note: Only supports Diablo II version 1.13c!
    Download: http://europebattle.net/d2/tools

    Decent computers won't really see a notable difference in-game but you can check your Task Manager, however those having low end spec computers with a single core or dual cores will be able to run multiple game instances and keep the CPU load under control. Feel free to share your experience in this thread and make a detailed post if you encounter any performance issues after applying the patch.
     
    Last edited: Mar 13, 2017
    Vacholindyr and Botlike like this.
  2. Amophor

    Amophor Active Member

    Joined:
    May 25, 2016
    Messages:
    32
    Likes Received:
    76
    Trophy Points:
    18
    Thank you. Made it right now.
     
  3. shadowhand

    shadowhand Active Member

    Joined:
    Feb 10, 2017
    Messages:
    99
    Likes Received:
    27
    Trophy Points:
    18
    It works, but definitely the game started to drop frames, making it unpleasant.

    Phenom II 965 Windows 10
     
  4. Gix

    Gix Founder

    Joined:
    Jan 1, 2005
    Messages:
    54,504
    Likes Received:
    5,070
    Trophy Points:
    113

    @shadowhand mind recording a video? I'm using Windows 10 Pro (x64) myself and have no issues at all.
    Like are you experiencing visually drop of frames thinking it will drop game performance or it's actually laggy? Below you can find some info taken from the official wiki page:
     
  5. dafranco

    dafranco Forum Legend

    Joined:
    May 21, 2015
    Messages:
    2,385
    Likes Received:
    1,035
    Trophy Points:
    113

    Thanks Gix, I'm with Win XP (Service Pack 3) and I found it useful, the CPU usage is lower and its awesome. No frames drops here.
     
  6. devilsreject

    devilsreject Forum Legend

    Joined:
    Jul 3, 2016
    Messages:
    231
    Likes Received:
    105
    Trophy Points:
    43

    Thanks!! Works awesome for me on Windows 7 Ultimate (64 bit) Service pack 1
     
  7. Stefansg

    Stefansg Supporter

    Joined:
    Jan 17, 2017
    Messages:
    1,727
    Likes Received:
    444
    Trophy Points:
    83

    I got a little qwestion : Does it makes any difference when you load 8ppl in a game ?
     
  8. Gix

    Gix Founder

    Joined:
    Jan 1, 2005
    Messages:
    54,504
    Likes Received:
    5,070
    Trophy Points:
    113

    In terms of what?
     
  9. Nickolaus

    Nickolaus Supporter

    Joined:
    Feb 10, 2017
    Messages:
    92
    Likes Received:
    15
    Trophy Points:
    8
    @Amophor Is this what you were talking about in my stream?
     
  10. Stefansg

    Stefansg Supporter

    Joined:
    Jan 17, 2017
    Messages:
    1,727
    Likes Received:
    444
    Trophy Points:
    83

    In terms of fps and gameplay
     
  11. Gix

    Gix Founder

    Joined:
    Jan 1, 2005
    Messages:
    54,504
    Likes Received:
    5,070
    Trophy Points:
    113

    No, @Stefansg. This fix only refers to the popular CPU bug that has an impact only for players using low-spec computers and wish to run multiple game instances without 100% CPU utilization. Those with decent computers won't tell the difference but why let Diablo II use 10%-25% cpu when it could use 1% or less instead. Neither the fix or the bug itself (without the fix) are not related to how many players are in a game at a time or someone's fps rates so it has no influence over that.
     
  12. TimmyDeezNuts

    TimmyDeezNuts Rezident Ninja Forum Legend

    Joined:
    Aug 6, 2016
    Messages:
    2,900
    Likes Received:
    1,473
    Trophy Points:
    113

    Thanks, running Win 8.1 with an Athlon II X3 455 3-core and this got it down to ~1%.
     
  13. inayat

    inayat Head Game Master Moderator

    Joined:
    Sep 12, 2016
    Messages:
    23,001
    Likes Received:
    5,956
    Trophy Points:
    113

    running on Windows 7 Home Premium SP1.

    With my usual stuff running and 2 games open, i have a stead 5-7% CPU usage.
    Also did some chaos runs with 2 games open.
    Didn't notice any performance issues, drop in framrates etc.
    Game is running smooth.
     
  14. Amophor

    Amophor Active Member

    Joined:
    May 25, 2016
    Messages:
    32
    Likes Received:
    76
    Trophy Points:
    18
    Yeah thats it
     
  15. Strutharald

    Strutharald Member

    Joined:
    Feb 9, 2018
    Messages:
    1
    Likes Received:
    1
    Trophy Points:
    1
    Is there anyway to pin point the places in the code of the DLL in order for other people to fix it for different patches? It's awesome that its fixed, but only for 1.13c seems a bit limiting if you have other d2-versions. Would be really great if someone could post the technical problem and maybe someone else can fixa for other version. Really stupid bug. Well done with this version anyway! :)
     
    Gix likes this.
  16. Gix

    Gix Founder

    Joined:
    Jan 1, 2005
    Messages:
    54,504
    Likes Received:
    5,070
    Trophy Points:
    113

    @Strutharald, location of the faulty code is different for all versions. We only fixed this bug for 1.13c patch because that's what we are using on our realm.
    On the other hand, keep in mind that this bug exists since diablo2 was launched and vast majority of players never realized it was an actual bug.
     
  • Loading...
    Thread Status:
    Not open for further replies.
    Loading...