Now you can use tokens and relative paths when setting up the destination for your rendered files. This means you can set up a consistent file name template that works from project to project without the need to manually change the render path. It also means you can now place each pass in its own subdirectory and give object buffers a descriptive name. Tokens appear within your path as a special string that starts with a dollar sign and the string is replaced with the data that the token represents. You can easily add tokens using the pop-up to the right of the file name and there's options to use the current camera, the current frame, the pass name, the take, the frame range, frame rate, project name, render settings and resolution. So I'll just click to add the project name to the end of my path. In my folder structure, there's a renders folder beside the folder that contains all of the C4D files, and I wanna get all of my files into this directory. And so, I'm using relative paths here, the ../ actually moves me up into that main parent directory and then I can go back down into the renders directory from there. And I'm gonna name my file based on the take name and the project name. And because the project name changes each time I save incrementally, I'll always know which version of the project was rendered. Now let's take a look at the multi-pass path, here I'm going into the same renders folder and I've got $take_$prj, but I wanna actually make that a directory so I'm gonna add a slash at the end. And this is where it gets really cool, next I'm gonna $userpass token which I can add by going into the pop-up here and choosing current pass name user defined. And you'll notice there's both a current pass name and a user defined pass name, and this user defined pass name is the really cool one because it actually allows me to use a custom pass name that I've defined over here. So here you can see I've got a whole bunch of object buffers that I've already created and I might just go ahead and create an additional one and I want that to be group ID one and then I'm just gonna double-click to rename this Trails. And I can reorder these however I want I'll just put that up at the top and now each of these object buffers will be named in the actual file name. Now I'm gonna go a step further and make that a subdirectory. So I'm going to put another slash after that and now I'm going to go ahead and put the name that I want for my file. And here again I'm gonna use the $take and an underscore and then the $prj name. So once you're familiar with the tokens, you can just simply type them directly into the file path as well. You don't have to use the pop-up to add them. Now one special thing down here I'm not using a multi-layered file because I want separate files for each of my passes and I've disabled layer name as suffix. Instead I'm using the user-defined layer name, which is the custom layer name I set here so it's actually going to be added into this file name as well as the take and the project. So let's go ahead and hit render and see how that looks in our file structure. Now we'll jump back into that renders folder. Here you can see that we've got our regular image which is named based on the take name and the project file name and then the frame number as normal and then I've got a folder for the take name and the project name and this is where all of my passes are located. And here you can see I've got an individual folder for each of my passes. So I can jump in here to the trails pass and there I have my object buffer, named trails, for specifically the trails pass. So this becomes really important when you've got all of your frames rendered and you're turning a folder that's got tons and tons of individual files into a much more organized hierarchy. So that's one example, let's take a look at another. In our pipeline, we actually deliver dailies each day and we put them in a folder that's up a couple of levels from where our C4D files are, so we're going up to shots and then from there up to the main project folder. And then we go back down into deliverables and then dailies. And then under there we've got the folder for each date and then we place any dailies for that day in the folder. So back in Cinema 4D, I've got a child render setting set up the renders all frames with the hardware render so I can get a quick daily render and I've set up a save path here where I'm using .. / several times to get back up to that mean parent folder and then going back down into the deliverables folder and then the dailies folder. But here's where we run into a little bit of a snag. We actually need to be able to generate the date and that's not a built-in token but the great thing is is that tokens is extensible via Cinema 4D API. So this lets you add more tokens to fit your own pipeline. So I've already started a plugin that we're going to distribute here on Cineversity called CV tokens that creates some of these additional tokens for us. And we'll go ahead and drop that into the plugins folder and restart Cinema 4D. And we're gonna reopen that file that we were working with. So now you can see that in the drop down, here, we've got some additional options, we can get the OS computer name as well as the OS username, the author name that's specified in the project settings as well as the day, month two digit year and four digit year. And by the time you download this plugin, there maybe additional tokens as well. But you see that now what I can do is generate this custom string based on the current day. And so now, I'll go ahead and fire off this render and that's going to start that hardware render and I'll jump into the project folder again and here you can see that we have a new folder for today's date and we also have our file and it's named based on the current project file name, the current take name and my initials which I placed in the author field of the project settings. Now you'll probably want default file name templates like this to be a part of every file that you create, and there's a couple of different ways to set that up. The easiest is to use a new. C4D file. So if I copy this under setting and create a new scene file and simply paste it once again into the render settings and I wanna clean this up to remove anything that seems specific like all of my individual pass names and also the global illumination and lens distortion. And then what I'll do is save this as a file on my desktop called new. C4D. Then what you want to do is go ahead and open your preferences folder using the open preferences folder button, and we'll go back to the desktop and copy new. C4D into the preferences. And now, each time you create a new scene file, you can see that that save path is going to be inserted by default. Now if you want a little bit more flexibility and additional file name templates, the other thing that you can do is create a new render setting and go in here and just copy the items that you want to change in a render preset. So we're going to take our file name template here and we'll go ahead and take multi-pass as well and take the file name template for that. And now what I'm going to do is select that new render setting and I'm going to go down here and choose Save Difference Preset. And here in the name dialog we're gonna type Fn-RenderFolder as a name for this specific preset. This stores a preset in the content browser that you can easily apply to any render setting by choosing the apply difference preset option. And this is nice because it provide a you the flexibility to have multiple different templates for different types of projects. So now whether you work in a big studio or a team of one, you've got a really flexible system to organize your rendered files.