Upvote Upvoted 1 Downvote Downvoted
crashing when ever i join any server
1
#1
0 Frags +

yea so today i launch tf2 try and play on a pub and it crashes i change my mat_que_mode and same thing i went through every server on my favorites tab and i crash on all of them idk what is wrong with my game

yea so today i launch tf2 try and play on a pub and it crashes i change my mat_que_mode and same thing i went through every server on my favorites tab and i crash on all of them idk what is wrong with my game
2
#2
0 Frags +

try going into the advanced options and turning of html motds, I crashed every time there was an ad. it might be the same with you.

try going into the advanced options and turning of html motds, I crashed every time there was an ad. it might be the same with you.
3
#3
1 Frags +

i have the tf2 add blocker

i have the tf2 add blocker
4
#4
0 Frags +

Try verifying your cache.

(In case you don't know: Right click TF in steam -> properties -> local files -> verify integrity of game cache)

Try verifying your cache.

(In case you don't know: Right click TF in steam -> properties -> local files -> verify integrity of game cache)
5
#5
2 Frags +

its probably a sign

its probably a sign
6
#6
0 Frags +

Try renaming your cfg folder to like "cfg_old" then start TF2 and see if it works. If that doesn't work, try the same thing for your hud with "resource" and "scripts"

If none of that works, back up your cfg, resource, scripts, maps, and addons folders, as well as all of your demos then delete your "team fortress 2" folder. Don't worry about it re-downloading TF2, it'll just pull a fresh copy from your GCFs. Start TF2 from a clean slate without copying over any of your old stuff yet. If it works, start adding back your backed up folders one by one until you start crashing again.

Try renaming your cfg folder to like "cfg_old" then start TF2 and see if it works. If that doesn't work, try the same thing for your hud with "resource" and "scripts"

If none of that works, back up your cfg, resource, scripts, maps, and addons folders, as well as all of your demos then delete your "team fortress 2" folder. Don't worry about it re-downloading TF2, it'll just pull a fresh copy from your GCFs. Start TF2 from a clean slate without copying over any of your old stuff yet. If it works, start adding back your backed up folders one by one until you start crashing again.
7
#7
0 Frags +
toothTry renaming your cfg folder to like "cfg_old" then start TF2 and see if it works. If that doesn't work, try the same thing for your hud with "resource" and "scripts"

If none of that works, back up your cfg, resource, scripts, maps, and addons folders, as well as all of your demos then delete your "team fortress 2" folder. Don't worry about it re-downloading TF2, it'll just pull a fresh copy from your GCFs. Start TF2 from a clean slate without copying over any of your old stuff yet. If it works, start adding back your backed up folders one by one until you start crashing again.

ive uninstalled my hud ill try the config thing and back up all my stuff

[quote=tooth]Try renaming your cfg folder to like "cfg_old" then start TF2 and see if it works. If that doesn't work, try the same thing for your hud with "resource" and "scripts"

If none of that works, back up your cfg, resource, scripts, maps, and addons folders, as well as all of your demos then delete your "team fortress 2" folder. Don't worry about it re-downloading TF2, it'll just pull a fresh copy from your GCFs. Start TF2 from a clean slate without copying over any of your old stuff yet. If it works, start adding back your backed up folders one by one until you start crashing again.[/quote]

ive uninstalled my hud ill try the config thing and back up all my stuff
8
#8
0 Frags +

Shadows would cause me to crash right after sending client info finishes for longest time if I had them enabled. It was only some servers still don't know what caused it. Magically fixed itself some way.

Shadows would cause me to crash right after sending client info finishes for longest time if I had them enabled. It was only some servers still don't know what caused it. Magically fixed itself some way.
Please sign in through STEAM to post a comment.