Page Comparison

...

The Library references set up here are project-level settings. They apply to all windows, and are saved with the project.

...

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. 

...

• 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.)

...

Alternately, the main resource library may be set up on a server. (Just add a path to the server in the Resource Manager.)