For the past few days, I have noticed a significant delay upon loading into a sector. It hangs on the transitioning black screen for about 0.5-1.5 seconds, similar to the extra delay tacked on during CSR (although not quite as long, and not as consistent). This happens with no plugins installed and default config. The only settings I changed while testing were to change Cinematic Camera Mode to First-Person and Preload All Resources on Startup to On to have an accurate idea of the jump time, since those are the settings I normally use. I've checked and reset my connection and there doesn't appear to be any change there. Ping is approximately the same as usual at ~60ms. I haven't noticed any difference in gameplay within sector, only on sector load.

I understand this is very vague..so let me know if there's anything else I can provide that would be helpful. This did start *around* the time the new persistent events were introduced, but obviously correlation != causation and I don't know if that had any effect on load times.

We actually saw your discussion in-game and made note of it internally, although we appreciate the bug report in addition (since we usually don't catch these kinds of chats).

We don't know what's impacting you, but it's probably not the Persistent Events.

We've actually made a lot of improvements to the network side of the game over the last 1.5 weeks, and perhaps the biggest change tonight, about 3 hours ago, with the addition of a new server-side congestion management algorithm for certain cases (like changing sectors).

We've been measuring some problems that we became aware of, because of our investigations after the LTT video, and so far it looks like we've managed to mitigate the issues we discovered.

But, if you continue to experience problems, let us know. There can be a variety of causes to this kind of thing, not all of which are purely on our side. We've seen some occasional internal issues with the cloud provider currently hosting the game. We want to migrate to another provider, but that's a big undertaking and we've been buried in client-side fixes of late.

This issue seems to be resolved, at least for now. I'm not sure what was causing it or if it was on my end, I didn't change anything in particular but you never know. I'll let you know if it happens again.

Thanks for the reply and thanks for all the work to make gameplay smooth and seamless :)