|
The amount of code involved in a game like starcraft 2 is mind boggling, considering the fact that it is both a server side with numerous servers and a client side that needs to be coordinated and factoring in just how often they are adding patches and hotfixes. The most suprising thing to me as a software engineer is that there has not been way way way waaay more bugs.
Most people do not realize just how many bugs can pop up in computer software by making changes to the most insignificant things, and the thing about bugs is that they are always surprising the coders more than anyone else. I bet you the first people who went "omg how the fuck did it do this?!" when the mass drops started happening was the programmers at blizzard 
There are no bugs that you expect, because if you expected them you would had prevented them in advance, bugs are those things where you go "...that... should not be happening??"
|
Aslong as they fix this shit, heres to hoping
|
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
False sir. I'm sure a large percentile of us have already paid the full payment to pre-order it such as myself. It could come out in November and that wouldn't bother me. I just want the game to be running 100% before it's released. I say take your time Blizzard and get it right.
|
Well, my last 20~ games have been problem less *knock on wood*, anyone else?
|
On May 24 2010 12:11 ymirheim wrote:The amount of code involved in a game like starcraft 2 is mind boggling, considering the fact that it is both a server side with numerous servers and a client side that needs to be coordinated and factoring in just how often they are adding patches and hotfixes. The most suprising thing to me as a software engineer is that there has not been way way way waaay more bugs. Most people do not realize just how many bugs can pop up in computer software by making changes to the most insignificant things, and the thing about bugs is that they are always surprising the coders more than anyone else. I bet you the first people who went "omg how the fuck did it do this?!" when the mass drops started happening was the programmers at blizzard  There are no bugs that you expect, because if you expected them you would had prevented them in advance, bugs are those things where you go "...that... should not be happening??"
So as a software engineer, are you saying that you would release a major patch that changed many fundamental things about the network architecture before you left work for the weekend? They have already said on the Bnet forums that it will not be fixed this weekend because the staff are not there to do it.
|
"just gonna fix this here, whoops, all well, have fun on wc3 and sc1 for the next couple days xD"
|
On May 24 2010 12:22 Design wrote:Show nested quote +On May 24 2010 12:11 ymirheim wrote:The amount of code involved in a game like starcraft 2 is mind boggling, considering the fact that it is both a server side with numerous servers and a client side that needs to be coordinated and factoring in just how often they are adding patches and hotfixes. The most suprising thing to me as a software engineer is that there has not been way way way waaay more bugs. Most people do not realize just how many bugs can pop up in computer software by making changes to the most insignificant things, and the thing about bugs is that they are always surprising the coders more than anyone else. I bet you the first people who went "omg how the fuck did it do this?!" when the mass drops started happening was the programmers at blizzard  There are no bugs that you expect, because if you expected them you would had prevented them in advance, bugs are those things where you go "...that... should not be happening??" So as a software engineer, are you saying that you would release a major patch that changed many fundamental things about the network architecture before you left work for the weekend? They have already said on the Bnet forums that it will not be fixed this weekend because the staff are not there to do it. If it is a beta test then ofcourse yes, if it was running on internal testing which I bet you it was because issues like the ones we are seeing now are usually the stuff you only notice once you get enough data going through the infrastructure. In a beta test there is no reason whatsoever to hold stuff back because you are on a really tight schedule and on the off chance that shit hits the fan, it was still worth the risk.
Obviously if this was a retail patch then you wouldn't ever put in a patch of any kind on a friday evening unless you got maintenance people working on weekends but this is not the case.
|
On May 24 2010 12:29 ymirheim wrote:Show nested quote +On May 24 2010 12:22 Design wrote:On May 24 2010 12:11 ymirheim wrote:The amount of code involved in a game like starcraft 2 is mind boggling, considering the fact that it is both a server side with numerous servers and a client side that needs to be coordinated and factoring in just how often they are adding patches and hotfixes. The most suprising thing to me as a software engineer is that there has not been way way way waaay more bugs. Most people do not realize just how many bugs can pop up in computer software by making changes to the most insignificant things, and the thing about bugs is that they are always surprising the coders more than anyone else. I bet you the first people who went "omg how the fuck did it do this?!" when the mass drops started happening was the programmers at blizzard  There are no bugs that you expect, because if you expected them you would had prevented them in advance, bugs are those things where you go "...that... should not be happening??" So as a software engineer, are you saying that you would release a major patch that changed many fundamental things about the network architecture before you left work for the weekend? They have already said on the Bnet forums that it will not be fixed this weekend because the staff are not there to do it. If it is a beta test then ofcourse yes, if it was running on internal testing which I bet you it was because issues like the ones we are seeing now are usually the stuff you only notice once you get enough data going through the infrastructure. In a beta test there is no reason whatsoever to hold stuff back because you are on a really tight schedule and on the off chance that shit hits the fan, it was still worth the risk. Obviously if this was a retail patch then you wouldn't ever put in a patch of any kind on a friday evening unless you got maintenance people working on weekends but this is not the case.
Why does it matter if it is a retail patch or not? It is just bad policy. Not that hard to wait til Monday, when you have people on hand that can go through and find the issues and fix them as fast as possible. Would definitely save the company a lot of the abuse that has been hurled at it these past two days.
|
Can someone decipher this gibberish for me? Does this mean it's official that the beta will be shut down sometime before the planned date of May 31st, or what? If so, why is this information being posted in some totally random thread instead of being announced? This was posted 7 hours ago?
|
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.
Unfortunately, in a paper, you can do that.
In software, there are concepts called cohesion and coupling. Coupling is a problem, cohesion is not. Coupling causes certain classes (basically what your software runs with) to be dependent on each other, while cohesion is classes working well with each other, but still independent of each other (meaning that one class can work in other systems).
In designing a large system, you are going to have a lot of information sharing, as software is built upon many classes and interfaces. Where as your words depend on each other, you can just mark out a word and a person will see that, and ignore the mark out and fix the issue in the brain. A computer won't. If you take something away that software looks for, without any logic that tells it to handle that, then it can (probably will) break down. They may not have expected something to happen when they finally implemented all these new features. Perhaps there was a conflict somewhere. Who really knows (I'm sure R1CH has an idea)?
|
the games running for me fine if anybody doesnt notice i haven't read most of the posts, but 6 games so far not a single problem/trace of lag
|
On May 24 2010 12:43 OptimoPeach wrote:Can someone decipher this gibberish for me? Does this mean it's official that the beta will be shut down sometime before the planned date of May 31st, or what? If so, why is this information being posted in some totally random thread instead of being announced? This was posted 7 hours ago?
I actually just went to the battle.net thread (the source) and read the quote in context with the thread it was posted in.
The thread creator was getting an error in SC2 from the latest patch. The repair utility he is talking about is something blizzard has been adding to their new games (like WoW) where you can repair the game without uninstalling/reinstalling.
I don't think the blue post is referring to the battle.net 2.0 lag issues at all. The beta shut down he mentions is the already announced beta phase 1 end (based on the wording). When Phase 2 begins, this repair utility will be included in that latest patch.
|
On May 24 2010 12:35 Design wrote:Show nested quote +On May 24 2010 12:29 ymirheim wrote:On May 24 2010 12:22 Design wrote:On May 24 2010 12:11 ymirheim wrote:The amount of code involved in a game like starcraft 2 is mind boggling, considering the fact that it is both a server side with numerous servers and a client side that needs to be coordinated and factoring in just how often they are adding patches and hotfixes. The most suprising thing to me as a software engineer is that there has not been way way way waaay more bugs. Most people do not realize just how many bugs can pop up in computer software by making changes to the most insignificant things, and the thing about bugs is that they are always surprising the coders more than anyone else. I bet you the first people who went "omg how the fuck did it do this?!" when the mass drops started happening was the programmers at blizzard  There are no bugs that you expect, because if you expected them you would had prevented them in advance, bugs are those things where you go "...that... should not be happening??" So as a software engineer, are you saying that you would release a major patch that changed many fundamental things about the network architecture before you left work for the weekend? They have already said on the Bnet forums that it will not be fixed this weekend because the staff are not there to do it. If it is a beta test then ofcourse yes, if it was running on internal testing which I bet you it was because issues like the ones we are seeing now are usually the stuff you only notice once you get enough data going through the infrastructure. In a beta test there is no reason whatsoever to hold stuff back because you are on a really tight schedule and on the off chance that shit hits the fan, it was still worth the risk. Obviously if this was a retail patch then you wouldn't ever put in a patch of any kind on a friday evening unless you got maintenance people working on weekends but this is not the case. Why does it matter if it is a retail patch or not? It is just bad policy. Not that hard to wait til Monday, when you have people on hand that can go through and find the issues and fix them as fast as possible. Would definitely save the company a lot of the abuse that has been hurled at it these past two days. It matters greatly, if it is retail then it is a marketing and service issue, if it is a beta then it is an effective testing issue.
Maybe it is not what people want to hear and it has been said before but this is a beta and "public relations" is not a priority. While this does not mean that blizzard are intentionally being asses towards their testers, they obviously value the aid of all the beta testers it also means that they cannot put our comfort before the test. A beta test is an extremely time pressed project under huge constraints both for time and resources. A weekend is a luxury of time that is not available. Since the beta actually works in some cases they are still getting valuable testing time over this weekend regardless of the fact that a majority of people are getting freezing issues, they are both getting lots of vital data on those issues as well as on other aspects of the beta. Even if it is the case that they don't have enough people working right now to sort it, it still means that they can start to fix it instantly on monday, rather than patching on monday, seeing the issues on tuesday and having enough time to figure out what is causing it and then starting to fix it on thursday. If a project manager of a beta test withheld a patch until monday to not risk causing bugs in the weekend and then a major breakdown happened with that patch after three days had been wasted, that project manager would be loved by the fans but still very much relocated to a different task.
Blizzard is more concerned with getting the game functioning in time than with our priviledge to play the game without issues over the weekend. Obviously though they did not expect these issues, it is always a calculated risk when doing a patch before a maintenance downtime.
|
On May 24 2010 11:59 FrogOfWar wrote: Still weird, being warned for being wrong, or for dissenting and asking people to look at it from another perspective. NO. And for calling people babies, and for informing us this is a beta. We already know that, and during beta is the time to make complaints known. Would you rather people wait until it's final?
|
Whether Blizzard care about it or not, people will form opinions on their company based on how they run this beta. Some of these opinions will be negative, some will be positive. It is still a marketing and service issue, whether or not people have paid to play. I don't understand how waiting two days is going to effect anything substantial that it is not worth it. It's the weekend anyway right? Not many people will be at work to look at the data.
They are actually wasting more time by releasing a patch on Friday. Why is that? Well, let's just hypothesize that it will only take one day to rectify the issues. In the case that they release the patch on Friday, they won't be able to fix it til Monday, which means that it will be Tuesday before a stable version is out. That is 3 days they lost in their beta testing phase. Now if they released the patch Monday, found the issues then and fixed the issues by midday Tuesday, that means they only lost 1 day in their beta testing phase. Also, it has the added benefit of not annoying those people who are helping test the game for them. The risk far outweighs any potential benefits.
Just want to add, I do believe in most circumstances it would be fine to release a patch on Friday. But that is only if that patch didn't include modification to the network architecture that the game relies on to run.
|
may 24th, will now be known as "fffffuuuuuuu" day.
|
The 31th the beta will be closed right?
|
I hate to imagine the hours per week the Blizzard staff will be pulling from now until the end of July.
|
On May 24 2010 12:53 Niteo wrote:
I don't think the blue post is referring to the battle.net 2.0 lag issues at all. The beta shut down he mentions is the already announced beta phase 1 end (based on the wording). When Phase 2 begins, this repair utility will be included in that latest patch. That's exactly what I thought when reading it as well, with luck the repair utility will be added by the time bnet gets back up after the shutdown on the 31st. And I really doubt they would take down the beta even earlier because the new patch would also need some public testing before the beta shuts down.
|
I have a theory as too why Bnet was having the problems, i think its beacuse as soon as they let maps be published the server(s) became to flooded, to many people, to many maps being uploaded etc... i could be wrong, but i really do hope it is fixed realtively soon
|
|
|
|
|
|