"endless loading screen" in spvp [MERGED]

#1 - Oct. 8, 2012, 10:02 a.m.

“nadjp.1079
wtf is this a bug or what? I died in tournament and cant get back to start becouse of the endless loading… cmmon its not rly funny -.-
October 08, 2012 13:14
Permalink
Revelstoke.8924
This happened to me during a regular game of Khylo. I can hear the game/battle noises in the background but the load screen won’t go away. Had to force quit the game and relog. First time it ever did that was after 10/7 patch.
October 08, 2012 13:16
Permalink
CC Eva
Community Coordinator
Hi everyone.
Nadjp, try to go out the game and reconnect, to see if the issue is still there (most of the times it vanishes after exiting). If not, please, contact Customer Support.
Thanks and sorry for the inconveniences”

dont close if there is still sth to be said

this is game bug not individual issue, happening to me and many ppl in khylo and capricom almost 100% so no rank points = no spvp till update

CC Eva

#31 - Oct. 9, 2012, 12:21 a.m.

Hi everyone.

I acknowledge my mistake as I did not know it was a general problem among players. Therefore we will forward this situation to the team today.

Thanks.

Edit: We have also merged threads to keep the reports about this problem in a big one

Mélanie Corolleur

#39 - Oct. 9, 2012, 6:34 a.m.

Thank you all for your reports regarding this issue. Our teams are currently working on this issue as a priority. We will update you on that matter as soon as possible.

In the meantime, we’d like to thank you all for your patience and understanding.

DavidOrtiz

#112 - Oct. 11, 2012, 7:53 a.m.

Hi everyone.

The team is aware of this issue and working to get it resolved. Thanks for your understanding.

Best

ColinJohanson

#152 - Oct. 11, 2012, 7:08 p.m.

Hey folks,

We will be pushing a build shortly that should resolve this issue. Thanks very much for being patient, this one was more complicated to fix than normal, but it looks we’ve got a handle on it and will get it taken care of very soon.

CameronDunn

#156 - Oct. 11, 2012, 11:44 p.m.

This should be fixed in this build (the one which just happened) – please reply to this thread to let us know!