Creating a linkable asset - Revision history

Bassam: /* Lib */

2013-03-04T21:01:59Z

Lib

Bassam: /* Models */

2013-03-04T20:33:14Z

Models

Bassam: /* Models */

2013-03-04T20:29:06Z

Models

Bassam: /* Models */

2013-03-04T20:27:44Z

Models

Bassam: /* Models */

2013-03-04T20:27:13Z

Models

Bassam: /* Introduction */

2013-03-04T20:25:33Z

Introduction

Bassam: /* Models */

2013-03-04T19:28:46Z

Models

Bassam: /* Introduction */

2013-03-04T19:26:47Z

Introduction

Bassam at 19:25, 4 March 2013

2013-03-04T19:25:59Z

Bassam: /* Chars */

2011-08-24T19:46:06Z

Chars

@@ Line 18: / Line 18: @@
 Linkable assets/library assets in this context are blender data, python scripts or image data, stored in the [[Project_directory_structure|project directory structure]].
-== Lib ==
+== General Asset Instructions ==
-This is the top level folder for library data.
+These will all live in lib/ under some subfolders.
-=== Models ===
+=== Models To be Linked in shots ===
 [[File:Layers.png|thumbnail|right]]
 All the models to be linked as groups in scene/shot files.
@@ Line 32: / Line 32: @@
 * Make your asset [[Reference_desk|reference deskable]]
 <br style="clear: both" />
-==== Chars ====
+==== Characters, or models with rigs ====
 Use the [[Armature_layer_names|armature layer names]] addon to name your armature layers. This will allow you and others to edit the file with ease. Do not place any bones on layers that you do not name.
 Follow the guidelines for models in general, note we prefer:

@@ Line 26: / Line 26: @@
 * Use [[layer_names|the layer names addon]] to document any layers you use.
 * Name every object, material, object data, texture, etc. in the file. We do not yet have a consistent naming convention, advice is to look at an existing file, e.g. gilgamesh.blend or roach.blend,both in lib/chars before starting.
-* Create groups of your work, with good names. Refer to for guidelines.
+* Create groups of your work, with good names.
 * Make sure you use the dupli group layer visibility buttons, so only appropriate layers are visible when the groups are linked.
 * Make sure you include '''everything''' in the group. This includes e.g. Bone shapes for the rigs, curve bevel profiles, etc. Not doing so can create a mess in scene files, and in the worse case, cause dependency lags for animators.
 * Make your asset [[Reference_desk|reference deskable]]
 <br style="clear: both" />

@@ Line 29: / Line 29: @@
 * Make sure you use the dupli group layer visibility buttons, so only appropriate layers are visible when the groups are linked.
 * Make sure you include '''everything''' in the group. This includes e.g. Bone shapes for the rigs, curve bevel profiles, etc. Not doing so can create a mess in scene files, and in the worse case, cause dependency lags for animators.
-* Make your asset reference deskable
+* Make your asset [[Reference_desk|reference deskable]]
 <br style="clear: both" />
 ==== Chars ====

@@ Line 21: / Line 21: @@
 This is the top level folder for library data.
 === Models ===
 All the models to be linked as groups in scene/shot files.
-* [[File:Layers.png|thumbnail|right]]Use as much as possible the project layer guidelines.
+* Use as much as possible the project layer guidelines.
 * Use [[layer_names|the layer names addon]] to document any layers you use.
 * Name every object, material, object data, texture, etc. in the file. We do not yet have a consistent naming convention, advice is to look at an existing file, e.g. gilgamesh.blend or roach.blend,both in lib/chars before starting.

@@ Line 22: / Line 22: @@
 === Models ===
 All the models to be linked as groups in scene/shot files.
-* Use as much as possible the project layer guidelines.
+* [[File:Layers.png|thumbnail|right]]Use as much as possible the project layer guidelines.
 * Use [[layer_names|the layer names addon]] to document any layers you use.
 * Name every object, material, object data, texture, etc. in the file. We do not yet have a consistent naming convention, advice is to look at an existing file, e.g. gilgamesh.blend or roach.blend,both in lib/chars before starting.
@@ Line 29: / Line 29: @@
 * Make sure you include '''everything''' in the group. This includes e.g. Bone shapes for the rigs, curve bevel profiles, etc. Not doing so can create a mess in scene files, and in the worse case, cause dependency lags for animators.
 * Make your asset reference deskable
 ==== Chars ====
 Use the [[Armature_layer_names|armature layer names]] addon to name your armature layers. This will allow you and others to edit the file with ease. Do not place any bones on layers that you do not name.

@@ Line 2: / Line 2: @@
 == Introduction ==
-Asset creation is in the start of our pipeline: it will get used and affect everybody down the line. this is why we have some tools and guidelines to make things easier.
+Asset creation is in the start of our [[Shot_pipeline|pipeline]]: it will get used and affect everybody down the line. this is why we have some tools and guidelines to make things easier.
 the main ways people get affected by the model file is:

@@ Line 6: / Line 6: @@
 the main ways people get affected by the model file is:
-- polygon count: while I'm not giving strict requirements, be reasonable and it is ok- millions of polies is probably too much.
+* polygon count: while I'm not giving strict requirements, be reasonable and it is ok- millions of polies is probably too much.
-- object count: blender is pretty bad at handling lots of objects! this hit us badly for instance, in the train file (created by a talented but inexperienced modeler) : high poly count and high object count, resulting in extreme slowness.
+* object count: blender is pretty bad at handling lots of objects! this hit us badly for instance, in the train file (created by a talented but inexperienced modeler) : high poly count and high object count, resulting in extreme slowness.
-- topology and clean-ness of model of course
+* topology and clean-ness of model of course
-- object and object data names: If you don't name everything it is very hard to understand.
+* object and object data names: If you don't name everything it is very hard to understand.
-- really slow modifiers: we suffered from this and now we try to keep it down, even applying some modifiers to get better frame rates (like arrays)
+* really slow modifiers: we suffered from this and now we try to keep it down, even applying some modifiers to get better frame rates (like arrays)
 Since an anim file will link in several models, and then the lighting file links in the anim files and some more models, you get a compounding affect, where something acceptable at the beginning (modeling) is now causing problem at the end (lighting).

← Older revision		Revision as of 19:25, 4 March 2013
Line 1:		Line 1:
		+
		+	== Introduction ==
		+
		+	Asset creation is in the start of our pipeline: it will get used and affect everybody down the line. this is why we have some tools and guidelines to make things easier.
		+
		+	the main ways people get affected by the model file is:
		+
		+	- polygon count: while I'm not giving strict requirements, be reasonable and it is ok- millions of polies is probably too much.
		+	- object count: blender is pretty bad at handling lots of objects! this hit us badly for instance, in the train file (created by a talented but inexperienced modeler) : high poly count and high object count, resulting in extreme slowness.
		+	- topology and clean-ness of model of course
		+	- object and object data names: If you don't name everything it is very hard to understand.
		+	- really slow modifiers: we suffered from this and now we try to keep it down, even applying some modifiers to get better frame rates (like arrays)
		+
		+	Since an anim file will link in several models, and then the lighting file links in the anim files and some more models, you get a compounding affect, where something acceptable at the beginning (modeling) is now causing problem at the end (lighting).
		+
		+
		+
	Linkable assets/library assets in this context are blender data, python scripts or image data, stored in the [[Project_directory_structure\|project directory structure]].		Linkable assets/library assets in this context are blender data, python scripts or image data, stored in the [[Project_directory_structure\|project directory structure]].