{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by delapug:
9/12/2014 10:33:01 PM
308
Could everyone getting bee error post in here
Please if you're getting this error post in this topic. No stupid remarks about get better internet or other childish remarks. I'll start off.
Xbox one - wired connection - ports forwarded - open nat - no problems on any other game.
[u]UPDATE[/u]
I don't want to be the one to say this but I went and bought a new modem/router(DSL) just plugged it in and no errors for the past 5 hours in the pvp which I couldn't play at all before. Don't know if that means anything but it seems to have taken care of me.
[u]UPDATE 2[/u]
I've been asked a few questions so I thought I'd do another update with my settings
I switched from a netgear combo unit supplied by my isp to an Actiontec GT784WN wireless N DSL Modem. Like I said when I first hooked it up I just made sure plug and play was enabled on the router and started up the xbox and destiny I went straight to the crucible and began playing and haven't stopped since, no more errors at all the only problem was that my nat type was strict. To fix that I forwarded the following ports
Port 88 (UDP)
Port 3074 (UDP and TCP)
Port 53 (UDP and TCP)
Port 80 (TCP)
Port 500 (UDP)
UDP Port 3544 (UDP)
UDP Port 4500 (UDP)
Port 3075 (UDP and TCP) *for call of duty
Ports 7500-17899 (TCP)*from bungie
Ports 30000-40399 (TCP)*from bungie
Ports 35000-35099 (UDP)*from bungie
I now have an open nat and no more errors and even though I suck I can play PvP. I really hope this helps this is exactly what I have done, I compared the settings on each modem/router and other than a few years difference in manufacturing there was no difference.
-
Edited by Mud Turkey 3: 9/20/2014 10:31:22 PMYou folks really need to get this sorted out. I was playing with my friends last night and ate 25 or so bee errors throughout the entire night. I would get booted, sometimes followed by a vulture error. Funny, xbox acted like I was still logged into the game after a bee booting. Regardless, I would reconnect, play a couple seconds just to get booted again. I've ate several today. Nothing like being right at the end of two strike missions only to get booted right at the end of the boss fights. I love that. I love getting the error right as soon as the Tower loads. But hey, I inexplicably was able to finish from the start a crucible match! That's new! If this is really caused by packet loss, you folks need to figure out to buffer it better. I would rather have 5 seconds of lag or re-synching than a straight out boot. I can play fine before the error with no lag. And no lag after the error (and reconnection), at least, until the next error. I play many other xbox one online games with ZERO dropping. On the same freaking connection. Why is it unique to this game? It's either on your end or your netcode's ability to tolerate dropped packets. This is what bothers me. Why is it unique to this game? Why do my other online games run with out constant drops? Again Ports are open Nat is open Wired Static IP DMZ Residential connection Baisc DSL, but my bandwidth monitors do not indicate that this game is using up the available space Nothing else on the network. I still get almost always bees. Sometimes followed by vulture. Mix in some lions and flys too. OH edit New wrinkle. I keep getting caterpillar errors now. Then I try to log in and get hit with CATTLE. That forces me to reboot everything. Because I can't even login.
