Please upgrade your browser for the best possible experience.

Chrome Firefox Internet Explorer
×

Client crash at the end of the queue

STAR WARS: The Old Republic > English > Customer Service
Client crash at the end of the queue

Firahin's Avatar


Firahin
12.23.2011 , 08:59 AM | #1
Hi, I am playing on Frostclaw and have been experiencing the following issue since the patch on wednesday morning.

I join the queue, and then the counter goes down to "zero", well 1, 3 or something close to it at least. Then when the game "pops" the client crashes. Since yesterday this have been happening 100% of the time, if there have been a queue. If there is no queue I am connected to the game directly.

The issue have been happening over two kinds of mobile broadband (~2.5 Mbit/s latency of approx 200ms) and one fixed line connection (100/100 Mbit fiber).

And like I said, this issue began with the morning patch on the 22:nd.

Any other people experiencing the same issue?
Any know solution to the known issue?

Regards
Firahin

Wootie's Avatar


Wootie
12.23.2011 , 10:17 AM | #2
bump kinda.. as I've seen this issue reported beore... meanwhile there's a lot of other freeze and crashes going on... so this might be related.. or not who knows.

Bump.. me and a lot of others... just try an advanced google search of just www.swtor.com/community using keywords crash or freeze... maybe try keywork queue crash or queue freeze...

http://www.swtor.com/community/showthread.php?t=43204 (my issue)
http://www.swtor.com/community/showthread.php?t=24693 (big thread on similar issues)
http://www.swtor.com/community/showthread.php?t=43860 (good summary thread of major issues)

Firahin's Avatar


Firahin
12.24.2011 , 06:15 AM | #3
With the last client patch the crashes occur frequently.

Almost 100% when the queue pops, which means i can only play when there is no queue.
Often when zoning, the cutscene starts with the ship and then client crash. And when coming back online you have to try the cutscene again... with a possible crash.

I REALLY hope this issue will be sorted soon, since it is very annoying.

And it all began with the patch that came 21:st of december.