Sorry for starting more then one thread on this topic but i want to be sure that Bungie can't ignore players with connection issues like me.
So as the title says i am getting the "bee" error. It happens if there are more then 6 players => on the tower after a few minutes and in the crucible in the 6vs6 matches. Strikes, Missions, 3vs3 matches are all running well. But i bought the game because i love the multiplayer / pvp part of those "mmo" like games. I really like the crucible but i dont like the bee error :( They have got my money but dont respond to me on this error. I tried to open my NAT Type, portforwarding, wired connection, static IP, etc. But nothings helps. The only thing bungie told us is: "Contact your ISP" -> what? My ISP is not responsible for my gaming experience, every other stuff is running well with my ISP but Destiny. I don't think it is really on "our / my" side, it has to be on bungies side (so far i know their servers are located in las vegas ) maybe that was a bad idea? I know some things about networking and programming so the first thing to solve this i thought about myself was: increase the timeout value or the trys for get a connection back if lost?
It would be really nice if you [Bungie] could react and inform us [players] about what you are working on and if there WILL BE any solution in the next few days / weeks / month.
Best regards,
Niclas
Your role as a moderator enables you immediately ban this user from messaging (bypassing the report queue) if you select a punishment.
7 Day Ban
7 Day Ban
30 Day Ban
Permanent Ban
This site uses cookies to provide you with the best possible user experience. By clicking 'Accept', you agree to the policies documented at Cookie Policy and Privacy Policy.
Accept
This site uses cookies to provide you with the best possible user experience. By continuing to use this site, you agree to the policies documented at Cookie Policy and Privacy Policy.
close
Our policies have recently changed. By clicking 'Accept', you agree to the updated policies documented at Cookie Policy and Privacy Policy.
Accept
Our policies have recently changed. By continuing to use this site, you agree to the updated policies documented at Cookie Policy and Privacy Policy.