{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
1/27/2020 1:22:35 AM
6
I run a pretty powerful pc with high end ssd’s and NVMe and I can still suffer with ridiculous load times into strikes and the tower.
I believe it’s a network issue.
English
-
PvP activities won't begin until all players have loaded into the instance, otherwise having an SSD would provide an unfair head start. If you have Destiny 2 installed on an SSD but get matched with other players who have it installed on an HDD, you will experience longer loading times in Crucible matches compared to the Tower or patrol zones.
-
[quote]PvP activities won't begin until all players have loaded into the instance, otherwise having an SSD would provide an unfair head start. If you have Destiny 2 installed on an SSD but get matched with other players who have it installed on an HDD, you will experience longer loading times in Crucible matches compared to the Tower or patrol zones.[/quote] So how do you explain long load times into the tower and strikes? I don’t see any advantage there.
-
It takes time to synchronize the connection between that many players in the Tower.
-
strikes have 3 players loading and the tower is a mystery
-
Could be network congestion, or some of the code is old and timing out before it allows the new code to run. Hard to tell without having their internal network access, but I see things like this that cross platforms in websites, and it's usually some old code everyone forgot about, or didn't want to take the time to update that just hangs on the server till it hits a 30 second timeout. Then everything is normal speed.
-
Yea, I’d put money on old code. Ever since Shadowkeep dropped there’s been no end of technical issues. Personally I think bungie have lost a lot of experience since the split with Activision and losing the two studios that were supporting bungie.
