JavaScript is required to use Bungie.net

论坛

由TheKungLao编辑: 8/5/2016 11:23:53 PM
2
Yesterday, every other match of pvp, I was weaseled out. Played pve for a while afterwards with no problems. Hope they fix this soon. Edit: This is the most disconnects I've experienced in a short time span since I started playing Destiny. Haven't had the desire to log on today because of it.
English

发贴语言:

 

遵守游戏礼仪。发送贴子前请花点时间阅读我们的行为准则 取消 编辑 创建火力战队 贴子

  • 由iDovahBear编辑: 8/5/2016 11:27:20 PM
    I've been getting consistently Weasel'd for the last week or so. When I don't get Weasel'd, it's a Baboon barely holding me in the game. I haven't seen any other error code for MONTHS. So when people talked about Beaver, etc., I was genuinely confused. I get the same problems, even in PvE rarely. Yesterday was bad, though it turned out to be my NAT setting. I reset the router and tried to get that sorted, seemed to work fine. I just don't get what makes Destiny so network intensive. Is there a midget in my router who hates Destiny? Is it the outdated coding that is the backbone of Destiny's hardware/software/matchmaking engines? All I know is everyone at Bungie thinks it's my ISP. I can't see how a cut-content, budgeted game could strain my router so much worse than a MOBA like Smite or a RTS like Halo Wars using reverse compatibility. There is nothing about this game that screams 'require intense bandwidth.' It's a glorified Halo/CoD shooter. It's not at all different from these. I feel like they're just using a biased skill > connection setting and displacing the blame on "players' internet" when most of us have internet provided by Comcast or Verizon, two of the leading ISPs. The fact they think they can blame peoples' internet when EVERYTHING was perfectly fine YEAR ONE is a complete cop out.

    发贴语言:

     

    遵守游戏礼仪。发送贴子前请花点时间阅读我们的行为准则 取消 编辑 创建火力战队 贴子

  • 由TheKungLao编辑: 8/6/2016 12:19:44 AM
    You're right, player error is the cop out. I didn't experience any beaver errors when it seemed everyone else was. When I started getting weaseled yesterday, I checked my NAT and all that and everything was cool. I even saw a currant error code, I'd never seen that one before. I have the best service my ISP provides and I make sure no one else is online when I'm doing crucible, so I don't know what more I can do as far as my connection. For an always online game, You'd think they'd have a better grip on how to keep things sailing smoothly.

    发贴语言:

     

    遵守游戏礼仪。发送贴子前请花点时间阅读我们的行为准则 取消 编辑 创建火力战队 贴子

你没有权限查看此内容。
;
preload icon
preload icon
preload icon