{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by springfinger:
9/6/2015 9:25:06 AM
4
Nightingale
Hi all,
Does anyone have experience with constant Nightingale errors? Destiny basically stopped loading up and now just craps out when checking for updates at sign-in. I've done all the usual troubleshooting steps and then some. I have pretty solid Internet, 200Mbps down/20-50 up, zero packet loss, open NAT. I haven't found much info on this error save Bungie's own help article (relaunch Destiny, restart Xbox/clear the cache or reinstall Destiny) no combination of which worked. I even reset my Xbox to factory which wiped the HD. I've reinstalled Destiny several times on the internal Xbox1 HD and even tried my external 2T 3.0 MyPassort HD, but despite downloading perfectly fine each time I get Nightingale as I 'press A to play' ...connecting...signing-in..checking for updates...Nightingale every time. Any ideas or suggestions would be more than welcome, I'd like to play IB with my clan and friends this weekend but at the very least TTK which I just pre-downloaded.
Tl;dr
Help: Nightingale! I probably tried that already.
https://www.bungie.net/en/Help/Article/11896
EDIT: 6 September: it's back again! Without reason the error has returned, what gives?
-
Edited by springfinger: 8/30/2015 9:09:07 AMBump! I'm still getting the Nightingale error. Any idea why? If I'm lucky I'll get online after 3 hours or 3 days, but there's no rhyme or reason as to why I start getting this persistent Nightingale error. And there's no clear reason as to what suddenly allows me to get onto Destiny servers, play a few games, then get the error again.
