User Tools

Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
collections [2017/05/05 14:04]
127.0.0.1 external edit
collections [2018/10/18 10:14] (current)
sechrest
Line 1: Line 1:
 ====== Collections ====== ====== Collections ======
  
-Collections allow tree geometry to be collected in a mesh asset during tree model compute. This gathered geometry can then be used by generators and forces just as any other mesh asset would be.+Collections allow tree geometry to be collected in a mesh asset while the model is being computed. This gathered geometry can then be used by generators and forces just as any other mesh asset would be.
  
 ===== Creating a Collection ===== ===== Creating a Collection =====
Line 19: Line 19:
 ===== Contributing to Collections ===== ===== Contributing to Collections =====
 {{ :​collection-properties.png?​nolink|}} {{ :​collection-properties.png?​nolink|}}
-To make a generator contribute to a collection, look for the Collections group with the "​Generation"​ properties (depicted to the right). ​ There will be a check box for each collection asset. ​ Check each collection that the selected generator should contribute to.  Repeat this for each generator whose geometry should be in the collection.+To make a generator contribute to a collection, look for the Collections group with the "​Generation"​ properties (depicted to the right). ​ There will be a checkbox ​for each collection asset. ​ Check each collection that the selected generator should contribute to.  Repeat this for each generator whose geometry should be in the collection.
  
 > **Note**: Order matters. Generators that contribute to collections should precede generators that use them during tree model computation. ​ This means contributing generators should be on lower levels and to the left of using generators when the Generation Editor is oriented vertically. > **Note**: Order matters. Generators that contribute to collections should precede generators that use them during tree model computation. ​ This means contributing generators should be on lower levels and to the left of using generators when the Generation Editor is oriented vertically.
Line 37: Line 37:
 ==== Example 2: Self-colliding branches ==== ==== Example 2: Self-colliding branches ====
  
-Collections can be used to prevent branches from colliding with each other as they grow.  For example, collect the roots of a tree into a collection and create a mesh force that uses that collection. ​ Set the Force Action, Collide Action, and Keep Action properties as desired and then apply that force to the root generator (the same generator that contributed to the collection). ​ Now, as each new root computes, it will collide with the roots computed before it.+Collections can be used to prevent branches from colliding with each other as they grow.  For example, collect the roots of a tree into a collection and create a Mesh force that uses that collection. ​ Set the Force Action, Collide Action, and Keep Action properties as desired and then apply that force to the root generator (the same generator that contributed to the collection). ​ Now, as each new root computes, it will collide with the roots computed before it.
  
 ==== Example 3: Vines growing over a trunk ==== ==== Example 3: Vines growing over a trunk ====
  
-Another good use of collections is when vines are growing over trunk geometry. In order to be able to change things about the trunk after the vines have been added, a collection of the trunk must be created first. Then, the vines can collide with a mesh force that has been assigned the collection, which is self-updating.+Another good use of collections is when vines are growing over trunk geometry. In order to be able to change things about the trunk after the vines have been added, a collection of the trunk must be created first. Then, the vines can collide with a Mesh force that has been assigned the collection, which is self-updating.