SC2 Beta Coverage (Loki Shack)

[Theia_Loki]

[Very Late Update]

Haven't been able to win any games against human opponents in phase 2. Could be because I'm rusty from not playing since phase 1 ended.

Asides from the lag (which is present about every two seconds for about a second), was experiencing a very weird bug whilst playing as zerg: the creep tends to go temporarily poof (as though it wasn't there, but the game functions as though it was still there).


And in case anyone asks about my conputer's System Specifications...

Operating System: Windows 2.5.1.2600 (Service Pack 2) (XP)
CPU Type: Intel(R) Pentium(R) 4 CPU 3.00GHz
CPU Speed (GHz): 3.019
System Memory (GB): 1.999
Video Card Model: ATI Radeon HD 3650 AGP
Hard Drive Space (D drive): close to 1TB overall
Desktop Resolution: 1152x864 (standard resolution I use)

Still a pain. I should be able to run the beta smoothly without having to lower the game settings, yet I still experience lag regardless.

[Mucky]

I should be able to run the beta smoothly without having to lower the game settings

lol your computer specs barely exceed that of my 4 year old computer's and doesn't meet the recommended requirements in either case

[Theia_Loki]

About that close to 1TB of HD space, it's split into two drives: D and C with over 200GB and 700GB respectfully. SC2 and other programs (i.e. Wc3 and MS Word) are on the D drive whereas C just has a lot of torrent stuff on it.

Might have to get to improving most (if not all) of it's current specs (mainly the Video Card and anything else major). Then again, the computer in question is the one that everyone in my household uses (and it's just one of two or three). Could just fix this by getting another drive so that I can have my stuff on it.


But, back to SC2. Tried logging in today, and it came up with an error saying I'm using a client that isn't recognized.
I've got a screenshot attached just in case you don't believe me.

[Ricky_Honejasi]

That client happened more than once before to me.

Usually it happened when there was a new patch and the b.net login server itself didn't update to the next patch. Although it might sometimes plain happen anyway.