JavaScript is required to use Bungie.net

Forums

8/19/2014 10:39:49 PM
1
Halo 3 is a prime example as to why a developer might prevent their users from installing to the HDD. This will explain the technical reasoning behind it. http://halo.bungie.net/news/content.aspx?type=news&cid=16252 So any game that handles it's resources in the same manner will suffer the same decrease in performance. So let's take a look at Titanfall. On the 360 Titanfall requires a mandatory install for its HD textures. Since it is mandatory that the package be present on your HDD to play then even if you installed it to the HDD it would want that package to be there. So now you have that one arm trying to read from two different parts of the HDD problem again. To fix that they would need another build which doesn't require you to install that texture pack. So this build would be the one that requires a mandatory full install of the game. Basically I think it is the devs catering to the users that don't have large HDDs. Remember a lot of 360 packages didn't have large HDDs out of the box. A lot of these people may not have upgraded their HDD either so a game requiring a 20GB or 30GB mandatory install would turn them away instantly and piss off those that bought it and can't play. Especially since external drives have a max of 16GB of storage.
English

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

  • And yet, it has already been confirmed on Amazon that it requires an install of 20GB and that you cannot play Destiny on, and I quote : "- Xbox 360 arcade console - Xbox 360 4GB console - Xbox 360 core system" Here's the link : http://www.amazon.co.uk/ACTIVISION-Destiny-Xbox-360/dp/B00BF95Q90/ref=pd_rhf_gw_p_img_2 So, given that, what do you think will be the case come release?

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon