Phys bone follower: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
No edit summary
(Re-wrote the page with new information)
Line 3: Line 3:
{{base point|phys_bone_follower}}
{{base point|phys_bone_follower}}


All props (except [[prop_static]] and [[prop_detail]]), generate phys_bone_followers if they have a collision model. These bone followers are created for every attachment on the model, and if it doesn't have any, it will create a default one. These can quickly eat up the [[Entity limit|edict count]]! However, if the "Disable Bone Followers" keyvalue on the prop entity is set to Yes, the prop will disable bone followers, although the prop will no longer have a functioning collision model.
All props (except [[prop_static]] and [[prop_detail]]), generate phys_bone_followers if they have a [[collision model]]. These bone followers are created for every convex piece of its [[collision model]]. These can quickly eat up the [[Entity limit|edict count]]! However, if the "Disable Bone Followers" keyvalue on the prop entity is set to Yes, the prop will disable bone followers, although the prop will no longer have a functioning collision model, and the model will not be able to [[ragdoll]]. The .phy of a model can also be deleted to remove the collision model and save file space as an alternative.
:{{tip|A model can be modified to to remove all attachments except the necessary needed, to decrease the amount of bone followers and therefore save the edict count and allow a functioning collision model.}}


{{todo|More information is needed! Why ''exactly'' is this entity needed/created?}}
[[File:Phys bone follower example.jpg|thumb|An example of phys_bone_followers on a complex model. 15 phys_bone_followers are created for each convex piece of the collision model, resulting in 16 entities! The IN represents the server traffic, a staggering amount for 1 model.]]
 
== External links ==
* [https://rafuron.wordpress.com/2011/03/11/good-news-everyone/ Mapping Tricks] phys_bone_follower information, and also where the image was received from.

Revision as of 04:14, 17 July 2018

Stub

This article or section is a stub. You can help by expanding it.

Icon-NotInFGD.png
This entity is not in the FGD by default.
See below for instructions on making it available.

Template:Base point

All props (except prop_static and prop_detail), generate phys_bone_followers if they have a collision model. These bone followers are created for every convex piece of its collision model. These can quickly eat up the edict count! However, if the "Disable Bone Followers" keyvalue on the prop entity is set to Yes, the prop will disable bone followers, although the prop will no longer have a functioning collision model, and the model will not be able to ragdoll. The .phy of a model can also be deleted to remove the collision model and save file space as an alternative.

An example of phys_bone_followers on a complex model. 15 phys_bone_followers are created for each convex piece of the collision model, resulting in 16 entities! The IN represents the server traffic, a staggering amount for 1 model.

External links

  • Mapping Tricks phys_bone_follower information, and also where the image was received from.