Recently it was announced that we need to update our top five ugc dynamic heads with a new head cages to comply with the makeup update. I have no problem doing this but the errors and issues I’ve gone through with unseen hope have been overwhelming
The main error I’ve encountered is:
“Dynamic Heads on the marketplace must be setup to properly animate the core facial movements, but our detection did not notice a substantial change.”
At first glance, this error makes it seem like the issue is related to FACS controls. I spent days trying to figure it out, but it turned out to be caused by the cage not properly fitting over the eyes and mouth.
So far, I’ve updated three heads and at first glance they appear as though they should validate but 2 out of the 3 still fail. How exactly does the validation for landmark projection work? Does it only read from a front view of the head? What about bundles with eyes on the sides of their heads, like most animals? If a head includes all 17 required facs controls and has a properly fitted cage surrounding the eyes and mouth, what else could still require changes?
I’ve noticed a pattern that the new validation may primarily be tested on humanoid heads rather than heads in all shapes and forms, I’m happy to send any of my bundles for review to help make the system better!
To be honest, I would have really appreciated more detailed errors before launching a campaign requiring all top 5 heads to be updated or it being removed from players inventories. My top five ugc bundles are currently at stake because of this issue
Expected behavior
I expect it to give us an error description explaining what actually needs to be changed, instead of repeating the message: ‘Dynamic Heads on the marketplace must be setup to properly animate the core facial movements, but our detection did not notice a substantial change.’
I would also like a revamped validation system that supports multiple types of heads in all shapes and forms.
I agree with this, the current system only allows you to make humanoids, if your head doesn’t have a mouth or has a small one then your screwed, they need to allow for it to have support for models without mouths or with only one eye etc, some of my best selling heads don’t have mouths.
Also going running into the same issue. The validation is extremely inconsistent and doesn’t give you any information about the root of the problem. I was able to make two bundles pass through the validation, but later today after a few adjustments on one of them, it simply stopped passing through the validation once again. None of them were humanoid, so that probably means that this validation is very biased.
Yes, at the very least we need numbers with any validation error so that we know if any changes we make are going in the right direction. Otherwise it’s just a frustrating loop of importing and hoping the error disappears, with no feedback on why it has or hasn’t.
I’m not surprised, but disappointed this is even an issue to begin with. The error itself doesn’t even specify anything whether it is an issue with the eye or mouth area + how much more movement it needs in order to validate..
On a side being able to make dynamic heads with no mouth, but movable eyes would be better for a good chunk of faces out on the catalog and i dont know why roblox just won’t do that since that still allows expression
HOWEVER, there is no feedback in the validator to which Action Unit Test is incorrect / doesn’t pass the threshold.
Just a horrible game of feeding a black box algorithm some values that you think are right, and then you get a Yes/No, with no further help.
This is a complete regression from how the validator used to work in the past.
Even using the built in tool for making bundles (Auto Avatar Setup) does not work anymore.
The cherry on top is that it applies retro-actively to already existing bundles, as mentioned in the post title
Roblox really needs to take their time releasing updates that don’t have cracks in the wall.
They can make whatever updates they want since it’s their platform, but they can at least eliminate so much stress by releasing a new validation system with specific error messages that states what’s not being tracked enough rather than just saying that the dynamic head didn’t receive substantial change.
I thought I figured it out with my latest GD head I made by making the head outer cage as aligned to the head mesh as much as possible and it worked.
but when I tried again with a more sinister head, I could never get it passed that infamous new error.
It’s messing us up big time, on top of the fact we need to update our heads that were uploaded before this update mess…
I agree that this new validation system is terrible. I can’t get anything to validate and I feel like more than 90% of the bundles and heads on the catalog don’t even pass this new validation system, so everyone is pretty much at risk. It’s counter intuitive to have dynamic heads this limiting.. It inspires zero creative liberty.
has anyone figured anything out or got some help from the roblox support? what are we supposed to do for bundles that have indistinctive mouths? literally crashing out here
The default blocky rig FAC rig in the resources page doesn’t validate either which is hilarious and horrifying at the same time. That comes to show how broken the validation actually is
Hi, we are going to release more detailed information on which expression(s) fails the validation later this week (eye close, mouth open, smile or frown). With that, we should also be able to fix a bug which could cause false negative validation results when PBR is enabled.
We are also working on visualization of landmarks but that is part of a bigger project to visualize all validation issues, not just the head, so it may take longer.
Thanks for the reply! I’m guessing the landmark visualization project is related to the issue with eyes being on the sides of the head? Do you think this will be rolled out before March 27th?
The dino you see in the post is one of the top 5 heads I’ll need to change before that deadline. However, without the validator being able to indicate eye placement it would be impossible for me to validate it. Would it be possible to extend the timeframe until the validator is actually fully ready for use?
This is honestly my main issue. Since today, I’ve gotten the hang of it and have been able to get some of the heads approved that have eyes on the front and not on the side of the head
Hi, I think the eye on the side is not an issue as long as the cage eye area are also on the side and can be projected properly. We have seen many published assets having eyes on the side and passing validation.
The visualization is not related to any specific types of head and it will not be ready by March 27. Sorry about that.
As you see on the picture the landmarks can be projected from the cage cause on the front view ur still able see them even though they have eyes on the sides of their heads. But even with this, if we move our camera over to the eyes itself (what the validator doesnt see) you’ll see the complications this will have for people that will equip their makeup in the near future
Closeup eye:
This validates my point even more of the validator only scanning the front of the face, this would never been validated if it werent from the front only view. So with this in the back of our mind if we look at the dino head right now this is what the validator would see
You’ll see that my dino has the cage perfectly surrounding the eyes like asked from you guys on the documentary, its just the validator not been able to pick it up cause from their view it looks like 2 landmarks are covering eachother guaranteeing an automatic error trying to validate it.
If you guys send us an email wanting to change our heads before the 27th march, but the validator clearly not being ready yet even though we have a perfect cage surrounding eyes and mouth what else do you guys want us to do? It’s been extremely frustrating to figure this all out, let alone having the pressure of needing the fix with a validation design that does not work properly
All im asking is to either shift the deadline or have the validator work on front and side view, thats why I was willing to send over my file to have this issue fixed.
Hi, thank you for sharing the images. The landmark projection has nothing to do with the camera angle or where the eyes are. It simply tries to find closest point on the head.
In your dino model, if I understand correctly the eye ball mesh is going to be smaller for eye close expression. If that is the case, then you will have to make sure the landmarks can be projected onto the eye ball instead of the head mesh, because the head mesh is not animating, the eye ball is. So we would expect to see landmarks like the image below.
In another example, if your mesh has eye lid and it is the eye lid that is animating for eye close, then you will need to make sure the landmarks are projected to the eye lid instead of the eye ball. Fundamentally, the landmarks should be landed to wherever things are animated/deformed. Simply making the cage around the eye may not suit your purpose. Hope this info would be helpful.