Models
Models are pre-designed objects that mappers can place inside our custom maps. Source SDK shipped with a relatively large collection of them, and they are easy to use. There are a few pointers to keep in mind when working with models, however. We'll start by discussing when models should be used.
Appropriate Use of Models
Unlike mapping for the original Counter-Strike, Source mapping requires extensive use of models. It's a blessing and a curse at the same time. The nice thing about all these models at your disposal is that anyone can make maps with realistic looking details. The bad thing is that the fixed collection of standard models tends to stifle creativity. Unless the mapper is willing and able to master making custom models, one map is going to look similar to the next if they use the same models.
In addition, placing models in the map can frequently be abused. What I mean by this is that I encounter a lot of mediocre maps that's nothing but a haphazard bunch of model and props thrown together. The models used in these maps don't seem to be related to each other, and they often just look out of place.
Judicial use of models can add tremendous immersion and realism in your map, but they can also destroy a map if they're abused.
New Model Browser
VGUI Model browser with substring filtering, 3D preview, and reference grid to indicate the size of the model.
Camera controls are:
o left mouse: rotate
o right mouse: zoom
o middle mouse or SHIFT: translate
Added option "Use VGUI model browser" under Tools->Options->General. Unchecking this option reverts to the old model browser.