{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
7/29/2020 9:16:58 PM
3
yes, let's store every roll schematic you've discovered in every weapon. What a great use of space, I'm sure that will make loading times better.
English
-
I won't presume to know exactly how Destiny's server data management works, but since this isn't related to pre-load during matchmaking, or asset-load during destination transit, this wouldn't likely affect load times at all.
-
yes. But these are variables and datasets that need to be saved to each bungie account, which will need to be recalled every time you open your collections. Because of the amount of data that every weapon can roll, along with the read speeds on the hard drive of the ps4 or xbox one, it would likely take the average players about 2 minutes for the full dataset to be loaded, meanwhile, server ram, trying to store this data without failure, would fail tremendously, completely reverting the point of the dvc. TL;DR consoles can run it at reasonable speeds. Bungie servers would kill themselves trying to store every players every role of every weapon.
-
Guess we'll see, lots of maybes here, and it's not like we know how the variables are stored or what kind of memory is available within that part of the game. Knowing what weapon perks we've unlocked for a given weapon doesn't necessarily have to be polled for the collections screen; if there was a different subprogram that loaded in order to create your custom weapon, it'd be worth waiting a couple seconds, and wouldn't necessarily affect anything at all.
