Difference between revisions of "Making Library Nodes: Properties and Modeling"

(Object Naming)
(Properties)
Line 11: Line 11:
  
 
The object name should be short and descriptive. It should not explain the details of your object, such as a plant's species. If an object similar to yours already exists in the <code>library</code> folder of the media repository, use a different variation letter. For example, if you were creating a palm tree model, you would notice that <code>stklib_palmTree_a</code> already exists. Therefore you would use <code>stklib_palmTree_b</code> for a library node ID.
 
The object name should be short and descriptive. It should not explain the details of your object, such as a plant's species. If an object similar to yours already exists in the <code>library</code> folder of the media repository, use a different variation letter. For example, if you were creating a palm tree model, you would notice that <code>stklib_palmTree_a</code> already exists. Therefore you would use <code>stklib_palmTree_b</code> for a library node ID.
 +
 +
 +
 +
=== Object Properties ===
 +
 +
  
 
=== Naming ===
 
=== Naming ===

Revision as of 01:19, 10 September 2016

This page won't go into detail about modeling—any Blender tutorial can help with that. For a list of good tutorials and other resources, see the Blender resources page.

Modeling

Use whatever methods you need to model your objects. However, it helps to understand the scaling of objects a bit—for more information, see the 3D Model Guidelines page, which you should have already read. If you are using level of detail, you may want to skip ahead to the Level of Detail page and then come back to this page.

Properties

Every library node has an ID. The format is

The object name should be short and descriptive. It should not explain the details of your object, such as a plant's species. If an object similar to yours already exists in the library folder of the media repository, use a different variation letter. For example, if you were creating a palm tree model, you would notice that stklib_palmTree_a already exists. Therefore you would use stklib_palmTree_b for a library node ID.


Object Properties

Naming

It is extremely important to have consistent naming for library nodes, since other artists will be using them.

  • The .blend file should be named with the library node ID with the .blend file extension.
  • The object to be linked in a scene (of type "Object," "LOD Instance," or "LOD Standalone" in the SuperTuxKart Object Properties panel) should be named with the library node prefix suffixed with _main. For example,


  • Other objects (e.g. LOD Models, particle emitters, etc. should be given a clear and identifying name to avoid confusion.)