-
Notifications
You must be signed in to change notification settings - Fork 35
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
Blender4.X-UPBGE_mmd-uuunyaa-tools_ERROR&FIX #117
Comments
I now understand the issue for 4.X blender. X3 Go into the armatures.py, edit Line 333 "BoneGroup" to "BoneCollections", Line 334&334 "bone_groups" to "bone_collections", then save the py, try to re-enable the plugin, and now it should work properly again. :3 |
Thank you for the report 😀 MMD UuuNyaa Tool's Blender version support policy is as follows: By the way, we need MMD Tools to support Blender 4.x first. And it is in progress with the following pull request: |
The above wiki link about v4.x upgrading is dead. Refer to this if needed https://developer.blender.org/docs/release_notes/4.0/upgrading/bone_collections/ |
The above fix only fixes the type hint error, which is a syntax check error before runtime. So in fact renaming pose.bone_groups to pose.bone_collections may produce errors. Initialization doesn't check this so I'm not sure about it. Another thing for v4.2 users. For marketplace "mmd_tools" installs, the module name is now "bl_ext.blender_org.mmd_tools" instead of "mmd_tools". Edit |
Hi, I'm using Blender's Game engine 4.1. :3
After doing the tutorial to the T, it still gave meh an error. X3
Before activating it:
After attempt to activate it:
(Updated 2023)
So I officially fixed dat by doing dis:
Renaming ""BoneGroup" to "BoneCollections" and "bone_groups" to "bone_collections", seem to have fixed the problem.
And TADA, just remember dat "mmd_tools" haz 2 be enabled first, save preferences, quit blender, launch blender again, open preferences again, add-ons section, search ""mmd", then enable "mmd_uuunyaa_tools", then save preferences, quite blender again, and now open blender again and U should be all set to go. :3
(U don't actually have to restart blender, although it's good practice to do so, dat way no conflicts will happen. ^w^
I even restart my computer after every update or GPU driver installation. X3 )
I hope that helps a few people out. X3
The text was updated successfully, but these errors were encountered: