I never base my assumptions to SPUF whine alone. That's just extra tool
i use to see if the reports i see are correct. I see players complaining
about more frequent crashes and such over IRC and on the actual
gameservers. Those complaints have increased and i even tell them to
inform me about them. Just yesterday about the time i posted here, some
guy told me that he had 4 crashes in a row just after the incident which
caused everyone on a server to crash. That's something i haven't seen a
year ago. True, there has been some bugs in the game but not nearly as
many people have been affected by those in the long run than these past
couple of months. But Valve is aware and is working on the issue.
-ics
8.2.2012 8:51, dan kirjoitti:
On 08/02/2012 05:44, ics wrote:
That's not what i ment. These crashes that folks are now complaining
started around December.
Some did, but I checked event viewer and saw at least one that seemed
to go back much further.
I suppose it's the frequency of crashes that decides when you notice
them (or blame the game) rather than the actual source.
People just go post into that thread too along with others.
There's not much point. There's no feedback there.
There's very little in the way of accurate reporting.
50 pages of "me too" and "fix it valve" and nonsense like "tf2 is
badly optimised, they only want to sell hats"
I used to see replies to people that posted crash reports that Valve
don't reply to threads but they do fix them. That's only half true now.
Bug fixing / crash reporting is a 2 way street. Post to lkml and talk
to linus about the crash, if your bug report is good, it's back and
forth while it's fixed - or at least until someone says "Yeah, we've
recreated that" Post to SPUF and the only thing acknowledging that
Valve read SPUF at all is that half the people who are posting in the
thread eventually get a forum ban.
Without Valve posting you're just peeing in the wind. (And I know
they've automated the crash reporting, so if they can reproduce the
bug they don't need a reporter, but that only works iff you fix the
bugs - otherwise you've just got a lots of threads, a mountain of
crash dumps and slowly even the most patient start to get frustrated
with the crashes)
Crashing is as important to fix as adding fancy pants new stuff for
2012. I've said before, if you have staff that are too intelligent you
end up like early MS, a company of bright sparks that wrote Windows 3
and 95 - full of amazing features but crashing every 5 minutes when
you tried to use them. TF2 isn't that bad yet, but 5/10 times the
replay you get - the one where you killed half of their team with
airshots, crashes to desktop with "engine error model loader null" and
4 or 5 times a day when you're playing it crashes with an access
violation (that's assuming whatever class or thing triggers the bug
isn't making some people that use that class crash more frequently)
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
