bug report for new branch version 1.5.1 and master

[engetudouiti]

So at current Master = try new things about morph importer (may cause un-expected things or show errors etc)

branch 1.5.1 = beta version of stable , which may fix error of stable version but not touch morph importer?

Do you hope user test and bug report about Master what you currently test, or you may hope user feed-back or bug-report about branch 1.5.1 main?

‌

[Alessandro Padovani]

For 1.6 I guess we have to wait until the new rig code is stable enough, and since it’s a major rewriting it will take some time. Then 1.5.1 is locked as for new features but serious bugs should be reported and fixed.

[Thomas Larsson]

Work on a new morph system is coming along nicely, but there are still too many obvious bugs that have to be crushed before a public release. I’m trying to implement both engetudouiti’s raw-fin properties and Xin’s non-python drivers (as an option) so it is a major change, but I think that the end result will be both much better and result in much less code.

[engetudouiti]

Thanks.. I only said about the raw and final value of (same as daz) property in the topic, I afraid if it bother you. \ anyway thanks to take time for those complex thing, at least if add on can make it work, I suppose maybe it can improt more daz morphs with keep ERC. (though I afraid if it cause new issue (performance) etc.. anyway I hope to test the way..)

I may report about Master, when you need test with many case.. at current I may report about 1.5,1 only when I found problem only.

‌