An amusing work around for the time being is as follows. (It's CRUDE!)
o Make a list of where you are keeping your materials for a given .3DS.
o Make a 'dummy' 3DS.set (I do this in its own directory, of course)
and in the file, have only one line;
MAP-PATH= <name the path you want to search>
o Run PACK3DS on your file. It will compress only what it finds.
o Now edit the dummy 3DS.SET file and point to another one of your
directorys. (repeat for all the directories)
Like I said this is crude but it get's the job done. If you keep your maps
in regular directories, you could make a batch file to automate this.
Jamie
Jamie,
Ahah! So pack3ds looks at the first entry in the map-paths in 3ds.set. OK,
I could definetly see how your workaround would work. I could also see how
the routine could be altered quite easily to check all the map-paths in the
first place. Maybe, when I make registered developer status (Chris Allis is
sending out the forms) they'll give me the source code and I could have a
crack at it….
Martin