I had this issue where every server showed a maximum occupancy of 1 and most of the server's names were replaced by their IPs instead. Any attempt in viewing server info or joining the server immediately crashed whatever Steam game (only saw with CS:S and TF2) I was playing, forcing me to use Task Manager.
The solution was to opt out of the Steam beta.
I had this issue where every server showed a maximum occupancy of 1 and most of the server's names were replaced by their IPs instead. Any attempt in viewing server info or joining the server immediately crashed whatever Steam game (only saw with CS:S and TF2) I was playing, forcing me to use Task Manager.
The solution was to opt out of the Steam beta.
Ah shit, well I hope AimIsADick has seen/heard of this TF2 crash.
Ah shit, well I hope AimIsADick has seen/heard of this TF2 crash.
Yes, hopefully he can tell us the real fix.
Yes, hopefully he can tell us the real fix.
FactsMachineYes, hopefully he can tell us the real fix.
If you change your DNS server to use google or cloudflare you can determine the exact frame of the crash (using frametime as a metric of couse) and then use a debugger and debug the game yourself. The error that shows just before this frame can run into the segmentation fault error (shown by GDB) that's crashing the game.
[quote=FactsMachine]Yes, hopefully he can tell us the real fix.[/quote]
If you change your DNS server to use google or cloudflare you can determine the exact frame of the crash (using frametime as a metric of couse) and then use a debugger and debug the game yourself. The error that shows just before this frame can run into the segmentation fault error (shown by GDB) that's crashing the game.