What is Published File Type for and how do I configure it?

When doing publishing with toolkit, I noticed that each publish is associated with a Published File Type:


How are these supposed to be used? Can I customize them? How would I go about organizing my data using different file types?

댓글 2개

  • 0
    Manne Öhrström

    As you may have already guessed, published File Types are used to group published file types together. You can configure them in any way you like based on how your pipeline is structured. 

    Toolkit Apps that create new publishes typically have an configuration option to set which Published File Type the publish should be associated with. For example, our Multi Publish App works like this – whenever you configure the multi publish app, you configure which File Type each publish should have. In our default configuration, Maya Asset Files will for example be of type Maya Scene and Photoshop files will be of type Photoshop Image.

    When you have types associated with your publishes, they are easy to group together. For example, when you want to load data into your scene, you can use our loader app. In the configuration, you can set it up to filter based on type, so you can create a loader app that only loads rigs, one that creates new shaders based on your selected textures etc. 

    You can use file types to group your data beyond just the extension: For example, it is useful that a publish is of type Tiff Image, but in a surfacing pipeline, it may be even more useful to categorize by content and not just by file format. In this case, it may be better to categorize published textures as Diffuse Texture, Specular Texture, Bump Texture etc. It is then easy to filter your textures not only by file type, but also by what the file actually contains.

    A recent thread on our shotgun-dev email list also contained several good production examples from our clients. Here are a few extracts:

    • We use the tanktype to differentiate between the filetype plus the pipeline step so an exr published from step matte becomes tank type "exr matte". The tank types become quite crucial in the loader app as they sort all by tank type

    • We use the software name that opens the file and the pipeline step where the file was created.


  • 0
    Sven Fraeys


    what if we are using published file type in a different way ?

    We tag all published files with as 'model' for all abc, ma, obj. 'texture' for all tifs, tga, ...

    This means that all geometry is grouped together as 'model'.

    With this setup is it still possible to use the loader system ? Since file types are mixed under a single published file type?

댓글을 남기려면 로그인하세요.