|
|
 |
|
|
Pages: 1
Starcraft Problem!
(Click here to view the original thread with full colors/images)
Posted by: Allanb
When I make a game no one ever joins. My friends make the same game right after and its fullhouse immediatly. Weird, because I have 1g lag (cable). I emailed Blizzard and they say its a packet problem with windows, and there is no official fix to this yet.
Does anyone here know a way to fix it?
Posted by: ZeRo_MaXwInG
did you try to experiment with your friends? you can create a game, phone your friend and tell him/her the game name and c if your friends can c your game on the post and join it. Post the results so we can help your further.
Posted by: Kdr Kane
Yes, this is primarily an issue with Windows 2000, XP and I think Windows ME. Blizzard blames it on Microsoft, but it's a bug in Blizzard's game client.
The solution is to logout, login and start a game immediately. You have to do this each time you create a game.
Posted by: ZeRo_MaXwInG
Everyone blames Microsoft. But I think your correct that Blizzard should do something about this. In that email u sent to Blizz, did the representative mention any sort of patch that would be released in the future for people using XP? I would like to know system specs of your computer but more importantly, your connection methods and details. This would also help the people at Blizzard.
Try emailing Blizzard and ask if there would be future patch that would fix this, if not already done so. Good luck
Posted by: Gunslinger
Actually, it's more the fault of Windows than anything, but not really intentional. That's not Microsoft bashing, as there's no way they could have known - just a simple fact.
I will quote the technical problem:
The problem is that the recvfrom function is enchanced in Windows
2000. It will now return a (non-fatal) error message if there has
been an ICMP port unreachable error for a previous UDP sendto on the
socket. The problem with SC/BW is that it treats any error from
recvfrom as a fatal error and stops processing data.
That quotation mentions Windows 2000, but this also applies to Windows XP.
This can actually be easily fixed by the user by setting up a firewall to block all ICMP port unreachable errors, as I have done on my machine. However, this is an issue that is easily fixable with a patch to Starcraft. Why has Blizzard not acted on this? Well, they're busy with other thing, I would imagine.
Ah well. It's a function of Windows that causes the issue, but Blizzard should be able to patch the client side problem easily. Call it a share of the blame.
Posted by: Allanb
I use windows ME. They siad theres nothing I can do about it and they are looking into the problem =P
Posted by: DemonBob
Are you behinda firewall? If so close it down. i use to have the same problem behind mine...
|
|
|
|
|
