{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
This thread is inspired by another: view original post
Edited by Sethicorn:
9/10/2014 8:44:14 AM
5
Caterpillar on release day -- I solved it
Hi Guys,
After trying a bunch of stuff, I was able to fix the caterpillar error (interrupting game transfer to hdd) by tracing it to the fact that I was being kicked off of Live for some reason. Never happened before... but something in Destiny was causing it to happen.
Long story short -- it was my old non-UPnP router. I had opened ports and forwarded and everything, but Live was never happy with it, and when caterpillar happened, I broke down and got a new router.
Cheapo Belkin router, $30 at the supermarket, UPnP built in, plugged it and played it. Got through everything without a hitch, and nary an error since.
So, if all else fails... try a modern UPnP router.
Sethicorn
-
Played the game for about 5 hours last night without being kicked off once. However, because Bungie put out a patch that was supposed to address network issues, I don't know if my problem was resolved due to that patch or due to my settings. FYI I turned off all the port forwarding that I had set up and just left my Xbox 360 in the DMZ. So, right now it's working with a Belkin N150 router, UPnP enabled, firewall disabled, Xbox set up with a static IP address and in the "Virtual DMZ". Xbox Live tells me I'm behind a Strict NAT... and I can't figure out a way around that... but at least Destiny seems to be working fine. (I might try forwarding those ports again to see if the Strict NAT message goes away.) Sethicorn
