Func clip vphysics: Difference between revisions
Jump to navigation
Jump to search

Bug:
(-removed irrelevant info) |
mNo edit summary |
||
| Line 7: | Line 7: | ||
==Keyvalues== | ==Keyvalues== | ||
{{KV|Filter Name|intn=filtername|filterclass|[[Filter]] to use to see if activator collides with this entity.}} | {{KV|Filter Name|intn=filtername|filterclass|[[Filter]] to use to see if activator collides with this entity.}} | ||
{{KV Targetname}} | {{KV Targetname}} | ||
Revision as of 04:39, 10 October 2022
Template:Base brush 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.
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.