• Hey Guest. Check out your NeoGAF Wrapped 2025 results here!

Destiny will not use Kinect, in favor of improved resolution

From what I understand from the clustermuck communication from MS, the 10% reserve was not being used for voice recognition anyway (Xbox, snap etc. etc.), and the reserve was probably for future functionality and/or as a forced incentive to devs to use Kinect, an already lost computational power that they could use for kinect functions.

This should mean destiny will not use things like kinect's head tracking (peek around corners etc etc.) and stuff like that, but things like "Xbox, please stahp!" should continue to work.
 
I like to remind everyone that the 10% reserve is for kinect + some other system functionalities (Snap...).
 
such a shame Spencer wasn't head of the division when this consoles was going through R&D





is it not possible to relay voice command via a microphone? why do you need a camera to do that?

Microsoft has a new vision because they are getting their ass kicked. Make no mistake that if they weren't you wouldn't be seeing these changes. Now Mr. Spencer was not on a pilgrimage to the mountains seeking the path of the true gamer when all the crap was going on. To say he didn't have a hand in the development of the system well that's disingenuous.
Microsoft needed a new strategy and this is it as of now. Kinect wouldn't have been a problem if the console had beefier technical muscle. Unfortunately its damn telling when you have to pull resources from your biggest differentiator compared to the competition.
 
Hmmmm am now interested to see how respawn will handle this because they have been waiting for this update.

I do wonder what it was before because the 10% reverse(most of it) being given back won't lead to any big increase in res right?

Side note - Sunset overdrive is also using it for something.

I would hope that they would try and use it to improve V-Sync and FPS while in Titans and not the resolution.

But if it hit 900p and nabbed VSync I could live with the in Titan frame drops (maybe dynamic resolution back to 792p when in a Titan?)
 
Why the hell would they use Kinect? They've got three or four other systems to put this on that don't have it. Cross-platform games never use it. This should not come as a surprise to anyone.
 
Interesting. Does this mean that certain games will essentially "switch off" Kinect and associated functions? So if you're playing Destiny Snap, etc. become unavailable?

If so then this could really impact Kinect use/features even for people with the device if it only becomes operable "part time" depending on the game you're running.

As someone who hasn't got an XB1 yet (initial price/features/etc) I'm curious to understand fully what the XB1 without Kinect will be like and what the implications for Kinect are with these sorts of low level alterations to the console's operation.

Yh sounds like something like that might happen which is a bit weird because I was expecting them not to release everything and leave enough for stuff like that. If it works like that there that's a kick to the nuts for early adopters that use kinect a lot for functionality like that.

“Everybody should leave Kinect plugged in,” Spencer explained. “Because as soon as the game isn’t running anymore, you quit the game, you go back to the dash, you are going to have all the great functionality that you ever had.”

Edit -

I would hope that they would try and use it to improve V-Sync and FPS while in Titans and not the resolution.

But if it hit 900p and nabbed VSync I could live with the in Titan frame drops (maybe dynamic resolution back to 792p when in a Titan?)

As far has resolution this is what they said might be possible.

"We've been experimenting with making it higher and lower. One of the big tricks is how much ESRAM we're going to use, so we're thinking of not using hardware MSAA and instead using FXAA to make it so we don't have to have this larger render target," Baker told us.

"We're going to experiment. The target is either 1080p non-anti-aliased or 900p with FXAA. We're trying to optimise... we don't want to give up anything for higher res. So far we're not 100 per cent happy with any of the options, we're still working on it. For day one it's not going to change. We're still looking at it for post-day one. We're likely to increase resolution after we ship."
 
The GPU reserve was for camera processing not for the Microphone.

The GPU reserve was for many things, according to Microsoft.

Xbox One reserves 10 per cent of graphics resources for Kinect and apps functionality, Digital Foundry can confirm, with Microsoft planning to open up this additional GPU power for game development in the future. This, and further graphics and performance-based information was revealed during our lengthy discussions with two of the architects behind the Xbox One silicon.

"Xbox One has a conservative 10 per cent time-sliced reservation on the GPU for system processing. This is used both for the GPGPU processing for Kinect and for the rendering of concurrent system content such as snap mode," Microsoft technical fellow Andrew Goossen told us.

http://www.eurogamer.net/articles/d...unlock-more-gpu-power-for-xbox-one-developers
 
Kudos to MS for taking the steps to help out in this area but they are atill fighting a losing battle...there are still large hardware deficiencies that simply cannot be fixed...and they are still hell bent on fighting a resolution war they can't win instead of focusing on what makes the Xbone unique...
 
Annnddd kinect is dead. Can't believe how quickly ms gave up on their vision. They made an underpowered console for the whole kinect angle, now they just have an underpowered console.


How is it dead? They freed up resources so devs can use the extra horse power if their game is not utilizing it. Makes sense. The way it was before, the reserve was there even if a game did not utilize Kinect, which in a way, didn't make sense at all. You'll still be able to use Kinect for the system level stuff, or at least that's the way I'm understanding it.
 
My guess is the voice commands and snap will still function.

I think this is about motion tracking during games. Which I'm all for ditching.

Yeah totally. It's most likely the constant video processing that's being ditched. The thing that signs people in when they walk in the room etc.
 
I would hope that they would try and use it to improve V-Sync and FPS while in Titans and not the resolution.

But if it hit 900p and nabbed VSync I could live with the in Titan frame drops (maybe dynamic resolution back to 792p when in a Titan?)

I agree. Back before Titanfall came out and they were talking about 900p and even 1080p, I said the same thing. Give me a solid 60fps and no tearing first, if you can do that "AND" increase resolution, then I am all for it. But if it is one or the other, I would take locked 60 and no screen tearing over an increase in resolution.
 
More like: "Like everyone else, we were not going to use kinect functionality, but it's neat we get to use those idle cycles now!"
 
I'd like to see what exactly this means. I'd assumed this was never coming (especially not this quickly) because it would still be needed for all the uses that allow for Kinect during a game even when the game itself doesn't use it. For example (I don't use Skype or Xbox in general, so this may not be possible in the first place) what about Skype calls during a game? Or using snap and having navigation/other apps requiring the camera? Previously I just figured that was why the power was reserved in the first place.
 
Annnddd kinect is dead. Can't believe how quickly ms gave up on their vision. They made an underpowered console for the whole kinect angle, now they just have an underpowered console.
The power gap is due to their memory choices. Kinect never necessitated ESRAM. They fucked this up completely independently.
 
How is it dead? They freed up resources so devs can use the extra horse power if their game is not utilizing it. Makes sense. The way it was before, the reserve was there even if a game did not utilize Kinect, which in a way, didn't make sense at all. You'll still be able to use Kinect for the system level stuff, or at least that's the way I'm understanding it.

The issue is that now it's looking like the Kinect functionality will mainly be for core system functionality. There's now incentive for developers to NOT develop Kinect functions due to getting more power out of the system, and because of the Kinectless SDK there's no guarantee of a "Kinect with every system," so exclusive games that utilize the Kinect are even less likely now.
 
For those who didn't hear this previously...this was always the plan. Microsoft talked right after launch about releasing this computing power to developers eventually. So this is not a reaction to the kinectless xbox...this was an ongoing attempt to free up more power
 
My guess is the voice commands and snap will still function.

I think this is about motion tracking during games. Which I'm all for ditching.

I used to think Kinect had some really cool potential for head tracking and or pointing at the screen to give NPCs commands.. but so far none of that has actually been very good.

So, more power to them.

Curious to see what older games may get a bump. I know Titanfall seems a given, but I wonder if we'll see improvements to BF4, AC4, etc.

shouldn't have needed ditching, because it should never have been a hard reservation in the first place. But still good that it is going.

If they're keeping system level voice controls (I hope they do), then I wonder if games can still use voice commands for free (or close to free)?
 
I don't think losing snap for resource-intensive games is a big deal, but I wonder how the Party app will be handled.

I guess if the game simply pauses when snapped, then that works.
 
So does this mean that games that use the kinect resources, the kinect wont work at all?

Does that mean OS level functions such as ''xbox off'' ''record that'' etc wont work with these titles?
 
http://www.totalxbox.com/77665/dest...-because-it-doesnt-use-kinect-says-microsoft/

Going off tangentially, it's amazing how their stance has changed within a year. They forced Kinect to be plugged in at all times, and now they're essentially phasing it out, with today's SKU and with incentives such as this. At least Spencer gets that it's really only necessary for UI navigation, and with an upcoming update even that might change.

Woah nelly, that's a hell of a reach. Allowing a title to not care about skeletal/controller tracking and reducing the "conservative" gpu reservation that was in day one is not exactly the same as phasing it out now, is it? There's millions already in the supply chain, too.

More like it's being given the appropriate emphasis: an optional add-on that millions will own and millions won't.
 
The power gap is due to their memory choices. Kinect never necessitated ESRAM. They fucked this up completely independently.

Kinect was almost certainly a centerpiece of 'living room control' and I doubt they'd have gone so big on 'one input' without kinect. Without kinect they may not have made the same investment in a separate win8 OS for the dashboard. Without that requirement the OS overhead may have been reduced to the point where they could have used 4GB ram, meaning GDDR5 may have been back on the table.
 
I don't think losing snap for resource-intensive games is a big deal, but I wonder how the Party app will be handled.

I guess if the game simply pauses when snapped, then that works.

games already get a notification when they are snapped, because they can choose to pause the game. So as part of the new SDK, MS will need to update the information so that if developers choose to take back that 10% GPU, they'll need to hand it back when snapped. So they may pause or scale the resolution down etc - I guess it'll be up to them.
 
Ok, I"m concerned that kinect will be disable while the game is running, even if I'm on the home screen. Worst case scenario I would have to close the game to use voice commands again. Midterm, when I'm back to home I can use voice command. Best, voice commands are alwats avaliable when I playing, like now.
 
I understand the pr move for putting this out there but this pretty much forces devs not to use kinect. Now every game that uses kinect gamers will know they are losing 10% gpu "performance".

Xbone really has no power to waste.

"Better without kinect"
 
So does this mean that games that use the kinect resources, the kinect wont work at all?

Does that mean OS level functions such as ''xbox off'' ''record that'' etc wont work with these titles?

No, it doesn't mean that. Most OS functions don't require the reserve. Some that do are (presumably) Snap, gestures and maybe facial recognition.
 
Out of interest - and for the more technical minded of you...

Say a dev decided to squeeze every last drop of that 10% from the GPU.

In the real world, what exactly would that equate to? And how would it affect resolution considering that the main stumbling block appears to be the ESRAM when it comes to output?
 
Will definitely help out for multi platform comparisons, but I'm interested to see the kinect support going forward. Other than kinect sports rivals, has there been a dedicated kinect game? I realize it hasn't even been a year yet, but 360 support wasn't that great either
 
I think if that had been the case the landscape of console gaming would be far more level today. Seems like he's actually listening.

I'm not so sure mind. I think the powers that be at Microsoft had already decided on the all-in-one TV box model. Spencer would have had to work a gaming system around that premise rather than instead of it. That'll have been one expensive box.
 
Woah nelly, that's a hell of a reach. Allowing a title to not care about skeletal/controller tracking and reducing the "conservative" gpu reservation that was in day one is not exactly the same as phasing it out now, is it? There's millions already in the supply chain, too.

More like it's being given the appropriate emphasis: an optional add-on that millions will own and millions won't.



They're officially encouraging developers to NOT use Kinect when their game isn't designed around it. And nobody will be designing games around it unless sales of the Kinect packin soar and the solo box dies immediately. And...that's not happening. This is as close to abandoning the Kinect as you can get before you start leaving them in baskets are fire stations around the country.
 
Out of interest - and for the more technical minded of you...

Say a dev decided to squeeze every last drop of that 10% from the GPU.

In the real world, what exactly would that equate to? And how would it affect resolution considering that the main stumbling block appears to be the ESRAM when it comes to output?

More stable framerate. Some devs might choose to up the resolution. Don't expect 1080p to become common as that's more a limit of the ESRAM.
 
Top Bottom