{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Unresolveddebt:
9/29/2014 3:05:36 PM
5
#BEE Error
Im one of many who is having this issue and ive gone through every means i can to fix it. Spent two days solidly contacting microsoft support now forwarding ports factory restarting my console my router (which i even got a new one) changing the NAT types and still cant play PvP consistently without getting a BEE error. And microsoft has basically told me now that they have (and I) have done everything they can do and they see no issue and i should contact Activision who dont have a support link for destiny so i ended up here with the numerous others with the same error as me. Bungie needs to figure out what the issue is and fix it because they said in a recent update they had lowered the rate of BEE errors by 50%. Well judging by how many people have it that hasnt doen alot so i just hope its fixed soon because right now for me Destiny is unplayable i cant Raid and i cant PvP without getting a BEE error code and you cant be re invited like a strike to most PvP games and you cant rejoin a Raid without the team wiping.
-
2 Replies
-
Bungie needs to figure out the issue or ill trade in the game i cant Raid or PvP as there are no invites back from your fireteam (that work) so its just a case of strikes and they are boring everytime you have to go through load screens every 10 minutes due to BEE
-
Same here. Can't do any pvp. That's half the game that I can't use. Even after going through port forwarding and static ip, it still doesn't work. Needs to be fixed, tired of all the BEEs!
-
I've had "bee" errors since the release. Done everything you have. Spent hours on the phone with tech support for my router, isp, and microsoft, static IP, port forwarding, wired and wireless connections, etc.. this is not a NAT problem and nothing to do with the customers internet setup. This is to the point of just wanting a refund. I love the game but if I can't even play through an entire raid, crucible, or strike without getting kicked and having to rejoin then why would I play? I wouldn't have bought the game to begin with. Bungie sold us a broken game that is unplayable for alot of us and should fix it or do a recall/refund.
-
I'm having the same problem man. Since the 15th I've gotten bee errors constantly. Sometime between 5-20 min I'll be sent back to orbit. Trying to do crucible bounties but I get kicked out of every pvp before the match finishes. I've also contacted ISP, set up static IP on my ps3, forwarded ports to it and no luck. In one of the other error topics bungie mentioned it's caused by packet loss from a wireless connection....but there's people using wired connections getting same errors. So if anything...know you aren't the only one putting up with this crap...
