Even on systems with significant memory, a slow drive will create lag in RC. Moreover, RC is doing this while also having very high graphical fidelity overall, including ray tracing, which is quite memory intensive. It’s not possible without Direct storage and reasonably fast SSDs.
Comment on [MEGATHREAD] Starfield - Your experiences!
Puzzle_Sluts_4Ever@lemmy.world 9 months agoR&C is cool as hell but it is NOT the revelation it was marketed as.
Titanfall 2 and Dishonored 2 had already done almost exactly the same gimmick years prior. And that MyHouse.wad DOOM map that everyone lost their mind over a few years back actually was ALSO doing the same trick. Hell, the Build Engine games (particularly Duke Nukem 3D) were entirely built around this trick.
The reality is not that you are “changing entire dimensions”. It is that the majority of the map is loaded into memory and you are teleporting between parts of it. This has been a solved technology for literally decades. You just have seamless “portals” between different parts of the map. But it boils down to just loading enough assets.
R&C mostly benefited from the larger memory of the PS5 (16 GB of GDDR6 versus 8 GB of DDR5 for the PS4) with the “direct storage” mostly being background in, ironically, the same way Morrowind was: You are loading a few “cells” ahead of you as you traverse the world map so that you never notice a load time (unless you use the boots of blinding speed… or are playing on a console).
rDrDr@lemmy.world 9 months ago
beefcat@lemmy.world 9 months ago
TF2 and Dishonored accomplished this by having all the other level data loaded in memory simultaneously. This means you can only switch between any number of maps you can actually fit in memory, and the more you want to switch between the smaller they have to be.
Being able to instantly load level data from an SSD means each map can use the full memory budget and there are no limits on how many you can switch between.
Puzzle_Sluts_4Ever@lemmy.world 9 months ago
At the end of the day: it is all the same “trick” Morrowind used. You load N cells ahead of where the player is so that they don’t notice the load times because they have been done by the time they get there.
In this case a “cell” could be a room or it could be DM-Deck 16 or it could be all of The Imperial City. It is the same trick. Hell, I think some streaming services even do this at different quality tiers so that you have no delay between one episode and another.
Size of levels is entirely a function of available memory. PS5 had more memory than PS4 and TF2 was targeting PS4 specs (… actually, was that PS3? Let’s say PS4 so I don’t feel too old). Faster load from disk helps a lot but NVMEs alone already get you there, as anyone who has experienced zero load times while playing a game can attest.
Like I said below where I already addressed this exact same point: It is great to applaud accomplishments. But by buying into this “only with the power of direct storage is this possible” nonsense you are not only parroting marketing: you are ignoring the legacy of all the devs who already did this years (really decades) ago.
beefcat@lemmy.world 9 months ago
How Morrowind and other open world games work has very little in common with the approaches used in R&C or Titanfall 2.
This approach has its own unique limitations. In Morrowind, you cannot instantly teleport from one side of the map to the other, in theory that would only be possible between adjacent cells. Otherwise, fast traveling would be instantaneous.
The beauty of what R&C does is that there are no limitations at all. You can almost instantly teleport between any maps the game has. No hacks or trickery beyond the brief animation concealing the 1-2 seconds it takes to shuttle the data from the SSD to VRAM. This is unique, and simply wasn’t possible on spinning rust without radically simplifying your level design and visual package to fit within the limited bandwith.
Puzzle_Sluts_4Ever@lemmy.world 9 months ago
I was going to talk about how the load times are mostly just masked but still there but you acknowledged that.
At which point: Mark and Recall (or any of the Interventions) on an NVME is nigh instantaneous.