Forced Despawn Cause?

[actrade]

I had several players tell me that restarting your computer helps with the force despawn, but none had any empirical data to back it up. Anyway, I had like 3-4 tonight and after the last one, did a quick speedtest.net and found that my DL speed had dropped from 75mbps to 11mbps. Interestingly, I did a speedtest on my iPhone right after that and got the 75mbps rate. I tested both my computer and iPhone two more times with the same result. I verified that nothing else was running on my computer. After a quick reboot, my computer was again humming along at 75mbps download speed. FWIW, I probably have restarted my computer 10 times today working on some other stuff, so it's not like it had been running for days without a reboot. While this may all be a coincidence, I have to wonder what within the game may be causing this?

Edited January 1, 2018 by actrade

[B2K]

try doing this and see what comes up

http://forums.wwiionline.com/forums/topic/415919-forced-despawn/?do=findComment&comment=6304926

 

[FRISBONE]

11 hours ago, actrade said:

I had several players tell me that restarting your computer helps with the force despawn, but none had any empirical data to back it up. Anyway, I had like 3-4 tonight and after the last one, did a quick speedtest.net and found that my DL speed had dropped from 75mbps to 11mbps. Interestingly, I did a speedtest on my iPhone right after that and got the 75mbps rate. I tested both my computer and iPhone two more times with the same result. I verified that nothing else was running on my computer. After a quick reboot, my computer was again humming along at 75mbps download speed. FWIW, I probably have restarted my computer 10 times today working on some other stuff, so it's not like it had been running for days without a reboot. While this may all be a coincidence, I have to wonder what within the game may be causing this?

As you and I have previously discussed privately your 4 drops out of over 100 spawns is fairly reflective of the MTR report that you sent me that indicated hops experiencing intermittent packet loss.  In the case of your very last despawn you had dropped out of netcode3 (which happens when it has detected unacceptable packet loss) and then fell into our fallback state which is a little more lenient but will queue if packet loss is high (which it did in this case).

I highly recommend that you send the information you have about the hops that are exhibiting higher packet loss than they should to your ISP.  A 4% incident rate doesn't seem all that surprising to me - I know we all want it to be perfect but if we play this game long enough we will eventually be effected by normal network hiccups.  ISPs are far worse than most of us believe in terms of performance and reliability and it has little to do with the bandwidth they provide.  All it takes is one node to get overwhelmed for it to behave badly.  If they don't keep firmware up to date and replace old routers went they should - you might get it worse than others.  The more information they have from customers the better as the only people they are accountable to is you.