Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
I've run into this plenty of time with system map and I've narrowed it down to I'm listening to debates on youtube while playing.
Turn those off and no issue, hit play and axe the video to 360 no problem, leave it at default 720/1080 and I get infinite loading.
I'm not putting it past Fdev to have done something in this years patches in regards to network resync but letting the game have all of my 24 mbit solves the issue.
No idea if this will solve your issues as I only have one single case to build a hypothesis from.
And if the desyncs never sync back then it doesn't have to be a bandwith issue but a quality issue. Wireless, bad ISP switches, not using screened cables etc etc all those can give you packetloss and even reaching 0.3% packetloss will make quite a few games totally unplayable and in the best of cases you experience severe rubberbanding.
So when you've checked for downloads in the background, network for connected devices I highly suggest you run a ping plotter program ( pingplotter is a good one eventhough the free is a bit meh). Run that baby and ping 8.8.4.4 every 1 second for 24 hours.
That'd be googles ping server that will not disconnect you due to ping flooding.
Every second so you won't miss if there's a sudden spike.
24 hours so you can check if the issue occurs when people get home from work (quite a few people think they have dedicated whatever mbit but they actually share it between many house holds).
The column you are looking for is called PL% and should be 0. Now if you find that in one of the jumps the thing spikes to 100% and never ever responds that's ok. Some ISP switches simply declines pings by default.
Edit: A bit rambly, but that's two things to check and I do hope you find the error.
It only happens when I jump to another system right after launching from a planet. Could be a specific network issue?
It could. It could also be a local issue, but my bet is on network. It could be just a tiny setting on your comp or router that means it only causes the problem in very specific cases.
For example, a few years ago i suffered frequent disconnections. I raised a ticket with FD and we ran some checks. Turned out my ISP router had a max packet size a tad lower than my PC. This meant that large packets hitting my router would get fragmented. Wouldn't affect a lot of things, including other games most of the time, but it did mean that sometimes packets would arrive out of order or just be lost. This is critical when jumping to a new system or changing instance.
It probably also explained why i was having smaller issues elsewhere with my networking that i could never really diagnose.
So we lowered the MTU on my NIC (didn't want to change the router setting, presumably the ISP did it like that to be compatible with their own network), and bob's your uncle, things improved massively.
I believe FD did make changes to their code to be more tollerant to packet fragmentation, but even so you want to avoid it where you can, as UDP won't resend lost packets and TCP will wait for packets to be resent, but that hits performance.
" ... problem in very specific cases ... ", you could on the money with that. It only seems to happen in that particular situation. I guess I could see what planet I launch from to jump to whichever system so I can better example what's going on.