Fajo wrote..God I hate my life.
WTF are you on steam is one of the MOST BUGGYEST programs out there before you post try to have some sense of wtf you are saying
CS Crash Fix Released
Collapse
This topic is closed.
X
X
-
To bad this unfortunate bug in a CS 1.6 update came at a point alot of people are switching to Steam.. It only fed the "steam sucks" whining by these new users.. Thankgod it didn't happen next week when WON is down, it would have been alot worse.. Lets hope it won't happen again soon..
And I repeat, this was a CS 1.6 bug, not a Steam bug!! Stop blaming Steam for everything (I understand it's easy for all ignorant to do that)..Comment
-
[CyW]-=BigBear=- wrote..
I wish more guys were like you... smart... knowing what the hell you're trying to say. As this guy said.. it's not steam that's making the game crash... it just so happens that other games ran fine cept for CS 1.6. Also, it appears that it was the shell ejection behavior that caused the crashing. Get your facts straight before you bash something (Steam).
Never crashed aswell.. Dunno why..
And it's CS 1.6 crashing, not Steam.. Steam is not a game engine or something where CS 1.6 runs on.. Maybe that's why people flame others when they blame Steam again..Comment
-
Yeah, this isn't a Steam bug, per se. I played DOD just fine when I had to get by without my beloved CS. I can understand why people equate CS with Steam though. CS 1.6 relies on Steam. I mean hell, lots of people think CS is HL.
At any rate, I'm glad they fixed the bug. I was going to say it is good this happened (and was resolved) before CPL, but there will probably be one of those special content servers again. Now the update that was released during CXG had been like this, there would have actually been some validity to the claims that Valve killed the tourny. Heh, I chuckle when I think about no-AWP clan matches.Comment
-
GameHopper wrote..
I'm constantly reading all these comments about VALVe not testing their updates before they release it. Now, I don't mean to side with VALVe (in fact I'm pretty annoyed with the crash bugs, and the general poor quality of each update) but I'm pretty sure they DO test it.
i always wonder if they ever test their code.
However, it's probably the thoroughness of the tests that is in question. With all the different setups and system configurations out there, it is virtually impossible to design AND TEST a software that works for everybody on every system.
I mean, VALVe can't go out and buy every different type of computer out there and test every update on every computer, making sure it works well on every system. There has to be a cut-off point somewhere, so I'm guessing the software is tested on a select range of PCs.
Obviously, from some of the comments above, not every user is experiencing this crash bug. I'm just guessing VALVe was just a little more sloppy this time round before sending this patch out and causing problems with quite a larger percentage of their consumers as they predicted.Comment
-
mathyou wrote..
Guy that was like 7 months ago it's old news and no one compares to CXG anymore
Yeah, this isn't a Steam bug, per se. I played DOD just fine when I had to get by without my beloved CS. I can understand why people equate CS with Steam though. CS 1.6 relies on Steam. I mean hell, lots of people think CS is HL.
At any rate, I'm glad they fixed the bug. I was going to say it is good this happened (and was resolved) before CPL, but there will probably be one of those special content servers again. Now the update that was released during CXG had been like this, there would have actually been some validity to the claims that Valve killed the tourny. Heh, I chuckle when I think about no-AWP clan matches.Comment
-
Helkite wrote..
we are basically one big beta testing croud.. however i don't understand how we are supposed to "feedback" anything usefull in the way of a system spec that they can work with.. if they only let us use 500 words..
I'm constantly reading all these comments about VALVe not testing their updates before they release it. Now, I don't mean to side with VALVe (in fact I'm pretty annoyed with the crash bugs, and the general poor quality of each update) but I'm pretty sure they DO test it.
However, it's probably the thoroughness of the tests that is in question. With all the different setups and system configurations out there, it is virtually impossible to design AND TEST a software that works for everybody on every system.
I mean, VALVe can't go out and buy every different type of computer out there and test every update on every computer, making sure it works well on every system. There has to be a cut-off point somewhere, so I'm guessing the software is tested on a select range of PCs.
Obviously, from some of the comments above, not every user is experiencing this crash bug. I'm just guessing VALVe was just a little more sloppy this time round before sending this patch out and causing problems with quite a larger percentage of their consumers as they predicted.
it's about time they sorted it
some stupid guy on the forums said something like "i'm sorry to break it to you all but it's your hardware, you don't have enough ram.. to which he got flamed by about 10 people with 1gb + (including me with 1.5gb) saying that it obv wasn't lol... those forums really do make me laugh!Comment
-
Edited by [user="23346"] @ [time="1090750993"]
yea, subneon.. and those are the EXACT same people who valve are listening to and to be honest, a ton of them have no clue what the hell they are talking about.
for a bit of time i wondered why the awp delay was even added (on top of the animation delay that was added a few versions ago) but then i was enlighted on the CAL and GotFrag forums about how some moron who probably had only played the game for maybe a few months, and most likely never played at a competitive level, made a thread about how the awp was a horrible weapon (or something to that effect) and was overpowered..
To be completely honest, in my perspective it was never overpowered. I'll admit it was really handy playing with a 1-hit kill gun, but when you're playing on pubs, the game is so distorted that it would be silly, IF you aren't an experienced player, to try and judge the guns. BUT, if you compare this to a controlled, competitive environment where people are actually thinking and playing with their brain instead of running around shooting anything that moves.. you can see just how effective the gun is, and to be completely honest, there are methods of overpowering the player and their awp with your mind and not just with reaction speed.
The people who replied to that moron's thread had mostly never played on that kind of level where you use your mind more than your muscle (if you get what I'm talking about) and spewed forth remarks about how overpowering it was because they rarely won 1 v 1, or even 5 v 1 battles against an awper.. and the reason this happens isn't because the awp is overpowering, its because they baited eachother instead of working together and thats the real problem in the game, especially in pubs. People don't work together, and when they can't win 1 v X's they find something extremely apparent to blame instead of their own willingness to cooperate with eachother. "Oh man, that guy killed us with an awp. It does way more damage than I or any of us alone could dish out, IT MUST BE OVERPOWERED!"
Even after the awp was "fixed" I still think their "fix" is bugged.. its purpose was to add a delay while the awp was ejecting its shell.. If this is true, then why, when you first take out the awp, does the delay still come into effect? Or, when I shoot my first bullet, and I wait for that shell to be ejected, why can't I THEN, switch to my USP run away, and setup a nice position without delay.. That extra delay + loss of speed from waiting for the shell to eject gives the enemy plenty of time to run after me and put me in a vulnerable position. Love for that bug to be fixed :PComment
, nevermind offline mode to CZ
Comment