The MetaHuman EULA window popped up for me once but as I was in the wrong browser, I closed it. Now when I try to rig a metahuman in 5.6, now it wont let me accept it, therefore not letting me use metahumans.
I have tried:
Signing into a different account.
Creating a new project.
Signing in and out.
Restarting PC.
Clearing cache.
but nothing works.
output error log:
LogMetaHumanCharacterEditor: Error: Auto-Rigging of Face failed with code ‘Eula Not Accepted’
I had the same problem where it wouldn’t even try and open the browser after I failed to accept the first time. I fixed it by right-clicking the Metahuman Asset in the Content Browser and selecting “Remove Textures and Rigs”.
Hey there @Kiercn! Welcome to the community! I came to recommend the method Ruffhaus mentioned, as I’ve seen this work for another user. Let me know how it works for you!
Double check if MetaHuman Face Mesh Consent (v. 1) is there, if so, then I would suggest there is a data error (not sure what the solution is) but if it’s truly not there then maybe try completely removing the engine and reinstalling or installing it on another computer, if possible, and trying there.
I just managed to do it on my laptop and what you suggested worked. It let me accept the EULA and it lets me rig on my laptop on a fresh project. However, when I try rig (on the same epic account) on my PC and existing project, it still gives the the EULA not accepted error.
Interesting, the fact that it is now on your account as having signed the EULA proves that it’s some kind of hung up data somewhere, not sure if it’s tied to the engine install but I’d definitely try and do a complete removal and reinstall.
If you try on a new character do you get the same error?
Also not sure if anything from Metahuman is stored in there but you could try deleting your saved and intermediate folders in case it is something in there.
If neither of those things work, we are reaching the end of what help I can be unfortunately. Hopefully someone who has experienced something similar or with some deeper knowledge of the engine than me discovers the thread and can help you. You could also try asking in the pipeline and plugins channel you might get some better coverage there.
If something does work or you do manage to solve it somehow make sure you post the answer here so if someone comes across this down the line it may help them too.
Yeah, it’s the same error on any character. I’m starting to think maybe the only way it will work is if I make the character and rig it on my other machine and transfer it across maybe.
Who knows maybe with a hotfix or at latest maybe the next engine release it will just fix whatever is causing the error. There’s still always the chance someone will find this thread and point you in the right direction .