Func clip vphysics: Difference between revisions
Jump to navigation
Jump to search
Bug:
(-added class hierarchy) |
No edit summary |
||
| Line 9: | Line 9: | ||
==Inputs== | ==Inputs== | ||
{{I EnableDisable}} | {{I EnableDisable}} | ||
== See Also == | |||
* [[script_clip_vphysics]] | |||
[[Category:Physics]] | [[Category:Physics]] | ||
Revision as of 08:50, 6 August 2023
| CFuncVPhysicsClip |
Template:Entity 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>
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentnameortarget).
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.