Support FAQ: Difference between revisions

From Project Diablo 2
Jump to navigation Jump to search
Content added Content deleted
No edit summary
No edit summary
Line 62: Line 62:
# Your installation may be corrupt and you'll need to reinstall. '''See: [[#How-to install Project Diablo 2]]'''
# Your installation may be corrupt and you'll need to reinstall. '''See: [[#How-to install Project Diablo 2]]'''
## Try installing to a non-default location (as mentioned in the install guide)
## Try installing to a non-default location (as mentioned in the install guide)
## Try reinstalling with enGB version of both the Diablo 2 + Expansion installers instead of enUS
## Try reinstalling with enGB (English EU) version of both the Diablo 2 + Expansion installers instead of enUS




Line 100: Line 100:
# Your installation may be corrupt. Reinstall everything (Diablo II and the launcher) and make sure you have an exception created. '''See: [[#How-to install Project Diablo 2]]'''
# Your installation may be corrupt. Reinstall everything (Diablo II and the launcher) and make sure you have an exception created. '''See: [[#How-to install Project Diablo 2]]'''
## Try installing to a non-default location (as mentioned in the install guide)
## Try installing to a non-default location (as mentioned in the install guide)
## Try reinstalling with enGB version of both the Diablo 2 + Expansion installers instead of enUS
## Try reinstalling with enGB (English EU) version of both the Diablo 2 + Expansion installers instead of enUS
# If it happens during Rathma or other specific encounters, use the '''[https://discord.com/channels/701658302085595158/802993961827696640 #create-ticket]''' channel on Discord to report the issue. The ticket will have information about logs you can submit.
# If it happens during Rathma or other specific encounters, use the '''[https://discord.com/channels/701658302085595158/802993961827696640 #create-ticket]''' channel on Discord to report the issue. The ticket will have information about logs you can submit.


Line 216: Line 216:




'''You must use an English installer.''' To select the English (enUS), click the small gear icon next to the game's download link. You can also try the enGB version which has fixed some additional issues for others.
'''You must use an English installer.''' To select the English (enUS), click the small gear icon next to the game's download link. You can also try the enGB (English EU) version which has fixed some additional issues for others.
https://www.blizzard.com/en-us/download/
https://www.blizzard.com/en-us/download/



Revision as of 20:58, 28 April 2023

Failed to join game

Try creating games on different game servers. If you continue to receive the same error then it is likely that the game server you were originally in crashed. The realm server still thinks your character is in-game because the game server did not report you leaving the game since it crashed. Therefore, the realm doesn't let your character into another game. While rare, this does unfortunately happen and the only fix is to wait for the game server to restart and let your character out of the void. This can take anywhere from a few minutes to a few hours depending on when the server restarts.


Security warning with PD2 Launcher

Windows Security/Defender (and other anti-virus/malware solutions) will sometimes trigger a false positive with one or more components of ProjectD2. While the team does try to submit the files to Microsoft and other companies to prevent this, they do still happen. To prevent these from happening, you can create an exception/exclusion in your anti-virus for the entire Diablo II folder where PD2 is installed. See: #How-to create an exception in Windows Security/Defender


Unhandled Exception: ACCESS_VIOLATION (c0000005)

This is not a Project Diablo 2 only issue. Nearly all other Diablo II mods have had some users suffer from this problem. The issue does not affect everyone, only some people ever run into this issue. For some it has appeared their first time playing, for others it has come up after many seasons with no prior issues.


Try each of these one at a time and test the game after. Don't change them all at once

  1. Reboot your computer as a first step and see if it goes away. This is all it is for some people.

  2. Try changing the Graphics to DDraw in the Launcher Options or to 3dfx, whichever it wasn't set to.

  3. Make sure you have an exception/exclusion created in your anti-virus (likely Windows Defender) for the entire Diablo II folder. See: #How-to create an exception in Windows Security/Defender This is part of the normal install process so you should have it anyways. If you get to the last option and end up changing the installation folder, you will need to update this.

  4. Create an ASLR exception/exclusion in Windows Exploit Protection specifically for the Diablo II.exe and Game.exe files inside of the ProjectD2 folder.
    1. Go to Control Panel -> Windows Security -> App & browser control -> Exploit protection -> Exploit protection settings.
    2. Click on Program settings, click the Plus (+), select “Choose exact file path” and select the Game.exe file in the ProjectD2 folder, NOT the base Diablo II folder.
    3. Repeat for Diablo II.exe
    4. Make sure to check the override and that the switch is set to Off

      Windows Exploit Protection Program Exclusion Window

    5. Reboot your computer. DO NOT SKIP THIS

  5. Change your DEP settings to allow for exceptions. While the default and preferred setting (the top one) should only affect certain Windows programs and services, it -appears- to also affect the game for some people.
    1. NOTE: Changing this setting will cause it to affect all applications and you may need to create exceptions for any other applications if you run into issues with them.
    2. Go to: Control Panel -> System -> Advanced System Settings -> Click Settings under the Performance tab
    3. Under the Data Execution Protection tab, change the setting to the second option for all programs.
    4. Add both Diablo II.exe and Game.exe in the ProjectD2 folder, NOT the base Diablo II folder to the exceptions list.
    5. Reboot your computer. DO NOT SKIP THIS

If the issue is still not resolved, you can try keeping or reverting any of the above changes clean reinstall (properly uninstall Diablo 2 and any PD2 Launchers) and delete the Diablo II folder if it still exists. See the #How-to install Project Diablo 2 guide. Make sure to backup anything you may want to keep (save files, loot filters, etc). Please read and follow the instructions closely. If you have any questions, please ask on Discord in the the #tech-support channel.



Stash tabs not working

  1. Close out of the game and launcher.
  2. Delete the bh.dll file in the ProjectD2 folder.
  3. Run the launcher and press Play.
  4. Make sure you have an exception made in Defender. See: #How-to create an exception in Windows Security/Defender


Crash when changing acts

Remove the -ns (no sound) argument from your game shortcut.


Crashes when creating or joining games

  1. Make sure you have an exception in Defender. See: #How-to create an exception in Windows Security/Defender
  2. Try compatibility mode. See: #How-to run the game with different compatibility settings
  3. Your installation may be corrupt and you'll need to reinstall. See: #How-to install Project Diablo 2
    1. Try installing to a non-default location (as mentioned in the install guide)
    2. Try reinstalling with enGB (English EU) version of both the Diablo 2 + Expansion installers instead of enUS


Crash when looking at skills

You more than likely used a non-english installer for Diablo II. You will need to download the English installers for Diablo II and the Lord of Destruction expansion and then reinstall everything including the PD2 Launcher. See: #How-to install Project Diablo 2 for links and information on downloading the proper installer.


Crash when looking at items

  1. The loot filter you are using likely has an error in it, try a different one to see if it still happens.
  2. It is also possible you are using a non-english version of the game. See: #Crash when looking at skills


Crash/error when viewing the Item menu in the in-game Settings screen

This happens when you disable your loot filter and your Filter level is set to anything but 1. Manually setting it back to 1 fixes it and you should be able to interact with the menu again. After you load your filter again you can set the level back to what it was.

  1. Close out of Diablo II and the Launcher.
  2. Go to into the ProjectD2 directory and open "ProjectDiablo.cfg" in notepad or another text editor.
  3. Look for the line beginning with "Filter Level:" and set it to "Filter Level: 1"


You have music/ambient sound but no other game sounds

  1. Try changing your surround sound settings on your sound card.
  2. Try changing your sound output device to another (headset, monitor, speakers, etc).
  3. Try running in windowed mode (-w) from the Launcher options.
  4. Try Compatibility mode if it is not already turned on. See: #How-to run the game with different compatibility settings


Halt error

  1. If you use separate game shortcut and not the PD2 Launcher, remove the -3dfx argument from the shortcut or use the Launcher to test.
  2. If you have tried using any Glide wrappers (such as Sven's) there may be an issue with the installation or configuration. Try adjusting the configuration or removing it.
  3. Try changing loot filters -- this is harder to test unless you can consistently reproduce the error.
  4. Your installation may be corrupt. Reinstall everything (Diablo II and the launcher) and make sure you have an exception created. See: #How-to install Project Diablo 2
    1. Try installing to a non-default location (as mentioned in the install guide)
    2. Try reinstalling with enGB (English EU) version of both the Diablo 2 + Expansion installers instead of enUS
  5. If it happens during Rathma or other specific encounters, use the #create-ticket channel on Discord to report the issue. The ticket will have information about logs you can submit.


Unable to connect to Battle.net

  1. The servers are down. Check the #announcements channel on Discord for any issues or maintenance updates.
  2. Your antivirus and/or firewall is blocking the game.
  3. You or your ISP or somewhere between your ISP and the PD2 servers are having network issues.
  4. If the error message states you were banned, do not discuss this in any channel. Read the #pd2-rules.
  5. Use the #create-ticket channel on Discord to check on your account status.


Can’t connect to the realm, port 6112 error

  1. If your account name begins with or ends with an underscore ( _ ) this will prevent you from connecting. Either create a new account or use the #create-ticket channel in Discord to open a ticket about your account.
  2. Your antivirus or firewall is blocking the game. See: #How-to create an exception in Windows Security/Defender
  3. You will need to use the #create-ticket channel in Discord to open a ticket to check on your account and find out any additional information. Mods will not discuss this in chat or DMs.


Empty list of loot filters in launcher

  1. Make sure you are running the PD2 Launcher as an administrator
  2. Make sure you are using the latest version of the PD2 Launcher from the website. Press Play to install any updates.
  3. Make sure your antivirus and/or firewall are not blocking the launcher.
  4. You may need to manually unblock and/or create exceptions for the launcher and the Diablo II and/or ProjectD2 folder.
  5. Reboot your computer.
  6. If you are unable to resolve the issue, you can manually download a filter and place it in the ProjectD2 folder. The file must be named loot.filter or you can replace the default.filter with yours.


Offline characters missing after playing Diablo 2 Resurrected

  1. Locate the D2R save game location.
    1. %USERPROFILE%\Saved Games\Diablo II Resurrected is the default location
    2. If nothing is there, the saves are either gone forever or you may have a different save location.
    3. You can try searching your computer for <charname>.d2s
  2. If you are able to locate them, now locate the Diablo II save location.
    1. The normal location should be in the Save folder where you installed Diablo II, not the ProjectD2 folder and not the D2R folder.
      You can also look in:
      1. %USERPROFILE%\Saved Games\Diablo II
      2. %USERPROFILE%\Documents\Saved Games\Diablo II
      3. %USERPROFILE%\Documents\My Games\Diablo II
      4. If you are still unsure, create a new test character and look in those locations, you should see a <charname>.d2s file
  3. Once you are able to locate the save files (including _LOD_SharedStashSave if you use PlugY) copy or move them back to the original Save folder.
  4. Open up the game to see if they are restored. If D2R modified the files in any way, the characters are likely unrecoverable.
  5. Make regular backups of your stuff.


Choppy FPS while playing online or offline with DDRAW graphics

  1. Reboot
  2. If the Launcher or in-game graphics (CTRL+O) Option for Show Window Borders is enabled, try turning it off.
  3. Reset the settings by closing out of the game and launcher and delete the ddraw.ini file in the ProjectD2 folder.


Strange graphics when moving with D2GL 3dfx graphics mode and Motion Prediction enabled

  1. In the Diablo 2 in-game Video Options (ESC Menu), change the Lighting Quality to High
  2. Also try turning Perspective Off in the same options menu


Slow mouse movement with D2GL 3dfx graphics enabled

  1. In the advanced in-game settings (CTRL+O) try turning off FXAA and/or the HD Cursor setting.


In-game Settings button missing

  1. Close out of Diablo II and the PD2 Launcher.
  2. Delete the UI.ini file in the ProjectD2 folder.
  3. Open the PD2 Launcher again and press Play.


Can’t click on in-game Settings button

Make sure you are using CTRL+Click and not just regular clicking.


How-to create an exception in Windows Security/Defender

Also See: #Security warning with PD2 Launcher

Below are guides from Microsoft on how to create an exception. A folder exception for the entire Diablo II folder should be created to avoid certain issues.

  1. https://support.microsoft.com/en-us/windows/add-an-exclusion-to-windows-security-811816c0-4dfd-af4a-47e4-c301afe13b26
    https://support.microsoft.com/en-us/windows/risks-of-allowing-apps-through-windows-defender-firewall-654559af-3f54-3dcf-349f-71ccd90bcc5c

  2. If you are using a different anti-virus or firewall solution, you will need to look through the settings or find other documentation for creating any exceptions.

  3. Again, make sure to create the exception for the entire folder, not just one file.


How-to run the game with different compatibility settings

  1. Open the ProjectD2 folder, NOT the base Diablo II folder, and locate the Game.exe and Diablo II.exe files.
  2. Right click the file and select Properties.
  3. Under the Compatibility tab, check the box and set the Compatibility Mode to Windows XP (Service Pack 3) and also check the box to Run this program as an administrator. You can also try Windows 7 as the compatibility.
  4. Repeat for the other file.
  5. Press OK to save the changes.


How-to install Project Diablo 2

See: #how-to-install channel on Discord.

Project Diablo 2 is a free mod but it requires a legitimate install of Legacy Diablo 2 and Lord of Destruction (not Resurrected) from Blizzard. If you do not own a copy or need to purchase a new copy, use the links below. Illegitimate cd-keys will result in the banning of your account. This will not be reversed but you are allowed to properly purchase a new copy and create a new account.

https://us.shop.battle.net/en-us/product/diablo-ii

https://us.shop.battle.net/en-us/product/diablo-ii-lord-of-destruction


If you already own the game you can use this link to check your keys. If you have Physical copies go to Account Overview to Redeem your cd-keys and download the digital installers. https://account.battle.net/games#classic-game-accounts


You must use an English installer. To select the English (enUS), click the small gear icon next to the game's download link. You can also try the enGB (English EU) version which has fixed some additional issues for others. https://www.blizzard.com/en-us/download/


As a general tip, it is typically better to install Diablo II, ProjectD2 (and games in general) outside of a protected folder (Program Files, your user folders, etc.) to prevent various issues. Example: C:\Games\<name of game>. For this guide we will be using "C:\Games\Diablo II" as the install location.

  1. Make sure you have a legal purchased copy of Diablo II and Lord of Destruction as stated above.
  2. Download the Diablo II and Lord of Destruction game clients from the link above.
  3. Download the PD2 Launcher from https://www.projectdiablo2.com
  4. Install Diablo II and when prompted, change the installation directory to C:\Games – the installation path should update to C:\Games\Diablo II – if not, create the Games and/or Diablo II folder and try again.
  5. Install the Lord of Destruction expansion. It should automatically detect the Diablo II installation folder.
  6. Create an exception in your anti-virus for the Diablo II folder. See: #How-to create an exception in Windows Security/Defender
  7. Install the PD2 Launcher – browse to the location you installed Diablo II (C:\Games\Diablo II in this example) if it does not find it automatically.
  8. Optional: Set the game to run in compatibility mode. See: #How-to run the game with different compatibility settings'
  9. Run the PD2 Launcher and press Play to automatically install any updates and launch the game.


How-to install PlugY

  1. Read First: https://github.com/BetweenWalls/PD2-Singleplayer
  2. Video installation guide: https://streamable.com/yhjhvs
  3. You can also look in the #how-to-install channel on Discord
  4. Try steps 1 and 2 again


Other error solutions

  1. Read This https://docs.google.com/document/d/1KHs3E9jWtheMOQ9ITKuJ6GN6AAK7-myXeK3STwBsRUQ/edit
  2. If you still can't resolve the issue, please ask on Discord in the #tech-support channel or the #create-ticket channel and react with the appropriate icon to open a ticket. Make sure to reply with all information requested in the ticket.