Transfer Utility Problems
Questions to the transfer utility
- Exporting genesis 3, importing as a prop and using the transfer utility (mapping genesis 3 on itself) will not give a real good result; E.g. some vertices of upper/lower lip and upper/lower teeth receive the same weight map values and rotating the lower jar will then move vertices from the upper teeth producing distortion. Is there any way to let transfer utility handle this better?
- Genesis 3 expressions seem to not transfer because they are not morphs. Is there any other way to transfer these?
- Is there a solution to the 22% crash? E.g. if I use the transfer utility again on the transferred figure the utility will hang/crash and also on other occations it hangs at 22%, e.g. when I select to transfer morph sub components.
Thanks :)
Comments
What are you trying to achieve by rerigging an exported mesh? Transfer Utility isn't expected to be a final, fire-and-forget solution - it just gives a very good starting point. Bits of mesh thata re very close to two (or more) areas of influence are always going to be tricky.
The actual mesh I want to rig has a bit of locally modified geometry, the description above is for illustration. Richard, can you reproduce the 22% issue and tell the developers? Furthermore, clicking "use uv space" in the above scenario instantly crashes studio.
If you want only local modifications a GeoGraft may be an easier option, as it leaves the bulk of the figure unchanged.
I am not quite following the steps that trigger the crashing.
1. export g3m with subd 0 as obj.
2. import the obj
3. use transfer utility
A) check the "uv space" option, run utility => crash
B) run transfer utility with default settings => works. run transfer utility again, using the new figure as target (overwriting it) => utility hangs at 22%, studio has to be force-closed
C) run transfer utility, using copy morphs option (all or some favorites) and check the "sub components" option. => utility hangs at 22%
A) and B ii (rerun TU on rigged target) do not crash for me.
What versions of Daz Studio are you both running? Are you testing the same versions?
I was using 4.23.0.1 64 bit, the current General Release.
No crash on my side with the above operation, in DS 4.22 / 4.23, and the rigging result is good.
So, yes, what's your DS version ?
You are right. I think I found the root cause: the g3m I had used contained unused vertices. Removing those and all went fine. @Richard: Maybe transfer utility could display a warning that it cannot handle these.
If it is crashing then it would first ned to spot and handle the issue - if you still have the OBJ that triggers it please upload that with a Technical Support ticket so that the devs canm look at it.