So November 14th it is. 
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I don't know if it is the original source: http://www.theverge.com/2013/5/21/4350578/the-new-xbox-controller
The controller has been updated with 40 design changes, including new dynamic impulse triggers, a newly designed precision directional pad that is more cross-shaped, an integrated battery compartment and a Wi-Fi Direct Radio Stack.
Xbox One passed FCC certification "earlier this summer before PS4", Microsoft's Larry Hryb has revealed, suggesting that the console had been further along in the production cycle than Sony's platform.
X360: 11.22.2005
are Iconic number progressions an MS thing?
XB1: 11.12.2013?(it's also a Tuesday)
Non-standard is better in order to better withstand wireless frequency crosstalk in a busy wireless environment (apartment building, for example). It will still have to deal with other wireless signals in the area, but if it is using proprietary encoding and possibly transmission protocols then it becomes easier to single it out amoung the other wireless traffic in the area.
Can you explain this? In my experience, devices operating in the same bands interfere with each other regardless of the device. In the UK 2.4Ghz (+100Mhz) is unlicensed so most 802.11 protocols are in there, bluetooth is in there, cordless phones are in, some alarm systems are in, other radio remote controls are in there. It doesn't matter they're using standard or proprietary protocols, isolating the carrier frequency you need is equally difficult because the band is saturated with lots of devices all hopping frequencies to find a clearer wavelength.
That's the closest to my birthday so it sounds good to me.So November 14th it is.![]()
GAF has:I just read XB1 is launching with Kinect voice support in five countries, need a link or verification though.
Edit: Found several links in google, but how do you get the address from the nasty redirect version? (can't go to the page itself through proxy).
MS are willing to release to 8 countries without voice support (unless the localisation excuse means something more, like translating the manual...). One also has to wonder why not support AUS and NZ, and why isn't MS ready with voice controls way ahead of time? What's Kinect 2/XB1 doing different to XB360 existing voice support that MS appear to be starting from scratch?MS said:"We want to ensure our customers get the best Xbox One experience the first day it is available. In order to meet initial demand and deliver the best product and experience for consumers, we are narrowing our November launch from 21 countries to 13."Xbox One will launch first in the US, Canada, Mexico, Brazil, Australia, New Zealand, United Kingdom, France, Germany, Spain, Italy, Ireland and Austria in November 2013. The system will launch in other markets, including Russia, Belgium, Netherlands, Switzerland, Sweden, Norway, Finland, and Denmark in 2014.
Interesting. Kinda puts the kibosh on the idea that it's localisation limiting countries than, if MS are willing to release in some countries with a sub-par experience.
http://www.xbox.com/en-US/xbox-one/get-the-facts
Bottom of the page, footnote #6.
"Xbox voice commands will not be available in all markets on the product release date. Voice commands will be available at launch in US, UK, CA, FR, and DE."
If the reason to exclude Benelux and Scandinavia is a lack of voice commands, why release the console without voice commands in 8 countries? AUS and BRZ et al are getting the hardware without voice support, so why not do the same with tier 2 countries? Unless it's literally a few days until the patch goes live for those non-supported tier one countries, so unavailable on the release date as per the factsheet, but still available at launch. That could be it.Doesn't the fact they're having so much difficulty with voice commands localization that they've now restricted it to only 5 countries at launch actually back up the idea of localization difficulties? That was my first take.
Doesn't the fact they're having so much difficulty with voice commands localization that they've now restricted it to only 5 countries at launch actually back up the idea of localization difficulties? That was my first take.
Either way it's signaling to me that Microsoft is relatively unprepared for this launch.