{{
`${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 AntwortenSadly, there are going to be allot of disappointed Christmas noobs soon. Maybe Santa could sprinkle some of that magic Christmas dust over there and Bungie and magically fix the problem. I think that's the best option we have of getting this issue fixed.
-
I'm having the same issue with my son. Cant play with him and I bought 2 copies just so we can help each other out with missions and quests.
-
1 AntwortenI had a little break: A few days holiday I did not want to spend with this trouble and an opportunity to play other games. The idea that there might be a solution in the meantime was obviously ridiculous. There is no more solution this year and I have little hope for next year. I love this game and I thought I could never leave my fingers, but I managed to do better in the course of the holiday. Think about it, Bungie. How does it go on?
-
Im haveing the same issue trying to play destiny with my girl. Our psns are evil_dragon_666 and creepy_kid333
-
Bearbeitet von Rain 130: 12/20/2016 10:26:22 PMIt would probably be easier to list who isn't affected by this. Guessing that anyone not experiencing this problem simply doesn't play with anyone on a local network. Since it started with the April update I'd recommend going over that first. Another option would be adding split screen, but then you wouldn't sell as many copies of the game and Sony and Microsoft wouldn't sell as many consoles. (that's secretly why Halo 5 has no split screen campaign.) //make sure it wasn't something commented out. Affected Xbox Players: III Paths TauKage BroomKnight64 CrimsonBadWolf OC Shad0w FoxyLady415 RainboWarrior31 afterthought: how about you try commenting out the April update see if that fixes it. I'm sure the other Sunsingers won't mind having their attack cut in half again if it means we can play with friends and family.
-
So we've still covered no ground since the RoI update? Nice one. We've given up attempting to join the same fireteam now because it's become too tedious and infuriating. Nothing seems to work. When I see pigs fly I'll know it's time to play Destiny with my family again. Thanks Bungo. And to think I actually believed in you guys!
-
Bearbeitet von superhellboy186: 12/20/2016 11:22:36 AMSo my brother and i are still having this issue but here's the thing we can both play the division together no problems and star wars battelfront skirmish together no problems also we have UPnP activated on our router. So it seems to me if it was the nat acceleration or whatever it's called then wouldn't it affect all games when people try to play on the same network together so it's not our routers at fault here but your shitty net code bungo seriously fix your shit people are getting sick and tired of you blaming our routers/internet. Also know that this problem will be reported more and more after christmas when the new christmas guardians come on to play
-
6 AntwortenIt's almost like the NES days, blow on it, push it in 7 times, pull it out, put back in.
-
3 AntwortenFix the problem bungie I bought 2 copies yesterday to play with my wife and I can't even play with her. It's a shame and I am highly disappointed.
-
Why do i keep getting canary when my connection if fine. Fix this problem. It's extreme;y annoying. It' s very frustrating when i press A the start my game only to get canary a mili-second later. There's no point in checking my internet connection because it's always fine at 4 bars.
-
I keep getting booted to orbit without an error code, 4 times now in less than an hour of gameplay. Doing my tits in
-
As explained in other threads the activation of UPnP may cause even more issues: https://www.bungie.net/de/Forums/Post/219237074?page=0&sort=0&showBanned=0&path=1 My point still is, that there was no fireteam issue (for me an my wive) before RoI (never had UPnP activated). It appears that the RoI patches broke something, so please fix it. I did not have the feeling that there was something fixed which impacted more players than the ones with two or more consoles in the home network.
-
it's time you pulled your finger out bungo and fixed this damn problem as it's not going to go away no matter how deep you bury your heads up each others arses people will keep posting about it here. Even if you ban us for speaking out about your incompetence you will never truly silence us as we'll spread it via word of mouth for a company that gave us halo to have sunk so low it's truly sad
-
Bought a second Xbox and a second game for it not to work.
-
5 Antworten1.both players go to tower. 2. Try to join team leader. 3. After it gives you the can not join player message have the person who is going to be the team leader go into orbit while the other stays on tower. 4 After the team leader is in orbit stay there and do not touch anything and have the person on the tower log out of destiny. 5. Soon as you can log back in and join the team leader waiting in space. This has worked for me my cousin and my father. It has worked 100% of the time for us. Bungie you really failed to fix a game you broke because you didn't want the PS3 and Xbox 360 to have the new stuff. I didn't want to post this because it seems bungie "fixes" these work arounds when people post them. I hope it works for anyone else having problems. Psn Moxionx Quietman J_B_F
-
Bungie: Let's turn it around. Is there any configuration where two consoles on the same router will work? [b]What is that configuration?[/b] I really like to play Destiny with my son, so much so that I bought two Xbox Ones just so we could play Rise of Iron. Getting both consoles to work at the same time is no problem, but getting them on the same fireteam ranges from unlikely to impossible unless I resort to using my LTE phone as a hotspot! I switched from Rogers cable (which was laggy, especially at Netflix hours) to Bell fibre, with totally different hardware. I've tried every configuration trick I could find on your site and elsewhere. I even rearranged the furniture so both consoles can use a wired connection without tripping over cables. Still no go. We consumers don't have much choice about the our home Internet connection, since ISPs are fussy about what connects to their network. But just about any modem/router lets you set up passthrough and/or bridge mode. Surely you have more than one console on the same subnet at Bungie. [b]So please tell us which router we can buy to connect two wired consoles to the same fireteam. If the router needs custom programming, tell us what that is. [/b] It's a simple enough solution if you don't mind the extra cost.
-
My wife and I would love to participate in the dawning event but it seems while you keep pushing out content you can't fix this on going issue. Guess it is back to the division or any other coop game on the planet except yours.
-
1 AntwortenSo aggravating!!! We have three PS4's and it always takes 20-30 minutes of work arounds to get them all in the same fire team.
-
Don't play for any real amount almost two months, come back in the hopes that the local network issues might be fixed and make it easy for me to play again, . Nope, still no fix, Bungie still can't be bothered to update us. Probably just leave again, and not spend on destiny 2.
-
1 AntwortenBearbeitet von BadKittn13: 12/15/2016 2:19:28 AMFIRST TRY: I stayed in game, my husband logged out of destiny and joined my game through the main side menu from the dashboard. It actually let us join!!!!! Maybe it'll work for someone else too..... EDIT: Wouldn't work the next night but after many attempts I think we've found the trick. Both players go to tower, team leader stays in tower. 2nd player quits game while in tower, and then joins on leader from their profile. It has worked twice so far tonight and seems to only work this way.
-
since you guys clearly don't care about this game anymore just release the source code, by the end of the day someone will have it fixed, of course there will also be hundreds of illegal copies, thousands of mods, and millions of cheats. but at least it will f'n work. you can wash your hands of it an just let the community deal with all future problems. personally i change my ip when a ddos hits and an aim-bot is the only thing guaranteed to miss me.
-
The only game I have ever had so many issues with that seem to never be resolved.
-
Having this issue as well. Just posted in the help forum. I hope this is something you guys are actively trying to fix cuz me and my wife are pretty bummed out
-
Not sure how to post so I hope I'm doing this right, one sure fire way I've been able to fix this problem for my girlfriend and I is to download a free virtual router on my computer and connect one of the ps4s to it and have the second one connect normally. This has worked 100% of the time for us... not that we should need to find our own fixes for it but at least it works
-
so there are now 52 pages of people still reporting this problem and you still have the gall to blame us bungo that's wow i'm speechless. Any other company and they would have investigated it and fixed right away but no apparently it's not your problem bungo it's apparently our routers causing the problems well i have news for you wankers at bungo it isn't our routers because i can play other games with my brother on my ps4 and pc with no problems at all but when it comes to crackstiny it's no dice
-
15 AntwortenBearbeitet von Groupal: 11/18/2016 5:45:09 PMSince Bungie isn't updating this, I will.. FROM THE 11/17/2016 Weekly Update: https://www.bungie.net/en/News/Article/45459/7_This-Week-at-Bungie--11172016 Local Network Fireteam Issues 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. We are actively seeking to resolve this issue as soon as possible, and will provide updates through our Local Network Fireteam Issues thread in the #Help forum, when available. -------------------------- It's been almost 4 months since an update was released for Destiny that ruined the game for a lot of people that loved to play it with the friends, family, and roommates sitting next to them. So right now it's still more #relax and #we'retrying. I've been in software development for over 30 years (the last 10 in gaming) and I get it. Sometimes this stuff doesn't work out the way you want and it takes a long time. All I'm asking for is updates and information. This "update" you released contains no information other than "we're trying". Is there any way to share more information to at least let us know what you've been doing and why it hasn't worked. I deal with a lot of people and sometimes you get a lot of talk and no results. I usually can sniff out when someone is dodging the question... So don't dodge this question please: What have you been working on when it comes to this issue? I don't want to hear about how complex it is. I don't care about why ideas 1 through 10 didn't work. I want to know WHAT you are looking into and WHAT you have tired. Give us some meat to chew on so we feel more comfortable that you really are working on it instead of a paragraph of empty words. Thanks, -G PS. Man I didn't plan on writing anything extra, just posting the update, but I miss playing with my kids. We no longer have the patience to go through the 20-30 minutes ordeal to try and connect. So we just don't play with each other any longer and that makes me sad.
