JavaScript is required to use Bungie.net

Service Alert
Destiny 2 will receive an update tomorrow. Players will be required to log in to Destiny 2 again after installing the update. Please stay tuned to @BungieHelp for updates.

#feedback

11/19/2014 1:38:15 PM
5

About the Connection Issues Post-1.0.3

I realize that there are many people screaming on the Forums about the connection issues after the 1.0.3 Update landed. This will not be another post like that. What it [i]will be[/i] is an attempt to articulate the difficulties I've experienced with my connections since the Update arrived a couple days ago. Before the 1.0.3 update, I rarely got the disconnects that the rest of the community suffered. After the update was applied to my copy of Destiny, I have been lucky to have more than two hours of solid game time logged in. Vulture, Weasel, and Ferret have been the downfall of my Destiny experience for the last two days. And it wasn't even really that bad on the day of the update. It didn't get bad until last night. I fist noticed it when first signing on at around 6pm Central time US. It seemed to take an inordinately long time for the game to stabilize my "party" (I was the only player) upon first signing in. Then I teamed up with some of my Clanmates to take on the Nightfall and Weekly Heroic. The Nightfall went alright aside from the framerate dropping into the dirt. It was in the Heroic that the issues started happening. The most noticeable was when we got to the part where we have to kill the Fallen Walker. As we entered the area, like always I jumped on my Sparrow to speed up the left side of the map to a side room with a staircase where I usually go to battle the Walker. It's not a "cheese spot" as are so frequently whined about nowadays, as it is still easy to get nuked by the Walker. But there is some cover and great sight-lines for firing upon the Walker. I was about halfway up the map, and the Walker had literally just bee dropped into the map. As soon as the Walker touched down, my Sparrow vaporized and my Warlock did a faceplant and died. I had taken no shots from the Fallen Captain and Dregs there. I hadn't taken any damage in about five minutes to be exact. But still, the Weasel killed me an forced me into a solid black screen with the loading icon in the lower right corner of the screen. It stayed that way for about three minutes before letting me resume orbit. I tried to rejoin my comrades, but the game wouldn't let me. So, I took a twenty minute break and came back to a Raid invite from some other Clanmates. Awesome. I love the Raid (really, there's no sarcasm there. I truly do love the Raid), and they were wanting to try it on Hard Mode again. I was genuinely excited at this point. So we fight through the Raid with no issues. We get to the Gatekeeper fight, and though we are faring somewhat poorly, all was going fairly well until our party members started getting kicked. One by one, we were ejected from the Vault by Atheon's new Weasel attack and Ferret shot. I was trying to explain to our Clan founder about the issues I was having earlier with disconnects, and apparently the Ferret decided I didn't need to finish my explanation. All of this was around 8 or 9pm Central time last night. Now, our clanmates kicked from the Raid were joining back up with us fairly easily, but Ferret kicked my back to the Title screen where it asked me to "Hit 'A' to play". Fine. After hitting A, it sat on blackscreen for about two minutes, then kicked me right back to the title screen because the Vulture said that my LIVE settings may have changed or my Profile might be signed in elsewhere... that's BS. I have Google Fiber for one. Two; I haven't changed my LIVE settings since I first got the One. Three; I was the only one in my house using the internet, so it wasn't that I was "signed in somewhere else". So I quit out of the App, and restarted it. After hitting A, same thing. Lost connection to the Bungie servers, the vulture ate the Bungie servers... So I went back to the home screen and quit the app again. After about three more minutes in black screen, I got an invite from my Clan founder to rejoin their Fireteam. So I did, and the orbit screen finally loaded. But as we were discussinn what to do, we watched someone else's ship just drift away as they got kicked from the game. We were only in orbit... maybe his ship ran out of gas and he couldn't hold an orbital constant? So, the Clan decided as a whole that the Raid was off for the night. We broke up into smaller groups to knock off some lingering bounties. Myself and two others headed for Mars to get six Patrols done. In the middle of my firefight with a bunch of Cabal, the weasel struck again, followed by two Vultures as I tried to get back on, and another Ferret kicking me back to the title screen finished off my night. It was about 10pm Central time that the final Ferret bit me, and so I went to the Home screen, quit out of the Destiny app, and shut down my console for the night. I love this game, and I sign in and play whenever I get the free time, and definitely for several hours every night. But I can't express my love because I can't stay connected to explore the rich worlds and intriguing story. The Weasel, Ferret, and Vulture are keeping me from enjoying the game right now. Now; this isn't a bitch-fest angst-rant, simply a recanting of what I have experienced since I updated my copy of the game with Update 1.0.3. Hopefully this tale helps you narrow down the issues and get them solved. because I very much want to spend many more hours exploring what you guys have created. I know that you are all busy, but again, I hope this post helps marrow down where it all is going wrong on your servers. Sincerely, Vampire Nox

Posting in language:

 

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

View Entire Topic
  • This is still going on. FFS, it was like this when I was playing at about 1:30 am (gmt) last night, so nearly 14 hours ago. 14 hours. How does it take that long to fix a server connectivity issue? I know it was reportedly an Xbox Live problem, but I'm sure I've seen a few complaints from PSN users too, so I wouldn't be surprised if there were problems on Bungle's side as well. Well, whoever is responsible, 14hrs really isn't good enough.

    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