" Access to the 7th core requires the October 2014 XDK or newer."
Huh? Hardware encoders likely retrieve frames the same way the display scan-out engine does. The data never touches the CPU. The performance of encoders in smartphone SoCs is also irrelevant when talking about AMD's desktop-class encoder which uses more silicon space (see die images of GPUs with a VCE block, it is pretty big) and runs at higher clocks.
In the October XDK this feature was flagged as Beta though so I doubt you can use it in the final game.
Even way beefier hi-end desktop CPU's can see 10~15% workloads when transcoding video on dedicated logic.
Why couldn't they just release this power from the get go? Does this mean we've had beta software all this time? I'm confused. They've done these performance updates numerous times with non-trivial improvements to power.
Then it will become even more noisy than it is.Good on MS for the continued optimization.
Sony just needs to bite the bullet and upclock the whole system by 10%. I'm sure there's headroom for it.
Good on MS for the continued optimization.
Sony just needs to bite the bullet and upclock the whole system by 10%. I'm sure there's headroom for it.
But doesn't avoid to some DF author to persist with this phantomatic cpu advantage in the multiplat titles. This thing start to be really annoying now.This is pure misinformation and although I can't say to be a great fan of DF even in the past generation, they literally dropped the balls too much for my tastes in this generation.The difference is not trivial either, though. 9% more clock speed on all cores, variable CPU time on a 7th core, and allegedly better compiler performance should add up enough to give it some significance. That's not huge, that's not even much, but it is above negligible.
Wouldn't that be a huge risk? a full 10% upclock in its current form and casing may cause failure to some units.
Good on MS for the continued optimization.
Sony just needs to bite the bullet and upclock the whole system by 10%. I'm sure there's headroom for it.
Good on MS for the continued optimization.
Sony just needs to bite the bullet and upclock the whole system by 10%. I'm sure there's headroom for it.
Because from the get go Kinect was mandatory. I don't see what's confusing here. spencer and Xbox team are systematically paring back as much of the previously mandatory functions around media/Kinect as they can and giving it back to being available for playing games.
Essentially they're working to make the Xbox One more like a PS4 in that it is primarily operating to supporting playing games with other stuff "on the side". Note though that this isn't some free lunch. They're allowing functions to be disabled to do this - so if you are a fan of Kinect and these functions you're going to have to accept some games disabling functions you actually want to use to access the resources. In addition the - current - improvement doesn't allow full access and complicates code operation.
This latest update is basically saying when you're playing games most other stuff is disabled unless I'm reading the info wrong and this is a major change from the OS and operation design at launch.
Of course MS launching with a weaker console due to the media side has been under a lot of presure in this area so its no surprise they're doing this. It's being driven by market results vs PS4.
The PS4 on the other hand at launch was already in better shape in terms of running games as its launch OS and design was already focused on "games first" with media and other functions very much being on the side.
Both consoles would have launched with reserves and MS is also eating into them fast to try and get closer to PS4 operation, something that could result in them getting caught with games that will limit what they can do in future with the OS.
Sony so far as I'm aware haven't' really touched their reserves because they haven't really had to although no doubt they'll be watching with interest. Given the late jump from 4GB to 8GB for them they should have cores/memory reserved for future functions they can chose to release to and it'll be interesting to see if they feel impelled to do so anytime soon.
Anyway the MS moves are welcome because, to be blunt, they reduce chance of Xbox One holding back PS4 titles (multi platform that is) and of course allow developers to produce better games on Xbox. But this does come at a cost in terms of applicability and MS will need to be careful they don't go so all in here they have no maneuvering room in future when they might want some of these reserves back again.
Have the docs on a different computer currently, so...
But if you have it at hand, DF is talking about a timeline and the development of the GPU driver. Feel free to put it in this thread if you found it
Good on MS for the continued optimization.
Sony just needs to bite the bullet and upclock the whole system by 10%. I'm sure there's headroom for it.
Why couldn't they just release this power from the get go? Does this mean we've had beta software all this time? I'm confused. They've done these performance updates numerous times with non-trivial improvements to power.
Did you not bother to read the OP. It's 80% max. Not 50%.
Because the encoded data has to be stored or sent over the network. That's why I write "mostly". But that stuff does not require that much CPU reserve, especially when you already have a dedicated chip for network communication. After all, the XBO is doing exactly the same while running a second OS with apps on now less CPU resources. It's also independent if the source stream being 1080p60 since the encoded stream is just 720p30
I haven't kept up with all of this, so I'm curious, have they talked about/has there been any leaks regarding the future of the 3-in-1 OS at all? That was always the most curious aspect of Xbone as a whole for me. As far as I recall, the system OS was a slimmed down/derivative of Win8, and now with Win10 in the horizon... Well, I'm curious.
But he said exactly that in the post you quoted. Maybe it's relative to the cloud stuff too this upgrade, I just hypotize eh.What the hell are you talking about? 15% overhead on a desktop class CPU just for sending data through network? What is this madness?
XBO has even more dedicated logic for that task than PS4, I have to remind you.
My bad read that element wrong then. It does mean that games that use it will automatically lock out ability to use the functions correct? Although given they probably weren't going to use them I guess it's moot.No OS level Kinect functions are affected with any of this. This is Kinect functionality that was being provided to devs regardless of whether they wanted to use them or not. Devs are not using them, so they are releasing those resources. MS thought that if they made Kinect functionality standard and always there, devs would be more inclined to use them. It did not turn out that way, lol. Once again, this has no affect on OS level Kinect functionality or even media related functionality. In fact, this should have been there at launch even when Kinect was always in the box. Was a silly assumption on MS' part to assume devs would always want to make use of Kinect stuff.
What the hell are you talking about? 15% overhead on a desktop class CPU just for sending data through network? What is this madness?
XBO has even more dedicated logic for that task than PS4, I have to remind you.
My bad read that element wrong then. It does mean that games that use it will automatically lock out ability to use the functions correct? Although given they probably weren't going to use them I guess it's moot.
Pity the acess is variable though - that's not nice from code point of view. I wonder if they shouldn't have picked a fixed amount to free up to make that easier.
No kidding mine is one of those noisy ones and almost at original 360 noise level when playing the more demanding (unoptimized?) games, it'll probably melt if they try getting more power out of it. It should be possible to optimize games to decent framerates without these type of changes. Some devs seem to just dump the PC code at high or even ultra settings and expect the consoles to be able to handle it without choking. Why not just bite the bullet and accept that you can't get high PC level visuals with these consoles and scale things down so at least locked 30fps or 60fps is always there and add as many graphical effects as possible but with some head room left to not melt the console when lots of stuff is happening. Evolution patched an amazing visual weather upgrade to Driveclub without a single dropped frame, that's the kind of head room they should go for.Wouldn't that be a huge risk? a full 10% upclock in its current form and casing may cause failure to some units.
Which? I hope you're not referring to the DMA engines.
Pity the acess is variable though - that's not nice from code point of view. I wonder if they shouldn't have picked a fixed amount to free up to make that easier.
Why not? The move engines are dedicated HW nonetheless additionally to the audio and video codecs
Thanks for cleaning up Y2Kev. It was getting bad in here.
Anyway this is good news for everyone. The better the XBO1 performs, the less likely other platforms will be held back by it.
That would mean more heat and the PS4 is already pretty much on the verge of overheating.
The concrete numbers are yours. Can you substantiate them with evidence? Otherwise I feel free to reject them for the time being.
Which? I hope you're not referring to the DMA engines.
Reject whatever you want so it can fit with your logic.
XBO have custom encode/decode hardware and DSPs. Not shocking news.
This is great news and MS is really doing a lot to make the system more competitive. I wonder if Sony has any plans for optimizing the platform further. It seems they would have done so by now.
Good on MS for the continued optimization.
Sony just needs to bite the bullet and upclock the whole system by 10%. I'm sure there's headroom for it.
This is great news and MS is really doing a lot to make the system more competitive. I wonder if Sony has any plans for optimizing the platform further. It seems they would have done so by now.
Of course they have too. Why not?This is great news and MS is really doing a lot to make the system more competitive. I wonder if Sony has any plans for optimizing the platform further. It seems they would have done so by now.
They've completely replaced the GPU profiling tools over the summer and the recent fall update added more controls for GPGPU functions and had more documentation on GPU based physics. Nothing huge and it's mostly intangible stuff for people that aren't directly working with it while the impact of MS' are more understandable to everyone.This is great news and MS is really doing a lot to make the system more competitive. I wonder if Sony has any plans for optimizing the platform further. It seems they would have done so by now.
I don't know, but I'm ready to read more quote like 'thanks to the beefy cpu stuff added to the majestic ms engineers' at the first casual fps advantage related to the minimal cpu scenario. Take note.Wonderif DF will start adding in extra scenarios to their analysis for XB1 to cater for the 50%-80% availability of the 7th core?
Will they need to shout 'Xbox snap...' while gathering performance metrics to check for impact? Might reveal some interesting insights into how much of the released reserve is being used.
That would mean more heat and the PS4 is already pretty much on the verge of overheating.
Interesting. Let's hope Sony can do something similar. In theory, their OS shouldn't need more CPU power, right?