6.15 Frequent disconnection

[BunchesOfBeans]

After updating to this version I have not been able to stay connected for more than 10 minutes or so. I get the 90002 error but I am usually able to reconnect immediately though I have gotten the data center error once. Anyone else having this issue? I don't see anything about network changes in the patch notes.

[WushuDragon]

After updating to this version I have not been able to stay connected for more than 10 minutes or so. I get the 90002 error but I am usually able to reconnect immediately though I have gotten the data center error once. Anyone else having this issue? I don't see anything about network changes in the patch notes.

Are you playing on the same data centre designed for your country?

Also, there's a noticeable resistance to VPNs in the new update.

[BunchesOfBeans]

Are you playing on the same data centre designed for your country?

Also, there's a noticeable resistance to VPNs in the new update.

Yep, my data center is in my country. No VPN, though I am on Starlink. I had a better ping on Starlink than my local ISP so I switched over to it exclusively about 3 weeks ago without any issues until this patch.

[BunchesOfBeans]

Just as a follow up, I've been playing other games with a sub 100ms ping today without issue. It seems to just be this patch

[Shibi]

Start an MTR to your world's lobby ( which is 204.2.229.11 for Bryn) and then when the DC happens the faulty equipment will be highlighted.

You can also tracert 204.2.229.11 when it happens, but that likely won't catch transitory errors like MTR will. (MTR is a looping version of tracert that runs in the background looking for internet problems)

I had a better ping on Starlink than my local ISP so I switched over to it exclusively about 3 weeks ago...

Also please be aware Starlink is very susceptible to weather (including some types of clouds) and other events between you and the satellite. Expect a lot of ramdom drops in general when playing FF on satellite, it seems to be a game that is lot more sensitive to packet loss than some other games. Meaning other games work, but FF drops all the time on satellite. There won't be a solution to this apart from moving off satellite when it's not sunny outside, or possibly using a TCP based VPN to add a little error correction (at the expense of lag)

However, the MTR will show it very clearly, as it does record lost packets and other such problems. Bad numbers in the Starlink part of your route will point the finger there, bad numbers in the NTT portion point the finger to SE.

https://www.reddit.com/r/Starlink/co...ming_starlink/

https://www.reddit.com/r/Starlink/co...g_on_starlink/

And from this page https://speedify.com/blog/how-to/avo...ection-issues/

rain, cloudy skies - >> Use your backup Internet connection until conditions are better

[BunchesOfBeans]

Start an MTR to your world's lobby ( which is 204.2.229.11 for Bryn) and then when the DC happens the faulty equipment will be highlighted.

You can also tracert 204.2.229.11 when it happens, but that likely won't catch transitory errors like MTR will. (MTR is a looping version of tracert that runs in the background looking for internet problems)



Also please be aware Starlink is very susceptible to weather (including some types of clouds) and other events between you and the satellite. Expect a lot of ramdom drops in general when playing FF on satellite, it seems to be a game that is lot more sensitive to packet loss than some other games. Meaning other games work, but FF drops all the time on satellite. There won't be a solution to this apart from moving off satellite when it's not sunny outside, or possibly using a TCP based VPN to add a little error correction (at the expense of lag)

However, the MTR will show it very clearly, as it does record lost packets and other such problems. Bad numbers in the Starlink part of your route will point the finger there, bad numbers in the NTT portion point the finger to SE.

https://www.reddit.com/r/Starlink/co...ming_starlink/

https://www.reddit.com/r/Starlink/co...g_on_starlink/

And from this page https://speedify.com/blog/how-to/avo...ection-issues/

That's just the thing, Starlink has been more reliable than Comcast and ATT fiber when I lived elsewhere. I've never had issues which is why I assumed it was a patch thing. Fortunately, it seems to have cleared up. Apparently, there was a health/bandwidth issue with one of the ground stations that caused my IP to jump every few minutes. Interestingly, connecting to a VPN fixed the issue as well.

Thanks for the IP to trace, that was going to be my next path as I had severe issues with packet drops on Comcast when going through certain routes. I did check a packet loss test on another IP and it didn't drop anything. Just tried that IP and out of 1000, I had 2 drops, which is far better than any other ISP I've been on.

[Rhombus]

I have the same issue. Only started after patch 6.15. Was perfect before that