The Diablo III Starter Edition provides players the ability to try out a limited demo version of Diablo III.
The Starter Edition has a number of restrictions:
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.
Game client window becomes unresponsive when a dialog box is opened in the background.
You may receive the error message:
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).
This fix has been acknowledged by Blizzard, but comes with its own warning from Omrakos:
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 frame rate.
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:
These messages may appear when trying to log in.
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.
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.
Error 75 means that Blizzard servers are down. Check Diablo III Server Status page for updates.
This is most likely caused by high or custom DPI settings in Windows.
This can be fixed by following these steps:
This error message may appear:
|This Battle.net account does not have a Diablo III License attached to it.
Running programs that put an overlay over Diablo III (such as Mumble and MSI Afterburner) can cause Diablo III to crash. Use these overlays at your own risk.
1. Edit %USERPROFILE%\Documents\Diablo III\D3Prefs.txt
2. find the PlayedCutscene lines, and edit them to read as follows:
3. Save and exit the file, and try again.
Update 8 June 2012: Blizzard appear to have restricted client language switching. 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.
Client language files can be adjusted from the options menu. Once the change is applied, a patch of approximately 3 GB 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.
Available languages are:
Some players are reporting the game getting stuck at installation in the "Updating game files" part.
The Blizzard Agent may be attempting to connect over the wrong network adaptor. The following steps may resolve your issue:
p2penable : true
p2penable : false
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%.
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.
Check that you haven't enabled Caps Lock as that disables ⌘+Tab ↹, although ⌘+M still functions correctly.