Phys constraintsystem: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{wrongtitle|title=phys_constraintsystem}} | |||
==Entity Description== | |||
An entity used to manage a group of interacting constraints and keep them stable. All constraints on a set of entities should be placed in the same system, or they will fight each other during simulation. | An entity used to manage a group of interacting constraints and keep them stable. All constraints on a set of entities should be placed in the same system, or they will fight each other during simulation. | ||
'''''Note:''' This entity is valid in many mods but only appears in the halflife2.fgd ({{not in fgd}}'' | |||
==Keyvalues== | ==Keyvalues== | ||
| Line 11: | Line 15: | ||
==Outputs== | ==Outputs== | ||
*{{o targetname}} | *{{o targetname}} | ||
[[Category:Entities]] | |||
Revision as of 06:05, 28 September 2005
Entity Description
An entity used to manage a group of interacting constraints and keep them stable. All constraints on a set of entities should be placed in the same system, or they will fight each other during simulation.
Note: This entity is valid in many mods but only appears in the halflife2.fgd (Template:Not in fgd
Keyvalues
- Template:Kv targetname
- additionaliterations <integer>
- Adding iterations makes the interactions among constraints in a system tighter. It will not compensate for errors due to collision, but will help in cases where objects of disparate mass are constrained to each other.