No metahumans are visible in “my metahuman” while launching through quixel bridge in unreal engine 5.2. Can anybody help me to resolve this?
Hey, @jobinmichael! Welcome to the forums!
Do you think you might be able to get us a bit more information? What have you done, what was your path up to this point? Did you follow a tutorial, etc.
Make sure you are signed into Quixel Bridge (separate sign-in from Unreal Engine on the top right of the plugin window)
Hi, Thanks for the reply.
I have followed the tutorial to make the metahuman from a model that I scupted in zbrush. Its available when we login to metahuman creator webpage. But once we open unreal engine 5.2 and login to quixel bridge, “my metahumans” tab is empty. (But 67 metahuman presets are available under “metahuman preset” tab.
Yes. we did, but bad luck
Hey Everyone,
If you are unable to see your MetaHumans in bridge, please ensure the bridge plugin is at the latest version (there will be an update available in the Epic Games launcher if it needs updating).
UE5.2 MetaHumans require Bridge version 2023.0.2 (which can be found in “About Bridge”
Hope that helps,
James
I have the same issue about MH doesn’t show up in my bridge plugin for UE 5.2.1, I’ve been do the same following suggest, unfortunetly it’s not solved yet.
Hey,
Can I just check you are selecting the UE5.2 drop down when using MetaHuman Creator? And also signed in to the same account in Bridge and Creator?
If that doesn’t sort it, I would try and uninstall Bridge plugin, and reinstall to engine.
I have a very similar issue in 5.3.2 with bridge 2023.0.5 (which is up to date). I don’t see “My Metahumans” at all, I only see the presets.
I was going to suggest all the restarting process but some people already mentioned it. Did you tryed to go back to Metahuman Creator, make a small adjustment and then return to check if it is avaiable?
Another point that already happened to me…more than one account lol
Yes, I already created a Metahuman in an account and then in the bridge I was logged in another account. When I discovered that this was the answer I felt so stupid hahaha
Hope that helps
Just open quixel bride inside UE5 and keep it open while you run metahuman on your browser just take a bit a of time, then just reopen bridge the one that is inside UE5 , its works for me, this just take a bit of time to refresh library
I was experiencing the same problem. My problem was that my UE version was 5.3 and I was opening MyMetahuman site in 5.4, on the first opening windows, I changed the version to match my UE version (5.3) . I reopened Quixel Bridege and my metahuman appeared!
I have the same issue. Latest bridge both app and in engine
There seems to be a broken metahuman asset in the creator that I can not delete which causes the issue. I think its tied to one of my account as other account seems to work
I now suddenly have exactly the same error and also a faulty, undeletable asset in MH. Since just now, I can no longer log in to QuixelBridge, and as soon as I open Quixel, the entire engine crashes.
Reinstalling Quixel did not help; the error only occurs for me in version 5.3 - 5.4 works perfectly fine.
I think it’s an error on the part of Quixel or MH.
I’m having the same problem, I can only see the Metahumans previously downloaded on the Local tab, but the new ones or an updated version can’t be seen on “My Metahumans” tab. And in the creator there is an undeletable asset that is causing an error. Anyone knows how to fix this?
Hey there, I found a fix hahaha.
This problem is caused by a broken asset in the Metahuman Creator, which leads to a series of errors between the different versions. I was trying to use my Metahuman on UE 5.2, but the current version is 5.4. So, what you need to do is go to Metahuman Creator and select the current version. Then, you’ll be able to see the affected asset. If you choose a previous version, you’ll get an error. After that, you will be able to delete the affected assets, and a few seconds later, you can update your Quixel Bridge. Then, the assets in your “My Metahuman” tab will appear. Hope this helps!
Thank you, that worked for me! Although I didn’t receive any error messages in 5.4, so i just randomly deleted some MHs that I no longer needed. Apparently, the faulty asset was among them, and now it works again. Thanks!