Game freezes while loading Zeds

  • Please make sure you are familiar with the forum rules. You can find them here: https://forums.tripwireinteractive.com/index.php?threads/forum-rules.2334636/
  • Weve updated the Tripwire Privacy Notice under our Policies to be clearer about our use of customer information to come in line with the EU General Data Protection Regulation (GDPR) rules that come into force today (25th May 2018). The following are highlights of our changes:


    We've incorporated the relevant concepts from the GDPR including joining the EU and Swiss Privacy Shield framework. We've added explanations for why and how Tripwire processes customer data and the types of data that we process, as well as information about your data protection rights.



    For more information about our privacy practices, please review the new Privacy Policy found here: https://tripwireinteractive.com/#/privacy-notice

DeliriousX

FNG / Fresh Meat
Dec 15, 2010
4
0
0
I haven't found anyone else with this problem -- even on this forum -- so I'm not expecting much luck, but here goes: The game has no problems starting up, or even loading maps... The problem comes on each wave, the first time I see a new type of Zed, it freezes for 10-20 seconds. The first time a Clot enters my line of sight, or a Bloat, or whatever, it freezes. After that, it doesn't freeze again for that type of Zed, but obviously it's a long enough freeze to get me seriously hurt or killed when I'm playing by myself. When it changes maps, or if I change servers, it happens again. I think it's some kind of zed skin cache problem, but I've got no idea.

I've tried several different things to solve the problem, but to no avail:
-Setting graphics settings to Medium, Low, and even Lowest.
-Changing Render Devices. I tried D3D 8, 9, OpenGL, and even Software.
-Running in lower resolutions, non-widescreen, and even windowed mode.
-Setting Engine.GameEngine's CacheSizeMegs to 256.
-Changing all the Precache variables to false.
-Verifying Integrity of Game Cache through Steam.
-Uninstalling (and deleting the KillingFloor folder) and Reinstalling the game.
-Excluding the KillingFloor folder from the Anti-Virus.
-Defragging the system, and letting Steam defrag KF.
-Verifying system page file size was at the recommended amount.
-Combinations of the above.

None of these things worked, so now I'm out of ideas.

System Specs:
CPU: Intel Core 2 Duo T8300 (2.4 GHz)
GFX: nVidia GeForce 8700M GT (512 MB VRAM)
RAM: 3 GB DDR2
HDD: 250 GB (about 5 GB free)
OS: WinXP SP3

Thanks in advance for any help :)
 
Last edited:

algnc

FNG / Fresh Meat
Dec 15, 2010
10
0
0
I am having the same issue, only since the patch. I have a C2D also, and slightly higher specs and Windows 7.
I've also gotten a couple crashes to Desktop with something about Virtual Memory, even though I have a ton of VM free.
 
Last edited:

[AU]hatori_hanzo

FNG / Fresh Meat
Oct 31, 2009
145
7
0
50
Argentina, South America.
Same problem here , this happens anytime a new type of zed spawns; i tried everything from defrag the files to use lower settings ( wich is annoying considering that i have always used the max settings and i never had any problem before , Even when the game had for sometime this same issue in the past ) , this could be realy annoying specialy in the first waves.
It cant be a problem with my pc specs but anyway here they are :

Dual core 2.81 AMD
Graphic card : ati radeon HD 4350 1 giga Gddr 3
4 gigas memory ram
HD 500 gigas with more than half free.
 

DeliriousX

FNG / Fresh Meat
Dec 15, 2010
4
0
0
Ah good, others with the same problem :X Hopefully someone knows what to do. And yeah, I didn't have this problem until after... this Christmas patch I think? or the one before?
 

DeliriousX

FNG / Fresh Meat
Dec 15, 2010
4
0
0
New discovery: On Solo, the freeze never happens except on the Patriarch. On Multiplayer, the length of the freezes seems to vary based on my latency. I'll test this with the Dynamic Netspeed option enabled and see if there's a difference, but it would seem odd that a networking-related issue would cause the client to freeze.

Oh, and I should probably add I'm not using custom skins or any external nonesense.