Hello, I’m sort of new to the engine and would like to import a metahuman from the ue 5.5 web app to the new integrated interface in 5.6. How would I go about doing this?
Hey there @derrick_og! Welcome to the community! I believe there was some documentation that updated recently for this, let me know how it goes!
Oh that looks painful! I’d be inclined to agree with you, if the migration guide isn’t working and producing artifacting like this, it may be better to just to try to manually recreate them. Though I wonder if the MH DNA could be read?
I’m now having that issue right now as well too on one my of metahuman character as I was migrating and import the previous character to the new metahuman creator plugin. And now I don’t know how to fix that either. And recreating manually ain’t really worth of doing all over again. Too much of a struggle and frustration for me
At this point I’m keeping 5.5 and 5.6 in their own folders (e.g. MetaHumans and MetaHumans55). So they don’t share or overwrite any assets. Because they don’t match.
The main issue I’m dealing with is clothes.
I’d just switch and focus on 5.6 except they don’t have any clothes. Existing clothes need to be adapted – with careful consideration to collar bone being different for different heads.
Epic has been announcing it as if there are already clothes on Fab, but practically speaking there are not. Most of them are not parametric for 5.6. Probably going to be unhappy customers finding that out. Not to mention the impractical prices.
That’s what I’ve come to so far, at least for what I’m working on.
same issues here. I’m also trying to renamte the OLD MH folder, but it takes years and doesnt find correctly the assets, also have a lot of cloths for them(no issue on adapting new cause I have the Marvelous Designer projects). This is going to be a huge mess if cannot have both on diffiferent folders.
Tried using it with the migration action as well, got the exact same deformation
in BP LOD sync LOD 4 will fix it I guess
Anyone able to fix this? Been chasing AI-recommended fixes, but nothing has helped so far.
Forcing a higher than 3 LOD works, but it’s not really a solution since you lose a lot of quality.
So for anyone who is still having this issue, I may have fixed it, at least it did in my case…so far.
When you “Import and Migrate” a 5.5 meta via Quixel it creates the legacy assets including Blueprint etc like it always has, IN ADDITION to creating the new Creator asset. Delete all assets except the new 5.6 Creator asset and restart. Then open the creator asset and under the “Body” category, there is an option to convert it to Parametric. Then you can rig and assemble it etc and you should be good to go.
Basically, my theory was that it’s not using the new meta framework as there’s already a blueprint from the import, and that’s what was causing these weird issues. So deleting everything and forcing it to rebuild from scratch resolves any version conflicts.
I only tested this on 1 character so far so it’s anecdotal but worth posting here.