Are You Experiencing Any Day 1 Issues

We all know Diablo 3 has just released but how many of you are actually playing and getting a smooth experience? Reports are coming in that even though you wish to play single player, the Diablo 3 DRM is similar to what Ubisoft have been slammed for in the past.

People cannot connect to the servers or are being kicked and losing their place. Some are facing complete region monster respawns and lost dropped treasure, all in single player mode...

I myself have played for a few hours and had no bad experience to speak of. But that might have been because I was playing in the early twighlight, when first day server load was somewhat "minimal".

Let us know your first experiences and what you feel about the DRM? Is it similar to Ubisoft DRM, where genuine gamers who purchased the game were often suffering, while the torrenting gamers were enjoying a hassle free experience from their pirated copies?

It is our collective voice that helps direct game publishers on what is acceptable and what works, so have your say below.

Are you experiencing any day one issues? If so what are they and are they acceptable?

Or are you having a brilliant Diablo 3 experience? If so what are your highlights of D3's system so far? NO SPOILERS!

If you are having troubles and need help getting the game going or understanding some of the error messages then help forums are already available and there is also a dedicated twitter feed.

I want to finish by saying, you are here because you love gaming, so please support the game industry. Do not promote piracy.

Diablo 3 Error Messages Explained

Error - If your installation disc has been ejected, please reinsert and try again. If not, or if you keep seeing this error, log in to Battle.net and install Diablo III digitally

Explanation - If you downloaded the installer digitally, this error indicates that it did not convert the files correctly. This can often be caused by closing the downloader early. Though the downloader may show 100%, please allow some time for it to fully complete. To resolve this issue, log into Battle.net and re-run the downloader.

--------

Error - Gray login button 

Explanation - You need to use your Battle.net email address as your account name. Your BattleTag is a nickname, not your account name.

--------

Error - No License Attached 

Explanation - Please create a BattleTag for your account. You can do so here.

--------

Error - Unable to Initalize Streaming 

Explanation - This error can generally be caused by security software on your computer. During this time, however, it's possible that the error is caused by the number of people hitting the servers.Please double check your firewall settings and try again.

--------

Error - Updating Setup Files 

Explanation - If you're stuck on "Updating Setup Files" try these troubleshooting steps, as well as these.

Diablo 3 Error Codes Explained

Error 108 - Similar to "An unexpected decryption error occurred", the error 108 can be caused by corrupted, damaged or incomplete installation files. This can often times be caused by closing the downloader early. Though the downloader may show 100%, please allow some time for it to fully complete. 

You may be able to fix this by running the downloader and pointing it to the same saved location so that it may scan and download any missing files.

Error 12 - This error is caused by the Global Play feature being disabled until all regions are active. Please make sure you choose the correct region when starting the game as per this sticky:
http://eu.battle.net/d3/en/forum/topic/4008341471

Error 33 and 34200 - The service is undergoing maintenance, please try again later. (Please note that Diablo III will not be available for play until May 15 at 12:01 a.m. PDT)

Error 37 - The server is full. This is likely due to high login traffic. The only solution is to keep trying to log in.

Error 24000 - Once logged in you may run into this error when attempting to start a game. We're aware and are working to resolve it as quickly as possible.

Error 3004, 3006, 3007, or 300008 - There are a number of possible causes for these errors. We've found that one of these suggestions can help.

Error 315300 - If you're sure you're typing your correct account information, check to make sure no additional spaces were added before or after your email address. If you're still running into this issue, there may be an error in your foreign language appdata files. Some players have found a workaround, but please be aware the steps they provide are not something we can currently support.