Summary
Can a 3200MB/S ssd run ratchet and clank?
- Yes
- No difference from human standards, data points exist within a margin of error of 1fps
I think this once again highlights the danger of trying use PR in technical discussions.
Only a week or two back we had people arguing that R&C gameplay was not possible on a lesser SSD because ... carefully worded dev tweets seemed to allude to that. Furthermore, that interpretation should be treated as gospel, and so Jon Burton of Travellers Tales was lying and jealous when he accurately talked about how transitions and micro levels could be constructed without such raw speed, by using things like deterministic pre-loading and micro areas built from small footprint, repeated assets.
It just bums me out, because we never learn collectively.
This isn't to say that R&C doesn't look awesome, because it does, or that the transitions aren't handled really well, because they are, or that PS5 SSD isn't great, because it is, or that even more impressive results can't be attained in the future, because they can be.
It's just to say ... ease off on the Cool Aid, and don't have an issue if people question drinking it.
R&C is not the test. Have Sony provided RTOS-like guaranteed API turnaround times for devs that are predicated on I/O bandwidth? What about running R&C whilst capturing video and downloading at maximum throughput..
It is always the worst case scenario that defines minimum standards.
I do agree that R&C isn't the test, and nor should it ever have been presented as the proof.
It's a great looking game, but the speed of the transitions isn't purely down to the raw speed of the SSD (which is really damn good for a
year 2020 console!). I mean, a lot of us could see that, but it wasn't a popular opinion.
MS reckoned that from their 2.4 GB/s for XSX, there was a guaranteed minimum of 2 GB/s at all times for games. Whether that was guaranteed over a second, or a frame, or some other period of times I don't know. I don't expect that PS5 would lose significantly more BW than XSX for the same types of operations.