3 ms·
Um, no. It's not speculation. Many games have been shown to use uncompressed assets, that's an objective fact. The thread might be speculating about _why_ they
by marcellus23 4y ago
Um, no. It's not speculation. Many games have been shown to use uncompressed assets, that's an objective fact.
The thread might be speculating about _why_ they do that, or whether this particular game does that, but that's a non sequitur, that isn't what I was talking about.
- forrestthewoods 4y agoYour statement that some games in the past have used uncompressed assets is a non-sequitur. Has any game in the past 5 years that has an install size >100gb used uncompressed assets? I would be very very surprised! The likelihood of this being the case on PS5 or XSX hardware is approximately zero. Yes I’m familiar with the infamous uncompressed audio in Titanfall.
- terafo 4y agoHitman would be very notable example. Fortnite almost got to 100 gigs when they enabled some kind of asset compression.
- forrestthewoods 4y agoHitman was a special case of bundling older games designed designed for spinning disks. Fortnite didn’t publish what they did. But I promise it’s not “bEnableCompression=true”. Compression is used up and down the stack with the utmost of care. Even the older games that didn’t use compression did so only after great consideration of the trade offs. “Games as a Service” games like Fortnite, Destiny, and Call of Duty have often bloated and then been optimized. The fix is never bEnableCompression. It’s more about how the content is sliced and packaged. How to efficiently serve new content is a really tricky problem. And a somewhat new problem that didn’t exist 10 years ago. At least for consoles.