Cage opened this issue on Dec 20, 2006 · 1232 posts
Cage posted Thu, 15 March 2007 at 3:55 PM
Hmm. Let's see. A few thoughts....
Mesh comparisons are run based on positions of the two selected actors in the 3D view window. They need to be "lined up" as well as possible. Some complex actors (like heads) may require several different comparison runs with various of the script's "screening" methods applied, and with the resulting datafiles merged at the end of the process. What you see in my last post is my own gradual effort to run through that process with two comparatively "easy" head actors.
After a comparison run, the script GUI refreshes itself, to prevent any subsequent actions from using the wrong datafile. If you compare one actor set, then try to transfer morphs between another set of actors, the datafile path needs to have changed or you'll have problems. I'm thinking about how I can adjust that process. In the meantime, after a comparison you need to re-select the same actor set and then select the desired morph before you can do a transfer run. It sounds like you may have done that, however.
20 seconds doesn't sound like a very significant comparison time. Between that and the error you encountered at the end, I would say either the meshes weren't lined up adequately to produce any valid data in the datafile, or there may have been some error with the actor selection and subsequent datafile handling. At the end of a morph transfer run, the script should still display the datafile path it used at the top of the GUI. If you browse to that path location, you can check to see if a datafile exists. Or you can make note of that location and try to select the appropriate datafile manually with the browse option. Or, in the "file" menu on the gui, there is an option to edit a datafile. If you open the datafile listed on the GUI using that edit option, you can check it to see if it contains any data.
It might help if you post a screen capture of the way you have your actors lined up. I think this is probably a simple problem, but with all of this still in development, it seems possible that you may have discovered some flaw in the process. Any more information you can give me might help me provide advice or a solution....
Also, I like Spanki's idea of sharing datafiles. They can be hard to set up. I'd like to create a page on my website where completed datafile sets can be posted for use by others. I'll put up my V1-V3 once it's done. If anyone else has any good datafiles, I will post them for everyone to use if you e-mail them to me. If we can build up a database of comparison files, perhaps this can offset some problems witht he script, like the fact that Mac users simply won't be able to use it to run comparisons....
===========================sigline======================================================
Cage can be an opinionated jerk who posts without thinking. He apologizes for this. He's honestly not trying to be a turkeyhead.
Cage had some freebies, compatible with Poser 11 and below. His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.