Tweet
Has anyone run into this before? Using max2016.
When I make a 3ds max archive/zip it fails with a vrmesh. As far as I can see everything is linked correctly and accessible. The character length of the file/location isn't over 256 either (113 to be precise). vrmeshes in the same location with similar naming work fine. I deleted the 1st one that gave the error and then it gave an error for another one in a different folder.
Deleted the vrmesh and now it gives an error for a jpg from a different object. The rest of the maps for the same object are fine, all in the same location, naming, ect.
*UPDATE*. Reloaded the map in the material editor and it worked again. Now stuck on another jpg.
*groans*
Is there a good script that can collect everything instead?
When I make a 3ds max archive/zip it fails with a vrmesh. As far as I can see everything is linked correctly and accessible. The character length of the file/location isn't over 256 either (113 to be precise). vrmeshes in the same location with similar naming work fine. I deleted the 1st one that gave the error and then it gave an error for another one in a different folder.
Deleted the vrmesh and now it gives an error for a jpg from a different object. The rest of the maps for the same object are fine, all in the same location, naming, ect.
*UPDATE*. Reloaded the map in the material editor and it worked again. Now stuck on another jpg.
*groans*
Is there a good script that can collect everything instead?
