PSA: Disable cl_new_impact_effects! It causes crashing/invisible models

[DannBo]

If you have been having crashing/invisible model problems after the January 27th update, check to see if you have cl_new_impact_effects enabled. If you do, disable it by setting it to 0 in console, as well as in your autoexec.cfg file if you have one. This should clear any crashing/invisible model problems related to the CUtlLinkedList overflow problem that was introduced with the aforementioend update. Typically these crashes occur on populated 32 player servers, particularly at the beginning of rounds when everyone is shooting.

[OrganicTaste]

Nice.

[Arby...]

You are the best person. Thanks a lot, I had no idea how to fix this problem

[Mashpit]

RIP upside down viewmodels

[Bush-Dog]

Isn't that disabled by default?

[Blk_Mage_Ctype]

That's odd, I use that convar and so far have no experienced any invisible models or crashes.

EDIT: Oops, missed this part...

Originally posted by DJMM DannBo:

Typically these crashes occur on populated 32 player servers, particularly at the beginning of rounds when everyone is shooting.

I don't play on 32 player servers, so no wonder why I haven't experienced this issue.

[Boogiman]

Is anything supposed to happen in the console when you write cl_new_impact_effects 0? Cause right now I cant see if its been implemented

[JarateKing (very rusty)]

Originally posted by Boogiman:

Is anything supposed to happen in the console when you write cl_new_impact_effects 0? Cause right now I cant see if its been implemented

If you type in cl_new_impact_effects 0 and get no message, you did it right.

If you get an error message saying unknown command, then you misspelt it.

[Boogiman]

Originally posted by J_ͣ_ͬ_ͣ_ͭ_ͤ King:

Originally posted by Boogiman:

Is anything supposed to happen in the console when you write cl_new_impact_effects 0? Cause right now I cant see if its been implemented

If you type in cl_new_impact_effects 0 and get no message, you did it right.

If you get an error message saying unknown command, then you misspelt it.

Allright, thank you for the quick respons.

[DannBo]

Originally posted by Bush-Dog:

Isn't that disabled by default?

Yes, it is disabled by default, but it's one of the common settings people turn on in an effort to maximize the quality of the game's graphics, and was suggested as one of the "ultra" settings on the tf2 wiki. Before the update that caused the crashing, the actual graphical effect this particular convar had was pretty unnoticeable, but it was included in those "ultra" settings nonetheless and probably found its way into people's autoexec.cfg file (like mine) as a result.