I've just noticed something that I need some input on.
I recently took the time to conver all of my Onyx Trees to Proxy objects saved into individual MAX files for a more simplified merging process. It all seems to work pretty well except for the fact that the path to the mesh file is not as dynamic as other file types.
I learned this the hard way when I changed the name of the folders where I placed my vrmesh files, and then tried to merge in a Proxy Object that was referencing the orphaned location.
But it got me to thinking. What happens when I need to exchange files with a client with mapping conventions different from mine?
Isn't there a way to set up search paths like with bitmaps?
I hope this makes sense.
I recently took the time to conver all of my Onyx Trees to Proxy objects saved into individual MAX files for a more simplified merging process. It all seems to work pretty well except for the fact that the path to the mesh file is not as dynamic as other file types.
I learned this the hard way when I changed the name of the folders where I placed my vrmesh files, and then tried to merge in a Proxy Object that was referencing the orphaned location.
But it got me to thinking. What happens when I need to exchange files with a client with mapping conventions different from mine?
Isn't there a way to set up search paths like with bitmaps?
I hope this makes sense.
Comment