Diablo III System Requirements. Posted by 8 years ago. Broadband. Internet connection 1024x748 minimum resolution. A mini game inside Diablo 3 where you try to level your character from 1 to 70 following randomized rules giving you new challenge on every try. Below are the minimum and recommended system specifications for Diablo® III for Windows® and Mac®. Due to potential programming changes, the minimum system requirements for Diablo III may change over time. Note: For a list of compatible video hardware, see our Supported Video Cards list. Diablo Posted on October 12, 2012 at 12:39 pm by thinkdj One good thing is that most modern computers would be able to run Diablo 3 as the minimum system requirements seem to be decent.
Diablo III system requirements, Diablo III minimum requirements and recommended requirements, Can you run Diablo III, specs. Awesome minimum requirements for 2012 game. 8 years ago 2012. 20:48:43 # AMD FX-4100 3.8GHZ ATI REDOEN.
Blizzard doesn't announce their system requirements or recommendations until shortly before a game is finished. They don't know before then, since the final stages of programming include lots of optimizations to lower the machine load and streamline the program. Their goal is to keep their games playable on reasonable systems, without sacrificing performance or graphics.
As a result, fans were left to guess and conjecture at Diablo III's system requirements for years. This page preserves those early hints and investigations, below the official information which Blizzard finally revealed in December 2011.
- 1Diablo III Minimum System Requirements
- 2Diablo III Recommended System Requirements
- 3Diablo III Demo Systems
- 5Starcraft 2 System Requirements
Diablo III Minimum System Requirements[edit | edit source]
From the official page:[[1]]
Windows[edit | edit source]
- Windows® XP/Vista/7 (latest service packs) with DX 9.0c
- Intel Pentium® D 2.8 GHz or AMD Athlon™ 64 X2 4400+
- NVIDIA® GeForce® 7800 GT or ATI Radeon™ X1950 Pro or better
- 1 GB RAM (XP), 1.5 GB (Vista/7)
- 12 GB available HD space
- DVD-ROM (required for retail disc versions only)
- Broadband* Internet connection
- 1024x748 minimum resolution
Mac[edit | edit source]
- Mac® OS X 10.6.8, 10.7.x or newer
- Intel® Core 2 Duo
- NVIDIA® GeForce® 8600M GT or ATI Radeon™ HD 2600 or better
- 2 GB RAM
- 12 GB available HD space
- DVD-ROM (required for retail disc versions only)
- Broadband* Internet connection1024x768 minimum resolution
* Be advised that some wireless connections do not meet the minimums required to be a true Broadband Internet connection. Wireless results may vary.
Diablo III Recommended System Requirements[edit | edit source]
From the official page:[[2]]
Windows[edit | edit source]
- Windows® Vista/7 (latest service packs)
- Intel® Core 2 Duo 2.4 GHz or AMD Athlon™ 64 X2 5600+ 2.8 GHz
- 2 GB RAM
- NVIDIA® GeForce® 260 or ATI Radeon™ HD 4870 or better
Mac[edit | edit source]
- Mac® OS X 10.7.x or newer
- Intel® Core 2 Duo
- 2 GB RAM
- NVIDIA® GeForce® GT 330M or ATI Radeon™ HD 4670 or better
Video Card Information[edit | edit source]
Blizzard tech support maintains lengthy lists of video cards sorted by High, Medium, and Low Performance. Refer to those for specific details of your own hardware:
Diablo III Demo Systems[edit | edit source]
Prior to the beginning of the Diablo III Beta test, and the ultimate release of the official system specs, fans derived information from any available source. One useful data point was the machines used at game demos. Here's the system info from the machines assembled to demo Diablo III at the G-Star show in Seoul, Korea in 2010. [3]
- CPU: Intel Core i7 870 (45nm, Soket 1156, 2.93GHz)
- Motherboard: Intel DH55HC (intel H55)
- RAM: EK Memory DDR3 10600 2GBx2EA
- Video Card: GIGABYTE GeForce GTX 460 1GB WindForce or ZOTAC GeForce GTX 460 1GB
- Hard Drive: Seagate Momentus XT 500GB
- Power Supply: Acbel iPower 500
- Case: Bestech Guardian
- Monitor: Orion TopSync 24
Some photos of the machines during their set up process can be seen below.
Demo Machines are Monsters[edit | edit source]
Knowing the specs of demo machines at game shows isn't necessarily very useful for predicting the actual game requirements, though, as Bashiok explained in 2009. [4]
Bashiok, could you tell us, what was the hardware configuration of the computer whereat the Diablo III ran?They were insane.
There's a few reasons why it doesn't matter what those machines were though.
Most machines are lent to us by hardware vendors. It's in our interest to have our games look good and run well, and it's in their interest to show off the latest and greatest their company has to offer. So generally they're top of the line, using all the newest and best hardware.
Because we're working with a pre-release version we work with the hardware that's going to be on the show floor to build a final show floor build. The game hasn't hit (obviously) final QA and hardware compatibility testing as it would before release to the public, so we need to ensure it's going to run smoothly on this one specific set of hardware for the show.
It can also help, to a degree, overcome some potential technical hurdles we could run into with a pre-optimized build of the game. Throw more CPU/RAM/3D processing at it, and generally those pre-optimized problems won't throw a wrench into the brief glimpse of a game that isn't finished yet.
So, the combination of having hardware vendors showing off the latest and greatest, coupled with our interest to have a unoptimized version of the game look good, leads to show floor specifications that are probably way beyond what even the final 'Recommended' specs for the game would be, let alone 'Required'.Diablo III's Technology[edit | edit source]
Diablo III is made completely in 3D, using custom in-house physics and graphics engines. The game is currently native to DirectX 9, and will not require DirectX 10 to run. The game will probably use a slightly higher level of system requirements than StarCraft II, which used Havok & DirectX 9, and is the closest thing we can compare the game to.
You can read more on StarCraft II's requirements and DirectX compatibilities as well as shader info here:
- Graphics Requirements Confirmed - The most prominent part of the system requirements, the graphics requirements released from Blizzard document.
- StarCraft II System Requirements - System requirements analyse from available information.
- Kalos' Chronicles - Technical articles for StarCraft II.
Here is a Blizzard quote on the system specs: [5]
Jay Wilson: Currently we have no plans for specific DirectX 10 support. Right now are running a DirectX 9, and we run on a pretty broad range of systems, really fast. Overall, across-the-board Blizzard's goal is that all of our games support a broad range of systems. We don't jump up the system specs in any grand way. We have no intentions of being a high-end game, and certainly no intentions of being an exclusive DirectX 10 game at this time.Starcraft 2 System Requirements[edit | edit source]
Fans often ask about Diablo 3's system requirements. While Blizzard won't make those known until much closer to the game's launch, we can look at the SC2 minimm requirements for some insight. Here's what Blizzard says, on their B.net support page. [6]
PC Minimum System Requirements[edit | edit source]
Due to potential programming changes, the Minimum System Requirements for this game may change over time.Mac Requirements
- Windows® XP/Windows Vista®/Windows® 7 (Updated with the latest Service Packs) with DirectX® 9.0c
- 2.6 GHz Pentium® IV or equivalent AMD Athlon® processor
- 128 MB PCIe NVIDIA® GeForce® 6600 GT or ATI Radeon® 9800 PRO video card or better
- 12 GB available HD space
- 1 GB RAM (1.5 GB required for Windows Vista®/Windows® 7 users)
- DVD-ROM drive
- Broadband Internet connection
- 1024X720 minimum display resolution
PC Recommended Specifications:[edit | edit source]
- Windows Vista®/Windows® 7
- Dual Core 2.4Ghz Processor
- 2 GB RAM
- 512 MB NVIDIA® GeForce® 8800 GTX or ATI Radeon® HD 3870 or better
Mac Minimum System Requirements:[edit | edit source]
- Mac® OS X 10.5.8, 10.6.2 or newer
- Intel® Processor
- NVIDIA® GeForce® 8600M GT or ATI Radeon® X1600 or better
- 12 GB available HD space
- 2 GB Ram
- DVD-ROM drive
- Broadband Internet connection
- 1024X720 minimum display resolution
Mac Recommended Specifications:[edit | edit source]
- Intel® Core 2 Duo processor
- 4 GB system RAM
- NVIDIA® GeForce® 9600M GT or ATI Radeon® HD 4670 or better
Compatible Operating Systems[edit | edit source]
- Windows XP compatible
- Windows Vista compatible
- Mac OSX compatible
Diablo 3 Barbarian Guide: Maintaining WotB Minimum Requirements submitted by Jim.
Having played a bit with dual wield and 2H setups, I became curious about what the minimums are to keep WotB up indefinitely and why it is so difficult to achieve with a 2H build and what you need in terms of IAS to make perma-wrath easy for WW and hammer builds.
Now, the APS listed below are the amount needed to simply spam just HotA or WW/tornadoes and maintain WotB. This means, APS beyond these amounts simply makes it easier to recharge the timer. You don't have to get more than these APS values, since you can also weave fury generators into your damage rotation to get more fury. But, you do want to be close, especially for HotA, otherwise you can't spam the skill as much and your damage suffers.
Guide continued after the page break..
WW/tornado Build
The basic cutoff is driven by making 25 fury per second. This depends on how many WW and tornado 'ticks' are actually hitting stuff. The analysis is based on the most difficult case -- an elite that runs away a lot with a small hitbox. So, 2.5 tornadoes are assumed to hit on average and 1 WW constantly channeling.
'-' column is non-mighty weapon (i.e. sword, axe, mace, spears, etc). All cc is assumed to be fully buffed with WotB active. Attack speeds are rounded up to nearest breakpoint. So .45 cc with MW would be 32% cc with just passives, 35% with battle rage, then 45% with WotB running. If you have Overpower: Killing Spree (OP:KS), then that would jump to 55% cc buffed. ALL OF THESE NUMBERS ASSUME WEAPON MASTER PASSIVE!
No fury passives
CC - MW
0.45 4.00 2.86
0.50 4.00 2.50
0.55 3.33 2.50
0.60 2.86 2.22
0.65 2.86 2.00
0.70 2.50 2.00
0.75 2.50 1.82
0.80 2.22 1.82
0.85 2.00 1.67
With Animosity
CC - MW
0.45 3.33 2.22
0.50 2.86 2.22
0.55 2.86 2.00
0.60 2.50 1.82
0.65 2.22 1.67
0.70 2.22 1.67
0.75 2.00 1.54
0.80 1.82 1.43
0.85 1.67 1.43
Blizzard doesn't announce their system requirements or recommendations until shortly before a game is finished. They don't know before then, since the final stages of programming include lots of optimizations to lower the machine load and streamline the program. Their goal is to keep their games playable on reasonable systems, without sacrificing performance or graphics.
As a result, fans were left to guess and conjecture at Diablo III's system requirements for years. This page preserves those early hints and investigations, below the official information which Blizzard finally revealed in December 2011.
- 1Diablo III Minimum System Requirements
- 2Diablo III Recommended System Requirements
- 3Diablo III Demo Systems
- 5Starcraft 2 System Requirements
Diablo III Minimum System Requirements[edit | edit source]
From the official page:[[1]]
Windows[edit | edit source]
- Windows® XP/Vista/7 (latest service packs) with DX 9.0c
- Intel Pentium® D 2.8 GHz or AMD Athlon™ 64 X2 4400+
- NVIDIA® GeForce® 7800 GT or ATI Radeon™ X1950 Pro or better
- 1 GB RAM (XP), 1.5 GB (Vista/7)
- 12 GB available HD space
- DVD-ROM (required for retail disc versions only)
- Broadband* Internet connection
- 1024x748 minimum resolution
Mac[edit | edit source]
- Mac® OS X 10.6.8, 10.7.x or newer
- Intel® Core 2 Duo
- NVIDIA® GeForce® 8600M GT or ATI Radeon™ HD 2600 or better
- 2 GB RAM
- 12 GB available HD space
- DVD-ROM (required for retail disc versions only)
- Broadband* Internet connection1024x768 minimum resolution
* Be advised that some wireless connections do not meet the minimums required to be a true Broadband Internet connection. Wireless results may vary.
Diablo III Recommended System Requirements[edit | edit source]
From the official page:[[2]]
Windows[edit | edit source]
- Windows® Vista/7 (latest service packs)
- Intel® Core 2 Duo 2.4 GHz or AMD Athlon™ 64 X2 5600+ 2.8 GHz
- 2 GB RAM
- NVIDIA® GeForce® 260 or ATI Radeon™ HD 4870 or better
Mac[edit | edit source]
- Mac® OS X 10.7.x or newer
- Intel® Core 2 Duo
- 2 GB RAM
- NVIDIA® GeForce® GT 330M or ATI Radeon™ HD 4670 or better
Video Card Information[edit | edit source]
Blizzard tech support maintains lengthy lists of video cards sorted by High, Medium, and Low Performance. Refer to those for specific details of your own hardware:
Diablo III Demo Systems[edit | edit source]
Prior to the beginning of the Diablo III Beta test, and the ultimate release of the official system specs, fans derived information from any available source. One useful data point was the machines used at game demos. Here's the system info from the machines assembled to demo Diablo III at the G-Star show in Seoul, Korea in 2010. [3]
- CPU: Intel Core i7 870 (45nm, Soket 1156, 2.93GHz)
- Motherboard: Intel DH55HC (intel H55)
- RAM: EK Memory DDR3 10600 2GBx2EA
- Video Card: GIGABYTE GeForce GTX 460 1GB WindForce or ZOTAC GeForce GTX 460 1GB
- Hard Drive: Seagate Momentus XT 500GB
- Power Supply: Acbel iPower 500
- Case: Bestech Guardian
- Monitor: Orion TopSync 24
Some photos of the machines during their set up process can be seen below.
Demo Machines are Monsters[edit | edit source]
Knowing the specs of demo machines at game shows isn't necessarily very useful for predicting the actual game requirements, though, as Bashiok explained in 2009. [4]
Bashiok, could you tell us, what was the hardware configuration of the computer whereat the Diablo III ran?They were insane.
There's a few reasons why it doesn't matter what those machines were though.
Most machines are lent to us by hardware vendors. It's in our interest to have our games look good and run well, and it's in their interest to show off the latest and greatest their company has to offer. So generally they're top of the line, using all the newest and best hardware.
Because we're working with a pre-release version we work with the hardware that's going to be on the show floor to build a final show floor build. The game hasn't hit (obviously) final QA and hardware compatibility testing as it would before release to the public, so we need to ensure it's going to run smoothly on this one specific set of hardware for the show.
It can also help, to a degree, overcome some potential technical hurdles we could run into with a pre-optimized build of the game. Throw more CPU/RAM/3D processing at it, and generally those pre-optimized problems won't throw a wrench into the brief glimpse of a game that isn't finished yet.
So, the combination of having hardware vendors showing off the latest and greatest, coupled with our interest to have a unoptimized version of the game look good, leads to show floor specifications that are probably way beyond what even the final 'Recommended' specs for the game would be, let alone 'Required'.Diablo III's Technology[edit | edit source]
Diablo III is made completely in 3D, using custom in-house physics and graphics engines. The game is currently native to DirectX 9, and will not require DirectX 10 to run. The game will probably use a slightly higher level of system requirements than StarCraft II, which used Havok & DirectX 9, and is the closest thing we can compare the game to.
You can read more on StarCraft II's requirements and DirectX compatibilities as well as shader info here:
- Graphics Requirements Confirmed - The most prominent part of the system requirements, the graphics requirements released from Blizzard document.
- StarCraft II System Requirements - System requirements analyse from available information.
- Kalos' Chronicles - Technical articles for StarCraft II.
Here is a Blizzard quote on the system specs: [5]
Jay Wilson: Currently we have no plans for specific DirectX 10 support. Right now are running a DirectX 9, and we run on a pretty broad range of systems, really fast. Overall, across-the-board Blizzard's goal is that all of our games support a broad range of systems. We don't jump up the system specs in any grand way. We have no intentions of being a high-end game, and certainly no intentions of being an exclusive DirectX 10 game at this time.Starcraft 2 System Requirements[edit | edit source]
Fans often ask about Diablo 3's system requirements. While Blizzard won't make those known until much closer to the game's launch, we can look at the SC2 minimm requirements for some insight. Here's what Blizzard says, on their B.net support page. [6]
PC Minimum System Requirements[edit | edit source]
Due to potential programming changes, the Minimum System Requirements for this game may change over time.Mac Requirements
- Windows® XP/Windows Vista®/Windows® 7 (Updated with the latest Service Packs) with DirectX® 9.0c
- 2.6 GHz Pentium® IV or equivalent AMD Athlon® processor
- 128 MB PCIe NVIDIA® GeForce® 6600 GT or ATI Radeon® 9800 PRO video card or better
- 12 GB available HD space
- 1 GB RAM (1.5 GB required for Windows Vista®/Windows® 7 users)
- DVD-ROM drive
- Broadband Internet connection
- 1024X720 minimum display resolution
PC Recommended Specifications:[edit | edit source]
- Windows Vista®/Windows® 7
- Dual Core 2.4Ghz Processor
- 2 GB RAM
- 512 MB NVIDIA® GeForce® 8800 GTX or ATI Radeon® HD 3870 or better
Mac Minimum System Requirements:[edit | edit source]
- Mac® OS X 10.5.8, 10.6.2 or newer
- Intel® Processor
- NVIDIA® GeForce® 8600M GT or ATI Radeon® X1600 or better
- 12 GB available HD space
- 2 GB Ram
- DVD-ROM drive
- Broadband Internet connection
- 1024X720 minimum display resolution
Mac Recommended Specifications:[edit | edit source]
- Intel® Core 2 Duo processor
- 4 GB system RAM
- NVIDIA® GeForce® 9600M GT or ATI Radeon® HD 4670 or better
Compatible Operating Systems[edit | edit source]
- Windows XP compatible
- Windows Vista compatible
- Mac OSX compatible
Diablo 3 Barbarian Guide: Maintaining WotB Minimum Requirements submitted by Jim.
Having played a bit with dual wield and 2H setups, I became curious about what the minimums are to keep WotB up indefinitely and why it is so difficult to achieve with a 2H build and what you need in terms of IAS to make perma-wrath easy for WW and hammer builds.
Now, the APS listed below are the amount needed to simply spam just HotA or WW/tornadoes and maintain WotB. This means, APS beyond these amounts simply makes it easier to recharge the timer. You don't have to get more than these APS values, since you can also weave fury generators into your damage rotation to get more fury. But, you do want to be close, especially for HotA, otherwise you can't spam the skill as much and your damage suffers.
Guide continued after the page break..
WW/tornado Build
The basic cutoff is driven by making 25 fury per second. This depends on how many WW and tornado 'ticks' are actually hitting stuff. The analysis is based on the most difficult case -- an elite that runs away a lot with a small hitbox. So, 2.5 tornadoes are assumed to hit on average and 1 WW constantly channeling.
'-' column is non-mighty weapon (i.e. sword, axe, mace, spears, etc). All cc is assumed to be fully buffed with WotB active. Attack speeds are rounded up to nearest breakpoint. So .45 cc with MW would be 32% cc with just passives, 35% with battle rage, then 45% with WotB running. If you have Overpower: Killing Spree (OP:KS), then that would jump to 55% cc buffed. ALL OF THESE NUMBERS ASSUME WEAPON MASTER PASSIVE!
No fury passives
CC - MW
0.45 4.00 2.86
0.50 4.00 2.50
0.55 3.33 2.50
0.60 2.86 2.22
0.65 2.86 2.00
0.70 2.50 2.00
0.75 2.50 1.82
0.80 2.22 1.82
0.85 2.00 1.67
With Animosity
CC - MW
0.45 3.33 2.22
0.50 2.86 2.22
0.55 2.86 2.00
0.60 2.50 1.82
0.65 2.22 1.67
0.70 2.22 1.67
0.75 2.00 1.54
0.80 1.82 1.43
0.85 1.67 1.43
With IK5 or Unforgiving
CC - MW
0.45 4.00 2.50
0.50 3.33 2.22
0.55 2.86 2.22
0.60 2.86 2.00
0.65 2.50 2.00
0.70 2.22 1.82
0.75 2.22 1.67
0.80 2.00 1.67
0.85 2.00 1.54
With Animosity + IK5 (or unforgiving - but lose cc here)
CC - MW
0.45 3.33 2.00
0.50 2.86 2.00
0.55 2.50 1.82
0.60 2.22 1.67
0.65 2.00 1.54
0.70 2.00 1.54
0.75 1.82 1.43
0.80 1.67 1.33
0.85 1.54 1.25
IK5 + unforgiving
CC - MW
0.45 3.33 2.22
0.50 2.86 2.22
0.55 2.86 2.00
0.60 2.50 1.82
0.65 2.22 1.67
0.70 2.22 1.67
0.75 2.00 1.54
0.80 1.82 1.43
0.85 1.67 1.43
Also see the following link for Tick Breakpoints:
https://docs.google.com/spreadsheet/ccc?key=0AjPQvt06HFyJdHJjY1JSVEo5dkI5QUttMzY1Q0pWR2c#gid=50
Hammer build 1.83 unbuff APS
For hammer, there are a couple of factors:
1) Fury per second spent from hammer
2) Fury per second gained from hammer
Assuming you are gaining infinite fury from superstition or getting mobbed (usual case when farming), 1) is the limiting factor. With no HotA cost reduction, you need only 1.25 aps to spend 25 fury per second with hammer (very easy). With -5 reduction, you need 1.67 aps. Note there is player skill here not factored in!! You can spam other fury spenders to dump fury when you are hammering on many targets. I find this carpal tunnel inducing, so I am just giving the faceroll numbers here (1.25 and 1.67).
Now for ubers or single target elite, 2) becomes the limit.
Assuming you have 100% crit chance on hammer with gear and items, the minimum APS you need is 25/(15x.8) = 2.08 APS. The 0.8 is for the proc coefficient of hammer:smash, what most people run for ubers. In practice, you need less than this, depending on your passives and combat situation. Damage received will generate fury, and you can cheat against most elites with superstition passive, which can generate a huge amount of fury per second (enough to sustain WotB on it's own as long as you are spending fast enough). Additionally, if you are using frenzy maniac, you will be weaving in a hit of frenzy, which generates 3 fury + battle rage procs.
So in theory, just spamming hammer on one target, requires the equivalent of 84% ias for a Skorn, which corresponds with 12 ticks per second for WW. So generally speaking, hammer builds require higher IAS to maintain WotB in single target situations relative to WW/tornado, but you can make up for the deficit with a passive like superstition and standing in pools on purpose. With animosity passive, the APS requirement drops to 1.60 (18 fury per crit), but I feel superstition is overall a better solution.
In actual play, these numbers mirror my experience.