1
00:00:00,000 --> 00:00:05,640
100 gigabytes. If you're excited to play a recent AAA title like

2
00:00:05,640 --> 00:00:09,800
Star Wars, Jedi Survivor, Microsoft Flight Simulator, or the latest Call of Duty,

3
00:00:09,800 --> 00:00:13,360
you're gonna have to have well over 100 gigs

4
00:00:13,360 --> 00:00:17,880
of free space on your computer. Even if you've got a healthy two terabytes

5
00:00:17,880 --> 00:00:21,440
of total storage capacity, just having three games installed

6
00:00:21,440 --> 00:00:25,240
would take up over 15% of your disk. Yikes!

7
00:00:25,240 --> 00:00:30,080
But why exactly is it that modern games are so freaking huge?

8
00:00:30,080 --> 00:00:34,080
To answer, we got in touch with some of our friends over at Paradox Interactive,

9
00:00:34,080 --> 00:00:40,440
and we'd like to thank them for their contributions to this episode. Let's start by talking about the main culprit, textures.

10
00:00:40,440 --> 00:00:46,680
If you're a little unfamiliar with how game rendering works, textures are the visuals that wrap themselves around

11
00:00:46,680 --> 00:00:51,600
the shapes on your screen to give you a complete image. For example, a building might be wrapped

12
00:00:51,600 --> 00:00:56,280
in a texture that looks like bricks, or a car might have a texture of metallic paint

13
00:00:56,280 --> 00:01:01,000
for a realistic and colorful look. Well, as processing power has increased,

14
00:01:01,000 --> 00:01:04,320
and we've expected our video games to look more and more realistic,

15
00:01:04,320 --> 00:01:07,840
these textures have become higher and higher resolution.

16
00:01:07,840 --> 00:01:12,320
And if you know how much space a single high-res image can take up on your drive,

17
00:01:12,320 --> 00:01:16,840
well, imagine having thousands of them in order to make sure that everything in your game

18
00:01:16,840 --> 00:01:20,320
looks true to life. There's a hardware component to this as well.

19
00:01:20,320 --> 00:01:25,320
Plenty of gamers are now playing at 1440p or 4K resolution,

20
00:01:25,360 --> 00:01:30,360
and textures have to be designed so that they won't look blurry on these high-res screens.

21
00:01:30,360 --> 00:01:33,600
You can really tell if you walk your character up to a wall,

22
00:01:33,600 --> 00:01:38,720
and it looks like a smeared mess, instead of having sharp-looking bumps and imperfections

23
00:01:38,720 --> 00:01:44,360
like a real wall would. But why can't game developers use space-saving tricks,

24
00:01:44,360 --> 00:01:47,360
like compression, to make this problem a little less painful?

25
00:01:47,360 --> 00:01:51,360
It's actually quite hard to compress down high-res images

26
00:01:51,360 --> 00:01:54,520
without having a noticeable loss in image quality.

27
00:01:54,520 --> 00:01:58,120
Think about how JPEGs often contain unsightly artifacts,

28
00:01:58,120 --> 00:02:02,000
especially when you view them up close, as frequently happens in our games,

29
00:02:02,000 --> 00:02:06,880
like in our wall example before. Although there are ways to lighten the load on the GPU,

30
00:02:06,880 --> 00:02:11,560
such as mit-mapping, these can actually increase the amount of space on disk

31
00:02:11,560 --> 00:02:15,960
that the game takes up. See, mit-mapping is a way to render faraway textures

32
00:02:15,960 --> 00:02:20,120
at lower resolutions, so the GPU isn't working super hard

33
00:02:20,120 --> 00:02:24,520
to render lots of detail at distances where the player won't even notice it.

34
00:02:24,520 --> 00:02:28,120
The problem, though, is that mit-mapping requires multiple

35
00:02:28,120 --> 00:02:34,400
low-resolution versions of the texture that are saved alongside the original high-res image,

36
00:02:34,400 --> 00:02:39,720
meaning mit-mapping can actually result in a 33% increase in file size.

37
00:02:39,720 --> 00:02:43,480
Now, there are games that try to minimize size on disk

38
00:02:43,480 --> 00:02:48,720
by procedurally generating textures. This means that the game uses its own internal logic

39
00:02:48,720 --> 00:02:54,880
to come up with textures on the fly instead of relying on pre-rendered images saved on a disk.

40
00:02:54,880 --> 00:03:00,080
But in photorealistic games, procedurally generating textures, at least today,

41
00:03:00,080 --> 00:03:04,120
takes up a great deal of processing power that's better used for, you know,

42
00:03:04,120 --> 00:03:07,720
actually rendering the game. So it generally isn't done.

43
00:03:07,720 --> 00:03:11,960
It also doesn't help that a game's textures are often stored in a manner that prioritizes them

44
00:03:11,960 --> 00:03:17,200
being easily read by the GPU rather than in a manner that's optimized for saving space,

45
00:03:17,200 --> 00:03:20,440
which is unsurprising, given that storage is relatively cheap,

46
00:03:20,440 --> 00:03:25,720
meaning that developers are far more concerned with making the game look good and run well

47
00:03:25,720 --> 00:03:28,720
than they are with having a small footprint on your SSD.

48
00:03:28,720 --> 00:03:34,160
Combine all of this with the fact that game audio is similarly hard to compress without sacrificing quality

49
00:03:34,160 --> 00:03:40,120
and you have a recipe for space-hogging games, a trend that isn't likely to end anytime soon.

50
00:03:40,120 --> 00:03:43,880
So keep an eye out on deals for storage, I guess,

51
00:03:43,880 --> 00:03:48,760
or you can just stick to playing Minecraft, as long as you don't install high-res texture packs.

52
00:03:48,760 --> 00:03:53,600
Or install liking this video if you liked it, or disliking it if you disliked it,

53
00:03:53,600 --> 00:03:56,980
and leave a comment if you have a suggestion for a future Techquickie video.

54
00:03:56,980 --> 00:03:59,080
Oh yeah, and don't forget to subscribe.