BlueMountain65 Posted January 19, 2016 Share Posted January 19, 2016 Since the last couple of weeks if I enable my Netduma router for PvP matchmaking in Destiny I'm getting booted with beaver error most of the times, up to 50% in 6v6 lobbies, up to 80% in 3v3 lobbies. Boot takes place either during "flying in" or between first 15 to 60 seconds of the match. Settings are strict mode, distance filter ca. 1300km, PA not enabled ... It's really frustrating as I now have the choice to accept very laggy lobbies most of the times, or loosing so much time trying to get a stable match/lobby for me ... Link to comment Share on other sites More sharing options...
PharmDawgg Posted January 19, 2016 Share Posted January 19, 2016 Destiny does not work well with strict mode enabled. Link to comment Share on other sites More sharing options...
Pranksterr Posted January 19, 2016 Share Posted January 19, 2016 Hi, BlueMountain Sorry to hear your problems, try these settings that work for me in Destiny - Geo- Auto Ping host , Show Dormant Hosts - All ticked Ping Assist set to 0.00 Congestion Control - Preemptive selected Settings - UPnP enabled Misc - Auto feedback, remote feedback cookies , wifi workaround - ticked Cloud settings, have auto cloud and bleeding edge, ticked and apply Reboot router, console and let us know if there is any difference Link to comment Share on other sites More sharing options...
BlueMountain65 Posted January 20, 2016 Author Share Posted January 20, 2016 Hey Pranksterr, thx for your feedback. If I'm not mistaken you recommend not to use "strict mode". If I un-tick it it works for me, but gets me quite some players from farer distances, especially some from the arab countries with laggy connections. Which I want to avoid ... Problem comes with stricked mode enabled. Link to comment Share on other sites More sharing options...
Pranksterr Posted January 20, 2016 Share Posted January 20, 2016 Hey Blue, With Destiny, the Netduma can only limit what servers you connect to. Who else joins that lobby is beyond our control. We set a limit to say, 1000miles, hoping to get a good connection within that radius. The problem you are seeing is Destiny's matchmaking, with it designed to put players into games as fast as possible, without regard to distance and quality of connection. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted January 20, 2016 Administrators Share Posted January 20, 2016 With strict enabled you will get booted, but have the chance to get very good games. Ensure you have both clouds ticked as above as there was a cloud update last week Link to comment Share on other sites More sharing options...
BlueMountain65 Posted January 20, 2016 Author Share Posted January 20, 2016 It was and is both enabled, Fraser. Sure, there is a chance to get very good games w/o lag, but it's no fun at all to get booted 8 out of 10 times ... I'm not saying you're guilty, it is just that from my perspective the router (investment) makes very limited sense if you mostly play Destiny's PvP ... I'm not a software engineer, so I hope that Bungie improves on the net code, and that you guys improve on your end too. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted January 21, 2016 Administrators Share Posted January 21, 2016 We do always recommend strict off and will ensure we do more cloud updates to best optimise the game Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.