They literally confirmed the expansion card runs at the same spec as the internal one, there is no "very high" chance of otherwise
Two things about this sdd viewport streaming comment. Its not exclusive to PS5 and I'll tell you why.
1. The XSeX is said to be capable of 4.8 GB/s compressed sdd loading. In half a second that gives you 2.4GB of compressed data you can swap out, just 1.6 GB shy of what Cerny said would be required for nextgen games on the ps5.
2. The XSeX features machine learning assisted smart loading of PORTIONS of assets in view with the Sampler Feedback Streaming feature. See below.
Sampler Feedback Streaming (SFS) – A component of the Xbox Velocity Architecture, SFS is a feature of the Xbox Series X hardware that allows games to load into memory, with fine granularity, only the portions of textures that the GPU needs for a scene, as it needs it. This enables far better memory utilization for textures, which is important given that every 4K texture consumes 8MB of memory. Because it avoids the wastage of loading into memory the portions of textures that are never needed, it is an effective 2x or 3x (or higher) multiplier on both amount of physical memory and SSD performance.
I don't understand how so many are missing the point here.
This more or less means, if it works, that where the PS5 may require 4 GBs of asset data to display a changing scene, the XSeX may need no more than 2 GBs....
Meaning their streaming rate as the viewport changes would be able to keep up with what PS5 is doing because it's effectively leaner to display a scene.
Am I the only to pick up on this or did I completely misunderstand something in the I/O breakdowns?
Yep. you did misunderstand.
1. SFS can only load textures. It's actually a well known Partially Resident Textures in disguise.
2. It can load only whole mip levels, IIRC. While PS5 can load any type of buffers.
3. It still uses filesystem and requires a lot of effort to support. While PS5 loads are fully transparent: source, target - load.
4. The 2x, 3x multiplier is a virtual multiplier. It doesn;t make XSeX faster. It's the same. Peak load for PS5 controller is 22Gb/sec, which is 10x multiplier from 2.4 GB/sec on XSeX. It doesn't mean much.
Overall XSeX solution is a very partial implementation of what PS5 has, and more than 2x times slower.