EDIT *** See 6th post for fix
*********************

Since the 6-28-06 update it appears you can walk through some models. Such as the boxes on dod_smallhill or boxes on dod_putten.

Is anyone else seeing this, and know what the problem is?

The thing that worries me is this now happens on my custom model I am working on, when before the update it was solid and you could jump, walk, stand on it. Maybe it has something to do with the model compile options in the .qc file?

Anyone one with ideas on this?

I noticed this on a custom map. For me it could have just been a problem with the map, or possibly the problem that you are talking about.

Well I have a small update. When I run a map locally from my machine the models are solid and you can't walk through them. When I run it on a dedicated server you can walk through them. This happens on my server and a few servers I play at. I checked my server.cfg and don't see any option that should allow this to happen. You do get a slight hang up where the model is, but you can still continue through it.

Seems to me like the mapper might have used a model that can only be used as a hysics entity and set it to not move, might have had some consistancy issues after the update . . . just a guess

Well I am still seeing this.

When you put a prop_static model in a map, you just put a prop_static entity and the browse for the model right? I shouldn't have to change any of the other options? I must not be putting them in hammer right, or not compiling right.

Ok I fully understand the problem now and the fix.

when I made my models I made them in directories:
~username\day of defeat source\dod\models\Bone\<modelfiles>

and the materials:
~username\day of defeat source\dod\materials\models\Bone\<modelmaterials>

Now when you put them in hammer the location of the models comes up as: ~models\bone\<model>

This is fine for windows and windows servers, they dont care about case sensitivity. Now when you put this stuff on a linux server that is where the problems start. Linux, or *nix for that matter care about the case sensitivity when looking throught the file system. The .bsp file is telling the linux server the model data is at ~models\bone\<model>

But the files are actually at ~models\Bone\<model>

So the linux server can't find the model data and that is why you can walk right through them.

So as a go forward I will use all lower-case letters when making and naming custom content.

As a side note if you bspzip the content into the .bsp you are ok.