Slashdot Mirror


Microsoft Relaxing Xbox One Kinect Requirements, Giving GPU Power a Boost?

MojoKid writes "News from gaming insider Pete Doss is that Microsoft is mulling significant changes to the restrictions it places on developers regarding the Xbox One's GPU. Reportedly, some 10% of total GPU horsepower is reserved for the Kinect — 8% for video and 2% for voice processing. Microsoft is apparently planning changes that would free up that 8% video entirely, leaving just 2% of the system's GPU dedicated to voice input. If Microsoft makes this change, it could have a significant uplift on system frame rates — and it's not clear that developers would necessarily need to patch the architecture to take advantage of the difference."

5 of 220 comments (clear)

  1. Re:Still lightyears off of today's PC hardware by fuzzyfuzzyfungus · · Score: 5, Interesting

    " Toying with 8-10% GPU consumption is insignificant in the big picture."

    I suspect that MS (and Sony) have no expectation of pulling a miracle out of their hat, or doing anything about the fact that consoles always become increasingly unimpressive vs. PCs as their release period drags on. However, given that MS is currently facing a modest; but somewhat embarrassing, graphical prettiness gap vs. Sony, they have a certain incentive to free up what they can to ensure that any comparisons are as flattering as hardware choices far too late to change will allow them to be.

  2. Re:Still lightyears off of today's PC hardware by Kartu · · Score: 5, Interesting

    Fact remains that even moderate PCs today outperform both the PS4 and Xbox One at a similar price point.

    I'm not quite sure about that.
    PS4 has a GPU that is between AMD 7850 / 7870, when building your PC you'd pay 150+ Euro for the GPU alone.

    Despite "common knowledge" that "PCs are faster", at least if we can trust Valve's statistics (about a third of their PC users run games on an integrated GPU!), no it isn't.
    7870 is a good mid range GPU these days even in PC world.
    One could argue about underwhelming CPU part , but 8Gb GDDR5 and software written to use most of it's 8 cores makes up for it.

  3. Re:Still lightyears off of today's PC hardware by Firethorn · · Score: 4, Interesting

    Despite "common knowledge" that "PCs are faster", at least if we can trust Valve's statistics (about a third of their PC users run games on an integrated GPU!), no it isn't.

    Consider how many laptops are out there... My laptops have both integrated and dedicated GPUs, depending on when Steam's survey comes up they can get quite different results. For that matter I've been playing quite a few 'casual' games that shouldn't stress ANY CPU on my laptop.

    Also, to echo the AC - Source on the 7850/7870 thing? I know that all of my cards from the last 5 years handles 1080P rendering just fine.

    --
    I don't read AC A human right
  4. I can't be bothered with either by Viol8 · · Score: 5, Interesting

    From what I've seen the improvement in graphics from my PS3 to the PS4 or XB1 just isn't enough to justify spending the money on a new console. I think like a lot of people I'll be skipping this generation and seeing what comes around in the next 5-10 years.

  5. Re:Too little, too late by stdarg · · Score: 4, Interesting

    The vast majority of my time on the Xbone so far has been in the Amazon Instant Video app. It turns out that the Kinect is (or rather, could be) a great tool for occasional user input. The irritating thing about using the controller in this scenario is that it turns off after some period of inactivity (which is still long enough that your battery drains pretty quickly). So if you want to pause, or move on the next episode, you have to turn on the controller and let it sync wirelessly with the console, which takes a good 5 seconds.

    Enter the Kinect.. now you can say "xbox pause" and it pauses. "Xbox play" resumes. "Xbox stop... yes... episode 6" goes to the next episode.

    In theory.

    The problem is, seemingly at random, one of the commands won't work. It opens up the xbox voice control screen which has some generic commands. It might say something like "Play is not available from here" or something. After many minutes of frustrating experimentation, it turns out that sometimes you have to say "select" before giving the same command that may have worked 2 minutes ago. So it's like, "xbox pause" then a few minutes later "xbox play... xbox.. xbox select.. play." That's dumb.

    The other problem is the app needs to be intelligently designed for voice control. Amazon Instant Video is NOT one of these apps. The voice commands map pretty directly to the controller commands, but of course the controller is much faster than the voice recognition. A good example of where that's annoying is rewinding and fast forwarding. "Xbox rewind" starts rewinding.. at 2x speed. So if you want to skip back 30 seconds, it'll take 15 seconds to do so. That's no good. So you can say "faster" which increases the speed. Of course, it takes the xbox a second to recognize the command. If you're rewinding 10 minutes, you end up saying "faster [pause] faster [pause] faster [pause]." It's obscene sounding and it takes forever. Then you let it go for a few more seconds... and "play!" But the voice control just timed out, so it's still rewinding. "Xbox play!" and a second later it starts, but you rewound a few minutes too far. And it's too much of a bother to fast forward.

    But that's mostly the app's fault, not the Kinect's.