Long loading after the update

(FireWorks) #21

Its kinda cool how you can summon good souls in this board. Reminds me of genie in a bottle :slight_smile:

(prothis) #22

Happening here too, and the difference is noticeable even on an SSD. From watching the drive activity LED on my case, there doesn’t even seem to be heavy read access to the drive, so I’m not sure what exactly it’s doing to take so much longer.

(x3mytiz) #23

It’s not a hardware issue. I have the same PC like last week, when I have not this problem at all.

(FireWorks) #24

So far I only had it when joining into running matches.
Connecting to a fresh one works fine.

Anyone can confirm?

(x3mytiz) #25

I think you are right. Lobby connection seems to work like past weeks, in match connection took over a minute :frowning:

(Wolven) #26

Same issue here. When joining a running match it takes forever and a half to load. I have a pretty nice rig, with SSD and plenty of memory. I did not have this issue prior to the October patch.

(NxA_Noxie) #27

Thanks for alerting me @Faraleth :wink: - Hey guys we are looking into this, if your PC is on the higher spec end it’s unlikely a PC issue. I do know there are issues with loading times with lower end PC’s ect. Bare with us, and as always please feel free to add any helpful information you may have. I know this issue is frustrating.

(Verticules) #28

@NxA_Noxie
The lengthy map loading screen only happens when joining a match in progress.

(FireWorks) #29

[quote=“VerticallyObese;92574”]@NxA_Noxie
The lengthy map loading screen only happens when joining a match in progress.[/quote]

After a day of playing: Confirmed.

(complimentaryTee) #30

+1

(Amerika) #31

Yup, I am getting it too. Only happens when I join an already in progress game and it lasted nearly ~60 seconds. I normally load in a couple of seconds.

(B_Montiel) #32

I also noticed it. And it may have appeared prior to the update. One already mentionned it in the patch note thread. But after thinking about it, the day before the patch, I was doing some .ini research/testing. I ended up having long loading times, from which I thought I messed them up. And deleting the incriminated .ini did not change anything. So that was probably this issue already acting.