Troubleshooting Level Design

Trouble with Compiling Maps

Compiling the map takes a very long time

If your map is large or complicated, make sure you are using func_detail appropriately. See Controlling Geometry Visibility and Compile Times.

The compile window says there is a memleak

Don't worry; this is not an error. Carry on.

Compiling the map gives an error

See Compile Errors for a list of compiling errors with explanations, or visit this site: Interlopers.net error list

In-game problems

People on the Internet join the game while you're trying to test it

By default, testing your map sets your computer up as a server over the Internet, so casual players may come across it and join. To prevent this, type sv_lan 1 in the console before loading your map.

Everything is very bright (no shadows)

You probably have a leak. It is also possible that you turned off the lighting stage in the Compile Options dialog.

Dynamic shadows (shadows for players and prop_physics) appear where they shouldn't

This is a shadow rendering error due to the method that shadows are calculated. It can often interfere with gameplay, because it gives away player positions when they think they're hidden. To fix it, create an info_no_dynamic_shadow entity, and use its Pick button to select the offending surface.

Reflections look weird or too bright

Type buildcubemaps in the console, and reload the map. Sometimes new cubemaps do not look correct until the map is reloaded. And make sure you've put in enough env_cubemaps.

Water is invisible from above, but looks correct from below

Sometimes this happens if cubemaps have not been built yet. (Type buildcubemaps in the console.) It will also happen if you skipped the visiblity or lighting stage of compiling. The visibilty compile phase will not run correctly if you have a leak.

Invisible Props

The prop may have its End Fade distance set too close. Sometimes the value is accidentely changed while moving prop entities.

Also, some props can only be used as certain types of props and otherwise will be invisible. For instance there are tables that only work as prop_physics, and other props that only work as prop_dynamics.

Certain textures appear black or unusual when moving around the map (often flashing from any distance when firing)

This is normally caused by using a texture that is made for small scale, specific usage (i.e. textures in the models directory). Check the full name of the texture and make sure it does not begin with 'models/'. There is usually a similar texture available elsewhere which does not appear incorrectly.

Ladder doesn't work

Make sure the ladder entity is not touching anything solid. It must be at least one unit away from all solid surfaces. Read the Creating Ladders instructions carefully. Ladders work differently in Half-Life 2 and in Counter-Strike: Source.

Building cubemaps causes the game to crash with a memory reference error

Make sure the game resolution is at least 800x600. This can also happen in widescreen mode.

In game the Console Is spammed with "warning Vis decompression overrun"

Try and tone down the number of leaves in your map

Trouble with Counter-Strike:Source Maps

The hostages won't move

Hostages require a navigation mesh in order to work. (They used to use info_nodes, but that is now obsolete.)

When the map is loaded, it says "Both Teams are Full".

You need to have both info_player_counterterrorist and info_player_terrorist entities in the map. See Making levels for Counter-Strike: Source for information on the necessary entities. Also check the console: if it reports that there are invalid spawn points, try moving them up away from the surface, because they may be intersection with the terrain. It is okay for them to start a little bit in the air.