onezerosix141 Posted August 5, 2015 Share Posted August 5, 2015 i thought it might be good to see how everyone is doing after the update in one place since i've updated, i'm getting error code Bee overall, it seems frequency of getting disconnected has gone down but error code: Bee is the only one i'm getting. prior to the update, i was getting multiple different error codes. https://www.bungie.net/7_Error-Code-BEE--FLY--LION/en/Help/Article/11829 6/26/2015 Error Code: BEE / FLY / LION BEE/FLY/LION errors can be caused by general disconnections between you and the various routes your traffic takes across the internet to get to Bungie. This includes packet loss or disconnections between your home network and Bungie (such as ISP saturation or general internet congestion). It can even be caused by certain WiFi setups, faulty in-home wiring, or other issues that require on-site support or expert investigation. Disconnects of this type can also be caused by bandwidth being claimed by other devices and applications. It may be necessary to avoid file-sharing, video streaming or other bandwidth intensive tasks on any device connected to your network while playing Destiny, including console applications that run in the background or in a window as you game. If you hit this frequently, please follow the suggestions in our Network Troubleshooting Guide to see if troubleshooting your setup, or switching from a wireless to a wired setup improves your experience. During investigation, Bungie has seen users hitting these errors in geographic clusters in different places at different times. For example, we recently detected 25% packet loss from the UK at the same time a number of users located there saw errors. These internet conditions usually pass quickly, and the errors often go away on their own when this happens. Link to comment Share on other sites More sharing options...
Chive972 Posted August 5, 2015 Share Posted August 5, 2015 Have you ticked strict mode on? In that cas, it's normal because servers can no longer communicate with your console sometimes. Link to comment Share on other sites More sharing options...
onezerosix141 Posted August 5, 2015 Author Share Posted August 5, 2015 Have you ticked strict mode on? In that cas, it's normal because servers can no longer communicate with your console sometime These are the setting i'm using: Destiny setting autocloud & bleeding edge = checked Ping Assist = 0ms Strict mode = off Peer ping = checked with Fast Search setup Link to comment Share on other sites More sharing options...
Administrators Netduma Iain Posted August 5, 2015 Administrators Share Posted August 5, 2015 Hi onezerox can you confirm that you don't get that error with the Geo-Filter disabled? thanks Link to comment Share on other sites More sharing options...
Chive972 Posted August 5, 2015 Share Posted August 5, 2015 Ok. I'm gonna check this afternoon if they're is something bad with the update. Link to comment Share on other sites More sharing options...
Administrators Netduma Iain Posted August 5, 2015 Administrators Share Posted August 5, 2015 Cheers Chive Link to comment Share on other sites More sharing options...
Chive972 Posted August 5, 2015 Share Posted August 5, 2015 Cheers Iain, there is something i can do to help on that issue? Test something with the cloud? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted August 5, 2015 Administrators Share Posted August 5, 2015 Cheers Iain, there is something i can do to help on that issue? Test something with the cloud? Hey Chive you can help by doing the following: If you have auto/bleeding edge ticked and applied with strict off is there booting? If so do you see anything that is getting blocked when this occurs? If the Geo is disabled do you get booting? Link to comment Share on other sites More sharing options...
Chive972 Posted August 5, 2015 Share Posted August 5, 2015 I can't for the moment, i'm working I'll do my best tonight to test all situations and give you my feelings with the new update. Link to comment Share on other sites More sharing options...
R3M!X Posted August 5, 2015 Share Posted August 5, 2015 Played last night , had some very laggy games. So I logged in checked my settings. Went to the cloud settings to ensure it was set on the recommended configuration. Everything was set right then I rebooted the R1. Went back online to play a match in clash. Game felt smooth, shot were registering as it would. Finished the match 22-5. So I guess the update and reboot worked. FYI this was with strict mode off. I did notice again this circle that's always in the same location. I brought this up to Fraser a week ago. Saw it again last night while I was idle in orbit and it was just me.None of my friends were online playing Destiny. I don't know what/who it maybe but it seems to pop up a lot. Fraser said its nothing to be concerned off. Anyone else experience this? I just find it weird. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted August 5, 2015 Administrators Share Posted August 5, 2015 Awesome to hear that! Next time you see it can you ping it please, I'm now suspecting it may ping at 0.5ms in which case I know exactly what it is. Link to comment Share on other sites More sharing options...
R3M!X Posted August 5, 2015 Share Posted August 5, 2015 I actually did ping it. It ranged from 18-25ms. I just added it to my good list. Link to comment Share on other sites More sharing options...
onezerosix141 Posted August 5, 2015 Author Share Posted August 5, 2015 Hi onezerox can you confirm that you don't get that error with the Geo-Filter disabled? thanks i'm not getting any errors with geo-filter disabled so far. Link to comment Share on other sites More sharing options...
Chive972 Posted August 5, 2015 Share Posted August 5, 2015 After multiple tests on crucible, i can say one thing: it's unbelievable ! My games are so smooth than ever before ! First skirmish, 24-3 and i'm sick ! Thank you so much to bring back the destiny i've loved before with awesome hitbox and bullshit less ! If anyone need some help on this, i'll be very glad to help him and the duma team Link to comment Share on other sites More sharing options...
JConnor Posted August 6, 2015 Share Posted August 6, 2015 Hi onezerox can you confirm that you don't get that error with the Geo-Filter disabled? thanks I, too, will confirm that I received the "BEE" error with Geo-Filter enabled, but with it disabled, I no longer encounter it. Just some more info., for Iain and crew... -My home location is still in Kansas, rather than NY where I live. -I was pinging about 60 in basic game tasks such as being in orbit, going to the tower (Earth) and doing some patrol missions (Earth) to dust the rust off my Destiny skills (getting ready for "The Taken King" that will make the game how it should have been at launch, according to many people, myself included). Link to comment Share on other sites More sharing options...
prencher Posted August 6, 2015 Share Posted August 6, 2015 I'm in Huntsville, AL, US - I've tried both a US wide filter and a ~1000km one around my actual home. No dice. Settings: Strict mode disabled. Auto cloud and bleeding edge cloud enabled. Ping assist 50ms. Peer ping disabled. I've been getting nothing but 'rabbit' errors since the update. With the filter disabled there are no issues (other than the poor connections, of course). To make it more fun, there is no documentation at all that I can find on bungie.net about the 'rabbit' error code. I've asked @BungieHelp on twitter for clarification. Before the update, I would use a tight filter for the search, and expand the filter to cover the world as it loaded in. This also doesn't work after the update for me. Tangentially related to that, disabling the filter while in a match disconnects me; It'd be nice if you could toggle it without that happening, instead of having to constantly change the filter size. In case it matters: I was playing with one other person (I was the party leader), about 10km away and whitelisted. I'm gonna try some more tonight. I also didn't reboot the router, gonna do that for good measure if it stays broken. Link to comment Share on other sites More sharing options...
Chive972 Posted August 6, 2015 Share Posted August 6, 2015 I, too, will confirm that I received the "BEE" error with Geo-Filter enabled, but with it disabled, I no longer encounter it. Just some more info., for Iain and crew... -My home location is still in Kansas, rather than NY where I live. -I was pinging about 60 in basic game tasks such as being in orbit, going to the tower (Earth) and doing some patrol missions (Earth) to dust the rust off my Destiny skills (getting ready for "The Taken King" that will make the game how it should have been at launch, according to many people, myself included). Bungie doesn't have any explanation about this error so, i think, it's something you can resolve yourself. Can you give us some screenshots of your configuration? It will be more simple to find the issue. I'm in Huntsville, AL, US - I've tried both a US wide filter and a ~1000km one around my actual home. No dice. Settings: Strict mode disabled. Auto cloud and bleeding edge cloud enabled. Ping assist 50ms. Peer ping disabled. I've been getting nothing but 'rabbit' errors since the update. With the filter disabled there are no issues (other than the poor connections, of course). To make it more fun, there is no documentation at all that I can find on bungie.net about the 'rabbit' error code. I've asked @BungieHelp on twitter for clarification. Before the update, I would use a tight filter for the search, and expand the filter to cover the world as it loaded in. This also doesn't work after the update for me. Tangentially related to that, disabling the filter while in a match disconnects me; It'd be nice if you could toggle it without that happening, instead of having to constantly change the filter size. In case it matters: I was playing with one other person (I was the party leader), about 10km away and whitelisted. I'm gonna try some more tonight. I also didn't reboot the router, gonna do that for good measure if it stays broken. There is no need of ping assist with Destiny: you can put the PA to 0. Both of you, make sure that UPNP is enabled and upnp port forwarding in miscellaneous. Make sure that your console has a fixed IP adress configured on the router and directly in her parameters. After that, reboot the router and play few games to see if something changed. Link to comment Share on other sites More sharing options...
onezerosix141 Posted August 6, 2015 Author Share Posted August 6, 2015 having Nashville, TN as home location, i ran into error code Bee when i exclude west coast. so, 3283km or less seems get the error code. If i have it set at 3283km, i don't get error code with strict mode on or off. Destiny setting autocloud & bleeding edge = checked Ping Assist = 0ms Strict mode = off/on Peer ping = checked Link to comment Share on other sites More sharing options...
Chive972 Posted August 6, 2015 Share Posted August 6, 2015 I think there is "maybe" a problem with the cloud in United States. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted August 6, 2015 Administrators Share Posted August 6, 2015 Disabling the filter when in a match should definitely not disconnect you, if anything it would allow more connections through, not limit them to the point of booting. So theres something essentially at that distance getting allowed that allows you to have no errors appearing. When you get this error does anything appear blocked on the Geo-filter? Link to comment Share on other sites More sharing options...
prencher Posted August 7, 2015 Share Posted August 7, 2015 I didn't get a chance to play last night, but I have been playing tonight. It seems whatever was happening the day of the update has cleared - I've been playing all night with a 800km filter, with no issues and good connections. The only difference is I'm playing alone tonight. I'll update with any changes when next playing in a party. It makes me wonder if the router just didn't take the cloud updates correctly or something? I didn't reboot it either, for what it's worth. Oh, and toggling the filter no longer causes a disconnect either - Not that I've needed to, but tested just in case. Good news all around, so far. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted August 7, 2015 Administrators Share Posted August 7, 2015 Excellent to hear that! Its possible it didn't flush properly, in which case clicking apply resolves that. Link to comment Share on other sites More sharing options...
prencher Posted August 10, 2015 Share Posted August 10, 2015 Just a quick update - played for an hour last night with a party, 800km filter and no issues at all! Good stuff. A few laggers here and there, but that's on Destiny's matchmaking; Connections were all close and pinging fine. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted August 11, 2015 Administrators Share Posted August 11, 2015 Just a quick update - played for an hour last night with a party, 800km filter and no issues at all! Good stuff. A few laggers here and there, but that's on Destiny's matchmaking; Connections were all close and pinging fine. Thanks for the update, thats awesome to hear! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.