Lighting and rendering workflow - Revision history

Bassam at 22:16, 26 November 2013

2013-11-26T22:16:26Z

Bassam at 22:03, 26 November 2013

2013-11-26T22:03:33Z

Bassam at 18:31, 23 October 2012

2012-10-23T18:31:31Z

Bassam: /* Lighting files */

2012-06-21T18:25:23Z

Lighting files

Bassam: /* Lighting files */

2012-06-21T18:16:19Z

Lighting files

Bassam at 17:47, 21 June 2012

2012-06-21T17:47:11Z

Bassam: /* Lighting files */

2012-06-21T17:46:25Z

Lighting files

Christine at 18:07, 18 June 2012

2012-06-18T18:07:39Z

Christine at 17:58, 18 June 2012

2012-06-18T17:58:29Z

Christine: /* Render Layers */

2012-06-18T17:53:53Z

Render Layers

← Older revision		Revision as of 22:16, 26 November 2013
Line 9:		Line 9:

	=== Diference between Lighting and Rendering ===		=== Diference between Lighting and Rendering ===
−	Lighting v.s Rendering: from conversation with Ivan we discussed that lighting i.e. interactive placement of lights, creative decisions about how the scene looks needs to be fast/realtime. Rendering on the farm doesn't to the same extent, how to do that? [[Speed up Lighting\|Tips to speed up lighting]] and [[Lighting Speedup Tools\|Future tools to speed up lighting]]	+	Lighting v.s Rendering: from conversation with Ivan we discussed that lighting i.e. interactive placement of lights, creative decisions about how the scene looks needs to be fast/realtime. Rendering on the farm doesn't to the same extent, how to do that?
		+
		+	=== Speeding up Lighting workflow ===
		+	There are two aspects to this, tips and tools (the former takes advantage of what is already in blender, the later is something we need to build:
		+	[[Speed up Lighting\|Tips to speed up lighting]] and [[Lighting Speedup Tools\|Future tools to speed up lighting]]

← Older revision		Revision as of 22:03, 26 November 2013
Line 1:		Line 1:
		+	== Introduction ==
		+	Our rendering tasks can be divided into:
		+	1- Lighting
		+	2- Compositing
		+	3- Rendering
		+	4- Final Grading
		+
		+	Order of 2 and 3 could get flipped based on pipeline choices. (If we comp image sequences then it 3-2 but if we comp renderlayers it is 2-3. The most likely outcome is 2-3 because [[Composite Then Render\|reasons]])
		+
		+	=== Diference between Lighting and Rendering ===
		+	Lighting v.s Rendering: from conversation with Ivan we discussed that lighting i.e. interactive placement of lights, creative decisions about how the scene looks needs to be fast/realtime. Rendering on the farm doesn't to the same extent, how to do that? [[Speed up Lighting\|Tips to speed up lighting]] and [[Lighting Speedup Tools\|Future tools to speed up lighting]]
		+
		+
	In the Weeks of October 22 and 29 we are working on figuring out the final lighting plan for the project. Please refer to (and edit) [[Lighting brainstorm]]		In the Weeks of October 22 and 29 we are working on figuring out the final lighting plan for the project. Please refer to (and edit) [[Lighting brainstorm]]

← Older revision		Revision as of 18:31, 23 October 2012
Line 1:		Line 1:
		+	In the Weeks of October 22 and 29 we are working on figuring out the final lighting plan for the project. Please refer to (and edit) [[Lighting brainstorm]]
		+
		+
	For a bit of background as to why we went this way, please see [[lighting pipeline choices]]		For a bit of background as to why we went this way, please see [[lighting pipeline choices]]

@@ Line 38: / Line 38: @@
 - you'll get panel called Gilgamesh overrides in the toolbar, use it to turn her fiber (eyebrows and eyelashes) on or off, change her subdiv level on render, and pick her level (proxy, high, ultra high)
-- in a text editor do Text-> Open text block, and pick lib/python/update_fixer.py from the svn root.
+- If you get problems with updating frames messing up, continue with these steps. in a text editor do Text-> Open text block, and pick lib/python/update_fixer.py from the svn root.
 - do Text-> Make Internal so you don't accidentally overwrite the original.

← Older revision		Revision as of 18:16, 21 June 2012
Line 37:		Line 37:

	10- you'll get panel called Gilgamesh overrides in the toolbar, use it to turn her fiber (eyebrows and eyelashes) on or off, change her subdiv level on render, and pick her level (proxy, high, ultra high)		10- you'll get panel called Gilgamesh overrides in the toolbar, use it to turn her fiber (eyebrows and eyelashes) on or off, change her subdiv level on render, and pick her level (proxy, high, ultra high)
		+
		+	11- in a text editor do Text-> Open text block, and pick lib/python/update_fixer.py from the svn root.
		+
		+	12- do Text-> Make Internal so you don't accidentally overwrite the original.
		+
		+	13- locate the gilgamesh rig in your file and note the object name, usually gilga_PROX_proxy or gilga_HI_proxy.
		+
		+	14- edit line 4 of update fixer.py and replace gilga_PROX_proxy with the actual name if different.
		+
		+	15- click on Register in the text editor header, and then Run Script
		+
		+	16- save the file.

	=== Comp files ===		=== Comp files ===

@@ Line 30: / Line 30: @@
 - Set the active camera to the same one from the anim file. Note this may have happened automatically in 5.
-- to use reference desk, create a custom scene property called library, and set it's value to ../../library.json
+- to use [[reference_desk]], create a custom scene property called library, and set it's value to ../../library.json
 - always good to save...

← Older revision		Revision as of 17:46, 21 June 2012
Line 29:		Line 29:

	6- Set the active camera to the same one from the anim file. Note this may have happened automatically in 5.		6- Set the active camera to the same one from the anim file. Note this may have happened automatically in 5.
		+
		+	7- to use reference desk, create a custom scene property called library, and set it's value to ../../library.json
		+
		+	8- always good to save...
		+
		+	9- install gilgamesh override from reference desk.
		+
		+	10- you'll get panel called Gilgamesh overrides in the toolbar, use it to turn her fiber (eyebrows and eyelashes) on or off, change her subdiv level on render, and pick her level (proxy, high, ultra high)

	=== Comp files ===		=== Comp files ===

@@ Line 65: / Line 65: @@
 - you may animate objects as needed. If the anim involves more than a few keyframes, consider creating a new anim task for the file, to be done in the anim file and linked to the lighting file.
-== Naming ==
+== Scene Layers ==
 Thanks to the nifty “3D View: Scene Layer Names” addon, we can keep track of what goes where.  This addon can be enabled in the User Preferences window; if it is not visible there, you can find it under lib > python > addons > scene_layernames.py in your svn folder.  Name your scene layers in a logical way.
 == Lamps ==
 - "Lamp" is the term used to describe the object that produces light.
 - The way you name lamps should taper from very general to very specific.  Separate the parts of the names with an underscore to make it more legible.  (Remember to name the lamp data as well as the lamp object!)  A good formula we could use would be something like light_[subject]_[purpose]_[direction]_[number/main].  Subjects are whatever is being illuminated, for instance gil, gil_hair, paper, station, bg(background) etc.  Purpose would be something like rim, fill, shadow, halo, etc.  Direction could be R(right), L(left), up, dn(down), back, front, etc.
 For example, your outliner might end up looking like this:
 light_gil_fill
 light_gil_rim_L
 light_gil_rim_R
 light_bg_fill
 light_bg_shadow
 light_hair_rim_back_1
 light_hair_rim_back_2
 light_hair_rim_back_3
 light_hair_rim_back_main
 light_hair_fill
 == Render Layers ==

@@ Line 96: / Line 96: @@
 == Render Layers ==
-Set up your render layers with appropriate names (typically, [subject]_[purpose]) and only include the scene layers necessary.
+- Set up your render layers with appropriate names (typically, [subject]_[purpose]) and only include the scene layers necessary.
-Before you hit F12 to render everything, make sure all the scene layers involved are toggled to be visible.
+- Before you hit F12 to render everything, make sure all the scene layers involved are toggled to be visible.
-If you want to ONLY render a specific render layer when you hit F12, toggle the little push-pin icon next to the render layer name.
+- If you want to ONLY render a specific render layer when you hit F12, toggle the little push-pin icon next to the render layer name.
-Render layers use alpha, so you can overlay one object over another.  If you have a situation where the object on render layer B is both in front of and behind the object on render layer A, you can tell render layer B to use “All Z” under the “Include” section of A’s render layer, which will cause the camera to render only what it can view without obstruction.  Alternatively, you can try to separate the foreground object of render layer A into its own scene layer and select that layer under the Mask Layer section under the Render Layer settings.
+- Render layers use alpha, so you can overlay one object over another.  If you have a situation where the object on render layer B is both in front of and behind the object on render layer A, you can tell render layer B to use “All Z” under the “Include” section of A’s render layer, which will cause the camera to render only what it can view without obstruction.  Alternatively, you can try to separate the foreground object of render layer A into its own scene layer and select that layer under the Mask Layer section under the Render Layer settings.
 == General Lighting Workflow ==