They have to go gold in like 3 weeks or less to hit release. It surely would have been locked down by now.
(RUMOR) Xbox One GPU reserve getting smaller soon, down from 10% to 2%
- Thread starter artist
- Start date
SwiftDeath
Member
I was under the belief that framerate is usually the last aspect finalized in game development and that resolution would have had to be decided on earlier in the development process? Perhaps not though
My main thought in this is that the whole 10% thing is a reserve in the first place - as though to suggest "this is the absolute maximum performance these functions could ever need," so I'm just a bit dubious that the snap functions were ever that great of a drain on resources to use the entirety of the reserve to begin with, outside maybe when snapping video. Hence why I figure these performance hits I'm proposing would be fairly negligible ones.
Maybe ElTorro/gofreak/someone else from TechGAF might have better/more interesting insight on this.
EDIT: wow i used "in the first place" like four times in one sentence
Chobel
Member
From 10% to 2% (80% reduction), that one of a hell optimization!
Dragonborn
Member
I get the feeling the 360 version is being kept under wraps because it's either a horrible mess or a great port. If it's a terrible mess, obviously they wouldn't want that getting out there. If it's a great port (and assuming the X1 version is 720p/60fps), then that'd mean the gap between a last gen, 8 year old console and a brand new next gen console isn't that big (at least, on this game) which would put the X1 in an even more embarrassing position.
This is a pretty big change to come so quickly. Usually it takes considerably longer for changes to start coming and they're often far more incremental than this.
cutting down features to allocate more power isn't optimization .
BWJinxing
Member
Id figured better automated ESRAM management would have been a priority. Well its a start.
8% wont raise resolutions but should enable small to semi moderate FPS gains.
Its highly unlikely MS would remove snap, that would give MS negative PR. Snap is more of a CPU-bound feature anyway, think of a PC.
8% wont raise resolutions but should enable small to semi moderate FPS gains.
Its highly unlikely MS would remove snap, that would give MS negative PR. Snap is more of a CPU-bound feature anyway, think of a PC.
ultratruman
Banned
8% of 1.2e+12 = 96,000,000,000 (96 gigaflops (not megaflops))
rakkadakka
Member
Xbox One was born in Kenya
infiniteheteroskdasticity
Member
Erm.... that's 96 Gigaflops.
TheLegendary
Member
. Hope this doesn't affect multitasking/snapping. MS better still to focus on those unique features. Was hoping they'd really overhaul it and add more functionality, maybe like adding the ability to snap video transparently like a movable PIP instead of having it framed, etc If this was just was allocated for Kinect skeletal tracking I'm not as concerned.
SwiftDeath
Member
Kazuma Kiryu
Member
Because that's not what the rumor is saying. It's saying they're going to split the resources into audio and video and are going to allow developers to not use them.
This is hardly "optimization" at all.
I use it 90% of the time while playing most games. I've got my PC plugged into the HDMI in and I just half-watch internet videos while playing. It's great.
miDnIghtEr20C
Banned
So it's been confirmed, or pretty much in the know what features will be cut?
ultratruman
Banned
nothing is confirmmed.
SEGAvangelist
Member
I'm wondering if "video" refers to the Kinect camera and not video as in Netflix, cable etc...
Yeah, that's what I'm wondering too. I assume that it's both but kinect camera features would seemingly use more power than video snapping.
OverHeat
« generous god »
more then 1/3 of the 360 GPU
And if it is kinect. Then another step toward kinectless sku
Chobel
Member
Well, I wouldn't call Netflix, cable...etc "audio".
ultratruman
Banned
You're right, it's 1.31 post-upclock.
Kazuma Kiryu
Member
Could be. I guess it depends on what they value the most, snap or kinect.
What we really need is some proper leak about this stuff.
gigantor21
Member
#dead
You know, I always wonder how the hardware makers allocate resources in the early days. It sounds like that was a real problem for devs when it came to the launch titles, as it was a constantly moving target.
SEGAvangelist
Member
They don't use Kinect video features, though.
Developing a game for launch is the worst scenario for any dev. Super tight deadlines, constantly shifting targets, and multiple dev kit configurations over time.
ultratruman
Banned
Hopefully that's all it takes to lockdown Titanfall's framerate.
Not really. Video kinect features are different from voice with kinect and the latter is used for a large portion of the Xbox UI when (and outside of) playing games.
Games that aren't motion controlled shouldn't have to be impacted by the video kinect functions and games that are motion controlled would still be in a better position (sales) via each Xbox One having kinect.
SEGAvangelist
Member
This is what I'm thinking too. Titanfall won't use ANY Kinect features, so I wonder if this is the first game launching that has the Kinect camera resources open. And yeah... we really need a solid leak on all this stuff. I'm so curious now!
Dragonborn
Member
$300-350 without Kinect (to make up for the inferior hardware) or $399 with Kinect included would be good. Doubt option 1 will ever happen (and even if they do, they'll still overprice at at $399 without Kinect).
ultratruman
Banned
I don't know a lot about computers, but I wouldn't have thought voice-processing would've required any use of the GPU. Isn't that sort of processing usually done by the CPU or a dedicated audio chip?
Hidden One
Member
Gonna suck for MS when Titanfall 2 comes out on PS4.
infiniteheteroskdasticity
Member
100GF is way too much for Snap features. My guess is it was a 8% GPU time reservation for Kinect to use for high precision motion tracking ie skeletal database matching. That would be extremely computation heavy and my guess is that Microsoft assumed that all devs would want to use this at all times.... because Kinect is so awesome and we all like doing everything by waving our arms around
. Now that they've noticed that the overwhelming bulk of Kinect usage is via voice commands, they're making it dependent on the dev to reserve in the rare title that uses it. I doubt snap is affected at all by this.
j/k
SEGAvangelist
Member
GPGPU is using a portion of the GPU like a CPU pretty much.
Chobel
Member
So this means TF or any that uses this extra resource , won't have any kinect motion control?
Interesting .
ultratruman
Banned
Maybe this answers my question as to why the GPU is required for voice, the mic likes to know where sounds are coming from in the room right?
SEGAvangelist
Member
The only games that even really use this stuff are Dead Rising 3, Battlefield 4, Crimson Dragon and Zoo Tycoon I think. It's not a huge loss at all for many existing games.
Respawn already announced Titanfall will have NO Kinect support during VGX. More fuel for the fire.
Does seem like a 'fuck, is there ANYTHING we can do?' type of change.
Chobel
Member
fastford58
Member
Absolutely. It's going to happen eventually, probably by the end of the year.
More than likely. As I said earlier, games that don't need kinect motion shouldn't have to suffer.
If snap is left intact. Then it's a win win situation for gamers and dev.