Team Fortress 2
TF2 Crash : CUtlLinkedList overflow! (exhausted index range)
Everything is said, according to this post (-> http://forums.tf2maps.net/showthread.php?t=24053) it was going to be fixed for next update and it wasn't. Apparently somebody have been messing with short integers.

Does anybody have a quick fix (not the weapon) so I don't have to wait for Valve to do something ? ;)
< >
กำลังแสดง 1-15 จาก 38 ความเห็น
Disable cl_new_impact_effects by setting it to 0 in console and inside your autoexec.cfg if you have it there.
It works ! Thanks !
...why though
โพสต์ดั้งเดิมโดย Tsouki™:
It works ! Thanks !
...why though
Because disabling this disable gun shot holes in walls and glass. The error is caused by too many entities. So disabling gun shot holes gets rid of alot of entities.
Can't developpers check their freaking arrays size before inserting new elements :'D
โพสต์ดั้งเดิมโดย Tsouki™:
Can't developpers check their freaking arrays size before inserting new elements :'D

It's a linked list, not an array...
this happens to me when I try to save replays on tf2.... I found the autoexec.cfg but it does not have cl_new_impact_effects in it ....what do i do?
โพสต์ดั้งเดิมโดย Hurp Durp:
โพสต์ดั้งเดิมโดย Tsouki™:
Can't developpers check their freaking arrays size before inserting new elements :'D

It's a linked list, not an array...
Weird, as a linked list is supposed to be more permissive concerning size varying



โพสต์ดั้งเดิมโดย Sylvesterthecat:
this happens to me when I try to save replays on tf2.... I found the autoexec.cfg but it does not have cl_new_impact_effects in it ....what do i do?
Sylvesterthecat: Just add it :)
โพสต์ดั้งเดิมโดย yartFF:
โพสต์ดั้งเดิมโดย Hurp Durp:

It's a linked list, not an array...
Weird, as a linked list is supposed to be more permissive concerning size varying

A linked list with an index ? What even. Is that a stack overflow ?
linked lists have no index, since it's theoritically spread in the memory, but it shouldn't be a problem to add elements into a linked list. If there was a (self inflicted or not) limit, it should just not display the bullet holes, and not quit the whole game. But whatev, glad there's a command to avoid demo files being corrupted.
โพสต์ดั้งเดิมโดย DJMM DannBo:
Disable cl_new_impact_effects by setting it to 0 in console and inside your autoexec.cfg if you have it there.
I write cl_new_impact_effects 0 in the console and nothing happen, the bullet holes are still there. The bug started after I downloaded all these mods/skins for me. How does the fact to have some mods give this error ?
For me, it's already disabled but I still get the error. What now?
โพสต์ดั้งเดิมโดย Byakuran {Scam Recovering}:
For me, it's already disabled but I still get the error. What now?

I have it too, but it's fresh for me. I rendered some replays after i got this error.
I think the last update cause this.
แก้ไขล่าสุดโดย Spyke; 25 พ.ค. 2015 @ 6: 42am
There's no way to fix this error for the moment unfortunately.
โพสต์ดั้งเดิมโดย Korbinian Neuerichter ☤:
There's no way to fix this error for the moment unfortunately.
dont you mean ever? as if valve even cares. they obviously dont care about us.
So many necroes...

They burn...
< >
กำลังแสดง 1-15 จาก 38 ความเห็น
ต่อหน้า: 1530 50

วันที่โพสต์: 12 ก.พ. 2015 @ 1: 37pm
โพสต์: 38