Packaging and Re-linking Assets
Using the Asset Tracking Utility and Packaging Scripts
This page is for those having issues with packaging 3DS Max scenes and those that are encountering the "More than one auxiliary named..." submission error in the Deadline Interface.
It is absolutely imperative that all files referenced by your scene are unique and have unique filenames. Please ensure that you DO NOT HAVE - Two identical assets that are in different locations. - Two different assets with the same filename.
Asset Tracking Primer
Asset management can be done through the 3DS Max Asset Tracking Utility [Shift + T]. You can refresh the asset list via File > Refresh.
Here you can manipulate the file location of any assets. A 'OK' or 'Found' status means the asset is mapped correctly.
Right Click any item to access important functions like setting a new file location or changing the file path.
Checking Assets
This section is for you to do on your Local Machine, and it is recommended that you check again once you have opened your scene on a Remote Citrix Machine.
Consolidating Assets
By scrolling through he Asset Tracking Utility, you will be able to identify identical assets located in different locations. In the example below, note that it is the same asset, but one is in the 3DS Max folder while the other is in the Downloads folder. This will cause errors for the render farm if not resolved.
Fixes
Identify file that you wish to relink. Right-Click > Set Path on the item and point it to the same file location as the other asset. Both assets should combine into one item.
This can be prevented by packaging the file in a more optimal way, refer to the next section on Packaging Files.
If you are doing this on a Remote Machine and ready to submit, ensure you [UPDATE Assets List] under Assets > Scene And Assets Files in Deadline
Dealing with Similar Filenames
By scrolling through he Asset Tracking Utility, you will be able to identify different assets that have the same filename. This can be hard to identify if you are using a lot of external assets so the Asset Tracking Utility is imperative for this. When working with the Render Farm, files are not case sensitive so the example below will cause errors.
Fixes
Simplify identify the offending files, note that you only need to rename one of them. Right-Click > Reveal in Explorer to on the item that you wish to rename, you will have to re-link this file, you cannot relink it through the Asset Tracking Utility as the filename itself has changed.
This can be prevented by packaging the file in a more optimal way, refer to the next section on Packaging Files.
If you are doing this on a Remote Machine and ready to submit, ensure you [UPDATE Assets List] under Assets > Scene And Assets Files in Deadline
Packaging Files
This section is for you to prepare on your Local Machine
If you do not package your file correctly, it can lead to errors such as mismatched textures and missing files.
You may use the methods in the Render File Preparation section on Packaging Files, but an automated way to ensure that there are no file clashes is to use a script.
There are many out there - as long as they include the following features:
We have tested Antomor's Asset Collector (Script Spot Link)
Install the script Navigate to the Utilities Panel > MAXScript > Run Script, locate the .mse file of the script and open it.
Add it to a tool bar first
Navigate to the Toolbars customiser via Customise > Customise User Interface > Toolbars.
Under Category, find Xirium.
Drag out the Collect Asset icon into your 3DS Max toolbar.
Use the Script Collect your assets and .max file to a directory, and then Set Path to ensure the paths get remapped. Follow the prompts to ensure duplicate files get renamed.
Zip up the Package Navigate to your newly created folder with a flat hierarchy for all your assets. Zip it up!
Missing Assets
This section is for when you have opened your file on a Remote Citrix Machine.
Removing Missing Assets
If you know that there are a series of broken links to assets and you are not using them, these assets should just be removed.
You should receive a prompt upon opening the file if there are missing Assets, [Remove All] will remove these assets so as to not cause any errors.
If you skipped past this alert dialogue you will be able to identify missing files in the Asset Tracking Utility. This is identified by the Status: File Missing and an empty path.
Remove Assets via Paths > Remove Missing Assets:
Remapping Missing Assets
Configure External File Paths
This utility can be accessed in two ways.
The first way is a prompt upon opening the file if there are missing Assets. Hit [Browse] to open up the Configure External File Paths utility.
The second way is through the Asset Tracking Utility, go through Paths > Configure User Paths and choose the External Files tab.
[Add] the path of your packaged folder. This should be a flat folder hierarchy if you have followed the previous section on Packaging Files. Otherwise, add any other file paths as necessary but if your assets are located in many different locations, it is easier to use the Asset Tracking Utility. See Remapping Individual Assets below.
In the Asset Tracking Utility, File>Refresh it to update the asset list, any assets in the newly added path should now have Status: Found.
Remapping Individual Assets
To remap individual assets, Right Click > Set Path and search for the file folder the asset should be located in. You can do this for a few assets at a time by Shift-Selecting as well.
V-Ray Assets
If you are using Assets from the V-Ray Assets Library, here are the limitations of the feature on the Render Farm that you should be wary of:
Work Locally
The V-Ray Asset Library cannot be accessed on the Remote Citrix Machines, but all files will work as intended. Please set up your file locally as you will not be able to make changes.
Check through the Asset Tracking Utility
Take note of the assets that you have used and double-check when you are on a Remote Citrix Machine through the Asset Tracking Utility. These assets should default to a 'asset\..' file-path and have Status: Found.
Encountering issues?
If you encounter any issues please see the troubleshooting section first. If your issue is not resolvable with the information provided here please log it with Stop1.
Please note that any issues with the Render Farm must be lodged via Stop1 for us to be able to process. Thank you for your help in establishing and making this new service more robust; We can only fix problems that we know about. So please log any issues you encounter with Stop1.
Last updated
