-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shape keys are not driven by bones #19
Comments
I am not sure I understand you correctly, shape keys are vertex position or offset, they just add some value to corresponding vertices location. They don't follow bone movement IMO. |
Sorry for my bad explanation and/or my average English :-) At import, the mesh is properly tied to the armature, and I can also see all the corrective shape keys on the mesh, but they are not synchronized. The last time I used the addon, they were synchronized with a driver. Am I missing something? |
Hi, I think this is the same issue I reported - #14. I've come up with a set of fixes to one of the bridge files, so that shapekeys will be correctly applied as the figure is posed. You could try:
Details are in my issue report. I don't know if this will fix what you see, but it would be great if it does. |
Thanks @andy-m-github for your awesome answer and investigation. |
We currently know about both of these issues. And are working on fixing them. We will keep you posted when we got a fix for it. |
There's been a huge update for shape keys it still needs a lot of work but, take a look and let us know what you think :) |
With the basic genesis 8 female (I have also tried 8.1), the character seems to be imported properly but when posing it, the shape keys are not following.
![image](https://user-images.githubusercontent.com/8912998/109621948-dd3d4880-7b3b-11eb-8f3d-8c4d3cfabf9e.png)
As a result, the mesh is deformed only by bones and joints are that strange:
I really love the way importing a character into blender is easy with this bridge. Tell me if I can do anything to help!
The text was updated successfully, but these errors were encountered: