Old news
2014:
The Xbox One could one day make use of a powerful rendering technique called "real-time ray-tracing," an advanced system used to achieve photorealistic lighting effects. Microsoft Studios executive Phil Spencer has confirmed that internal tests are already underway.
https://www.gamespot.com/articles/x...ring-system-for-amazing-visuals/1100-6418060/
Ok, I have a different view than you do.
It will definitely be interesting picking apart the differences.
Lol that’s an impressive memory you have there. That totally would have flown under the radar for just about everyone here because we know there isn’t enough juice on Xbox.Old news
2014:
The Xbox One could one day make use of a powerful rendering technique called "real-time ray-tracing," an advanced system used to achieve photorealistic lighting effects. Microsoft Studios executive Phil Spencer has confirmed that internal tests are already underway.
https://www.gamespot.com/articles/x...ring-system-for-amazing-visuals/1100-6418060/
Old news
2014:
The Xbox One could one day make use of a powerful rendering technique called "real-time ray-tracing," an advanced system used to achieve photorealistic lighting effects. Microsoft Studios executive Phil Spencer has confirmed that internal tests are already underway.
https://www.gamespot.com/articles/x...ring-system-for-amazing-visuals/1100-6418060/
Old news
2014:
The Xbox One could one day make use of a powerful rendering technique called "real-time ray-tracing," an advanced system used to achieve photorealistic lighting effects. Microsoft Studios executive Phil Spencer has confirmed that internal tests are already underway.
https://www.gamespot.com/articles/x...ring-system-for-amazing-visuals/1100-6418060/
Navis CUs will be smaller on the 32 SIMD wide config.Contrarly to popular believe CUs don't take most of the GPU die, they take around 40% a CU increase its not a linear area increase.
Need to revise my calculations for next generation APUs, I was under the assumption that the non-cpu and gpu portions of the chip would take up a constant percentage of the die, but further research shows that this is not the case. Bus controllers + etc shrink in size too with each node progression. In fact, you can fit a 384 bit bus in less die space as the 256 bit bus on the Pro.
So my new conclusion is that non-cpu / gpu on the next gen console should only be around ~80mm2 (1.8x scaling over the 140mm2 in the ps4 pro) if they don't add extra bus controllers, caches, dark silicon. In a 350mm2 die there should be 270mm2 to use, assuming cpu and Rops take around 100mm2, there is ~170mm2 remaining, which should fit 64 Vega 7 sized CUs with 30mm2 to spare.
New estimates for me is that >330mm2 SOC should be big enough to accommodate 8 core Zen2, 64CUs (4 disabled), 64 Rops.
Another epiphany of the new conclusion is 512 bit bus for the GPU is not crazy out of the world. It's less die space expensive than the 256 bit bus in the base PS4.
So we're straight up limited in next generation by Navi clock speed and the 64 CU limit.
If there is no CU limit, you can do ~100 CUs in a xb1x sized 360mm2 die.
I am not sure how what he said in that tweet means or contradict anything. The tweet doesn't specify that said experiment with RT is on or will appear on X1. If anything this means the platform team has had RT in mind as a future technology with potential way back then. His recent statement in the 2018 vid was a direct statement on what they are working on with regards to the next generation of Xbox in which he name-checks framerate and RT as two things he has in mind for the next gen box.
Sure. But in 2014 we all ignored it. It wasn’t until DXR and We saw RTX demos in 2018 did RT mean anything to the entire gaming community.
Hmmm So perhaps while MS has moved onto Navi 20 (full Navi), PS5 is based on NAVI 10 architecture with GCN to facilitate easier BC. Sony does not have the software stack and software engineering capacity as MS, so perhaps they may have had to go with a more hardware based approach to backwards compatibility given GNM IS an arch specific api originally designed to go low level with Southern Island and GCN 1.0.
