Posted by Rugalitarian on Fri Jan 23rd 2009 at 4:29pm
Thanks a lot. I actually got my flattened cardboard boxes working last night with the prop_static entity. I used to make lots of maps for Half-Life 1, and am just now trying to learn all the new features and such of the Source/Orange Box engine.
Posted by haymaker on Fri Jan 23rd 2009 at 5:51am
prop_static
http://developer.valvesoftware.com/wiki/Prop_Types_Overview
you'll find, if you haven't already, that you may want to use a particular model as static but it doesn't show up in game, you should look at the "info" tab in the model viewer to see what properties that prop was compiled with.
You can set any type using _dynamic_override or _physics_override, and disable motion and collisions on that prop in its property sheet in Hammer afterwards.
It works the other way, too, you can set static compiled props to physics if you want.
Both of these scenarios come with a slight performance hit, so try not to go overboard
Posted by Rugalitarian on Fri Jan 23rd 2009 at 4:24am
Alrighty, so which is the correct entity to use for props such as light posts, trees, desks, flattened cardboard boxes, etc?
Posted by haymaker on Fri Jan 23rd 2009 at 2:25am
prop_details pretty much refer to automatic things like grass iirc
generally not useable through Hammer
Posted by fishy on Fri Jan 23rd 2009 at 1:59am
I've only known this to happen when a map has been compiled for one game then run in another. Like compiling a map with the sdk set to dod:s, which lets the editor see all the dod:s models, then trying to run the game in hldm or something.
