Best Practices for Managing Asset Versions and References in ShotGrid - Emmanuel Katto Uganda

Flow Production Tracking
1

Hello everyone,

My name is Emmanuel Katto. I’m currently working on a project in ShotGrid that involves numerous assets being developed across different departments (e.g., modeling, texturing, rigging). As the assets progress, we often find ourselves needing to manage multiple versions of assets and references effectively. I’m looking for advice on best practices to streamline this process.

  • How can we effectively manage asset dependencies? For instance, if a texture asset is updated, how should we ensure that all dependent models reference the latest version without breaking the link?
  • Is there a built-in feature in ShotGrid that allows for automatic updates of references when an asset version changes?
  • What are your strategies for documenting changes between asset versions? How do you ensure that team members are aware of significant updates or changes in asset specifications?

I appreciate any insights or tips from your experiences using ShotGrid.

Thank you!
Emmanuel Katto

2

Hi @emmanuelkatto

You can create parent and sub-asset hierarchies by use the provided fields in FPTK. This can help with variations and component asset tracking. But regarding reference tracking and pushing version changes into larger asset collections or environments (as an example) you might want to leverage something like USD which is designed to handle that level of usage.

3

Yes, the Breakdown and Breakdown2 Apps are designed for this purpose.

https://help.autodesk.com/view/SGDEV/ENU/?guid=SGD_pc_app_breakdown_html

1 Like