adp001 opened this issue on Nov 28, 2020 ยท 39 posts
odf posted Sun, 12 September 2021 at 8:17 PM
adp001 posted at 8:11PM Sun, 12 September 2021 - #4427273
odf posted at 7:11PM Sun, 12 September 2021 - #4427269
Okay, turns out the only thing I really needed to change (on Poser 12.0.500) was the
import wxPreparein WXTools.py toimport local_libs.wxPrepare.Ups! Yes, Python 12 has different import logic. But I thought I catched that.... Thanks for finding that out! Will change it tomorrow.
When loading the script I get an error complaining about a checkbox event with no object that I ignore, then the GUI for the tool appears and I only have to move it to a spot where I can see everything.
Problem is that if an error is generated while wxPython is active, Poser Python often can't recover. Silly things may happen then :)
Just checking obj for None before trying to access its name field got rid of that error.
I have now managed to import a morph from an OBJ file using the tool. Do I understand correctly that I have to export the unmorphed figure each time directly before I import a new morph? Why is that necessary? I'm assuming some weirdness of the Poser interface?
No. One export at the start of a session. Pre-morphed or posed. Exports are the Reference used in the modeller. What you add or subtract to this reference is your imported morph. It's late here in germany and I'm pretty tired. I think I do something like a manual the next days (online and "realtime", but in German).
The gist of it (in technical terms) is:
morph = numpy.array(imported_vertices) - numpy.array(exported_vertices)
Okay, that's making more sense to me now. It might be useful to make that more explicit in the interface. Maybe separate between reference and regular exports, display the file name of the reference export for the current figure, and if none exists either refuse to import morphs, issue a warning, or automatically create one.
-- I'm not mad at you, just Westphalian.