On 26/01/2012 22:02, ics wrote:
Whenever there is a crash issue, they need to know what is causing it in order to fix it. Perhaps the crash dumps are not enough (they don't have any leads).
They're enough for me :p So, on the assumption Valve are at least as clever as I am, probably a lot more, we each lack one or more of these things to let us fix it :-
(i) The source code (ii) The time (iii) The ability to recreate the crashes I'm sure between us we have all 3, I just lack (i) :)
But since the ball is physics object and i have had 2 mysterious crashes on regular servers related to events that had physics related issues going on (pyros airblasting a heavy that was being shot by sentry) but this is just be guessing.
Others have reported getting a similar error when using SMAC. Is your crashing server default or does it have plugins?
In perspective, according to steam I've played around 105.5 hours of TF2 over the last 2 weeks and I've averaged around 3 or 4 client crashes day (of which the vast majority are one of 2 fault addresses - although since the last update I've not played enough yet to determine for sure, but I've had neither crash, so they could be fixed - although it has crashed once)
But I've never seen a server crash - not since viaduct_event crashed my server if I wore Bills hat back at Halloween. You'd think I would have seen one in 105 hours - and more than that if this goes back to Xmas. If it was triggered by airblasting, throwing nades or SG throwback etc. But most of the time I'm playing on servers that don't use any plugins and only stock Valve maps. Whereas it's clear from SPUF that lots are experiencing the client crashes.
That said, garrysmod has required you to replace the vphysics.so library since forever hasn't it? Maybe that would fix this?
-- Dan. _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
