anexanhume
Veteran
“In things like Arden’s test result, you can see the letters ‘Raytracing’.”
Its already like that for Xbox One X. This is a terrible wording though."CPU Built-in with DirectX 12.X, DXR, DirectML and Havok instructions into the chip."
The credibility is dwindling....
Not additional instructions; less work rather."they integrated dx12 into the chip"
I don't understand what that means, what additional instructions could possibly be so application-specific on a cpu?
To help developers get the most out of Scorpio, Microsoft has moved the GPU command processor—the hardware that takes instructions from the CPU and funnels them through to the graphics core—over to a DirectX 12-optimised solution. In theory, this will massively improve draw call performance on Scorpio, and cut down on CPU overheads.
"We essentially moved Direct3D 12," Microsoft told Digital Foundry. "We built that into the command processor of the GPU and what that means is that, for all the high frequency API invocations that the games do, they'll all natively implemented in the logic of the command processor—and what this means is that our communication from the game to the GPU is super-efficient."
So what does this all mean? What kind of performance boosts can we expect in DX12 games like Gears of War 4, Halo 5: Guardians, Battlefield 1, and Forza Horizon 3 while running on Project Scorpio?
Microsoft told Digital Foundry's Richard Leadbetter that Project Scorpio's DirectX 12 hardware implementation should cut CPU workloads by half on DirectX 12 games.
"Roll call instructions on the CPU that would typically require thousands of instructions are now reduced to just 11," Leadbetter said in DF's exclusive Scorpio reveal.
"State changes that are also heavy on CPU are now cut down to just 9. Microsoft tells me that this custom hardware automation should cut CPU workload by half on titles built on DirectX 12 renderers."
https://arstechnica.com/gaming/2017/04/Xbox-scorpio-hardware-specs/
The wording of your post makes it sound like the CPU was enhanced. Instead, the GPU had hardware DX12 enhancements, moving the work from the CPU to the GPU. So how does that tie in with a new SOC having a CPU that has DX12 built in? Surely MS will again place the DX12 hardware in the GPU command processor. Similarly, what Havok enhancements fit on the CPU when the last demos were showing compute based Havok?Not additional instructions; less work rather.
"they integrated dx12 into the chip"
I don't understand what that means, what additional instructions could possibly be so application-specific on a cpu?
I can only assume this is what the leaker implied. I've only been looking at the SOC.new SOC having a CPU that has DX12 built in?
haha fair enough.That's an interpretation that better fits what you expect than what's written. Why group those things with the CPU rather than the GPU or the SOC? Rationalising nonsensical pastebins is of course a hobby, but authentic leaks probably won't require us to join the dots in different ways to find a workable interpretation.
I generally don't trust any leaks; most of them are made with information perusing forums and like you suggest it's their interpretation of what they read likely.Note I'm not saying it's not true. Could be true with the leaker not technical enough to present it accurately. But I'm totally with MrFox that credibility is dwindling with each peculiar notion that appears in a rumoured spec. Looking at just the numbers and ideas, what's the plausibility like? Seems pretty reasonable to me, assuming hardware features for DX12 on the SOC as you suggest. 52 CUs (56 CU chip, 4 for redundancy) at 1.6 GHz and 275 W total? What lithography is going to enable that? And then the little things like two HDMI ports.
How does it work ? do they exclude the 2GB reserved for the SSD cache ?24GB GDDR6 @ 560GB/s
I call bulloks just because nobody at this point can forecast a so precise final gpu frequency based on an ES of a not yet released architecture