Quixel Help Center home page

Metahuman UE5 upgrade warning not going away

Answered

Comments

8 comments

  • Laila Shahzad

    Hi LostHarbinger42, thanks for posting! 

    For Unreal Engine 5, go to the Quixel Bridge plugin inside the editor and log in using your Epic Games account. In the left navigation panel, go to MetaHumans. From here, you can download pre-made characters from the MetaHuman Presets view or a MetaHuman that you created from My MetaHumans view.

    Please note: Re-adding or overwriting an existing character in project is not supported. You may attempt to manually place it in the project folder.

    Please do not attempt to import UE4 characters in a project containing UE5 MetaHumans as it may result in unexpected issues.

    Looking forward to your update!

    0
    Comment actions Permalink
  • Nino Mancuso

    A follow onto this question, thank you for your time. I also upgraded my ue4 project to ue5. It already contained metahumans, and they are being utilized in sequences with animations, etc. 

    What is the appropriate way to swap these ue4 metahuman versions for the ones in ue5 bridge (Most were simply stock metahumans not custom). Do I download all the ue5 replacements and ignore the error, then delete the ue4 metahumans?
    thank you

    1
    Comment actions Permalink
  • Nino Mancuso

    For example it says " to continue importing this metahuman, please close the project and copy the following files from: "

    but then it doesnt say where

    0
    Comment actions Permalink
  • Ian - Product Support Specialist

    Hi Nino Mancuso,

    When using non-custom MetaHumans, you could delete and re-download the UE5 versions. Unless you're doing something specific, you shouldn't have to move files around on the back end of your project.

    If you have custom MetaHumans or need an exact MetaHuman from your UE4 project to be set up in UE5, you can launch the UE4 project and migrate the MetaHuman folder into the Content folder of your UE5 project.

    I'd recommend creating a clone of your projects before performing any transfers, just in case. However, if you encounter any issues with either of the above-listed workflows, please let me know, and I'd be happy to be of further assistance!

    0
    Comment actions Permalink
  • Dale Darling

    Hi guys,

    I have the same issue as the OP and as Nino Mancuso. Unlike LostHarbinger42, it is not just a nuisance for me - I can't see the instructions on the dialog telling me where to copy the files, because the dialog wasn't designed to show more than a few names (and I have 12 metahumans in my project). I tried creating a new project and migrating my metahumans but Unreal Engine crashed partway through the asset migration every time.

    I posted on the Unreal Engine forums but nobody has responded. 

    Ian - Product Support Specialist if you could escalate these issues with Epic, it would be really appreciated:

    - The dialog that warns about not being able to mix UE5 and UE4 Metahumans needs to support an arbitrary number of names. Preferably it would have a scroll bar, or at least be resizable, so those who have more than a few metahumans can actually see the instructions in that dialog. I had 12 Metahumans in my project, and thanks to the dialog layout, the instructions telling me which files to copy and where to copy them were off the bottom of the dialog so I couldn't actually see them. 
    - Migrating Metahumans from one engine version to a newer one should be fully supported. I created a large number of Sequences using UE4 Metahumans. Then UE5 came out along with the newer version of Metahuman, and the UI on the website strongly encouraged me to switch to the newer version of Metahuman, so I did. As soon as I did, I could no longer import updates of my Metahumans or any new Metahumans into my project (even after updating my project from UE4 to UE5). And thanks to that dialog issue, I couldn't even read how to manually copy the files (tho it seems that the OP attempted to follow the instructions and they didn't work). 

    In the end, I created a brand new UE5 project, imported my new Metahumans to it, then manually redid all the customizations to their blueprints I had done in the UE4 project... then I migrated the levels and other assets to the new project. I just abandoned the sequences I already created since I saw no way of migrating them given that the Metahumans they referenced were the old UE4 ones. Luckily for me, these sequences are all promotional material and not essential to the final product...

    But if Metahuman and/or UE updates in a breaking way again in the future, then I may be in a lot of trouble. I can only imagine many indy and pro developers and cinematographers are in a similar position. It would be amazing if Epic prioritized backwards compatibility and robust migration support in future updates!

    1
    Comment actions Permalink
  • Nino Mancuso

    I’ve just keep in mind (to get me through the frustrations) Ue is a free program and going thru massive changes constantly. It’s marginally acceptable for production at the moment in my humble opinion, and I learned never to switch versions mid project ever

    0
    Comment actions Permalink
  • Dale Darling

    All good points Nino. I will definitely be cautious when upgrading in the future! I didn't mean to come across as negative - just hoping to add some constructive feedback with context. Hopefully your project is going well!

    1
    Comment actions Permalink
  • Nino Mancuso

    My friend, believe me, I am completely sympathetic!!!

    0
    Comment actions Permalink

Please sign in to leave a comment.