|
On May 24 2010 13:37 trace wm wrote: I hate to imagine the hours per week the Blizzard staff will be pulling from now until the end of July.
Just think of the 6+ years they have been going at turtle pace and you might not feel so bad for them
|
On May 24 2010 14:04 standingcow wrote:Show nested quote +On May 24 2010 13:37 trace wm wrote: I hate to imagine the hours per week the Blizzard staff will be pulling from now until the end of July. Just think of the 6+ years they have been going at turtle pace and you might not feel so bad for them
Agreed. Considering the gap between SC1 and 2 and Diable 2 and 3.... yea they had time.
|
On May 24 2010 09:13 theDreamStick wrote:Show nested quote +On May 24 2010 09:03 Sc1pio wrote:On May 24 2010 09:01 Two_DoWn wrote: Can someone just explain to me how a patch can fuck a game up so badly? I'm not at all programming savy, so im not sure if this is an apt analogy, but if i am writing a paper and decide i want to change a word to something else (change ultra health) i just go in and make the change, and it doesnt mess up the rest of my paper. If i want to change a paragraph around (add facebook/ map publishing to bnet) I add the paragraph, then go back to make sure I didnt repeat myself in another paragraph and that the paper still makes sense. Did blizzard just not go back and check to see if the paper still made sense?
Or does my analogy not make sense and I should stick to writing. My best guess as to what the problem is (and your analogy is wrong for a bunch of reasons which I can't really explain because I'm not smart enough) is that they changed the protocol from TCP to UDP, which people think was a good change, but somewhere in that code they screwed something up. So I'm an ECE student that's going to focus on networking/security. But I'm still a student, so what would I know. Here's my guess: Essentially, they tried to implement UDP. Probably involved a small amount of code. Shouldn't really mess things up that badly. For those that don't know, UDP is actually pretty good for games. TCP: reliable internet connection. If I send the integers 1, 2, 3, 4 over the internet to you, you WILL receive them in the exact same order. UDP: an unreliable connection. Packets can be lost, or sent out of order. Imagine if you were running a clock on a server. I wouldn't care about a packet that got lost 5 seconds ago because that's not the current time anymore. So for something like Starcraft 2, obviously TCP is nice, so that there's less syncing between clients. The problem is that this contributes lag to the game (Think SC:BW with setting to extra high latency, etc,) From a programming perspective, implementing UDP must be simple, right? Not really. I assume they're writing everything with multi-threading. Networking with multi-threading is a nightmare. I only have a bit of experience (I did a multi-threaded web proxy with a cache in C. This is nowhere near SC2's complexity, and it had tons of bugs). Factor that in with trying to sync both clients, and syncing the TCP/UDP among multiple threads, and you have a nightmare that has tons of hidden bugs. As to why their server has been crashing like mad, well it's Blizzard. my 2 cents.
My guess would be a threading or synchronization error. If you run your server and its calling CreateThread() for each new connection and you forget to ExitThread() then that can cause problems. If your server just constantly creates new threads, you can run out of memory. Once your server hits a threshold it will start killing threads.
Now, picture a machine with 10,000+ users trying to connect to it and play. That is a lot of threads being created and if it exceeds the amount of memory that the server can handle, it will tear down the process. This in turn should not give a warning that someone is dropping from game. It will most likely just freeze or give unexpected results.
In saying that above, that is only one possible race condition or logic error that could be occurring. It is pretty difficult to test for every logic error or race condition. Even ones staring you in the face saying HOW COULD YOU MISS THIS?
|
On May 24 2010 20:09 Tllyx wrote: My guess would be a threading or synchronization error. If you run your server and its calling CreateThread() for each new connection and you forget to ExitThread() then that can cause problems. If your server just constantly creates new threads, you can run out of memory. Once your server hits a threshold it will start killing threads.
This is almost certainly written in c++, and there for has no automatic memory manager. So threads would not get killed. you would just run out of memory and the server would probobly just crash at some point.
edit: And the beta won't be going down before the end of p1
http://forums.battle.net/thread.html?topicId=25026564212&sid=5000&pageNo=2#28
|
On May 24 2010 21:32 Vip3ra wrote:Show nested quote +On May 24 2010 20:09 Tllyx wrote: My guess would be a threading or synchronization error. If you run your server and its calling CreateThread() for each new connection and you forget to ExitThread() then that can cause problems. If your server just constantly creates new threads, you can run out of memory. Once your server hits a threshold it will start killing threads.
This is almost certainly written in c++, and there for has no automatic memory manager. So threads would not get killed. you would just run out of memory and the server would probobly just crash at some point. edit: And the beta won't be going down before the end of p1 http://forums.battle.net/thread.html?topicId=25026564212&sid=5000&pageNo=2#28 Thanks for that post, updated the URL, seems as though this thread is useless now and blizzard had a fun little troll.. /facepalm
|
On May 24 2010 09:28 Opinion wrote: Given that i have no idea what goes on inside of Blizzard, have no advanced degree or knowledge of computers, servers or the inner workings of Battlenet I'm going to make a juvenile assumption that they are doing this to personally attack me and the other beta testers.
I base this on nothing but my own egocentric world view and entitled attitude.
And what would a baseless attack against Blizzard be without also stating with 100% certainty that Blizzard will Nerf a unit i enjoy and this Nerf will be based on their lack of knowledge in how to create games and their desire to make it impossible for me to win games.
tldr: Blizzard hates me personally and this server "maintenance" is a thinly veiled spiteful attack against me.
Haha this post made me smile a lot.
It describes so many people that just post uneducated, opinionated nonsense because they are angsty about the beta not being finished or whatever gripe they have. Obviously it's Blizzard's fault and they obviously aren't trying to fix it and they obviously are doing it just because they hate us.
Opinion (your name reflects your tone quite well), you are my new best friend.
|
On May 24 2010 09:13 theDreamStick wrote:Show nested quote +On May 24 2010 09:03 Sc1pio wrote:On May 24 2010 09:01 Two_DoWn wrote: Can someone just explain to me how a patch can fuck a game up so badly? I'm not at all programming savy, so im not sure if this is an apt analogy, but if i am writing a paper and decide i want to change a word to something else (change ultra health) i just go in and make the change, and it doesnt mess up the rest of my paper. If i want to change a paragraph around (add facebook/ map publishing to bnet) I add the paragraph, then go back to make sure I didnt repeat myself in another paragraph and that the paper still makes sense. Did blizzard just not go back and check to see if the paper still made sense?
Or does my analogy not make sense and I should stick to writing. My best guess as to what the problem is (and your analogy is wrong for a bunch of reasons which I can't really explain because I'm not smart enough) is that they changed the protocol from TCP to UDP, which people think was a good change, but somewhere in that code they screwed something up. So I'm an ECE student that's going to focus on networking/security. But I'm still a student, so what would I know. Here's my guess: Essentially, they tried to implement UDP. Probably involved a small amount of code. Shouldn't really mess things up that badly. For those that don't know, UDP is actually pretty good for games. TCP: reliable internet connection. If I send the integers 1, 2, 3, 4 over the internet to you, you WILL receive them in the exact same order. UDP: an unreliable connection. Packets can be lost, or sent out of order. Imagine if you were running a clock on a server. I wouldn't care about a packet that got lost 5 seconds ago because that's not the current time anymore. So for something like Starcraft 2, obviously TCP is nice, so that there's less syncing between clients. The problem is that this contributes lag to the game (Think SC:BW with setting to extra high latency, etc,) From a programming perspective, implementing UDP must be simple, right? Not really. I assume they're writing everything with multi-threading. Networking with multi-threading is a nightmare. I only have a bit of experience (I did a multi-threaded web proxy with a cache in C. This is nowhere near SC2's complexity, and it had tons of bugs). Factor that in with trying to sync both clients, and syncing the TCP/UDP among multiple threads, and you have a nightmare that has tons of hidden bugs. As to why their server has been crashing like mad, well it's Blizzard. my 2 cents.
you have to think of it like this, TCP is a checked packet and UDP is an unchecked packet.
TCP is like a heat sinking missle, it is going to hit it's target and the information is going to be received in the correct order.
UDP is unchecked, meaning the data goes from your computer to the receiving computer, but there is no order involved and it is the application's responsibilitiy to receive and interpret the data.
Here is an analogy.
TCP, microing your army against an opponent. UDP, setting your unit waypoints to the opponents base and pay 0 attention to your units after creating them.
|
I'm sure the Facebook friend implementation fucked up the servers.
|
Wait, I'm confused. I get that the beta isn't going down until June 1st. But from the way this is worded, does that mean it's only going down for a few days? Or for a couple of weeks like they originally said on the 17th?
|
On May 24 2010 22:49 accaris wrote:Wait, I'm confused. I get that the beta isn't going down until June 1st. But from the way this is worded, does that mean it's only going down for a few days? Or for a couple of weeks like they originally said on the 17th?
The way I was interpreting it was that they were taking it down for a few days prior to the prolonged downtime to address some critical issues. I assume the prolonged downtime will stand.
|
On May 24 2010 22:49 accaris wrote:Wait, I'm confused. I get that the beta isn't going down until June 1st. But from the way this is worded, does that mean it's only going down for a few days? Or for a couple of weeks like they originally said on the 17th?
Almost surely weeks. Probobly just badly formulated by the blue poster
|
Due to network congestion, traffic load balancing, or other unpredictable network behavior, IP packets can be lost, duplicated, or delivered out of order. TCP detects these problems, requests retransmission of lost packets, rearranges out-of-order packets, and even helps minimize network congestion to reduce the occurrence of the other problems. Once the TCP receiver has finally reassembled a perfect copy of the data originally transmitted, it passes that datagram to the application program. Thus, TCP abstracts the application's communication from the underlying networking details. TCP is optimized for accurate delivery rather than timely delivery, and therefore, TCP sometimes incurs relatively long delays (in the order of seconds) while waiting for out-of-order messages or retransmissions of lost messages. It is not particularly suitable for real-time applications such as Voice over IP. For such applications, protocols like the Real-time Transport Protocol (RTP) running over the User Datagram Protocol (UDP) are usually recommended instead.[2]
It could totally be that their engine expects that all packets arrive and in order.. But with udp you never know...Some might be lost or arrive later via different route and the engine is confused when that happens..
I played 4 matches since patch and was dropped from 3..
|
he is speaking about May 31st or June1st. so why did you make this post in the first place???
prolly why you added the ending of your post
|
|
|
From Blizzard:
TCP involves a lot of extra overhead. We're changing stuff to see what would happen on both the client and server. The current issues we're having don't involve UDP.
+ Show Spoiler +
|
On May 24 2010 22:59 Dukke wrote:Show nested quote +On May 24 2010 08:49 NuKedUFirst wrote:We have a repair utility in testing internally right now and we're also going to shut the beta down for a few days. With luck, it'll be in the next time the Beta is brought up. 6. Re: Patch issue 05/23/2010 01:45:10 PM PD Source: http://forums.battle.net/thread.html?topicId=25026564212&sid=5000&pageNo=1#6Currently it's planned to be ended on June 1 to give people time to play during Memorial Day. It may change if we have to take the servers down earlier but if things stay up, that chance is there.
Source: http://forums.battle.net/thread.html?topicId=25026324408&sid=5000&pageNo=1at least the repair will get done? no word if on if they are extending phase one. Edit: added another quote on a separate thread. Edit2: seems as though blizzard was trolling us.. ...Kinda makes this thread useless.. Wow, what a quality post. hint, hint? lol he is speaking about May 31st or June1st. so why did you make this post in the first place??? prolly why you added the ending of your post
The first quote seemed like they were taking it down before may 31st because of the server issues.
|
On May 24 2010 23:19 Onean wrote:From Blizzard: TCP involves a lot of extra overhead. We're changing stuff to see what would happen on both the client and server. The current issues we're having don't involve UDP. + Show Spoiler +
I wouldn't really trust a blizzard employee to say the the current issue isn't UDP related. It is most certainly a connection stability issue, and while UDP is a great protocol for gaming, they obviously aren't checking in the data correctly.
I'm sure most everyone here has been getting the lag window pop up and say that you are not connected to the game, and you can watch it count all the way down from 60 to 0 without re-establishing a connection.
One thing that is odd, if you alt tab out and back into the game during one of these "lag-out" sessions, you re-connect to the game and don't get dropped.
|
I'm kind of confused by the edits on the first post and saying Blizz trolled, because I missed that part?
How long is it roughly going down for? Till the 31st? Only for a bit?
|
It wouldn't make any sense for Blizzard to say that bnet will be down for "a few days" after May 31, because that was the date it was supposed to go down anyway. So that's where a lot of confusion lies right now.
|
On May 24 2010 09:06 eXNewB wrote:Show nested quote +On May 24 2010 08:54 Gamer0ne wrote:Nobody is taking the beta seriously anymore  IT'S BETA!!!!! omg what is wrong with you people! seriously the replies in this thread seem like a bunch of babies crying A) THE GAME IS NOT EVEN OUT YET B) be happy bliz let you play it in the first place C) you have not paid a dime yet for this game so sick of people cussing Blizzard when really you should be thanking them for the opportunity to play "the next big competitive game" User was warned for this post
EX?-newb
have you played any other "Beta" test versions of games like Heroes of Newerth or that other one? They were nearly flawless, had thousands of players, and updated without massive cluster-fails... and it was only the company's 2nd or 3rd release.
We are talking about Activision-Blizzard here (not Blizzard since it has been dead for some years now)... This kind of company's beta-tests should be better than a company like S2's retail product. A-Blizz should not be releasing this crappy platform (i.e. bnet 2.0) at all as it is... and they have the gall to call it an upgrade from the original battle.net ?
if this beta should offer any insight into the current state of the company, activlizzard, then I can only be make the analogy of something like... hmm... how about mickey mouse in fantasia with the broomsticks? "The Sorcerer's Apprentice"
Mickey (Blizzard) is that little guy in all of us who dreams that some day he too can make it big. Unfortunately, his dreams are bigger than his abilities, as he borrows his mentor's forbidden magic hat (WoW cash plus + legacy created by the legendary blizzard teams of yore) and enchants a broomstick (hires xbox and C&C daryls) to do his work for him.
Sure that he's mastered the sorcerer's art (game design), Mickey relaxes into a nap.
Fantasizing that he's in control of the very forces of nature, he's rudely awakened to a flood of reality (TL netizenz); even the simple broomstick (the basic bnet platform) is beyond his control. Realizing too late that there's no shortcut to greatness, Mickey learns you've got to slosh your way to the top one bucket at a time (or just make a deal with Zuck the Fuck, get paid, and wait for your new MMO to debut)
If sc2 turns out to be a great game.. so be it. But as Browder has said in interviews, they just made a game with cool units and balanced from there... Let's face it, this is what they are concerned with, namely turning a profit on all the SC intellectual property and parleying it into some kind of passive revenue cash-cow (pay-to-play outside of NAmerica, facebook renting banners on bnet, micro-transactions, license fees in korea/elsewhere, merchandise, film, etc) while they develop this new MMO of theirs.
RTS is dying in the face of other, more "relevant" (see profitable) ventures. This is battle.net web 2.0. Rage directed towards Activlizzard for their failures subsides if one understands that the strategies, tactics and motives of game companies have changed tremendously from the time when Brood War was produced. Its not about making a good game any more- chinese MMOs prove this- its about making a shinny piece of crap that other crap can be lynch-pinned onto and sold to fund the next, new-and-improved shinny piece of crap.
|
|
|
|
|
|