▲ 56 ▼ Arrowhead is public beta testing a "slim" PC version of Helldivers 2 which reduces install size from 154 GB to 23 GB (store.steampowered.com) submitted 11 months ago by GhostlyPixel@lemmy.world to c/helldivers2@lemmy.ca 16 comments fedilink hide all child comments See link for instructions on how to join the test
[–] GhostlyPixel@lemmy.world [S] 10 points 11 months ago* (last edited 11 months ago) (3 children) 154 GB to 23 GB permalink fedilink source hideshow 3 child comments replies: [–] TriangleSpecialist@lemmy.world 8 points 11 months ago (2 children) And that's just by removing unused assets, not doing anything clever /s Jokes aside, a pet peeve of mine is how most of my colleagues seem to think memory is free, and that if something is too computationally intensive, too bad, nothing we can do but wait for the hardware to "catch up". So it's good to see some effort to curb the insane (and useless) memory requirements of modern games from time to time. permalink fedilink source parent hideshow 2 child comments replies: [–] essell@lemmy.world 2 points 11 months ago (1 child) Memory requirements? Or hard-drive? Would this change impact on both? permalink fedilink source parent hideshow 1 child comment replies: [–] TriangleSpecialist@lemmy.world 4 points 11 months ago Sorry I was ranting about a couple loosely related things (which have more to do with a general attitude of the industry) and thus was not clear. What I meant to say was that I speak a lot with programmers who treat resources (be it computational, RAM, or disk space) as free and infinite. This is indeed only about disk space (as far as I can tell). Although, their post does explain that the reason for the bloated build was to speed up loading times with duplication of data (if fact they quadrupled it even) because they were allegedly afraid of the loading times on older HDDs. permalink fedilink source parent
[–] TriangleSpecialist@lemmy.world 8 points 11 months ago (2 children) And that's just by removing unused assets, not doing anything clever /s Jokes aside, a pet peeve of mine is how most of my colleagues seem to think memory is free, and that if something is too computationally intensive, too bad, nothing we can do but wait for the hardware to "catch up". So it's good to see some effort to curb the insane (and useless) memory requirements of modern games from time to time. permalink fedilink source parent hideshow 2 child comments replies: [–] essell@lemmy.world 2 points 11 months ago (1 child) Memory requirements? Or hard-drive? Would this change impact on both? permalink fedilink source parent hideshow 1 child comment replies: [–] TriangleSpecialist@lemmy.world 4 points 11 months ago Sorry I was ranting about a couple loosely related things (which have more to do with a general attitude of the industry) and thus was not clear. What I meant to say was that I speak a lot with programmers who treat resources (be it computational, RAM, or disk space) as free and infinite. This is indeed only about disk space (as far as I can tell). Although, their post does explain that the reason for the bloated build was to speed up loading times with duplication of data (if fact they quadrupled it even) because they were allegedly afraid of the loading times on older HDDs. permalink fedilink source parent
[–] essell@lemmy.world 2 points 11 months ago (1 child) Memory requirements? Or hard-drive? Would this change impact on both? permalink fedilink source parent hideshow 1 child comment replies: [–] TriangleSpecialist@lemmy.world 4 points 11 months ago Sorry I was ranting about a couple loosely related things (which have more to do with a general attitude of the industry) and thus was not clear. What I meant to say was that I speak a lot with programmers who treat resources (be it computational, RAM, or disk space) as free and infinite. This is indeed only about disk space (as far as I can tell). Although, their post does explain that the reason for the bloated build was to speed up loading times with duplication of data (if fact they quadrupled it even) because they were allegedly afraid of the loading times on older HDDs. permalink fedilink source parent
[–] TriangleSpecialist@lemmy.world 4 points 11 months ago Sorry I was ranting about a couple loosely related things (which have more to do with a general attitude of the industry) and thus was not clear. What I meant to say was that I speak a lot with programmers who treat resources (be it computational, RAM, or disk space) as free and infinite. This is indeed only about disk space (as far as I can tell). Although, their post does explain that the reason for the bloated build was to speed up loading times with duplication of data (if fact they quadrupled it even) because they were allegedly afraid of the loading times on older HDDs. permalink fedilink source parent
