...
Resource Manager
The Resource Manager fixes broken links to files needed for your rendering, usually automatically.
...
There are a several situations where file paths to Maxwell resources may become invalid, resulting in 'file not found'-type errors when attempting to render:
When moving a formZ project between workstations
After relocating resources, such as MXMs or images, that a project relies upon
Attempting to use a collaborator's MXMs, which may contain file paths your OS cannot parse
Attempting to use an MXM downloaded from the internet, which contains file paths referring to the original creator's hard disk
The Solution:
The Resource Manager remedies all these situations. Simply set one or more paths to folders containing the missing resources, and when they are needed, the Resource Manager will search until the missing file is found. Search is recursive: If a folder contains subfolders, those will be searched as well.
Add Search Folder: Adds a folder to be searched.
Remove Search Folder: The reference to the folder is deleted. (The folder itself, and its content, remains untouched.)
Entries List
Use: Click in this column to enable or disable searching a particular folder.
Lock: The project-relative "Resources" search folder is locked by the plugin. It cannot not be deleted, but it may be disabled.
Downloads: Click to set the destination for materials downloaded from the online gallery.
Search
Folder PathFolder Path: The path to the folder.
mxm: Enable/disable searching for MXM files in search folder.
img: Enable/disable searching for bitmap images (jpg, tiff, etc.) in search folder.
ior: Enable/disable searching for complex IOR files in search folder.
hdr: Enable/disable searching for HDR and MXI files in search folder.
ies: Enable/disable searching for IES and LDT files in search folder.
mxs: Enable/disable searching for MXS files in search folder.
Search folders may be dragged to change the search order.
...
The locations where the Resource Manager will search for missing MXM, HDRI, IES, and MXS files, in order:
In a folder called 'Resources' in the same directory with your project. This project-relative path is refreshed when each render is started. Search is recursive (all sub-folders in 'Resources' will be searched for the missing file).
In each library (folder) as it appears in the Resource Manager list. Search is recursive (all sub-folders within the library will be searched for the missing file).
Only libraries that are active and are flagged as valid for the missing file type will be searched.
...
The locations where the Resource Manager will search for missing MXM dependencies (Bitmap textures, IORs, etc.), in order:
In the same folder with the MXM
In a subfolder in the same folder with the MXM called 'textures' (this folder search is not recursive).
In a folder called 'Resources' in the same directory with your project (e.g., this path is project-relative). Search is recursive (all sub-folders in 'Resources' will be searched for the missing file).
In each library (folder) as it appears in the Resource Manager list. Search is recursive (all sub-folders within the library will be searched for the missing file).
Only libraries that are active and are flagged as valid for the missing file type will be searched)
Paths to missing MXM dependencies are not corrected in the external MXM. Instead, a searchpath is added to the MXS when the scene is translated which tells the Maxwell render engine where to find the missing file.
| Info |
|---|
The 'Resources' project-relative folder reference may not be deleted, but it may be disabled. |
When files are still not located
If the file is not found at the existing path or an any libraries, an alert is issued, indicating that the Log should be checked for missing resources. To correct:
Check the Log and identify the file. It will be located just after the blue-highlighted ERROR lines.
If you know what library the file resides it, simply add a new search path to that library.
If you do not know, click on the Log entry with the filename. It will appear in copy-able form in the text box below the Log list. Select the filename here, then paste it into your preferred file-find utility and proceed to search. When found, move it to an existing library, or add a new library reference, as appropriate.
Using the Resource Manager Effectively
A Common (and Easy) Approach
Keep one general resource library on each computer, containing all your IES, MXMs, HDRs, etc. organized in folders as you see fit. This is where resources common to many projects can be kept and shared. Unless you have thousands of resources, it is not necessary to link one search folder to MXMs only, one to HDRs only, etc. In the screenshot above, adding a single path to a general assets folder called 'Modeling Resources' will suffice to fix everything.
Keep any project-specific resources in the project's 'Resources' folder. If you decide later that a something is best kept in the general search folder, just move it there; the path will be corrected on the next render (as long as there is a reference to that general search folder).
(Alternately, you could set paths to search folder designated for each project.)
Transferring projects between workstations
When moving to another workstation for the first time:
Copy your project, including it's 'Resources' folder.
Copy the contents of any other general resources folders that are in use. (If you want to copy only relevant resources, use the Workstation Transfer command.)
Add a search path to the general resources folder when you first open the project on the new workstation.
After that, you can freely move just the project (and its project-relative 'Resources' folder, if needed) back and forth between the two workstations, and all of your resources will be re-linked automatically. Do not delete paths to other machines, so these can be used to fix paths if the file is moved back in the future.
...