Talk:Prop static

Physics prop reported as static

Despite having both physics and static flags in model browser, when I try to use furnituretable003a as prop_static, it gets deleted during compile :

Error! prop_static using model "models/props_c17/furnituretable003a.mdl", 
which must be used on a dynamic entity (i.e. prop_physics). Deleted.

The same problem occurs with other mdls boasting both physics and static modes. I want these props to get involved in the lightmap ... so they need to be prop_static right ? --Beeswax

yeah oddly the same happens for me, also some phys_props tend to have incorrect collisions too, some of the car's mainly. The only fix would to be to recompile the original model into a static prop. Oddly they might be missing the $static parameter.--Gear 19:50, 27 Mar 2008 (PDT)

Is it not a bug in the Hammer compiler ? I tried to search the SDK bugzilla db but could find nothing relevant ... --Beeswax 06:03, 28 Mar 2008 (PDT)

I believe what's happening here is that this prop has the $staticprop keyvalue in the .qc, but does not have the allowstatic key in the Prop Data block. Without compiling the model with the allowstatic key, it cannot be used as a static prop. This was on done Half-Life 2 to force physics consistency with props. The fact that Hammer reports it as static looks like a bug. Thanks for pointing this out. --JeffLane 12:00, 28 Mar 2008 (PDT)

This isn't as weird as it sounds, dear readers, because $staticprop means that the model has no moving parts, not that it does not itself move. --TomEdwards 12:24, 28 Mar 2008 (PDT)

If so the $staticprop description needs some clarification --Beeswax 12:48, 30 Mar 2008 (PDT)

That's really weird stuff, thanks for pointing that out. If only it allowed you to override QC settings like in prop_physics entities. Solokiller 12:31, 28 Mar 2008 (PDT)

Wouldn't it be nice to have a prop_static_override entity ? ;) --Beeswax 12:48, 30 Mar 2008 (PDT)