But it’s a start.īottom line here is that Blizzard proper isn’t very well versed in accessibility yet. In other words, it’s essentially alpha level integration. 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. 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.Īnd if you think it’s “easy”, go check out World of Warcraft’s built in controller “support”. 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. They are developed by a different team altogether. The console versions are also not developed in-house using the Diablo franchise team. 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.
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. (IE: “It’s two separate games”) which is false.īelieve it or not, it actually is two separate games, as far as the game client is concerned. It’s disheartening to constantly read the mis-information when it comes to games not supporting native controller support.
0 kommentar(er)
