Automating Multi-actor morph loading would be higher on my list than Multi-actor comparisons (!).. simply because not everyone who might use this (suite of) scripts would have the knowledge/patience/know-how or even 'need' to use the front-end side to do comparisons (assuming good correlation files were available for download or purchase).  But pretty much anyone using the script(s) would be using them to transfer morphs.

I'm not sure what the issues are, but I suggested merging the info into one file because of the above.  It makes sense to keep all the data relative to a particular bodypart transfer in one file, rather than having to track down some other file that may or may not exist or may have had it's name changed or whatever.

No help on erlang code, sorry.

Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.