Believe it or not, it actually is two separate games, as far as the game client is concerned. While the actual game file data is the same (minus monster HP totals, which are doubled on console to “account for” the Nephalem Glory buff difference), the clients themselves are not. That doesn’t mean Blizzard couldn’t bring over the console UI and controller support, but it isn’t as simple as just transplanting the code either. The console versions are also not developed in-house using the Diablo franchise team. They are developed by a different team altogether.
Ideally the PC version would handle both UI types, let you customize the layout of the UI to suit your needs, and allow you controller or mouse/kb support independent of which UI type you chose to use. Unfortunately as much as I’d love this and even knowing Blizzard now has an accessibility team that handles player input on accessibility issues, I know that it’s almost a pipe dream short of management giving the green light to make it so.
And if you think it’s “easy”, go check out World of Warcraft’s built in controller “support”. Virtually no UI to speak of for it, and you have to resort to reading a forum guide and using almost completely undocumented CVARs in the config.wtf file to configure the controller, and on top of that it’s trial and error going back and forth between editing the file and testing the setup. In other words, it’s essentially alpha level integration. But it’s a start.
Bottom line here is that Blizzard proper isn’t very well versed in accessibility yet. Even Overwatch, several years after launching, still doesn’t have full controller customization. It has certain controls hard locked to specific parts of the controller and you cannot override that, severely limiting accessibility for those of us that prefer or require controllers to play the game.
Blizzard’s trying, but they have a very long way to go toward actually making end-user configurable accessibility access a reality.
1 Like
You might want to check out the Benjamin Odom Youtube channel. He wrote a program that allows controller support for Diablo 3 and Path of Exile. I’ve been using the program for a while now, and it works well.
1 Like
Get a wireless keyboard and mouse and ta-daaaa XD
Go talk to Blizzard then. They are the one who said they had to rebuild the game for consoles and create a seperate client version of the game.
Bad faith argument. You know this is incorrect. Sad you continue to spread false information.
You know, I’ve been anti-controller 'til D2R. Now I want that scheme on D3 PC. My only gripe is that I want to use the right stick as a cursor to aim ranged or ground targeted attacks.
1 Like
Maybe check out reWASD, they have already made configs for diable III for the Xbox and Xbox Elite Controllers.
This works very well too and I saw was mentioned before in this thread.
2 Likes
This forum is entertaining. Blizzard made a mistake not supporting native controller support. The game is better with a controller. Blizzard doesn’t care. They must really think D3 is trash. I’ve played hundreds of hours on Nintendo Switch and PS4. Every once in while I try to play on PC, but quickly realize it is inferior. ALL OF THAT CLICKING OF THE MOUSE IS CRAZY. The controller adds flow. Please add a patch or something. Some people claim it’s impossible. I would laugh in their face IRL.
1 Like
People will make excuses all day. The simple answer is laziness. I asked for controller support many, many years ago. They have a hard time adding new features to games these days I guess. Probably something to do with disgruntled staff quitting the projects.
1 Like
Its called diablo (3) because its hell.
Quite sure the simple answer is resources. It would be a loss to spend them since they would in all likelihood not see a return on the investment.
hello im looking for some help ive recently purchased Diablo 3 on my PC and for some reason whenever i launch the game it loads up but my battle.net account wont connect to it and just says error code 1021 im not sure what to do ive done everything that it says to try and restablish the connection
they are the same game… this sounds like a lazy excuse
1 Like
They are not. Know the history of the game before posting such ignorance please.
I works like a charm in D2R so I want to see the same setup in D3 please…
2 Likes
Yeah, becasue D2R was designed to be played with a controller from the start. It’s not an “easy fix” as some claim just becasue there a console version that has controller support. Yes in the early stages of development(pre 2008) they tested movement with a controller and thought it was smooth but decided not to move forward with it. They would have to do some serious retooling of the PC version of the game to add controller support including reworking the UI, inventory, menus, picking up items, and so on.
D2R and D4 are good templates to look at if they are going to add controller support. I would ignore the D3 console menus and inventory altogether.
Actually, consoles were an afterthought. the game was PC/mac from day one. They spent years in added development to add console support. I’ve been playing since original Diablo hit shelves and following development of Hellfire, D2 & D3 all along the way. If you feel the need to spread false information to others, join the Trump campaign.
1 Like
There are some actual differences in game design between the two versions beyond just the interface and control scheme. The most obvious one is how nephalem glory works completely differently in the console version. They’re not the same game, regardless of what their binary is compiled for.
I consider console D3 overall the better version though. Ever since I got it on switch, I never touched the PC version again.
Controllers weren’t however. There was a Jay Wilson interview where they talked about controlling a very early build with a controller. Unfortunately they never fully went that direction.
