Asset Format
From Another End
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:
- 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
- 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.