Am I correct in assuming that the Scene Breakdown app is not currently able to track loaded published files with local storages different to the default Project local storage? At our studio, we use a different storage for cache files under L:, while other project files are under M: drive. This is also reflected in the PublishedFile entities themselves, alembic cache publishes having their “Path Cache Storage” field set to a local storage that points to the L: drive, instead of the default M: drive.
At the moment, I cannot get the breakdown app to detect the following published file I’ve loaded in Nuke: ‘L:\shows\test\sequences\999-999\999-999-999\3D\publish\cameras\999-999-999_camera1_v002.abc’
However, it does detect the publish if it were saved under the default drive:
Is there no support for scene breakdown to track multiple storage publishes and if so - what’s the best way to go about modifying the breakdown hooks so that it does track publishes on different drives.
Any advice is much appreciated, thanks!