{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by psychopanda27:
2/28/2015 11:37:19 PM
4
Baboon.... why....
I bought destiny against the advice of all of my friends. They ask me constantly, how can you put up with that game, I tell them: Destiny is not a bad game, but it has a bad connection. Today, I tried to play destiny, specifically the Daily mission on Venus, I tried 8 times.... 7/8 of those times I received the baboon error, one specifically on the last enemy of the last wave of the last battle which killed all of my enthusiasm. the 1 time out of the 8 tries that I didn't get a baboon, I got a weasel so yeah, not the best day. This is a question post so I'm going to ask Why?
Why am I getting this error?
Why has it been half a year without progress?
Why is the word "investigating" used yet with every update to the game the errors increase in frequency.
I have read the networking pages many times, I have read the Baboon help page many times, I have opened my ports, I have gotten rid of my Strict NAT... What more can I do, and I'm definitely not the only one with this problem.
I'd appreciate any responses, especially ones that don't simply state the errors are "being investigated", as they were "being investigated" months ago.
Thank you.
-
Dont listen to these clowns telling you its on your end. I bought this game on release. Played for a month without a hiccup...them from mid oct to mid dec the game was unplayable w random disconnects. Its been fine since then...tonight? Baboons out the a$$...cant play shit. Just like in oct. F what they say if this last for longer than a day or two im out. I havent changed shit in my end. Unless u guys get commission stop working for the love of god...
-
9 RepliesTo be fair this is not bungies fault. It is your router but not in the way you think. First this is how Xbox live/PSN works. You Xbox/Playstation tells your router what packets it needs from what address, it sends the info the server needs digitally signed by your console to prevent it from being delivered to another device on the network. Your router receives this information, then sends it to where it needs to be. The server recieves it, decodes it, figures out what you console needs from it, then sends the info your Xbox/Playstaion needs. It does this in a fraction of a second, and can send multiple megabits of information at once. The problem is, if you are a decent amount of space from your router and have walls between them, and cell phones and other things that take "Air Time" priority over the Xbox/Playstation according to the FCC wireless communications laws. This can cause brief (and I mean like .5 milliseconds) interruptions in constant communication with the service, that's not a big deal in terms of information loss. However this can be a big deal if this interruption happens while a packet is going from Xbox/Playstation to router or vice versa. The use of the UDP connection type from Bungie is also not their fault but nor is it ours or our hardwares. That one you can blame on your ISP. The reason so many game development companies and publishers choose UDP instead of UDP and TCP for more stable packet sending and delivery, is because only North American ISPs support that. Microsoft is a North American Company. Sony is not. So for Halo they have support for UDP and TCP connections when on a North American Internet service. Destiny can't because of Sony being priority console. So to fix your issue if you are in North America (USA and Canada) try port forwarding the ports instructions are here https://support.xbox.com/ just search port forwarding. These are the Xbox live ports I don't know if Sony has their ports publicly accessible but if they are I'm sure Google knows! If that doesn't work I'm sure that bungies ports are somewhere. I hope I helped, Regards, TRVM, TheVerbalMurder
-
[quote]I bought destiny against the advice of [u]all[/u] of my friends. ... Why am I getting this error? Why has it been half a year without progress? [/quote]Although not the cause, why did you ignore good advice? And now onto the error; [url=https://www.bungie.net/en/Help/Article/11783net]"[i]This error can be due to packet loss or disconnections[/i]"[/url] First up ... Disconnections: This is not YOUR router. Checking [url=https://twitter.com/bungiehelp]bungie's own twitter page[/url] and we see this happens more days than it is clear. Look at the start of February and the [u]whole first week[/u] was full of sign-in and disconnection errors. So a whole week of errors effecting so many people ?!? And bungie blame YOUR router ?!? How can they not see the single common element in all these disconnections ? How can this game have more days a month with these errors than it has clear playing days ... and we are 6 months in ? Second cause ... packet loss: The game uses UDP ... which by design has [url=http://en.wikipedia.org/wiki/User_Datagram_Protocol]"[i]no guarantee of delivery, ordering, or duplicate protection[/i]"[/url]. And again it is somehow [b]YOUR[/b] fault ?!? 5 games developed and released under Microsoft's watch. And yet take the total number of bugs for all those games and we come nowhere close to the number in this one game alone.
-
2 RepliesHey there, I'm sorry you're getting this error. I know you have mentioned that you have visited the error page but I want to confirm the following with you: Are you on WiFi? Have you attempted to force quit Destiny by completely closing the game and relaunching Destiny to get out of this state. Have you powercycled your router/modem?
