{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Chikout1:
9/11/2014 4:50:40 AM
4
caterpillar
So I got caterpillar errors throughout the beta and I have continued to get them in the full game. I have played with all my modem settings with no effect . I am just hoping for a response from DeeJ or someone else at Bungie. If this is confirmed to be on Bungie's end I will stop trying and wait for a patch. A simple message like the one recently posted in reference to the centipede error would go a long way to making me feel better about my purchase.
-
Hey guys. A fella named DataLV426 offered a great solution. This may not work for you but it fixed my Caterpillar error problem. I had to configure my ISP so that the filters which blocked P2P were set to zero. If that doesn't make sense, please read the thread here: http://www.bungie.net/en/Forum/Post/69185054/0/0/1 I couldn't play more than 5 minutes before, but now I'm up and running with no problems. I don't know if this fix is only helpful to people in Japan, but I guess the method should apply to anyone anywhere. I hope it can help you out.
-
2 RepliesOkay Chikout1, If you could answer a few questions, that would be awesome. A) Are you playing from disc? B) Are you hitting constant Caterpillar errors? Step 1) Attempt to restore your licenses from the Home screen. Step 2) If that doesn't work, can you completely delete and reinstall the whole game? This isn't guaranteed to work, but it has worked for some! If possible, can you also post answers to the following: - Have you been able to play at all? - What platform are you playing on? - Wired or Wireless? - NAT type - ISP company - ISP type (Cable, DSL, etc.) - Region
-
4 RepliesIf you search "caterpillar" in the search bar, you will find a bungie article for this error.
-
2 Replies[quote]Error Code: CATERPILLAR Please retry that activity again and resume what you were doing before the error occurred. If you encounter this error again, please exit Destiny then relaunch. If you continue to see this error, it’s likely due to testing we are doing on our end, please pardon our dust! Watch help.bungie.net and follow @BungieHelp for updates.[/quote] Just to help make sure it isn't on your side, could you run a [url=http://www.pingtest.net/]Ping Test[/url] and post the results?
