-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
660 lines (614 loc) · 61.5 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
<!DOCTYPE html>
<html lang="en">
<head>
<!-- Basic Page Needs
–––––––––––––––––––––––––––––––––––––––––––––––––– -->
<meta charset="utf-8">
<title>How to Use the BYU Pipeline Tools</title>
<meta name="description" content="">
<meta name="author" content="Ben DeMann">
<!-- Mobile Specific Metas
–––––––––––––––––––––––––––––––––––––––––––––––––– -->
<meta name="viewport" content="width=device-width, initial-scale=1">
<!-- FONT
–––––––––––––––––––––––––––––––––––––––––––––––––– -->
<link href="https://fonts.googleapis.com/css?family=Open+Sans:300,600|Nunito:400,700|Homemade+Apple" rel="stylesheet">
<!-- CSS
–––––––––––––––––––––––––––––––––––––––––––––––––– -->
<link rel="stylesheet" href="css/normalize.css">
<link rel="stylesheet" href="css/skeleton.css">
<link rel="stylesheet" href="css/styles.css">
<!-- Favicon
–––––––––––––––––––––––––––––––––––––––––––––––––– -->
<link rel="icon" type="image/png" href="images/favicon.png">
</head>
<body>
<!-- Primary Page Layout
–––––––––––––––––––––––––––––––––––––––––––––––––– -->
<div class="container" id="main-wrapper">
<div class="row">
<div class="twelve columns" style="margin-top: 5%">
<h1>How to Use the BYU Pipeline Tools</h1>
<p>Hello friend,</p>
<p>You are here because you have decided to embark on an epic journey to complete a short film.</p>
<p>Look around you. You are in the midst of the most brilliant creative minds in the history of the world. Look at yourself. You are one of those creative minds. Now all you need is a set of tools to help unlock your creative prowess and work in harmony with the titans around you.</p>
<p>My friend, if you seek those sacred tools then you have come the right place. These are the BYU Pipeline tools. These tools will help you unlock the mysteries of teamwork and harmony. And this documentation will be your guide to learning the full potential of these tools and thus uncover the full potential of you!</p>
<p>Read on and you will master your fate and take control of your destiny!</p>
<p>Best of Luck,</p>
<p class="signiture">Pipeline Management</p>
<p>Pipeline Management</p>
</div>
</div>
<div class="row" id="table-of-contents">
<div class="twelve columns">
<h2>Table of Contents</h2>
</div>
</div>
<div class="row">
<ul class="one-third column">
<li class="list-title"><h5>Introduction</h5></li>
<li><a href="#overview-anchor">Basic Overview</a>
<ul>
<li><a href="#preface-anchor">Preface</a></li>
<li><a href="#getting-access-anchor">Getting Access</a></li>
<li><a href="#important-terms-anchor">Important Terms</a></li>
<li><a href="#life-of-an-asset-anchor">Life of an Asset</a></li>
</ul>
</li>
</ul>
<ul class="one-third column">
<li class="list-title"><h5>Software</h5></li>
<li><a href="#maya-anchor">Maya</a></li>
<li><a href="#houdini-anchor">Houdini</a></li>
<li><a href="#mari-anchor">Mari</a></li>
<li><a href="#nuke-anchor">Nuke</a></li>
<li><a href="#slack-anchor">Slack</a></li>
</ul>
<ul class="one-third column">
<li class="list-title"><h5>Reference</h5></li>
<li><a href="#element-browser-anchor">Production Sheet</a></li>
<li><a href="#advanced-anchor">Advanced</a></li>
<li><a href="#glossary-anchor">Glossary</a></li>
</ul>
</div>
<div class="row" id="overview">
<a id="overview-anchor"></a>
<div class="twelve columns">
<h2>Basic Overview</h2>
<p>The <strong>pipeline tools</strong> are here to help you focus more on the art and less on the saving-the-files-into-the-right-place. It also provides some handy tools to make your life a little easier.</p>
<a id="preface-anchor"></a>
<h3>Preface</h3>
<h4>What is "The Pipeline"</h4>
<p>"The Pipeline" refers to the process by which the film is created. This process goes from concept to storyboard to animation to editing to the end. If an asset is in the pipeline then that means that it was entered into the flow of the film, so the pipeline can also refer to the collection of assets that make up the film. The "pipeline tools" are all of the softwares that keeps track of all of the assets in the pipeline. Since the pipeline and the pipeline tools are so deeply connected, in this document (and in talking about filmmaking) you may see "pipeline" and "pipeline tools" used interchangeably. Just be aware of that as we move forward and you should be able to distinguish the when "pipeline" refers to The Pipeline and when it refers to pipeline tools.</p>
<h4>The Pipeline is Like an Enormous Library</h4>
<p>It only works if all the little books mesh together.</p>
<p>A helpful analogy is to think of the pipeline like a library. You go to the library, find the book you want, check it out, read it, then return it to the library. The pipeline works the same way: you go to the pipe, check out the scene you want, change it*, then return it to the pipeline. That way, people can checkout the most updated scene and not worry about using outdated assets or duplicating work.</p>
<p><strong>*Note:</strong> In that sense it's nothing like a library because you return books to the library without editing them. In this case it's as if you are returning your asset to the pipeline-library better than when you picked it up. As a matter of fact there are lots of differences between the pipeline and a library, so don't hold onto to that analogy too tightly.</p>
<p>One important difference between the pipeline and a library is that multiple people can check out the same item at the same time. This is so that when Mike is working on a model Brennan can still check it out and do tests on it or show it off to someone instead of Mike having a monopoly on the model.</p>
<h4>A Word About Loosely Coupled Documentation</h4>
<p>In an ideal world I might be able to write this documentation to be not so tightly coupled to the current years film. In other words it would say things like "your film" or "the current film" instead of "Gendel." However it can be fairly difficult to do so and not be feel overly wordy. As we move forward though these instructions please note that every time you see the word Grendel, you can replace it with the name of your film, Every time you see the word Grendaya, Grendini, etc, replace it with "TheNameOfYourFilmaya, TheNameOfYourFilmini etc. But for the sake of brevity (and for the sake of our egos) we will just use Grendel, Grendaya, Grendini etc.</p>
<p>Also note that for fun and to help distinguish between the regular Maya and the Maya that has all of the BYU pipeline tools loaded in, we have renamed it and all the other software you will be using. Maya becomes Grendaya, Houdini becomes Grendini, etc.</p>
<a id="getting-access-anchor"></a>
<h3>Getting Access to the Pipeline Tools</h3>
<!-- TODO define what "the group" actually means -->
<p>In order to have access to the pipeline you need to be a member of "the group". Talk to Seth and he will be able to add you.</p>
<p>Once you are part of the group open up a file explorer and navigate to /groups/FILM/byu-pipeline-tools/. FILM will be the name of the group (ie grendel, dusk, etc). This directory is where all of the tools are located.</p>
<p>There will be a number of icons, most of which will be some humorous combination of the film name and the software. These icons will launch the software and load all of our custom tools.</p>
<img src="images/screenshots/general-byu-pipeline-tools.png"/>
<p>To add these icons to your desktop:
<ol>
<li>Right click on the icon</li>
<li>Click 'Make Link'</li>
<li>Right click on the link that was just created</li>
<li>Click 'Move to' -> 'Desktop'</li>
</ol>
</p>
<p>Hopefully that is the last time you will have to go into that folder. Should you find yourself interested in what else is there you can learn more in the advanced section.</p>
<a id="important-terms-anchor"></a>
<h3>Important Terms</h3>
<p>
The pipeline handles three different types of <a href="#body-def">bodies</a>: Assets, Tools, and Shots.
</p>
<ul>
<li>
<a href="#asset-def">Assets</a> are either props, accessories, sets, or characters. Assets are composed of various <a href="#element-def">elements</a>: <a href="#model-def">models</a>, <a href="#rig-def">rigs</a>, <a href="#texture-def">textures</a>, <a href="#design-def">designs</a>, <a href="#material-def">materials</a>, and <a href="#assebly-def">assemblies</a>.
<p>A common misconception is that an asset is the same as a model, however the appropriate relationship (at least as the pipeline tools see it) is to say that an asset has a model, it is a subtle difference and you will likely hear people (even those that are very familiar with the difference) slip up with it all the time. So just keep in mind as you read through this documentation and talk to others that an asset could potentially refer to:
<ul>
<li>something useful or valuable</li>
<li>short for Houdini Digital Asset</li>
<li>a model</li>
<li>Often it is used in place of body, maybe because the asset is the most common type of body. Or perhaps because "creating a body" sounds stranger than "creating an asset."</li>
</ul>
</p>
</li>
<li>
<a href="#tool-def">Tools</a> refer to the Houdini digital assets (HDAs) that have been developed specifically for the film. HDAs can be created to assist in various things while working in Houdini and saving them in the pipeline will allow everybody to have access to these tools. Tools are only composed of one sub element: <a href="#hda-def">HDAs</a>.
</li>
<li>
<a href="#shot-def">Shots</a> are...well shots I guess. The elements that make a shot are <a href="#animation-def">animations</a>, <a href="#cfx-def">character effects</a>, <a href="#comp-def">compositions</a>, <a href="#fx-def">effects</a>, <a href="#layout-def">layouts</a>, <a href="#lighting-def">lighting</a>, and <a href="#render-def">renders</a>.
</li>
</ul>
<p>To better understand how the pipeline works you first should understand the life of these bodies. And to understand the life of a body you need to understand these terms:</p>
<p><strong>*Note:</strong> For the sake of clarity we will discuss these terms looking at the specific case of the model element of an asset body. But everything should also apply to other elements and other bodies as well.</p>
<h4>Body Creation</h4>
<p>In order to do anything you need to create a new asset. Assets are usually the first bodies to be created and then shots will be made from assets. Tools will be made as you need them; if you never need them then you will never make them. When you create an asset you will give it a name and the pipeline tools will construct a bunch of folders to store the various elements of the body. For example it will create a model folder that will store the Maya file and the alembic exports for that model. This folder starts out empty but we can fill it by creating the model in Maya and then publishing it to the pipeline.</p>
<img src="images/screenshots/maya-body-creation.png"/>
<p>If you are creating an asset there are four different types of asset that it could be: Set, Prop, Character, and Accessory. When you create an asset it the body creation tool will ask you which type of asset it is.</p>
<img src="images/screenshots/maya-body-creation-asset-type.png"/>
<p>It is important that you select the appropriate type at this point because the pipeline will treat the different types very differently. Here are the differences:</p>
<ul>
<li>Set: Places in the film. These will be made up of props and accessories.</li>
<li>Characters: A person or creature in the film.</li>
<li>Props: Objects that are used by character. These objects will likely be animated.</li>
<li>Accessories: Objects that just sit in the set. These objects will likely not be animated.</li>
</ul>
<h4>Publishing</h4>
<p>First up is to make a part of the assets: the model. Once you have created the model you will need to save it into the pipeline. This is called publishing. When an asset is published, the pipeline tools will make a copy of your file and save it into the pipeline. In the case of the model, the pipeline will take your Maya file and make a copy of it to store in the model folder. Once you have published an asset it will be available for anyone to see and use. The way to access a file that someone else has published is through checking out the assets.</p>
<img src="images/screenshots/maya-publish.png"/>
<p>When you publish an asset make sure that you leave a good comment about the changes that you made. This makes it easy to track important changes on the asset and will become crucial if ever you need to rollback (discussed later).</p>
<h4>Checkout</h4>
<p>To use an asset you need to check it out. Checking out is the opposite of publishing. When you check out an asset the pipeline tools will create a copy of the production asset and save it to your personal files so that you can work on it. You can make whatever changes you need to it and when you are done you publish the asset again so that everyone can have access to your changes.</p>
<img src="images/screenshots/maya-checkout.png"/>
<p>Since the pipeline tools make a personal copy of the file for you, you can modify and save changes as you wish without worrying about changing the production version until you are ready to publish.</p>
<p>
Multiple people can check out the same asset and work on it at the same time. This is nice because it means that multiple people can look at, do tests on, or work on the the same file. However you need to watch out! Imagine a case where two people, Austin and Kalee, both are working on the model for Grendel. Austin is hard at work modeling Grendel's arms; it has taken him hours. Kalee has checked out Grendel's model as well to check on it's progress. Since Austin hasn't published his changes yet Kalee has an old version. She notices that Grendel's eyes are backwards and in a couple of seconds she fixes them. Austin finishes his changes and publish. Moments later Kalee publishes her changes, but her version doesn't include Austin's changes. There is no way to merge the changes, so the pipeline will use the model that was published most recently, in this case Kalee's version that has the eyes the right way but has the wrong arms. So make sure that you are communicating will all the people that are working on your asset.
</p>
<p>Now in the case of Austin and Kalee it is likely that they would actually want to use Austin's version and just apply Kalee's quick changes to it. Thankfully there is a way to revert a production model to a previous version, rollback!</p>
<h4>Rollback</h4>
<p>When you publish an asset the pipeline will keep track of the history of that item. So at anytime if you need to revert to a previous version of the asset you can rollback the changes.</p>
<img src="images/screenshots/maya-rollback.png"/>
<p>In the case of Kalee and Austin (discussed in the Checkout section), we see that Austin needs to restore his version. He would scroll through the revision history and find his version. If he doesn't remember the exact time of his publish he can look in the comment section for the descriptive comment that he wrote when he published it. Then he can rollback to his version, re-do Kalee's changes and republish.</p>
<h4>Naming Conventions</h4>
<p>You will find that there are a lot of names that end in "_main" and folders that are called "main." Why is this? The idea is that at some point you might want to have different variations of the same asset. For example in Taijitu we had the regular or main Ten and then we also had Dream Ten that had the same model and rig but had a different shader. So the idea is that you would have ten_texture_main and ten_texture_dream and those textures would be stored in /groups/dusk/production/assets/ten/texture/main/ten-skin.tex and /groups/dusk/production/assets/ten/texture/dream/ten-skin.tex. At the time of writing this there is no software that leverages this file structure of naming convention, at least not to my knowledge. In the future we might so we will just leave the folder structure and naming convention in the hope that one day we might support that.</p>
<a id="life-of-an-asset-anchor"></a>
<h3>The Life of a Pipeline Asset</h3>
<p>Now let's see these in context of the life of an asset:</p>
<ol>
<li>
Story artists take the story concept and draw each acting moment and scene in the film.
<br>At the time of writing this document there is no place for the storyboards in these pipeline tools.
</li>
<li>Assets are created for each prop, set, and character in the film using the create body tool.</li>
<li>Shots are created for each shot in the film using the create body tool.</li>
<li>
Vis Dev artists develop the look of objects and characters that are needed to help tell the story told by the story artists.
<br>There is presently no place for vis dev in the pipeline. But if the future the vis dev work could be saved into the pipeline along with all of the other elements of an asset.
</li>
<li>Modelers use the concept to create models in Maya and use the publish tool to save the model to the asset.</li>
<li>Riggers use the model to create all the necessary rigs in Maya and use the publish tool to save the rig to the asset.</li>
<li>Set dressers will bring all the models from each set together and arrange and size them to fit properly in the set. They will them use the publish tool to save the set to the pipeline as a set.
<li>Pre vis artists use the rigs and models to create a rough 3D outline of the film. Pre vis artist will layout the basic timing, positions, and camera motion for each shot in Maya and use the publish tool to save the layout to the shot.</li>
<li>Animators will use the pre vis layouts to inform their animation. They will animate all of the characters and props in Maya and use the publish tool to save the animation to the shot.</li>
<li>Shaders will create textures for the the asset in Mari and publish the textures to the proper asset.</li>
<li>Each asset will be assembled in Houdini using the models and textures created earlier and publish it as the assembly part of the asset. Each assembly has the the shader, set placement, and animation built into it.</li>
<li>Lighters will bring in the all of the assemblies for each shot and add lights to the set to create the appropriate mood for the shot.</li>
<li>Render Wranglers will brake the assets in the shot into layers and render each shot.</li>
<li>Compositors will bring the renders from Houdini into Nuke, add composite each shot to make sure that the film has a unified polished look. Then they will publish the composition to the shot</li>
<li>Editors will bring the composites of each shot together and join it with music and foley to create the final product.</li>
<li>Critics at the Television Academy will then watch the film, decide it is the best short film that they have ever seen, and award BYU with a Student Emmy for it's wonderful animated film.</li>
</ol>
<p>It's that easy*.</p>
<p><strong>*Note:</strong>Just keep in mind that at almost any point you can go back to a previous point and then move forward again only to jump back to revisit a different point etc.</p>
<p>That is the general overview of the pipeline and what it is doing. Now we will move on to the different tools in the various software.</p>
</div>
</div>
<div class="row" id="maya">
<a id="maya-anchor"></a>
<div class="twelve columns">
<h2>Maya</h2>
<p> For our production, we use Maya for modeling, rigging, pre vis, animation, and character effects. These tools are made to help with those tasks.</p>
<p>To access the pipeline, open up Grendaya and look at the row of tabs at the very top. Click the tool shelf tab on the furthest right labeled "Grendel".</p>
<img src="images/screenshots/maya-tools-shelf.png">
<h3><img class="icon" src="images/icons/checkout.svg"> Checkout</h3>
<p>The checkout button is exactly what it sounds like: you use it to check out, or access, previously worked on scenes or models. When you click it, a window will come up and you will notice that there are 5 tabs: model, rig, layout, anim, and cfx.</p>
<img src="images/screenshots/maya-checkout.png">
<p>If you are a modeler, you'll find the model you want to check out; if you're an animator, you'll find the scene you need to check out; If you're a CFX (character FX) artist you'll need to check out the cfx scene, etc.</p>
<p>In the list of assets or shots select the body you want to work on. Notice the box to the right of the list. This box will give you information about the current state of the body: who was the last person to work on it, when was the last time the body was changed, and what things were changed. If everything looks in order, click "Check Out" and Maya will load the file and you will be able to work on it.</p>
<p>However if you notice that Eric has been working on Beowulf constantly for several days and the last publish was a week ago it may be that Eric is still working on some changes and has not published them yet. Make sure you communicate with those that are working on the same body as you so that you can avoid duplicating work. Our checkout-publish system allows multiple people to check out an asset or shot at the same time so that none of the bodies are locked down. However with this power comes great responsibility! Make sure you are a good communicator!</p>
<p>Another possibility is that you see "No publishes for this element." That means there is nothing for you to check out. First you must model the asset or create a rig or setup the shot locally and then publish it to the pipeline.</p>
<h3><img class="icon" src="images/icons/new-body.svg"> Create Body</h3>
<img src="images/screenshots/maya-body-creation.png">
<p>As discussed in the basic overview section, creating a body will add a new asset, tool, or shot to the project. After the body is created you will then be able to publish and check out it's various parts. When you click this button, a window will come up that has three tabs, "Asset", "Tool" and "Shot". If you are making a new asset, you will name it under the asset tab, and so forth. Following proper naming conventions (that have been established by those in charge of the film), type in the name of the asset or shot and then click "Ok." The body is now added to the project and is ready to receive its first publish!</p>
<h3><img class="icon" src="images/icons/publish.svg"> Publish</h3>
<p>The publish button will allow you to upload your model or scene's progress to the pipeline so that others can access it. After checking out a model or scene, you can modify it then publish it back out. Once your asset is published, you should be able to check it out any time you or someone else needs it. Your publishes will replace the previous publishes but it will not overwrite them. This allows you return to a previous version with a rollback (see further down below).</p>
<p><strong>Important: </strong> before you publish an asset make sure you are following these conventions:
<ul>
<li>Geo is properly named. There should be no "polysurface87" in the Outliner. If each piece of geo doesn't have a descriptive name then it will very hard for shaders to know what textures to assign to which geo later on.</li>
<li>Make sure that there is as little geo as possible. If the geo is going to use the same texture as another geo in the model you should consider joining them into one mesh. This will make it easier for the shaders to shade and it will make it easier for Houdini to load in and group the asset</li>
<li>Make sure that all the geo is grouped into one parent group. Beneath that group there can be any number of groups that you want but all of those groups and meshes need to be contained in one group. Otherwise the sets that reference that asset are going to very cluttered and the alembic export my not export your asset correctly.</li>
<li>Make sure you freeze transformations and delete history.</li>
</ul>
</p>
<img src="images/screenshots/maya-publish.png">
<h3><img class="icon" src="images/icons/frame-range.svg"> Set Current Frame Range</h3>
<p>Theoretically, this would read into the Asset Browser app thing that we have and make it easier for you to make the correct frame range on any given animated shot. However, we aren't using the Asset Browser anymore, and this button essentially does nothing. So don't click it.</p>
<h3><img class="icon" src="images/icons/playblast.svg"> Playblast this Shot</h3>
<p>A playblast is essentially making a really low-res, non-shaded render that takes seconds instead of hours. Use this to playback your animation in real time, as playing your animation in the viewport (even in the real-time setting) can be inaccurate.</p>
<h3><img class="icon" src="images/icons/alembic-export.svg"> Export as Alembic</h3>
<p>For exporting alembics you have two options. Animated or static.</p>
<h4>Animated</h4>
<p>An alembic is essentially an .obj file for animated objects and it has a buch of other features too. It will export your animation into a format that other packages like Houdini can read. Uploading an alembic to the pipe is a way to backup your file and keep the animation safe even if your animation file explodes, but keep in mind that uploading alembics constantly will slow down the pipe for everyone if it becomes too full of files. We recommend that you export your alembic to the pipe either when you are finished with your animation or reach a major checkpoint. (You may export your animation as an alembic to your local drive (using Maya's built in exporter) as often as you want though.)</p>
<h4>Static</h4>
<p>Normally a static version of each asset is exported to an alembic when you publish. However should you ever meet a case where you need to re-export the static alembic for an asset but you haven't made any changes that need to be published (sometimes, though rarely, the Houdini tools may prompt you to do so) then you can just checkout the asset and use the static option to create the static alembic export.</p>
<h3><img class="icon" src="images/icons/tag.svg"> Tag Selected Objects for Export</h3>
<p>There are a lot of parts of a character that should not be included in an alembic. For example, the rig controls for a character should be left out and only the deformed mesh should be included in the export, or simulation meshes for cloth should not be included but the high res hero cloth that deforms to that simulation mesh should be included. Use the tag tool to mark the geometry that needs to be exported and then when the Export as Alembic tool is run it will only export the tagged geo. You should only ever need to tag an item once. Therefore you should tag it as early in the process as possible. For a model you could tag it when you are rigging it. Tag the geo and then any time the rig is referenced it will still have those tags.</p>
<h3><img class="icon" src="images/icons/untag.svg"> Untag Selected Objects for Export</h3>
<p>If you tag something that should not be tagged or for any other reason you need to untag something then you can untag it with this tool. Since objects are untagged by default, you should only have to do it to objects that have been tagged previously.</p>
<h3><img class="icon" src="images/icons/reference.svg"> Reference a Model or Rig</h3>
<img src="images/screenshots/maya-reference.png">
<p>A reference is like importing a model or rig into your scene except it pulls from another location and updates as the owner of that file updates it. This is especially important for character rigs as the riggers will continue to polish deformations and your referenced rig will update with those changes. You will need to re-reference your rig(s) every time a change is made to the rig in order to see it in your animation; this will not affect your keyframes.
Other notes: You cannot modify a model or rig when it is referenced. Referenced rigs are generally faster and less expensive to run than the real rig itself.</p>
<h3><img class="icon" src="images/icons/quote.svg"> Inspirational Quote (AKA the Brent Button)</h3>
<p>Click to be inspired by your favorite faculty's inspirational quotes. Also submit more quotes to the tool_suggestions channel on Slack.</p>
<h3><img class="icon" src="images/icons/gnome.svg"> Gnomic Test Geo (AKA Summon the Garden Gnome button)</h3>
<img src="images/screenshots/maya-gnome.png">
<p>Need to blow something up or set it on fire? Have we got the gnome for you! This is kind of like Myth Buster's "Buster" test dummy except a garden gnome and also virtual. Have fun, go play with scissors and fire on us.</p>
<h3><img class="icon" src="images/icons/ik-fk.svg"> IK FK Snapping</h3>
<p>The IK FK Snapping Tool allows you to match an IK limb of a rig to the corresponding FK limb. When you click on the tools you will see a small window that will allow you to select the character, limb, and side to snap. Then you click on the mode you want switch to.</p>
<img src="images/screenshots/maya-ik-fk-snapping.png">
<h3><img class="icon" src="images/icons/refresh-scripts.svg"> Reload Tools Scripts</h3>
<p>If you have made changes to the code that runs any of these buttons then you can use the Reload Tools Scripts tool to reload the scripts without having to restart maya. You can find more information about this in the <a href="#advanced-anchor">Advanced section</a>.</p>
<h3><img class="icon" src="images/icons/rollback.svg"> Rollback Body to Previous Version</h3>
<p>Occasionally, you might publish a scene or model that for some reason you wish you didn't because the last version was better. Or maybe the current published version has crashed and there's no saving it, so the best bet is to go back in time and reverse the damage.</p>
<p>That's what rollback is for! Rollback will take you back to a previous version. To use it, click the element you want to rollback to and click the date of the version you want.</p>
<img src="images/screenshots/maya-rollback.png">
<p>To rollback an element first check it out. Then click the rollback button. A window will come up that will list all of the previous publishes for that element. Click on the publish that you want to go back to and click "Rollback." Maya will essentially recall the file from that past publish and republish it so it becomes the current publish (<strong>*Note:</strong> In the list of publishes this publish will now occur twice, once when it was originally published and again when it was rolled back). It will load publish into Maya and you can then start working on it.</p>
</div>
</div>
<div class="section" id="houdini">
<a id="houdini-anchor"></a>
<div class="row">
<div class="twelve columns">
<a name="houdini"></a>
<h2>Houdini</h2>
<p>For our production, we use Houdini for shading, lighting, rendering, and most of the FX.</p>
<p>Do you remember all of those neat things you learned back in the Maya section? Well, throw them out. They only partially relate to the Houdini pipeline tools and having them tightly coupled in your mind will lead to errors.</p>
<p>Let's take a look at Houdini</p>
<p>Go ahead and open the film version of Houdini. Now at this point Houdini probably didn't load in the shelf like Maya did. To get there you will need to add it.</p>
<img src="images/screenshots/houdini-add-tools-shelf.png"/>
<p><strong>Sidenote:</strong> Additionally you can find all the tools in the menus. Just incase you prefer that to a shelf button. Also tools will show up in the menu first because they are easier to add to the menu then they are to add to the shelf. So if you are looking for a BYU tool and it's not on the shelf, check the menu.</p>
<img src="images/screenshots/houdini-menu.png"/>
<p>With the tools shelf added in, let's take a look at all of the tools.</p>
<img src="images/screenshots/houdini-tools-shelf.png"/>
<h3><img class="icon" src="images/icons/new-body.svg"> Create Body</h3>
<p>The create body tool here is actually the exact same as the one in Maya, so about forgetting everything what I mean is don't forget this one.</p>
<h3><img class="icon" src="images/icons/assemble.svg"> Assemble Asset</h3>
<p>To understand how the checkout and publish buttons are different we first need to understand how the assemble asset tool works.</p>
<p>In Houdini the method of adding geometry to a scene is typically by using the tab menu in the Network View. In order to add our geometry to Houdini we first need to make digital assets for them. Once we have we will be able to simply tab in all of our assets into Houdini. The assemble asset tool creates the digital assets for you.</p>
<img src="images/screenshots/houdini-assemble-asset.png"/>
<p>Find the asset that you want to turn into a digital asset and then click "Assemble." This will load in the alembic that Maya exported when you published it, and turn it into a digital asset. Once the digital asset is created you can add the shaders for the various objects into the digital asset. Once you are pleased with your work, select the digital asset, and then click publish. Now the digital asset is ready for anybody to tab into their scene.</p>
<p><strong>Important:</strong> Once the asset is assembled you no longer need to assemble it. You can just tab it in. If you click assemble asset again it will completely rebuild the digital asset, bringing in the alembics from Maya again but it won't bring in any of the shaders that you created. If someone else has already assembled the asset you will receive a message warning you that the asset has already been assembled. You can assemble it again if you want but you will wipe out any changes that may have been there. If you don't need to assemble it again then you can tab it into the network view without assembling it again.</p>
<p>If for some reason you do need to reassemble the asset you may find that the <a href="#reassemble-tool-anchor">reassemble tool</a> will do the trick for you without loosing the shader information.</p>
<p>Overview
<ol>
<li>Click assemble asset</li>
<li>Click on the asset you wish to assemble</li>
<li>
Click "Check Out", which should lead you to here:
<img src="images/screenshots/houdini-asset-hda.png"/>
</li>
<li>
Add shaders and perform whatever other edits (More details below)
<img src="images/screenshots/houdini-shop-net.png"/>
<p>Here you will notice that there is a subnet called "dont_touch_this_subnet." At the time of creating this tool there was an issue with adding displacement to groups for RenderMan for Houdini. The only thing we could come up with was to break the groups into their own geo nodes and store them into this subnet. However we were able to make the interface the same as if we didn't have to do this work around. So you shouldn't have to touch this subnet at all. If you find yourself tempted to put stuff in it or to edit any of it's parameters you should really consider if there is a different way you can accomplish what you are trying to do.</p>
</li>
<li>Select the digital asset in the network view</li>
<li>Click publish</li>
</ol>
</p>
<p>If you need to make changes to the asset the instructions are a little different:
<ol>
<li>Tab in the asset</li>
<li>Select it in the network view</li>
<li>Make the necessary changes</li>
<li>Select the digital asset in the network view</li>
<li>Click publish</li>
</ol>
</p>
<h4>Building Shaders</h4>
<p>Each asset will have it's own shopnet and you should create the shader for each asset within it's own shader so that whoever checks it out can have the shaders with it.</p>
<p>Each texture that is exported from Mari using the Tex export will be found here: "/groups/grendel/production/assets/ASSET_NAME/texture/main/cache/TEXTRUE_NAME.tex."</p>
<p>When you assign the filename of the texture to the shader make sure that the path uses $JOB. When using Grendini $JOB refers to "/groups/grendel" so the path from above would become "$JOB/production/assets/ASSET_NAME/texture/main/cache/TEXTRUE_NAME.tex."</p>
<img src="images/screenshots/houdini-asset-geo-shaders-job.png"/>
<h4>Asset Parameters</h4>
<p>Once the asset has been assembled and all of the shaders have been created you can assign them to the geometry. In the geo node (Img 2) you will find all the parameters for setting up the shaders. The Material tab (Img 3) will have a set of parameters for each geometry group in the alembic. These groups are based off of the pieces of geometry in Maya. If you have 1000 geos in the outliner you will also have 1000 groups that you are going to have to deal with here. Make sure that the geo is clean and organized in Maya so that it is easy to deal with in Houdini. For each group you can assign the material, the displacement, and the displacement bound.</p>
<p><strong>Important:</strong>When you are working on the shaders make sure that the paths to the shaders are relative paths. One way this can be achieved is in the operator selector (Img 1) make sure you have "Export Relative Path" checked before you click accept.</p>
<img src="images/screenshots/houdini-asset-geo-shaders-relative-path.png"/><p class="caption">Img 1</p>
<p>The RenderMan tab (Img 4) in the geo parameters will have several RenderMan settings such as "Render Polygons as Subdivisions" and "Interpolate Boundary." If there are other RenderMan parameters that would be good to include here let us know and we can add it.</p>
<p>If the geometry hasn't loaded you can try going to the Troubleshooting tab (Img 5) and click the "Refresh" button. This will try and reload the geometry from the alembic. If it still doesn't work feel free to poke around any of the nodes and see if you can find the problem. If all else fails just find a Pipeline technician to help fix the problem.</p>
</div>
<div class="row">
<div class="three columns"><img src="images/screenshots/houdini-asset-geo-selected.png"/><p class="caption">Img 2</p></div>
<div class="three columns"><img src="images/screenshots/houdini-asset-geo-shaders.png"/><p class="caption">Img 3</p></div>
<div class="three columns"><img src="images/screenshots/houdini-asset-geo-renderman.png"/><p class="caption">Img 4</p></div>
<div class="three columns"><img src="images/screenshots/houdini-asset-geo-troubleshooting.png"/><p class="caption">Img 5</p></div>
</div>
<div class="row">
<div class="twelve columns">
<p>There are also some new parameters on the digital asset (Img 6). In the Grendel tab (Img 7-9) there are options for loading different versions of the asset. These versions can be selected from the "Source Menu" in the Grendel Tab.</p>
<p>First, the Object Space (Img 7) option will load the geometry as it was modeled in Maya.</p>
<p>The Set Space option (Img 8) allows you to select a set in the film and if this asset appears in that set if will load the translation, rotation, and scale of this asset so it will fit into that set. The set can be selected from the set menu that will appear if the source is set to "Set."</p>
<p>The Shot Space option (Img 9) will load in any shot specific animation for this asset. If in the shot the asset remains static then you can leave the source set to Set Space. However if the asset moves then you can select the shot and the tool will load in the dynamic alembic for that specific shot.</p>
<p>Additionally there is a hide toggle that will allow you to hide or show the asset and a "Reload" button that is just the "Refresh" button from above that has been promoted up to the HDA level for your convenience.</p>
</div>
</div>
<div class="row">
<div class="three columns"><img src="images/screenshots/houdini-asset-selected.png"/><p class="caption">Img 6</p></div>
<div class="three columns"><img src="images/screenshots/houdini-asset-object-space.png"/><p class="caption">Img 7</p></div>
<div class="three columns"><img src="images/screenshots/houdini-asset-set.png"/><p class="caption">Img 8</p></div>
<div class="three columns"><img src="images/screenshots/houdini-asset-shot.png"/><p class="caption">Img 9</p></div>
</div>
<div class="row">
<div class="twelve columns">
<h4>Assembling a Set</h4>
<p>Since a set is a bunch of assets put together the assembly process for a set is a little different. Instead of loading in alembics directly from the set in Maya the assembler will instead load in all of the HDAs for all of the assets that are in that set. It will then promote many of the options discussed above to a parent HDA that represents the set.</p>
</div>
</div>
<div class="row">
<div class="twelve columns">
<div class="six columns"><img src="images/screenshots/houdini-set-hda.png"/><p class="caption">Img 1</p></div>
<div class="six columns"><img src="images/screenshots/houdini-set-insides.png"/><p class="caption">Img 2</p></div>
</div>
</div>
<div class="row">
<div class="twelve columns">
<div class="six columns"><img src="images/screenshots/houdini-set-parms.png"/><p class="caption">Img 3</p></div>
<div class="six columns">
<p>Sets also have a different set of parameters. In the "Set Options" you will find controls to set set the shot for any animation that takes place on the items in that set. You will also find two checkboxes for each item in the set: "Hide" and "Animated". If the Hide box is checked the asset in the set will be hid. If the Animated box is checked then instead of using the typical static geo for the set the animated alembic will be used for the shot specified in the shot folder.</p>
<p>All of the shaders should be hooked up on each of the assets in the set so once it is assembled you shouldn't have to do much to it. However you might find it useful to organize the assets in the set into several tabs (as seen in image 3) so that it is easier to find them.</p>
<p>Additionally if any of the assets in the set have any custom controls you may want to promote them to the set HDA so you can access those controls without needing to unlock the set HDA.</p>
</div>
</div>
</div>
<div class="row">
<a id="reassemble-tool-anchor"></a>
<div class="twelve columns">
<h4>Reassembling an Asset</h4>
<p>There may be times when you will need to reassemble an asset. This might be because the parameter interface for the assets has changed and it needs to be updated. Or maybe the names of groups and geo changed so much that they don't show up anymore. If the changes are small enough it might be easier to do them by hand. But if the changes are very extensive then the reassemble tool might be the tool for you!</p>
<p><strong>WARNING!:</strong> The reassemble tool is going to delete all geo nodes in the HDA. Make sure that anything you want to preserve is stored in a subnet or an HDA tool. Maybe make a copy of it just in case.</p>
</div>
</div>
<div class="row">
<h3><img class="icon" src="images/icons/checkout.svg"> Checkout</h3>
<p>Checkout is a little tricky in Houdini because there are three different things you can checkout (Assets, Shots, and Tools) and they all get checked out a little differently.</p>
<p>For Assets and Tools you only need to check them out if you are going to edit them. If you only need to use them in the shot then you can just tab them in. If you do need to checkout an asset or a tool you just tab in the HDA for the Asset or Tool, right click on it, and click checkout.</p>
<img src="images/screenshots/houdini-asset-checkout.png"/>
<p>It will unlock the node and give you the following confirmation.</p>
<img src="images/screenshots/houdini-checkout-asset.png"/>
<p>For shots you can checkout either a lighting scene or an effects scene. Just use the "Checkout Shot" tool in the tool shelf, select the shot you want to work on from either the lighting or fx tab, and click checkout.</p>
<p><strong>Sidenote:</strong> As you were looking in the shelf you probably noticed that there is also a "Checkout Tool" and "Checkout Asset" buttons as well. You can use these if you want but you are going to have to make sure that you select the node that you want to checkout in the network view and then click checkout.</p>
<img src="images/screenshots/houdini-checkout-shot.png"/>
<h3>Reference</h3>
<p>There isn't a reference tool per se but since we are using HDAs you can tab in any asset into Houdini. These act as references that will get updated anytime that the HDA get's updated, But you can also then check out the asset after you have tabbed it in, and then it is no longer a reference but a checked out asset.</p>
<h3><img class="icon" src="images/icons/rollback.svg"> Rollback</h3>
<p>Rollback works in Houdini similarly to Checkout. If you want to rollback and Tool or Asset just tab it into the network view right click and click Rollback. If you have a shot checked out then you can use the "Rollback Shot" tool to rollback that shot. From there it's the same as any other rollback.</p>
<h3><img class="icon" src="images/icons/publish.svg"> Publish</h3>
<p>Publish is like Checkout and Rollback. (<strong>*Note:</strong> you can only publish an HDA if you first checked it out. In the context menu the option to publish the asset will only show up if you had previously checked out the asset.)</p>
<img src="images/screenshots/houdini-asset-publish.png"/>
<p>When the publish window comes up, make sure the right asset, or shot is selected, write a publish message descripting what you changed, and click publish.</p>
<h3><img class="icon" src="images/icons/quote.svg"> Inspire</h3>
<p>See also <a href="#maya-inspire-tool">Maya Inspire tool</a>. It's the exact same.</p>
<h3><img class="icon" src="images/icons/gnome.svg"> Gnome</h3>
<p>This is essentially the same as the Maya Gnomic Test Geo tool but in Houdini it also will load in the gnome's textures!</p>
</div>
</div>
</div>
<div class="row" id="mari">
<a id="mari-anchor"></a>
<div class="twelve columns">
<h2>Mari</h2>
<p>For our production, we use Mari for painting textures. Instead of having a shelf we have a menu. Because it's a little easier to make.</p>
<img src="images/screenshots/mari-tools-menu.png"/>
<h3><img class="icon" src="images/icons/assemble.svg"> Create Project from Geo</h3>
<p>First things first is to grab all of the geometry of the asset that you are texturing. Click on Create Project from Geo tool, select the asset you wish to texture, and Click "Assemble." Mari will bring in the alembic file for the geometry associated with that assets.</p>
<img src="images/screenshots/mari-create-project-from-geo.png"/>
<p>The alembic will load into Mari with all of the groups from Maya. This is one of the reasons it's important to make sure that all of the geo is well named, organized, and grouped all under one group.</p>
<img src="images/screenshots/mari-geo-layout.png"/>
<p class="caption">Geo heirarcy for the small cabinet. Shelves, jars, etc are all children of the small cabinet.</p>
<h3><img class="icon" src="images/icons/renderman.svg"> Export Tex</h3>
<p>You don't need to wait until you publish to export your textures. You can export .tex files easily with the Export Tex tool. Select the geo or channel you wish to export textures for and then click the corresponding Export Option (All, Selected Geo, or Selected Channel).</p>
<img src="images/screenshots/mari-tex-export.png"/>
<p>If you used the Import Geo tool then Mari will already know where to export the textures to. If you brought the geo in by yourself (because you started working on it before this tool was made) then it will prompt you to select the asset to which the texture belongs. If you need to get to the texture it can be found in /groups/grendel/production/assets/ASSET_NAME/texture/main/cache/.</p>
<img src="images/screenshots/mari-tex-location.png"/>
<p>In the future we will probably be able to make Houdini bring them in automatically for you but until the future has arrived you are going to have to get those manually. Thank you for your patience!</p>
<h3><img class="icon" src="images/icons/checkout.svg"> Checkout</h3>
<p>One the surface checkout and publish look the same as they do anywhere else. You pick the the asset you want to checkout and BYU Pipeline Tools will load it into Mari. Then you can publish it and anyone else will be able to open the Mari project and work on it as well.</p>
<img src="images/screenshots/mari-checkout.png"/>
<p class="caption">Checkout looks the same as every where else, but it acts differently.</p>
<p>However there are a couple of weird things that you need to be aware of. Deep down checkout for Mari is a little different because Mari handles projects a little differently. In order to make sure things are running as fast as possible Mari keeps all of your projects in a cache. In order to get them out of the cache and into the pipeline we need to create an archive of the project, and then that archive can be put into the pipeline. Then when you checkout a Mari file the pipeline tools will load the archive from the prodcution folder and extract it into your projects list where you can easily edit it. Where it gets a little weird is that this project will stick around until you delete it. So if you checkout the file again it pull out the production archive and load it again into your project cache and it will create a second version of the asset.</p>
<img src="images/screenshots/mari-double-checkout.png"/>
<p class="caption">Viking_sword_01 has been checked out twice, so in the projects list we have viking_sword01 and viking_sword01(2)</p>
<h3><img class="icon" src="images/icons/publish.svg"> Publish</h3>
<p>Publish works the same as usual with the caveat that we discussed in the checkout section. When you publish it will archive your project and save it into the pipe. You are then free to delete it from your projects. In fact the publish tool can do it for you if you want. It will give you the option to delete the project all you have to do is say yes. Or no if you are the paranoid type or you have additional things you are going to do with the file and you aren't ready to say goodbye yet.</p>
<img src="images/screenshots/mari-delete-published-project.png"/>
<p class="caption">Published projects can be removed from your projects</p>
<p>At this point BYU Pipeline Tools will also export all of the textures for that file, and you are good to move on to the next thing.</p>
<h3><img class="icon" src="images/icons/rollback.svg"> Rollback</h3>
<p>Rollback works the same as usual. When you rollback the pipeline tools will copy the archive of the publish you selected and load it Mari. (To make sure everything is clear you are replacing the current version of your project with an old version. Since that old version is replacing the current version the old version becomes the new version and your current version is now the old version.) The new project will take the place of your current project and you will not be able to undo this action. If you think that at any point in the future you are going to need to go back to the old version make sure that you have published it before attempting to rollback.</p>
<h3><img class="icon" src="images/icons/quote.svg"> Inspire</h3>
<p>See also <a href="#maya-inspire-tool">Maya Inspire tool</a>. It's the exact same.</p>
</div>
</div>
<div class="row" id="nuke">
<a id="nuke-anchor"></a>
<div class="twelve columns">
<h2>Nuke</h2>
<p>For our production, we use Nuke for compositing.</p>
<p>The pipeline tools for Nuke are located in the sidebar</p>
<img src="images/screenshots/nuke-tools-shelf.png">
<h3><img class="icon" src="images/icons/checkout.svg"> Checkout</h3>
<p>Nothing weird here! It's just a pretty straight forward checkout process!</p>
<h3><img class="icon" src="images/icons/publish.svg"> Publish</h3>
<p>Nothing weird here! It's just a pretty straight forward publish process!</p>
<h3><img class="icon" src="images/icons/rollback.svg"> Rollback</h3>
<p>Nothing weird here! It's just a pretty straight forward rollback process!</p>
<h3><img class="icon" src="images/icons/auto-comp.svg"> Auto Comp</h3>
<p>This tool does a lot of the set up for you. I don't know if it is general purpose or if it has some stuff that was specifically just for Taijitu. Try it and let me know.</p>
<h3>The Future</h3>
<p>There are many tools that could be made for Nuke but haven't been made or even dreamed of. If you have a vision for an awesome tool for Nuke, let us know if the tools-suggestions channel on slack!</p>
</div>
</div>
<div class="row" id="slack">
<a id="slack-anchor"></a>
<div class="twelve columns">
<h2>Slack</h2>
<p>For our production, we use Slack for communication.</p>
<p>In Slack you can find important links in the important links channel</p>
<p>Each department has their own channel where you can collaborate on the current projects, show of your progress, and ask questions.</p>
<p>Also check out <a href="http://2018byuanimation.blogspot.com/" target="_blank">the blog</a> for more information.</p>
</div>
</div>
<div class="row" id="element-browser">
<a id="element-browser-anchor"></a>
<div class="twelve columns">
<h2>Production Sheet</h2>
<p>This <a href="https://docs.google.com/spreadsheets/d/1FJA5kKAydy96g65tcNo613BLzah4Rg5QlsbUldysdAk" target="_blank">Google sheet</a> keeps track of the progress on each asset and shot. It keeps track of who is working on what and helps us see what needs the most work.</p>
</div>
</div>
<div class="row" id="advanced">
<a id="advanced-anchor"></a>
<div class="twelve columns">
<h2>Advanced</h2>
<p>With any luck at all you won't need this but if you are curious here is some more information about the insides of the pipeline. For even more information look at our <a href="https://github.com/byu-animation/byu-pipeline-tools" target="_blank">git repository</a> or talk to you local pipeline technician.</p>
<h3>Switching definitions for Houdini Digital Assets</h3>
<p>Have you noticed that for some reason when you tab in an HDA that it isn't the same as when someone else tabs it in? Are you particularly frustrated because it's an asset that you assembled? Houdini may have switched HDA definitions on you! Don't worry it's super easy to fix.
<ol>
<li>Tab in the asset in question</li>
<li>Right click on the asset</li>
<li>
Select "Type Properties"
<p>A little window with a ton of different options and setting should appear</p>
</li>
<li>Find a drop down menu labeled "Switch definition"</li>
<li>
Click it to reveal a couple different paths to a couple different definitions of the HDA.
<p>Likely the one that is selected will be something along the lines of "/groups/grendel/users/USERNAME/ASSET_NAME/ASSET_NAME.hdac"</p>
</li>
<li>Select the option that is "groups/grendel/production/assets/ASSET_NAME/assembly/main/ASSET_NAME.hdac" to switch to the production definition of the digital asset</li>
<li>Click Save</li>
</ol>
</p>
<h3>Where Do Files Go When I Check Them Out</h3>
<p>When you check out a file the pipeline tools make a copy of the production file for you to work on. This file is yours and you can edit it as you wish without worrying about messing up the production assets.</p>
<img src="images/screenshots/general-users-folder.png">
<p>Since they are part of the film they can be saved in the groups folder and it won't count against your quota!</p>
</div>
</div>
<div class="row" id="glossary">
<a id="glossary-anchor"></a>
<div class="twelve columns">
<h2>Glossary</h2>
<p>This glossary contains the definitions of these words as they fit into the the pipeline tools. So even if you know the words if might be good to review how the pipeline thinks about them.</p>
<ul>
<li>
<a id="accessory-def"></a>
Accessory: Objects that just sit in the set. These objects will likely not be animated.
</li>
<li>
<a id="animation-def"></a>
Animation: a shot level element. A Maya file that contains the animation of all the moving objects in a shot.
</li>
<li>
<a id="asset-def"></a>
Assets: assets are all of the props, accessories, sets, or characters that are in the film.
</li>
<li>
<a id="body-def"></a>
Body: bodies are just a shorter way to refer to both assets and shots. A shot is a body but not all bodies are shots; same for assets. You probably won't here about them outside of this documentation.
</li>
<li>
<a id="cfx-def"></a>
Character Effects (CFX): a shot level element. A Maya file that contains all of the character effects, (ie fur/hair, and cloth)
</li>
<li>
<a id="character-def"></a>
Characters: A person or creature in the film.
</li>
<li>
<a id="comp-def"></a>
Composition (comp): a shot level element. A Nuke File that puts together all of the render layers and helps to unify the shots.
</li>
<li>
<a id="designs-def"></a>
Designs: an asset level element. Any concept art that has been created for an asset. At the time of writing this documentation there is not really a way to bring designs formally into the pipeline so that they are managed by the pipeline tools.
</li>
<li>
<a id="fx-def"></a>
Effects (FX): a shot level element. A Houdini file that contains all of the effects sims for a shot.
</li>
<li>
<a id="element-def"></a>
Element: elements are the building blocks of bodies.
</li>
<li>
<a id="element-browser-def"></a>
Element Browser: a piece of software used to keep track of shots and assets. It never really got off the ground and typically we use a <a href="#element-browser-anchor">Google Sheet</a> to keep track of the progress of all the production bodies.
</li>
<li>
<a id="hda-def"></a>
Houdini Digital Asset (HDA): also called just digital asset. HDAs are the way that SideFX has created to make custom nodes for Houdini that can be shared by a production team.
</li>
<li>
<a id="layout-def"></a>
Layouts (Pre Vis): a shot level element. A Maya file that contains the basic poses for a character, the timing of the shot, the location and settings of the camera, the composition and layout of the shot, and how the shot transitions to the next shot.
</li>
<li>
<a id="lighting-def"></a>
Lighting: a shot level element. A Houdini file that contains all of the assets for a shot, has been lighted, and is ready to be rendered.
</li>
<li>
<a id="material-def"></a>
Materials: are the shaders that get assigned to the geometry. Typically the materials are built into the assembly instead of being it's own thing. However there still exists the old file structure for materials to be separate elements. Don't get confused about it. They are just going to be empty folders.
</li>
<li>
<a id="model-def"></a>
Models: an asset level element. A Maya file that contains all of the geometry for an asset.
</li>
<li>
<a id="prop-def"></a>
Prop: Objects that are used by character. These objects will likely be animated.
</li>
<li>
<a id="render-def"></a>
Renders: a shot level element. EXR files that are rendered images of each frame of the shot.
</li>
<li>
<a id="rig-def"></a>
Rigs: an asset level element. A Maya file that contains the rig from an asset.
</li>
<li>
<a id="set-def"></a>
Sets: Places in the film. These will be made up of props and accessories.
</li>
<li>
<a id="shot-def"></a>
Shots: shots are all of the animation, cinematography, composition, effects, etc in a continuous film sequence.
</li>
<li>
<a id="texture-def"></a>
Textures: an asset level element. A Mari file that has all of the painted layers of an asset. It could also refer to the exported tiff or tex files.
</li>
<li>
<a id="vis-dev-def"></a>
Visual Development (Vis Dev): see also <a href="#designs-def">Designs</a>. The process of making designs and developing the look and feel of the film.
</li>
</ul>
</div>
</div>
<!-- Section Template
<div class="row" id="blank">
<a id="blank-anchor"></a>
<div class="twelve columns">
<h2></h2>
<p></p>
</div>
</div>
-->
</div> <!--End Main Wrapper-->
<!-- End Document
–––––––––––––––––––––––––––––––––––––––––––––––––– -->
<div id="bottom-corner">
<a href="#">Back to the top</a>
</div>
</body>
</html>