Diablo III

From PCGamingWiki, the wiki about fixing PC games
Revision as of 21:59, 13 September 2012 by Newmansan (Talk | contribs)

Jump to: navigation, search

Template:Infobox

Diablo III is the third title in the Diablo series (preceded by Diablo in 1996 and Diablo II in 2000). It is developed by Blizzard. A general known issues list is well-maintained and kept updated by Blizzard.

Contents

Windows

Availability

Source(s) Store unlock Notes
Retail Battle.net Activates on Battle.net via serial key.
Battle.net Battle.net Activates on Battle.net through digital purchase.

All versions of Diablo III unlock a download of the game on a Battle.net account, which does not require installing an external downloader or client. Retail editions are expected to be cheaper than directly purchasing from Battle.net.

Battle.net

The game is fairly restrictive in requiring constant online access in order to play both single and multiplayer portions of the game, which is a departure from how Diablo II and StarCraft II handled their singleplayer campaigns. An 'always-on' connection requirement for singleplayer can be considered a form of Digital Rights Management (DRM).

Digital Edition

Once a digital edition of Diablo III is registered, it is limited to Starter Edition status for 3 days or 72 hours. This has been done to combat economy unbalancing.[1]

Starter Edition

The Diablo III Starter Edition provides players the ability to try out a limited demo version of Diablo III. Currently the only way to acquire a Starter Edition is to have a Guest Pass key, of which 2 are allocated per every retail box of Diablo III. [2] The Starter Edition will only be available with a guest pass until "further notice". [3]

The Starter Edition has a number of restrictions:

  • Act I up to the Skeleton King is available
  • Level 13 cap
  • Matchmaking available only with other Starter Edition players
  • No Real Money Auction House access
  • Global Play is not available. Players attempting to connect to Diablo III Starter Edition in a region other than their Battle.net Account's home region will receive Error 12.

Matchmaking of Starter Edition is only possible with other players of the Starter Edition, and not the full accounts. This includes public matching and private invitations. Counterintuively, this means that Starter Edition players will not be able to play with players with full Diablo III accounts.[4]

Real Money Auction House

The real money auction house has a number of restrictions.[5]

Video Settings

Template:Video Settings

Multi-Monitor

Reportedly working by setting Fullscreen Windowed mode and setting a multi-monitor resolution.[6]

Graphics Adjustment

D3Prefs.txt

Some settings are held in the file D3Prefs.txt:

  • Windows 7: C:\Users\%Username%\Documents\Diablo III\D3Prefs.txt

Settings can be adjusted, such as:

  • TonemapExposure
  • TonemapContrast
  • TonemapSaturation
  • TonemapGain

Darker D3

Using the Darker D3 Pixel Shader by Pyloneer, it is possible to make a change to the brightness and sharpness of the shaders.

Usage
  • Run Diablo III at least once.
  • Select a setting from the website.
  • Extract the .zip into the Diablo III folder.
  • Use the 'Pause' key to toggle the effect.
Breach Of Terms Of Service

Jay Wilson, Game Director of Diablo III, stated the following on 13 May 2012:

"TOS against mods is so we can ban cheaters. I agree DarkD3 is not a cheat...yet. As long as it is not a cheat, no ban is likely."[7]

Jay Wilson previously stated that altering graphics is against Terms Of Service, and can result in a ban.[8] Following this guide using Darker D3 is at one's own risk.

Improve Graphical Sharpness Filtering

The FXAA Injector is reported to work with Diablo III to improve graphical sharpness filtering.[9][10]

Video Card Not Supported

Unsupported video card error.
Demo version of Swiftshader, on Intel G41.

You may receive the error message:

We have detected that your video card is not supported by Diablo III.

Diablo III will block certain systems running the game if it does not detect a certain spec of video card. However, it is possible to force the game to run on any video card (even if it does not meet the minimum specification of the game).[11]

This fix has been acknowledged by Blizzard, but comes with its own warning from Omrakos:

...if you decide to do this and have terrible performance as expected, please do not contact us reporting it. We know the unsupported cards aren't going to perform well and there's nothing we'll be able to do to remedy it.[12]

Method - Press Escape

Pressing Esc instead of cancel will make one's computer attempt to load the client.

Pressing cancel will load up a list of unsupported video cards on Blizzard's website.

Method - Edit D3Prefs.txt

Open D3Prefs.txt using notepad in the following location:

  • Windows 7: C:\Users\%Username%\Documents\Diablo III\D3Prefs.txt

Change:

HardwareClass "0" to HardwareClass "1"

DisableTrilinearFiltering "0" to DisableTrilinearFiltering "1"

Method - Swiftshader

Using the program Swiftshader can successfully load the game even on extremely low powered machines. For example, the game can be run on integrated graphics as low powered as the Intel G41, albeit at extremely low framerate.[13]

High DPI Setting

Disable DPI scaling settings.

By default, it appears as if Diablo III has a number of issues with high or custom DPI settings in Windows.

This can result in:

  • Mouse cursor not being moveable whilst in fullscreen mode.
  • Mouse being imprecise on the screen.
  • Taskbar showing over the game window.

This can be fixed by following these steps:[14]

1) Right-click on the Diablo III shortcut (or Diablo III.exe) and go to the 'Compatibility' tab.

2) Select, 'Disable display scaling on high DPI settings'.

Login Errors

These messages may appear when trying to log in.

Error 12

This means that no license is attached to the Battle.net account, a problem with many users in Asia. Check this thread for more information.

Error 37

This message means that the login servers are at full capacity. Official advice is to try logging in later when the servers are less busy.[15]

However, it is possible to bypass Error 37 using this trick:[16]

  1. Enter password.
  2. Presss enter.
  3. Press cancel before anything happens.
  4. Log back in straight away.

This might be considered an exploit of the way that the client is reporting Error 37 to indicate that servers are too busy. However, this does not seem to have any particular consequences, except that Blizzard's servers will be busy.

Error 75

Error 75 means that Blizzard servers are down. Check Diablo III Server Status page for updates.

Installation Issues

Migrating From Beta To Full Release

Blizzard has advised those who have the beta installed, to uninstall the beta and delete all extra beta files, including:

  • Windows XP: C:\Documents and Settings\All Users\Application Data\Battle.net
  • Windows Vista/7: C:\ProgramData\Battle.net

Once the files are deleted, run the full retail installer.

Changing Client Language

Update 8 June 2012: Blizzard appear to have restricted client language switching.[17] Errors 81, 82 or 84 displays: "The client does not match the accounts native language. Please, use the game native client." There is no known fix as of yet, as Blizzard controls the language restrictions from their servers.

Language change menu.
Client language files can be adjusted from the options menu. Once the change is applied, a patch of approximately 3GB is downloaded. Client language cannot be changed back until this download reaches the 'playable' state, and one re-enters the client to change the language option again.[18]

Available languages are:

  • English (United States)
  • Spanish (Latin American)
  • Korean
  • Chinese (Traditional)
  • German
  • Spanish
  • French
  • Italian
  • Polish

"Updating game files" Issue

Some players are reporting the game getting stuck at installation in the "Updating game files" part.

Method - Disable Anti-Virus Software

  • Turn off your anti-virus software and firewall.
  • Loading the setup file again.
  • Running the launcher as administrator.

Method - Connect Using Different Network Adaptor

The Blizzard Agent may be attempting to connect over the wrong network adaptor. The following steps may resolve your issue (in Windows 7):

  1. Open the Control Panel.
  2. Select "View network status and tasks".
  3. Select "Change adapter settings".
  4. Right click on each adapter and select "Disable". Leave your primary adapter (the one that provides your internet connection) enabled. You should now have only one enabled adapter.
  5. Visit google to ensure you are still connected to the internet.
  6. Navigate to "C:\ProgramData" (a hidden folder) and delete the folder named "Battle.net" if it exists.
  7. Retry the installer/launcher.

Method - Delete/Modify Agent Files

Delete Agent.exe in:

  • Windows 7: C:\ProgramData\Battle.net\Agent\

Modify Agent.db by:

  • Opening using notepad.
  • Find p2penable : true to p2penable : false.

Installation Stuck At 10%

If the user has any connections configured in "Dial-up and Virtual Private Network settings" and they're set to "Dial whenever a network connection is not present," the install won't proceed past 10%.[19]

Installation Not Doing Anything

If the installation has yet to do anything you might need to make sure your secondary logon has been enabled. Do so by going through - Control Panel/Administrative Tools/Services, right click Secondary Logon and proceed to enable it by setting the start up type to automatic.

Issues And Fixes

Can't Move Mouse In Fullscreen

Disable DPI scaling settings.

This is most likely caused by high or custom DPI settings in Windows.

Method - Compatibility

This can be fixed by following these steps:[20]

1) Right-click on the Diablo III shortcut (or Diablo III.exe) and go to the 'Compatibility' tab.

2) Select, 'Disable display scaling on high DPI settings'.

Method - Edit D3Prefs.txt To Windowed

If one is stuck in fullscreen mode, one can change the D3Prefs.txt settings to force a windowed mode.

Open D3Prefs.txt using notepad in the following location:

  • Windows 7: C:\Users\%Username%\Documents\Diablo III\D3Prefs.txt

Make sure that this line is adjusted:

DisplayModeWindowMode "0" to DisplayModeWindowMode "1"

No Diablo III License Attached

This error message may appear:

|This Battle.net account does not have a Diablo III License attached to it.

A possible fix is to correctly set the region within the game settings, within the Options > Account > Server Region settings.[21]

Overlays

Running programs that put an overlay over Diablo III (such as Mumble, Xfire, and MSI Afterburner) can cause Diablo III to crash. Use these overlays at your own risk.[22]

System Requirements

Template:SysReq BaseTemplate

Mac

Issues And Fixes

Migrating From Beta To Full Release

Blizzard has advised those who have the beta installed, to uninstall the beta and delete all extra beta files, including:

  • Mac: /Users/Shared/Battle.net

Low Frame Rate

Using settings in the D3Prefs.txt mentioned below one can achieve a reasonable frame rate on e.g. the Macbook Pro Mid 2010 with the Nvidia 330M. Open the D3Prefs.txt and set the following to options to 1:

  • DisableTrilinearFiltering
  • HardwareClass

D3Prefs.txt

D3Prefs.txt on Mac is kept in a hidden folder. To access it:

1) Go to Go Menu at top of screen -> Go to Folder ~/Library/

2) Application Support > Blizzard > Diablo III

Can't ⌘ + Tab

Check that you havn't enabled Caps Lock as that disbales ⌘ + Tab, although ⌘ + M still functions correctly.

Unresolved Issues

Window Unresponsive

Game client window becomes unresponsive when a dialog box is opened in the background.

System Requirements

Template:SysReq BaseTemplate

Linux

WINE

Reportedly working using WINE, with more information on the Diablo III WineHQ entry.

Ubuntu 12.04

Users connecting through WINE while using Ubuntu 12.04 need to run code echo 0|sudo tee /proc/sys/kernel/yama/ptrace_scope before logging into the game in order to pass the "Authorizing" portion of login. Users who do not run this code will have the game spit out an error message. The code must only be run before the first login since the computer's startup, not every time before logging in, so it's recommended to run when the computer first starts up.

General Information

A list of general known issues has been published by Blizzard:

Databases

Forums

References

  1. http://www.pcgamer.com/2012/06/21/diablo-3-digital-editions-restricted-to-starter-edition-for-up-to-72-hours/
  2. http://us.battle.net/support/en/article/diablo-iii-starter-edition-guest-pass
  3. http://eu.battle.net/support/en/article/diablo-iii-starter-edition-guest-pass
  4. http://us.battle.net/d3/en/forum/topic/5150755817
  5. https://eu.battle.net/account/d3/auction-house/real-money.html
  6. http://www.wsgf.org/node/21375
  7. https://twitter.com/#!/Angryrobotics/status/201726183740686336
  8. https://twitter.com/#!/Angryrobotics/status/201405207039578113
  9. http://timothylottes.blogspot.se/2011/03/nvidia-fxaa.html
  10. http://eu.battle.net/d3/en/forum/topic/3950095509?page=1
  11. http://www.reddit.com/r/gaming/comments/tn8la/im_going_to_die/c4o2ada
  12. http://us.battle.net/d3/en/forum/topic/4903520596
  13. Tested by Andytizer.
  14. Fix by Andytizer.
  15. http://eu.battle.net/d3/en/forum/topic/4064636470
  16. http://www.reddit.com/r/Diablo/comments/tnxw1/trick_for_logging_in/
  17. http://us.battle.net/d3/en/forum/topic/5578597286?page=1
  18. http://gaming.stackexchange.com/questions/66164/can-i-change-the-language-the-game-client-uses
  19. http://us.battle.net/d3/en/forum/topic/4916972036
  20. Fix by Andytizer.
  21. http://www.gamefromscratch.com/post/2012/05/15/Picked-up-Diablo-3%E2%80%A6.aspx
  22. http://us.battle.net/d3/en/forum/topic/4916972036
Namespaces

Variants
Actions
Logo
Twitter Facebook Steam
Found us useful? Help by donating