It took Microsoft two and a half years and over $100 million to develop the Xbox One's controller, according to CVG, talking to Xbox Accessories general manager Zulfi Alam. Were they lacquering them in truffle oil and ambergris?
Hundreds of interviews and iterations have birthed a controller well beyond the desired 360-controller-but-with-a-d-pad-that-isn't-trash. "Honestly, some of us felt like we were putting our career on the line," Alam said. "We were afraid we were going to burn through $100 million and come back with an under-developed controller." No, but maybe not enough money went into planning the actual console, huh?
Of course, the controller is outstanding. Even fans who have been scared off by Microsoft and the Xbox One have shown interest in purchasing an Xbox One controller for PC gaming. As someone who loves both the Dual Shock 3 and 360 pad just fine, I noted the improvements when I used one at E3. It was probably the only thing about the Xbox One at E3 that I did enjoy (note, I didn't play Forza 5).
Unfortunately, according to Microsoft, speaking to GamesBeat, the Xbox One controller won't be compatible with PCs out of the gate. Microsoft is estimating some time in 2014. Vague. Reminds me of a weird inverse of the fact that the Xbox One will, until "the near future," require you to buy a new, One-specific headset. It also continues suggesting Microsoft has had to rush this console launch. At least it means you can wait until the controller goes on sale before rushing out and picking one up, right?
Get more destructoid: We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out
Unsavory comments? Please report harassment, spam, and hate speech to our moderators, and flag the user (we will ban users dishing bad karma). Can't see comments? Apps like Avast or browser extensions can cause it. You can fix it by adding *.disqus.com to your whitelists.