FM-Structures and Conventions

Naming

It is very advised to follow strict naming convention as this allows us to use Automation in our pipeline or helps us avoid running into some problems.

Use prefixes as follow:

• "CHAR_" for character asset.

• "VEH_" for vehicle asset.

• "PROP_" for vehicle asset.

• "ENV_" for environment asset.

Use this button to create suggested structures, following the same will allow us to use Automation etc.

Structure

Let's say there are two pages, One is "Project", "Context"(Denoted in yellow from the image below) Each page has three sub folders. For reference lets remember them as follows. (follow R>G>B color code from the image)

1. Project page:

   1. Projects # refers to your project names

   2. Contents # refers to main sub categories, default: assets, sequence

   3. Assets # refers to the assets that contains in the project

2. Context:

   1. Contexts # refers to the asset departments or such.

   2. ContextTypes # refers to the sub categories, Example: ctrlRig may have a proxy, and a final

   3. Versions #refers to the version numbers

Comment

(Denoted in cyan)

Use this section to tag any info you need to a file. This is very useful to track what's happening in the file. And what are due, etc. Use Edit button to edit any existing comments.