I realized that, although I saw it as a possible fix in a single email the
other day, no one had put out an actual topic describing the fix for players
with the Dual Core options on (I've only seen it happen for those with it
on, though I may be wrong!). I tested various situations, and it always
happened with the whole gibs-in-water situation (not sure what to call it in
a technical sense), and those with *r_waterdrawrefraction 0* didn't crash
while those with it set to *1* did. Through every test, this was the case*.
*Take note that *this resets anytime you restart tf2, so it must be either
in your autoexec.cfg or set every time you start tf2. *People kept thinking
our server was the problem, so I actually added an entry into our ads plugin
that reads as (copied straight from the ads file)
*"text" "{GREEN} HAVING CRASHES? SET r_waterdrawrefraction 0 (Note
that for it to stick through TF2 instances, you'll need to put it in your
autoexec.cfg)"*
Deal with it however you wish, but at least now it's out there. Hope this
helps someone.
-Atreus
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
