JavaScript is required to use Bungie.net

Assistenza

Aiutaci ad aiutarti.
12/28/2019 4:17:18 AM
2

Lettuce and Cabbage Errors happening very frequently

I've been trying to do the Zero Hour quest for a couple of weeks now and I've been disconnected almost every time, ruining it for my friends and myself. I keep getting randomly disconnected in every other place too. The only warning I get is that nothing new will spawn in and my friends won't be able to kill anything that does on their computers. This has been going on for around 2 weeks. I've tried everything. Your guide on fixing either bug was useless and many others were too. None have changed the bug. Could you please help? I'm using NetComm Wireless NF18ACV Version: NC2-R6B013.EN (Up-to-date)

Lingua:

 

Fate i bravi. Prima di postare date un'occhiata al nostro codice di condotta. Annulla Modifica Crea squadra Invia

  • Modificato da hL Xemnas: 12/28/2019 7:41:16 AM
    Nvm

    Lingua:

     

    Fate i bravi. Prima di postare date un'occhiata al nostro codice di condotta. Annulla Modifica Crea squadra Invia

  • Modificato da RAIST5150: 12/28/2019 6:19:42 AM
    Two key questions: WiFi or Ethernet? How much bandwidth do you have in each direction? I am guessing you are running on DSL... which is not always able to meet the "Broadband Internet" standard listed in the game's requirements... in many markets it can struggle to provide even a sustained 512kbps upstream. Until they recently started restricting bandwidth, the game required at bare minimum right around 1mbps in BOTH directions. But even with them clamping down, you still need to be able to sustain at least close to around 700kbps. That is not bursting mind you, but constant throughput. You also need your end-to-end latency to be consistent, with no large spikes or packet loss. The game relies on UDP and not TCP, so there is no error correction for data transfers--if a packet does not arrive in a reasonable time frame it is at risk for being discarded. WiFi is highly prone to fragmentation and other issues that can lead to erratic latency numbers, putting you at risk for dropped packets--especially if you have high natural latency to the Seattle area, and/or the cloud service portals and players with whom you get paired. You should be running on ethernet for best results on this front. Those are two of the biggest issues we regularly run up against... not enough upstream bandwidth because of lighter weight internet plans, or various issues that cause end-to-end latency to drift too far out of spec. If EITHER of these crucial aspects of your internet service are not up to snuff you WILL have issues.

    Lingua:

     

    Fate i bravi. Prima di postare date un'occhiata al nostro codice di condotta. Annulla Modifica Crea squadra Invia

    2 Risposte
    Non ti è permesso visualizzare questo contenuto.
    ;
    preload icon
    preload icon
    preload icon