Using Relative (//file) paths, Make All Paths Relative doesn't work
How Relative paths work:




If you are working on COM 2
Your .blend file references paths on COM 2 relatively
If your same structure &amp; content then exists over on COM 1


THEN:

When you copy your updated reference content &amp; .blend from COM 2 over to COM 1, everything should work fine.



If what you are really doing is:

Working on a .blend over on COM 2, using all of your references from COM 1 as something like: //COM1/A/HDPE_Plastic_Texture_001.png

Then relative pathing will not work inherently.

To give you a sense of how you could get it to work, I will demonstrate a few use cases, and it should help you understand what you would need to do in your particular case.



Use Case #1 (The best case):


Your .blend exists at the root of COM 1


SOLUTION:

REPLACE: //COM1/A/HDPE_Plastic_Texture_001.png

WITH: ./A/HDPE_Plastic_Texture_001.png



Use Case #2:


Your .blend exists in a sub-folder of COM 1 - such as //COM1/B/myWorkingFile.blend


SOLUTION:

REPLACE: //COM1/A/HDPE_Plastic_Texture_001.png

WITH: ../A/HDPE_Plastic_Texture_001.png