{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by ForMyNinjas:
10/10/2015 2:43:35 AM
28
The Taken King patch ruined my Destiny experience.
I have disabled QoS, I have ports forwarded, I am wired, and my router firmware is up to date. I do not have any network issues with any other PS4 game except Destiny.
Since The Taken King: my game crashes in orbit whilst in transit to a mission (loading). The screen will go black before the ship dives onto the mission.
I did not have this problem before the patch, but now it happens very frequently. The latest errors I notated are:
Cacao
Beetle
Quail
Multiple instances of each, no particular order. This seems to be an issue with Bunjie's patch and/ or servers due to the sheer amount of complaints on the same matter (despite always pointing fingers at ISPs).
As someone that bought a PS4 for Destiny on release day, all subsequent dlc, got hustled to re-buy the original (now useless) DLC again with TTK, and whom has gone through steps (I shouldn't have) to config my router specifically to cater to this game: it's disappointing to see a lack of acknowledgement on of the issue.
I enjoyed this game. I really did. And was very happy with the changes TTK had brought to the game.
But I can only play it on days I'm feeling lucky, because there seems to be no rhyme or reason to when I'll be booted next. If this persists, I don't think I'll waste my time nor money anymore.
-
39 RepliesEdited by BNGHelp2: 10/25/2015 10:08:25 PMHi ForMyNinjas, The specific errors you're seeing (Bee, Beetle, Cacao) indicate that you are having problems connecting to what are known as the activity servers. Whenever you enter a new in-game public area (a "bubble"), your console will attempt to make a connection to one of multiple activity servers for that area. If your connection to that server times out or is blocked in some way, you will see one of a few errors codes (including Bee, Cacao, Rabbit, Beetle). It's interesting to me that only these specific connections are failing. Typically when we see this sort of thing it impacts more than just those specific connections. It's possible that your network configuration or ISP are somehow blocking, filtering, or de-prioritizing connections to those specific destinations. You may want to contact your ISP and provide them with the Port Forwarding information found in our [url=https://www.bungie.net/en/Support/Troubleshoot?oid=12915]Network Troubleshooting Guide[/url]. Explain the situation to them and see if they can help determine why those specific connections might be blocked or filtered.
