{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Bearbeitet von BNGHelp5:
12/10/2016 12:01:55 AM
1389
[BUNGIE] UPDATED 11/17: Marionberry, Canary, and Local Network Fireteam Issues
[quote][b]Update 11/17[/b]
Since the release of Destiny Update 2.3.1.1, we have been investigating an issue where players on Local Networks are unable to form a Fireteam within Destiny. We have made some progress in identifying the root cause, and are continuing to investigate ways in which we may resolve this issue.
We wish to ensure Destiny remains stable for all players. One change may resolve the issue at hand, while creating more issues that impact a greater number of players in alternate ways. As such, we must approach any proposed networking changes with caution and vigorous testing.
For players impacted by this issue, please ensure that UPnP is enabled, if possible. Not only do UPnP settings create a better Destiny experience when playing online, this also makes it possible for multiple consoles on a Local Network to form Fireteams. Additionally, manual port forwarding on your network may negatively impact your ability to connect to other players in Destiny. For additional information concerning UPnP, please see our Network Troubleshooting Guide.
[/quote]
[b]Previous Updates[/b]
[spoiler]
[quote][b]Update 9/15:[/b] From [url=https://www.bungie.net/en/News/Article/45223/7_This-Week-At-Bungie--09152016]This Week at Bungie - 09/15/16[/url]
[b][u]Local Network Fireteam Issues[/b][/u]
Since the release of Destiny Update 2.3.1.1, we have been investigating an issue where some players are unable to join Local Network Fireteams. Through our investigation, we have identified some of the causes for this issue. Destiny Update 2.4.0 addressed one of these, and we are continuing to investigate other potential causes.[/quote]
[quote][b]Update 9/9:[/b] From [url=https://www.bungie.net/en/News/Article/45188/7_This-Week-At-Bungie---09082016]This Week At Bungie - 09/08/2016[/url]
[b][u]Local Network Fireteam Issues[/u][/b]
[url=https://www.bungie.net/en/News/Article/45172/7_Destiny-Update-090816]Destiny Update 2.4.0[/url] contains a potential fix for an issue where players were unable to join Fireteams with other players on Local Networks. If you continue to experience this issue, or encounter any other issues after accepting the update, please let us know by posting a thread in the [url=https://www.bungie.net/en/Forums/Topics/?tg=Help]#Help[/url] forum or visiting our pinned 2.4.0 Known Issues Thread.[/quote]
[quote][b]Update 9/1:[/b] From [url=https://www.bungie.net/en/News/Article/45135/7_This-Week-At-Bungie---09012016]This Week At Bungie - 09/01/2016[/url]
[b][u]Local Network Fireteam Issues[/u][/b]
Over the last few weeks, we have been actively investigating an issue which is prohibiting players on Local Networks from forming a Fireteam. We have identified the issue, and are investigating a potential resolution. [/quote]
Hello all,
With update 2.3.1.1 an issue was introduced where players experiencing connection issues were not receiving proper Error Codes when attempting to log in to Destiny. After successfully logging in, players experiencing this issue were not able to launch activities or performing other in-game tasks.
On Aug. 9th, 2016, we have reverted back to the previous behavior which allows these players to see these error messages again. If you are met with Marionberry or Canary error messages consistently when attempting to log in, please refer to our [url=https://www.bungie.net/en/Support/Troubleshoot?oid=12915]Network Troubleshooting Guide[/url] for proper network settings. If you continue to experience these issues, you may need to contact your ISP for further assistance.
Investigations concerning Local Network Fireteam Join Issues are ongoing.
As a first troubleshooting step, we recommend that all impacted players ensure that proper connections are allowed for Destiny Gameplay. Please see the [url=https://www.bungie.net/en/Help/Troubleshoot?oid=13612]Allowing Destiny’s Connections[/url] page of our Network Troubleshooting Guide for a list of Ports that should be allowed, unblocked, or forwarded.
[b]NOTE:[/b] We highly recommend disabling any network restrictions going to your Console, as this may cause additional issues when attempting to play Destiny.
Additionally, players should clear the cache of both consoles on a local network, and attempt to form a Fireteam once more.
[quote][b]If this issue continues to impact you and your desired Fireteam members, please post a report below.[/b]
When filing a report, please provide the following information:
• Have you [url=https://www.bungie.net/en/Help/Article/12539]cleared cache[/url] of all consoles on your local network?
• Have you followed appropriate steps in the “[url=https://www.bungie.net/en/Help/Troubleshoot?oid=13612]Allowing Destiny’s Connections[/url]” section of the Network Troubleshooting Guide?
• Are you experiencing any specific error codes when attempting to join Fireteams, or are you only witnessing “Unable to join. You were unable to join the Fireteam.” messaging?
• Please list the PlayStation Network ID’s or Xbox Live Gamertags of all impacted accounts.
[/quote]
[/spoiler]
English
#Help
-
3 AntwortenSo yet another week of no useful updates on local fireteam issues... -blam!- off Bungie, this is beyond a joke... Useless kunts...
-
2 AntwortenI know you guys are probably still working on this, but most everyone here complaining on the silence have reason to be upset. I'm also in league with those who purchased an entirely separate gaming setup so their significant other can play with them (bought a 2nd tv, xbox, game copies, etc). Appreciate any help or feedback you guys can provide. Have you cleared cache of all consoles on your local network? Yes Have you followed appropriate steps in the “Allowing Destiny’s Connections” section of the Network Troubleshooting Guide? Yes Are you experiencing any specific error codes when attempting to join Fireteams, or are you only witnessing “Unable to join. You were unable to join the Fireteam.” messaging? Only getting Unable to join mesage Please list the Xbox Live Gamertags of all impacted accounts. FatterAsteroid Parser
-
They even left us out of this week at bungie also they've given up on us they said well it's your problem were out.
-
Still a major error on your end. Fix what you broke. Tired of trying to jump through hoops just to play
-
Once again Bungie shows us its loyal customers how much they don't care by not answering ANY of our posts and ignoring us in their weekly update. I will say it and continue saying it, worst customer service I have ever experienced playing online games. Orbe and Elqenna, two unimportant customers who had been playing without issue until your July update. Thank you Bungie for treating us like garbage.
-
2 AntwortenI would like to report the issue as well. Issues began last night. However, I will say that I just installed a new router last night, a Linksys AC5400 router. I had the issue of being unable to join an LAN fireteam briefly, but was able to fix it by reserving DHCP addresses for each console. Each console is wired directly to the router. However, this morning the issue came back of being unable to join fireteam. UPnP is enabled on the router. I also found a setting in the router called Express Forwarding, which I assumed is similar to NAT Acceleration. I disabled this. Still no luck. Both Xbox One consoles say they have Open NAT. Both consoles can play destiny simultaneously, just not in a fireteam together. All guides you have recommended have been followed, still no luck. It is worth noting that I had a Netgear Nighthawk AC1900 that briefly had the issue, but was able to be resolved by turning on UPnP. The same fix is not working for the Linksys Router.
-
Hey everyone. So currently my brother and i can start playing together on the same network. What you have to do is restart destiny on one xbox (prefereably one thats on wireless - if both are it doesnt matter). Restart destiny continuously until you get error code weasel. Then restart once more and it works. Idk why this works but it does... really annoying though. Maybe bungie can figure why? Thanks
-
Crossing my fingers for news soon as to when this issue will be fixed.. 3 months is too long...
-
I have been sending Bungie private messages everyday with the same content. Feel free to use this strategy too. https://www.facebook.com/brad.rice2/posts/10153782325742651?pnref=story Like, share, comment. Somehow we have to get their attention as I haven't managed to get a reply from them. Just a word of warning. I will send this message every day until I get a response. Thank you. This is a message to confirm that you have seen my post. The reasoning for this is for the desperation of the situation. This message is in regards to not being able to connect to another person on the same network. How hard can it be to use a GIT repository in order to rollback your networking code? "This is a repost since there has been no communication to the community regarding this issue in over 2 and a half months. It looks increasingly likely that we won't get any action for a quarter of a year, and potentially ever. This issue has made myself and my partner stop playing the game. If Bungie wants to keep customers like ourselves happy then either communicate about the issues or rollback to a previous version of the network engine. I would dearly love to continue to dump my money into this game if it worked. Other titles such as Titanfall don't have these issues, so why should I play Destiny when there are other games that work as designed? My faith is waning, I am becoming jaded with Destiny, please prove me wrong. Git repositories exist for a reason. Code should be separated into their functions, i.e. Network, character, weapons, armour etc. Just rollback the network component when you know there is an issue affecting playability for people. All you need to do is check your data to see who is no longer playing. So my Fianceé and myself have loved Destiny and have become addicted to it, however since the announcement of RISE OF IRON we are unable to join each others fireteam, we have resorted to usual power cycling, troubleshooting and heck even reinstalling the games on both consoles. Now I am a mathematician not a network engineer but having two xBox Ones next to each other located on the same network and unable to join each other in an activity for several weeks in a row doesn't seem right. I understand the way you guys have set up the way we communicate within the world of destiny to be something unique but instances like this should've been accounted for, especially for PvP (don't get me started about the lag in the crucible which allows so many people to have an instant edge against others... not BIASED at all! -sarcasm if you couldn't tell-). Now to have this seemingly trivial issue of two Xbox Ones on the same network playing a game we paid double for in order to play together, not come to fruition has turned us away from the game. Suggestion to Bungie would be to fix this issue, inform the community of expected time frame or at least give transparency to what is occurring, no matter how embarrassing the cause is, and to give myself and my partner a free pre ordered copy of RISE OF IRON for our troubles, and heck everyone that is having this issue as it seems ridiculous that the only way people can play the game is through others, and not all of us can interact with certain people, alas making your coding/infrastructure/game incomplete and unreliable as a product. A big thank you to whoever actually reads this post, but a bigger thank you to whomever it is that acts upon this post. The way this post is handled will ultimately determine if my partner and myself will play and spend money on not only destiny but anything that is produced by Bungie in the future, so Bungie your name as a developer is on the line here. Just as a side note, I do believe that my writing within this post fulfils the code of conduct and so shouldn't be censored. This post is a part of my own intellectual property and any censorship will be regarded as suppression of speech which all people have a right for."
-
My boyfriend and I have been having this issue since we moved in July, not the 2.4 update. (Previously, we had been playing on the same network with no issues of joining each other with a different ISP.) We have cleared the cache (after each play session sometimes), we have tried port forwarding (which worked a few times and then the error was back), we have tried UPNP. I called our ISP for help so many times that they told me to contact Sony because they couldn't try anything else. We tried workarounds which have been successful despite the cache/port forwards/UPNP but after two or three times of a workaround being successful, we still have the error come up again. We clear the cache and try joining each other again and it's hit or miss if it works. In the past week, we've only been able to join each other once, which was Tuesday, October 11, after UPNP was [i]disabled[/i] and we have no idea why. The only error we get is "Unable to join," nothing else. We have the best modem/router combination our ISP has and can join each other just fine on any other game on Playstation or XBox. PSN ID's are meeko1972 and Resurii-chan.
-
Bungie, the problem still isn't fixed. My husband and I have tried every single "fix" you have come out with to no avail. The problem is not the players. We will fight the fireteam connection for hours and *maybe* get lucky enough to join each other. Only after fighting so long, we don't have time to actually play. I honestly don't see the point of trying this hard anymore when it clearly doesn't seem to be a big issue on your side. It saddens me, really, because if this was a problem with connecting non-locally it would have been fixed already. But sadly those of us who have loved ones in the same household are tough out of luck. If only there was foresight for split-screen. Here is the error we get every time: "Not all players are currently joined in a fireteam."
-
Orbe and Elqenna still not able to join fireteam without a struggle. Bungie still doesn't own up about being responsible and still doesn't provide a bare minimum of customer service.
-
Bearbeitet von highidle: 10/14/2016 2:16:26 AMJust got off the phone with X box help the connection section. They had us change the DMZ to enable and select one of the x boxes. Tech said this allows the router/modem to see each box a little differently. So far this has resolved our in net work fire team issues.
-
Since a few days my wife and me have the same problem others describe here. We play on XBO. ++ we are behind the same router ( NAT type open on both XBOX One ) ++ we can play Destiny at the same time without problems ++ we are in XBL party chat at the same time with others BUT -- we have trouble joining the same fireteam / raid-team It got worse during the last days, when RoI launched we had no problems joining the same fireteam, it started a few days ago. The only thing that works for us is to restart Destiny or both XBO at the same time. And on the next day the problems are back again. There is no visible switch for NAT acceleration in our router config, so i can not try this. I hope there will be a fix soon, in more than 2 years of Destiny we never experienced this problems before, so i assume it is on Bungies side to fix this. Best regards.
-
1 AntwortenHow about give us some thing to tell us you're at least trying to work on it?
-
Local fireteam is still -blam!-ed dickheads...
-
I have been sending Bungie private messages everyday with the same content. Feel free to use this strategy too. https://www.facebook.com/brad.rice2/posts/10153782325742651?pnref=story Like, share, comment. Somehow we have to get their attention as I haven't managed to get a reply from them. Just a word of warning. I will send this message every day until I get a response. Thank you. This is a message to confirm that you have seen my post. The reasoning for this is for the desperation of the situation. This message is in regards to not being able to connect to another person on the same network. How hard can it be to use a GIT repository in order to rollback your networking code? "This is a repost since there has been no communication to the community regarding this issue in over 2 and a half months. It looks increasingly likely that we won't get any action for a quarter of a year, and potentially ever. This issue has made myself and my partner stop playing the game. If Bungie wants to keep customers like ourselves happy then either communicate about the issues or rollback to a previous version of the network engine. I would dearly love to continue to dump my money into this game if it worked. Other titles such as Titanfall don't have these issues, so why should I play Destiny when there are other games that work as designed? My faith is waning, I am becoming jaded with Destiny, please prove me wrong. Git repositories exist for a reason. Code should be separated into their functions, i.e. Network, character, weapons, armour etc. Just rollback the network component when you know there is an issue affecting playability for people. All you need to do is check your data to see who is no longer playing. So my Fianceé and myself have loved Destiny and have become addicted to it, however since the announcement of RISE OF IRON we are unable to join each others fireteam, we have resorted to usual power cycling, troubleshooting and heck even reinstalling the games on both consoles. Now I am a mathematician not a network engineer but having two xBox Ones next to each other located on the same network and unable to join each other in an activity for several weeks in a row doesn't seem right. I understand the way you guys have set up the way we communicate within the world of destiny to be something unique but instances like this should've been accounted for, especially for PvP (don't get me started about the lag in the crucible which allows so many people to have an instant edge against others... not BIASED at all! -sarcasm if you couldn't tell-). Now to have this seemingly trivial issue of two Xbox Ones on the same network playing a game we paid double for in order to play together, not come to fruition has turned us away from the game. Suggestion to Bungie would be to fix this issue, inform the community of expected time frame or at least give transparency to what is occurring, no matter how embarrassing the cause is, and to give myself and my partner a free pre ordered copy of RISE OF IRON for our troubles, and heck everyone that is having this issue as it seems ridiculous that the only way people can play the game is through others, and not all of us can interact with certain people, alas making your coding/infrastructure/game incomplete and unreliable as a product. A big thank you to whoever actually reads this post, but a bigger thank you to whomever it is that acts upon this post. The way this post is handled will ultimately determine if my partner and myself will play and spend money on not only destiny but anything that is produced by Bungie in the future, so Bungie your name as a developer is on the line here. Just as a side note, I do believe that my writing within this post fulfils the code of conduct and so shouldn't be censored. This post is a part of my own intellectual property and any censorship will be regarded as suppression of speech which all people have a right for."
-
9 AntwortenHas anyone taken this to Sony? Activision?
-
Still having the issue here, been at least four months now. Each attempted hot fix still makes worse than the one prior. Tonight was the first time my son and I just couldn't get it to eventually work. Full team ready to raid watching us go through what I now define as the process. God bless each and every one of those helpful people that chime in and say that they can join just fine. Yes, you can, we aren't on the same network... Cleared caches multiple times Tried with and without psn party chat connected (before and after clearing) No, I am no longer following your recommended settings. If I do, I see "beaver" after about five minutes of solo game play in any activity Presently not getting any error codes, just "unable to join target player" PSN's are zero_gd_ & kingoffrogs628
-
8 AntwortenI have been sending Bungie private messages everyday with the same content. Feel free to use this strategy too. https://www.facebook.com/brad.rice2/posts/10153782325742651?pnref=story Like, share, comment. Somehow we have to get their attention as I haven't managed to get a reply from them. Just a word of warning. I will send this message every day until I get a response. Thank you. This is a message to confirm that you have seen my post. The reasoning for this is for the desperation of the situation. This message is in regards to not being able to connect to another person on the same network. How hard can it be to use a GIT repository in order to rollback your networking code? "This is a repost since there has been no communication to the community regarding this issue in over 2 and a half months. It looks increasingly likely that we won't get any action for a quarter of a year, and potentially ever. This issue has made myself and my partner stop playing the game. If Bungie wants to keep customers like ourselves happy then either communicate about the issues or rollback to a previous version of the network engine. I would dearly love to continue to dump my money into this game if it worked. Other titles such as Titanfall don't have these issues, so why should I play Destiny when there are other games that work as designed? My faith is waning, I am becoming jaded with Destiny, please prove me wrong. Git repositories exist for a reason. Code should be separated into their functions, i.e. Network, character, weapons, armour etc. Just rollback the network component when you know there is an issue affecting playability for people. All you need to do is check your data to see who is no longer playing. So my Fianceé and myself have loved Destiny and have become addicted to it, however since the announcement of RISE OF IRON we are unable to join each others fireteam, we have resorted to usual power cycling, troubleshooting and heck even reinstalling the games on both consoles. Now I am a mathematician not a network engineer but having two xBox Ones next to each other located on the same network and unable to join each other in an activity for several weeks in a row doesn't seem right. I understand the way you guys have set up the way we communicate within the world of destiny to be something unique but instances like this should've been accounted for, especially for PvP (don't get me started about the lag in the crucible which allows so many people to have an instant edge against others... not BIASED at all! -sarcasm if you couldn't tell-). Now to have this seemingly trivial issue of two Xbox Ones on the same network playing a game we paid double for in order to play together, not come to fruition has turned us away from the game. Suggestion to Bungie would be to fix this issue, inform the community of expected time frame or at least give transparency to what is occurring, no matter how embarrassing the cause is, and to give myself and my partner a free pre ordered copy of RISE OF IRON for our troubles, and heck everyone that is having this issue as it seems ridiculous that the only way people can play the game is through others, and not all of us can interact with certain people, alas making your coding/infrastructure/game incomplete and unreliable as a product. A big thank you to whoever actually reads this post, but a bigger thank you to whomever it is that acts upon this post. The way this post is handled will ultimately determine if my partner and myself will play and spend money on not only destiny but anything that is produced by Bungie in the future, so Bungie your name as a developer is on the line here. Just as a side note, I do believe that my writing within this post fulfils the code of conduct and so shouldn't be censored. This post is a part of my own intellectual property and any censorship will be regarded as suppression of speech which all people have a right for."
-
Still not working. No accelerated network. Restarted both xboxs. Cleared both caches. Still cant join.... Why is this happening...
-
STILL NOT FIXED. I BOUGHT 3 COPIES. 3 Xbox's. Other games work. All three of us can play. Just not together. Please fix local network fireteams.
-
Come on bungie fix this major major bug in your network code. Me and the rest of the community are becoming more than pissed off at the fact you are failing to do anything on your end to really fix the problem. Blaming our routers when they've worked fine with your game since day 1 is a big middle finger to loyal players. The problem also appears to be very random in the fact that 1 day we can get a work around to work (static ip's and 1 console in dmz) then the next day it doesn't work. Again nothing changed on my end so why doesn't it work anymore? Give us the real fix and revert your network code/ servers / whatever it was you changed in patch 2.3.1.1 back to a proper working version say the settings from patch 2.3. Just fix the issue already!!!!!!!!!!!!!
-
Bearbeitet von TheOsmethne: 10/12/2016 4:08:49 PMI've posted this as a reply to another user, but I also don't want it buried and unread. I believe that one of the main issues is that, I think it's safe to say, most players don't use, let alone know about the forums. This means that the numbers will skew lower than the real numbers. As for prominent advocates? We're not Youtubers, nor do we stream on Twitch(as far as I know). We don't offer lighthouse carries, and we aren't pushing for World First status. We're players. That's apparently not enough. Unfortunate, but seemingly true. I don't know anyone who is, shall we say, YouTube or Twitch famous. If I did, I'd have been pushing them to take the issue on. But that's a step that I shouldn't even have to consider. The fact that this is impacting us, John Q. Guardian. Alpha, Beta, Day one, Dark Below, Wolf-Pup, Taken-Tot, Iron-Pup players all should simply be the end of the discussion. I'm going to keep after the issue, as I know others will, so that I can again play Destiny with my girlfriend, and so other couples, families and roommates who are impacted as well, can again play together.
-
2 Antworten"Our investigation has found that routers with "NAT Acceleration" enabled may be causing issues for some players attempting to join a Fireteam on the same local network. Please ensure that this setting is disabled in your network hardware." What kind of BS answer is that? I know my router settings by heart ( because of this stupid issue ), and there's no setting for NAT acceleration, CTF, o FA ( the latter two are also forms of NAT acceleration - or at least according to routerguide.net ). Bottom line. For almost two years I had no problems whatsoever. The only change on my end was installing your update(s). And since then nothing has worked correctly in regards to local fireteams. Hundreds of others have been affected as well, so it's not like this issue is isolated to just my household. Please dedicate more than one intern to this problem. It's been 3 months for crying out loud. I'm really tired of this issue and would like to play with others in my household which is why I bought the game in the first place. Thank you in advance. Even though you won't read or care about this mini-rant.
-
1 AntwortenBeen playing weekly with my son for over a year. Haven't been able to since the July update. Very frustrating this can't be fixed timely. We were looking forward to playing Rise of Iron together, but had to do the quests all solo due to matchmaking bug. I have tried everything suggested, but nothing resolves it. Very disappointing this isn't a bigger priority to fix, been broken 2 and half months now...
