Difference between revisions of "Asset Format"

From Another End
Jump to: navigation, search
(Created page with "== Asset Modeling == Assets should be modeled hierarchically: * Core pieces * Secondary pieces * Tertiary .. and so on Example: '''Tree''' Core piece: Trunk Secondary piece:...")
 
Line 2: Line 2:
  
 
Assets should be modeled hierarchically:
 
Assets should be modeled hierarchically:
* Core pieces
+
* Core pieces - pieces that are central to the asset
* Secondary pieces
+
* Secondary pieces - pieces that are placed relative to the core piece
* Tertiary .. and so on
+
* Tertiary - pieces that are relative to the secondary
 +
* .. and so on
  
 
Example:
 
Example:
 
'''Tree'''
 
'''Tree'''
Core piece: Trunk
+
*Core piece: Trunk
Secondary piece: Branch(es) and leaves
+
*Secondary piece: Branch(es) and leaves
  
  
Line 15: Line 16:
  
 
* Asset pieces should be exported as separate meshes
 
* Asset pieces should be exported as separate meshes
* Each asset should have a readme specifying the following:
+
* Each asset should have an accompanying readme specifying the following:
 
# The core pieces
 
# The core pieces
 
# The hierarchical pieces and what acceptable positions they can be placed relative to the core pieces. Example - a tree branch can be placed at a y value of 60-100 relative to the trunk, with any y rotation and a range of 0 - 40 degrees z rotation
 
# The hierarchical pieces and what acceptable positions they can be placed relative to the core pieces. Example - a tree branch can be placed at a y value of 60-100 relative to the trunk, with any y rotation and a range of 0 - 40 degrees z rotation
 +
# What levels of modification are available for the entire asset. e.g a tree can be scaled in any direction, but cannot be rotated about the x or y axis.
  
  

Revision as of 19:25, 5 October 2014

Asset Modeling

Assets should be modeled hierarchically:

  • Core pieces - pieces that are central to the asset
  • Secondary pieces - pieces that are placed relative to the core piece
  • Tertiary - pieces that are relative to the secondary
  • .. and so on

Example: Tree

  • Core piece: Trunk
  • Secondary piece: Branch(es) and leaves


Asset Delivery

  • Asset pieces should be exported as separate meshes
  • Each asset should have an accompanying readme specifying the following:
  1. The core pieces
  2. The hierarchical pieces and what acceptable positions they can be placed relative to the core pieces. Example - a tree branch can be placed at a y value of 60-100 relative to the trunk, with any y rotation and a range of 0 - 40 degrees z rotation
  3. What levels of modification are available for the entire asset. e.g a tree can be scaled in any direction, but cannot be rotated about the x or y axis.


Specific Asset Notes

TBD as we go through the asset list.