Hey, I'm having a problem which I think is related to my computer but I thought I'd check here to rule out being a game error.
Basically, Starcraft 2 takes a good 2 to 3 minutes to launch after clicking it. The little rectangle logo shows up in windows then the delay before switching to the log-in screen. I was wondering if this could be related to the maintainance, maybe the game checking for a response from b.net or something. Has anyone else seen this? Tried reinstalling it (then lost the patches, doh), thought it was a problem with my computer, did a clean system recovery to factory conditions, and yet the problem persists.
Like I said, I think it's a problem with my computer, so if anyone is knowledgable in that area and has any idea, that'd be helpful too. I took it to a computer service place who said they detected no hardware issues. I tried swapping out memory cards, and afterwards I also notice dxdiag isn't seeing all 8g of my ram, just 6g. I was under the impression that it didn't matter which slots the cards went in though, so would swapping them cause this if all the cards and slots were indeed functional?
I opened SC2 to see if anything had updated and the box with the logo came up and froze, but my computer's fine, so... it just might be a launch thing?
It's because it's trying to connect to battle.net to check for a patch, but since the patch servers are down it isn't getting a response.
It'll go away when the beta servers come back online. But why would you be trying to start SC2 directly anyway instead of through a launcher or the editor (which don't have this problem.)
But why would you be trying to start SC2 directly anyway instead of through a launcher or the editor (which don't have this problem.)
Because the computer AI on maps that uses it sometimes doesn't work when playing the map via test document. Thanks for the replies guys. I think the problem can be temporarily solved by going into tools in internet explorer and checking "work offline."
Hey, I'm having a problem which I think is related to my computer but I thought I'd check here to rule out being a game error.
Basically, Starcraft 2 takes a good 2 to 3 minutes to launch after clicking it. The little rectangle logo shows up in windows then the delay before switching to the log-in screen. I was wondering if this could be related to the maintainance, maybe the game checking for a response from b.net or something. Has anyone else seen this? Tried reinstalling it (then lost the patches, doh), thought it was a problem with my computer, did a clean system recovery to factory conditions, and yet the problem persists.
Like I said, I think it's a problem with my computer, so if anyone is knowledgable in that area and has any idea, that'd be helpful too. I took it to a computer service place who said they detected no hardware issues. I tried swapping out memory cards, and afterwards I also notice dxdiag isn't seeing all 8g of my ram, just 6g. I was under the impression that it didn't matter which slots the cards went in though, so would swapping them cause this if all the cards and slots were indeed functional?
I opened SC2 to see if anything had updated and the box with the logo came up and froze, but my computer's fine, so... it just might be a launch thing?
I'm going to go out on a limb here and say it's tied to owning retarded forum icons.
It's because it's trying to connect to battle.net to check for a patch, but since the patch servers are down it isn't getting a response.
It'll go away when the beta servers come back online. But why would you be trying to start SC2 directly anyway instead of through a launcher or the editor (which don't have this problem.)
Well, I've got a mere 2 gigs and it doesn't even take me that long to start it up, so it's definitely not a hardware issue.
I have the same problem, sometimes I just exit the application and start it again and it goes away.
Because the computer AI on maps that uses it sometimes doesn't work when playing the map via test document. Thanks for the replies guys. I think the problem can be temporarily solved by going into tools in internet explorer and checking "work offline."