Talk:Prop static: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
Despite having both physics and static flags in model browser, when I try to use furnituretable003a as prop_static, it gets deleted during compile : | 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. | 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 ? --[[User:Beeswax|Beeswax]] | 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 ? --[[User:Beeswax|Beeswax]] | ||
Revision as of 18:24, 27 March 2008
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