Why does a content creator have to delete and replace the obj files that Poser saves for him?
The video shows that Poser is unable to save a properly grouped and welded obj file for you.
This brings a TON of problems for morph creation, rigging, fitting room transfer and morph transfer, because all verts at all welds have a double, and the groups are left unwelded.
The video also shows the two ways to get around the issue, and continue working with the correct obj file.
@anomalaus Thanks for enlightening me!
I take it that the meditational pause cannot be avoided, so I will live with it.
I also try to run a Poser instance as long as possible, but sometimes disfunctional area rendering or sudden translations in morphs created by the Morphing Tool make a restart necessary.
If you have a large runtime (s), start the indexing and let it run. Once it has indexed all, there is hardly any delay the next time you start Poser. It will only check ti see if there are any updates.
The initial indexing may take quite a long time if your runtime is very large (mine is 700GB), but the update check takes only a few minutes and is hardly noticable. Turn on the message log and you can see what is happening.