• Camelcase naming (e.g. ‘redBall_01’ not ‘Red_Ball_01’)
• No spaces, only underscores
• Only english language (no cyrilic, or translite)

Structure:

<funcType><logicalGroup><objectName><localType><position>_<number>

• <funcType> – type of object by its functional purpose: jnt - joint without binding bind - joints bound to geometry anim - animation controllers crv - curve (spline) loc - space locator (it’s called ‘dummy’ in 3DS Max) ROOT - root objects (mostly for joints) grp - group mat - material GEO - geometry. Skip this one unless you need to particularly highlight that the object is a geometry
• <logicalGroup> – a master object that this object belongs to. For example, if you have 10 buildings in a scene, and you’re naming a window of a particular building, the name of the window should indicate that (e.g. ‘redHouse_window_04’). That’s necessary to keep all names unique.
• <objectName> – the name of what the object is (e.g. ‘window’)
• <localType> – alphabetic marking of object’s type (e.g. ‘bolt_A_01’, if there are 5 types of bolts in the scene, the rest would be marked ‘B’, ‘C’, ‘D’, ‘E’)
• <position> – logical position of the object if similar objects are present in the scene (e.g. for the front left wheel - ‘jnt_wheel_FT_LF_01’) FT - front BK - back RR - rear LF - left RT - right
• <number> – number of the object in the scene if there is more than one. Format - ##, ###, etc (e.g. ‘boltHexa_A_032’)

Examples:

• BAD: ‘Left front door group’ ‘kontroller_krishka_bardachka_01’ ‘bind_indexFinger_2_right’
• GOOD: ‘grp_door_FT_LF_01’ ‘anim_gloveBox_lid_01’ ‘bind_indexFinger_B_RT_01’