JavaScript is required to use Bungie.net

Service Alert
Destiny 2 will receive an update tomorrow. Players will be required to log in to Destiny 2 again after installing the update. Please stay tuned to @BungieHelp for updates.

Help

Help us help you.
9/17/2015 6:18:12 PM
2

Error code weasel again... and again... and again... and again (Repost)

Ever since the 17GB version 2.xxx download came out, I have had nothing but "weasel" errors. Between last Sunday and last night, I have been on about 10 hours and have had almost 30 weasel errors that kicked me back to the login screen. Did NOT have this problem before TTK (v2.xx). WTF Bungie? Looked up the weasel error fix(es) and Bungie's best solution was to hardwire the internet connection between the PS4 and my router/modem. Are you for real, Bungie? You want me to spend nearly $700 to re-wire my home so I can play this game? I have 5 gaming consoles in two different rooms at opposite ends of the house and the router/modem is on the second floor. So I need two ethernet switches, close to 700 feet of cable and ethernet connectors, a connector installation tool and lots of tie-down hooks to go on the outside of the house, not to mention drilling new holes in the walls, etc. Unacceptable solution, Bungie. I would bet that greater than 80% of the users out there are running wireless. Your solution to hardwire the system leads me to believe that you have misjudged latency issues when writing your internet software and your transmit/receive timeouts are WAY too short. Result: the user is KTO'd. I understand the reasoning: longer timeouts slow down the game. The people who spend hard-earned money and invest time in this game deserve better. Please fix this, or AT LEAST post something the tells people how EXACTLY to run wireless.

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
You are not allowed to view this content.
;
preload icon
preload icon
preload icon