Activision has moved to explain the enormous file sizes Call of Duty fans can expect to hit their hard-drives with the launch of Modern Warfare 3 this month.
This is due to the increased amount of content available day one, including open world Zombies, support for item carry forward from Modern Warfare 2, as well as map files for current Call of Duty: Warzone. (Note: as part of our ongoing optimization efforts, your final installation size will be actually smaller than the combined previous Call of Duty experiences).”
I would understand a 100 or so GB but 230 for something like Mw3 sounds a bit bloated.
Even GTA 5 is smaller and has probably more nooks and crannies than the first map of Mw3.
Game size are not determine by the size of the map most of the time but the amount of assets you kept inside the shipping build. Usually the size of the files ranked are textures, audios(especially if you support multiple language), cinematic (pre-rendered), animation.
edit: MooseBoys reminds me how much cosmetics we have now in our games.
edit2: If game engine allows artist to paint over game world and save painted virtual textures tiles for location decoration purpose, texture will scale with game map size, see my response below using BG3 as example.
It really depends on game types, most of story driven game audio still out size textures cause they can’t use more compressed version like say, Apex Legend. But yeah if we judge most played game in steam ranking would have textures over audio since GaaS games have tons more cosmetics than gun bullet sounds. But if we check say BG3, Alan Wake 2 or Spider Man 2 then audio should win pretty easily. (But, if game have lots of weapons with pre-recorded clip for firing sound for each gun and interaction sound like, reload, jam, idle fiddling, the audio also tends to win pretty convincingly. Many GaaS game use pitch and/or mix head/tail to make you feel like you aren’t looping the same firing audio, but it’s not as good as from sampling from actual recorded clips. those have their own issue as well. )
Will be interesting what GTA6 will bring to the table. The visual fidelity will probably surpass and be as big as RDR2.
If GTA6 doesnt surpass MW3 I feel like it has no place to be bigger. Even if MW3 supports multi-dub, cinematics, etc.
Actually, my statement might be a bit wrong regarding map size once I think more carefully. Modern trend that allows artist to directly paint on game world could create really heavy virtual texture assets that scale with size of the world. Games that approach “unique” look or feeling per area without making you feel they reuse or have tileable textures all over the place tends to use this as you can just stream in textures that mask over tileable and make it looks really decorated for that area. They basically trade file size with artist freedom.
One example is BG3, where the VirtualTextures_*.pak have 18 files, 72GB. While normal asset textures has only 4 pak files and aobut 13GB.
TLDR:
This is due to the increased amount of content available day one, including open world Zombies, support for item carry forward from Modern Warfare 2, as well as map files for current Call of Duty: Warzone. (Note: as part of our ongoing optimization efforts, your final installation size will be actually smaller than the combined previous Call of Duty experiences).”
Sounds like something marketing would write lol
Because a dev would write a technical explanation which would be translated by game journalists into “my boss sucks”
Yeah certainly would have been written by them.
I would understand a 100 or so GB but 230 for something like Mw3 sounds a bit bloated.
Even GTA 5 is smaller and has probably more nooks and crannies than the first map of Mw3.
Game size are not determine by the size of the map most of the time but the amount of assets you kept inside the shipping build. Usually the size of the files ranked are textures, audios(especially if you support multiple language), cinematic (pre-rendered), animation.
edit: MooseBoys reminds me how much cosmetics we have now in our games.
edit2: If game engine allows artist to paint over game world and save painted virtual textures tiles for location decoration purpose, texture will scale with game map size, see my response below using BG3 as example.
Textures have been the biggest size contributor by far for a while.
It really depends on game types, most of story driven game audio still out size textures cause they can’t use more compressed version like say, Apex Legend. But yeah if we judge most played game in steam ranking would have textures over audio since GaaS games have tons more cosmetics than gun bullet sounds. But if we check say BG3, Alan Wake 2 or Spider Man 2 then audio should win pretty easily. (But, if game have lots of weapons with pre-recorded clip for firing sound for each gun and interaction sound like, reload, jam, idle fiddling, the audio also tends to win pretty convincingly. Many GaaS game use pitch and/or mix head/tail to make you feel like you aren’t looping the same firing audio, but it’s not as good as from sampling from actual recorded clips. those have their own issue as well. )
Will be interesting what GTA6 will bring to the table. The visual fidelity will probably surpass and be as big as RDR2.
If GTA6 doesnt surpass MW3 I feel like it has no place to be bigger. Even if MW3 supports multi-dub, cinematics, etc.
Actually, my statement might be a bit wrong regarding map size once I think more carefully. Modern trend that allows artist to directly paint on game world could create really heavy virtual texture assets that scale with size of the world. Games that approach “unique” look or feeling per area without making you feel they reuse or have tileable textures all over the place tends to use this as you can just stream in textures that mask over tileable and make it looks really decorated for that area. They basically trade file size with artist freedom.
One example is BG3, where the VirtualTextures_*.pak have 18 files, 72GB. While normal asset textures has only 4 pak files and aobut 13GB.
@nanoUFO@sh.itjust.works put this bit in the description!