Shot pipeline - Revision history

Bassam at 19:25, 24 August 2011

2011-08-24T19:25:40Z

Bassam at 18:01, 24 August 2011

2011-08-24T18:01:34Z

Bassam at 17:59, 24 August 2011

2011-08-24T17:59:50Z

Bassam at 17:59, 24 August 2011

2011-08-24T17:59:23Z

Bassam at 17:58, 24 August 2011

2011-08-24T17:58:57Z

Bassam at 17:58, 24 August 2011

2011-08-24T17:58:22Z

Bassam at 17:57, 24 August 2011

2011-08-24T17:57:34Z

Bassam: Created page with "
File:pipeline_diagram.png
* Assets are created in the lib folder. These maybe materials, models, python scripts, etc. Th..."

2011-08-24T17:54:06Z

Created page with "<br style="clear: both" /> File:pipeline_diagram.png <br style="clear: both" /> * Assets are created in the lib folder. These maybe materials, models, python scripts, etc. Th..."

New page

<br style="clear: both" />
[[File:pipeline_diagram.png]]
<br style="clear: both" />
* Assets are created in the lib folder. These maybe materials, models, python scripts, etc. These should be organized into layers, and named (every datablock needs a name). Models may need multiple versions which can live in the same file, or in multiple files.
* Layout files link in assets, preferably using reference desk, and conform to the layer organisation guidelines.
* Anim can start after layout begins, so long as the animated assets, and non-animated parts of the scene that they interact with are finished. Not that animation uses the layout file.
* Lighting can start after animation begins. Lighting files are seperate and link in the data from the anim files as objects.
* Optionally, we can render out multilayer EXRs and comp in a separate file. This can be done for complex comps where we do not want to pollute our 'artistic' comp with lighting hacks such as light and material overrrides.

@@ Line 4: / Line 4: @@
 * Assets are created in the lib folder. These maybe materials, models, python scripts, etc. These should be organized into layers, and named (every datablock needs a name). Models may need multiple versions which can live in the same file, or in multiple files.
 * [[Layout]] files link in assets, preferably using [[Reference_desk|reference desk]], and conform to the layer organisation guidelines.
-* [[Animation_Notes|Anim]] can start after [[Layout|layout]] begins, so long as the animated assets, and non-animated parts of the scene that they interact with are finished. Not that animation uses the layout file.
+* [[Animation_Notes|Anim]] can start after [[Layout|layout]] begins, so long as the animated assets, and non-animated parts of the scene that they interact with are finished. '''Note that animation uses the layout file'''.
 * [[Lighting_and_rendering_workflow|Lighting]] can start after animation begins. Lighting files are seperate and link in the data from the anim files as objects.
 * Optionally, we can render out multilayer EXRs and comp in a separate file. This can be done for complex comps where we do not want to pollute our 'artistic' comp with lighting hacks such as light and material overrrides.
 <br style="clear: both" />
 [[File:layers.png]]

← Older revision		Revision as of 18:01, 24 August 2011
Line 7:		Line 7:
	* [[Lighting_and_rendering_workflow\|Lighting]] can start after animation begins. Lighting files are seperate and link in the data from the anim files as objects.		* [[Lighting_and_rendering_workflow\|Lighting]] can start after animation begins. Lighting files are seperate and link in the data from the anim files as objects.
	* Optionally, we can render out multilayer EXRs and comp in a separate file. This can be done for complex comps where we do not want to pollute our 'artistic' comp with lighting hacks such as light and material overrrides.		* Optionally, we can render out multilayer EXRs and comp in a separate file. This can be done for complex comps where we do not want to pollute our 'artistic' comp with lighting hacks such as light and material overrrides.
		+	<br style="clear: both" />
		+	[[File:layers.png]]

@@ Line 4: / Line 4: @@
 * Assets are created in the lib folder. These maybe materials, models, python scripts, etc. These should be organized into layers, and named (every datablock needs a name). Models may need multiple versions which can live in the same file, or in multiple files.
 * [[Layout]] files link in assets, preferably using [[Reference_desk|reference desk]], and conform to the layer organisation guidelines.
-* [[Animation_Notes|Anim]] can start after [[layout]] begins, so long as the animated assets, and non-animated parts of the scene that they interact with are finished. Not that animation uses the layout file.
+* [[Animation_Notes|Anim]] can start after [[Layout|layout]] begins, so long as the animated assets, and non-animated parts of the scene that they interact with are finished. Not that animation uses the layout file.
 * [[Lighting_and_rendering_workflow|Lighting]] can start after animation begins. Lighting files are seperate and link in the data from the anim files as objects.
 * Optionally, we can render out multilayer EXRs and comp in a separate file. This can be done for complex comps where we do not want to pollute our 'artistic' comp with lighting hacks such as light and material overrrides.

@@ Line 4: / Line 4: @@
 * Assets are created in the lib folder. These maybe materials, models, python scripts, etc. These should be organized into layers, and named (every datablock needs a name). Models may need multiple versions which can live in the same file, or in multiple files.
 * [[Layout]] files link in assets, preferably using [[Reference_desk|reference desk]], and conform to the layer organisation guidelines.
-* [[Animation_notes|Anim]] can start after [[layout]] begins, so long as the animated assets, and non-animated parts of the scene that they interact with are finished. Not that animation uses the layout file.
+* [[Animation_Notes|Anim]] can start after [[layout]] begins, so long as the animated assets, and non-animated parts of the scene that they interact with are finished. Not that animation uses the layout file.
 * [[Lighting_and_rendering_workflow|Lighting]] can start after animation begins. Lighting files are seperate and link in the data from the anim files as objects.
 * Optionally, we can render out multilayer EXRs and comp in a separate file. This can be done for complex comps where we do not want to pollute our 'artistic' comp with lighting hacks such as light and material overrrides.

@@ Line 4: / Line 4: @@
 * Assets are created in the lib folder. These maybe materials, models, python scripts, etc. These should be organized into layers, and named (every datablock needs a name). Models may need multiple versions which can live in the same file, or in multiple files.
 * [[Layout]] files link in assets, preferably using [[Reference_desk|reference desk]], and conform to the layer organisation guidelines.
-* [[Anim|Animation_notes]] can start after [[layout]] begins, so long as the animated assets, and non-animated parts of the scene that they interact with are finished. Not that animation uses the layout file.
+* [[Animation_notes|Anim]] can start after [[layout]] begins, so long as the animated assets, and non-animated parts of the scene that they interact with are finished. Not that animation uses the layout file.
 * [[Lighting_and_rendering_workflow|Lighting]] can start after animation begins. Lighting files are seperate and link in the data from the anim files as objects.
 * Optionally, we can render out multilayer EXRs and comp in a separate file. This can be done for complex comps where we do not want to pollute our 'artistic' comp with lighting hacks such as light and material overrrides.

Shot pipeline - Revision history

Bassam at 19:25, 24 August 2011

Bassam at 18:01, 24 August 2011

Bassam at 17:59, 24 August 2011

Bassam at 17:59, 24 August 2011

Bassam at 17:58, 24 August 2011

Bassam at 17:58, 24 August 2011

Bassam at 17:57, 24 August 2011

Bassam: Created page with " File:pipeline_diagram.png * Assets are created in the lib folder. These maybe materials, models, python scripts, etc. Th..."

Bassam: Created page with "
File:pipeline_diagram.png
* Assets are created in the lib folder. These maybe materials, models, python scripts, etc. Th..."