ProjectNA

Somehow I torqued L4D - I downloaded some of the new maps, and started getting string table errors. After researching, reinstalling seemed to make sense. After a fresh install (and removal of the L4D folders/content in steamapps), I still get a string table error on NM, and engine error on others.

Maybe it was that TG-3rd whooping I took last night.

Thoughts?

EDIT: Part of it was the Dead City update. Doesn't solve the engine errors.

__________________

Reaperassault

its usually when you are trying to play a custom map but the map is not in the correct spot.

__________________

Boot

It happened to me too after loading the dead city maps. I restarted steam and the game, and it seemed to help a bit. I think my lobby-to-server transition may be buggier, but that's like saying the sirloin steak is tastier than anything else on the menu at Denny's.

__________________

ikonic

Solution:

Ensure that your custom maps are up-to-date with the server and are placed in the correct area.

Restart Steam if L4D was running when you extracted the maps to your maps folder.


If you follow these two steps, then you shouldn't have any string table/engine errors.

__________________

Avs

I see that this issue occurs when you extract the data to your L4D folders while L4D is still running. Ikonic's suggestions should do the trick (though sometimes restarting L4D is enough).

ProjectNA

Nicely done. I ordered that once......once.

__________________