JavaScript is required to use Bungie.net

Forums

8/26/2016 10:06:30 PM
5
A lot of people, including myself, play plenty of other online games without any issues, specifically without the constant issues that Destiny has. From vanilla through today, there has always been issues with connection on Destiny, in PvE AND PvP activities. There is no excuse for it. The code is simply bad, and probably a result of shipping an unfinished game after scrapping everything a year before release. I can play 64 man BF4 games and have no issues. Titanfall, no issues. CoD, no issues. Destiny? Error codes out the ass, lag and disconnects. No amount of router configs or ISP help is going to fix bad code. I am tired of Bungie placing the blame on players, when it is clearly a problem within Destiny itself.
English

Posting in language:

 

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

  • I only have problems with BO3, I don't get it

    Posting in language:

     

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

  • Wow dude. Did I not say that there was no such thing as Plug-and-Play? i agree that dedicated servers would go a long way to solving lag, cheating and network manipulation issues, but since we don't have any of those nice things right now, you need to work on your set up. I remember playing PC games where the first thing you had to do was check the network set up to make sure the network ports are open. Thats the first thing I still do when I get a new online multiplayer game. The games you mentioned above run on standard PSN / XBL ports that you probably have open anyways for certain things to function. BF4 runs on standard ports, so does COD:BLOPS3. Titanfall runs on mostly open ports with the exception of 53000-3999 TCP; 27015-27045 TCP. Destiny works on slightly different ports. Planet Destiny has a great article [url]http://planetdestiny.com/nat-settings/[/url] Although if your running your console in a fixed address within a DMZ with uPnP (not port forwarding as you probably have more than one console?) all correctly configured you should have no problems. But hey, I already stated that you have to contend with other players bad network setups, but your the expert, right?

    Posting in language:

     

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

  • Edited by The Quicken: 8/27/2016 1:22:39 AM
    Good post- meant to help those willing to be helped. Unfortunately the vast majority of players don't know their TCP from their UDP or care that they don't know. If your employed in Information Technology this post is straight forward common sense - the majority of this forum are simply too far removed from us to comprehend. Trying to correct a network ignorant person trying to tell you what the problem is ...is maddening-- so just don't. Kudos for trying though.

    Posting in language:

     

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

  • All I really wanted was to get people thinking about their networks, when they were set up, whats changed since that time, what other devices are connected to the network at the same time your playing Destiny. I see lag as a personal challenge, but I know without a shadow of a doubt that its never me :O Networking is such and abstract concept and most people cant really see or imagine whats going on logically. It makes it hard to get the more advanced concepts across. I believe that if everyone does the bare minimum to change their network set ups 70% of the PvP issues will be cleared up.

    Posting in language:

     

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

  • Rekt

    Posting in language:

     

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

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