Func clip vphysics: Difference between revisions
Jump to navigation
Jump to search
Bug:
m (Updated old entity format to {{this is a}}. This action was perfomed by a bot.) |
Thunder4ik (talk | contribs) m (→See also: Unicodifying, replaced: See Also → See also) |
||
Line 11: | Line 11: | ||
{{I EnableDisable}} | {{I EnableDisable}} | ||
== See | == See also == | ||
* [[script_clip_vphysics]] | * [[script_clip_vphysics]] | ||
[[Category:Physics]] | [[Category:Physics]] |
Revision as of 09:33, 8 January 2024
![]() |
---|
CFuncVPhysicsClip |
![]() |
func_clip_vphysics
is an e2 available in all Source games. It is considered solid to VPhysics objects (such as a prop_physics). QPhysics objects (such as players) can pass freely. It can also use a filter to only collide with specific objects.

StartDisabled
is a keyvalue in Hammer, but it is not present in the code. Use a logic_auto and the Disable
input instead. [todo tested in ?]Code Fix:In
bmodels.cpp
, findBEGIN_DATADESC( CFuncVPhysicsClip )
and replaceDEFINE_FIELD( m_bDisabled, FIELD_BOOLEAN )
withDEFINE_KEYFIELD( m_bDisabled, FIELD_BOOLEAN, "StartDisabled" )
. No changes to the FGDs or existing maps are required.
Keyvalues
- Name (targetname) <string>[ Edit ]
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentname
ortarget
).
Also displayed in Hammer's 2D views and Entity Report.See also: Generic Keyvalues, Inputs and Outputs available to all entities
Inputs
EnableDisable:
- Enable / Disable
- Enable/disable this entity from performing its task. It might also disappear from view.