Comment on This new 40TB hard drive from Seagate is just the beginning—50TB is coming fast!
sugar_in_your_tea@sh.itjust.works 4 days agoWhen I say “compress” I mean downscale. I’m suggesting they could have dozens of copies of each texture and model in a host of different resolutions (number of polygons, pixels for textures, etc), instead of handling that in the code. I’m not exactly sure how they currently do low vs medium vs high settings, just suggesting that they could solve that using a ton more data if they essentially had no limitations in terms of customer storage space.
When I say “compress” I mean downscale. I’m suggesting they could have dozens of copies of each texture and model in a host of different resolutions.
Yeah, that’s generally the best way to do it for optimal performance. Games sometimes have an adjustable option to control this in game, LoD (level of detail).
MentalEdge@sopuli.xyz 3 days ago
They do.
And that’s completely normal. Every modern game has multiple versions of the same asset at various detail levels, all of which are used. When you choose between “low, medium, high” that doesn’t mean there’s a giant pile of assets that go un-used. The game will use them all, rendering a different one depending on how close to it you are. The settings often just change how far away the game will render at the highest quality, before it starts to drop down to the lower LODs (level of detail).
That’s why the games aren’t much smaller on console. They’re not including all the unnecessary assets for different graphics settings from PC. They are all part of how modern game work.
“Handling that in the code” would still involve storing it all somewhere after “generation”. Same way shaders are better generated in advance, lest you get a stuttery mess. Not to mention that such code does not exist. Human artists produce better results.
Finally automating this is what Unreals nanite system promises to do, but it has ran into snags.