mmdtools cant work in the blender 4.0

[Ray-lea]

when I import the models,it say:

[Ray-lea]

[nagadomi]

Blender 4.x breaks many compatibility. Many changes are needed to make mmd_tools work. (I don't know about 4.x support plans of mmd_tools.)

Here are some incompatibilities I have confirmed.

• Material Node Socket spec is changed (links.new(a, b) -> bpy_extras.node_utils.connect_socket(a, b), and more)
• Linear Colorspace is renamed (Image.colorspace_settings)
• Bone Layer is removed (new Bone Collection)

[1790374044]

see https://github.com/UuuNyaa/blender_mmd_uuunyaa_tools/issues/108#issuecomment-1781458613
The situation is similar. According to https://mmd-blender.fandom.com/wiki/MMD_Tools#Requirements , it may be difficult to support 4.x at this stage.
(Non-native English speaker, so the above content may contain grammatical errors（；´д｀）ゞ

[wikid24]

Python API Changes:

https://wiki.blender.org/wiki/Reference/Release_Notes/4.0/Python_API

[ghost]

https://wiki.blender.org/wiki/Reference/Release_Notes/4.0/Animation_Rigging/Bone_Collections_%26_Colors:_Upgrading

[UuuNyaa]

• 117

[Ray-lea]

Thanks for uuunyaa,the model import successfully,but there is still a lot of functions is not work,such as "convert to blender",there is lots of adaptive changes for blender V4 need to do.

[97lily]

First of all, I would like to mention that this is a comment because I am reporting the results of a trial run on a version that is not yet supported, and I am using LTS when creating my work.

Currently, the shape of the model is generally loaded, but the model is displayed as a pure white, probably because the paths such as textures cannot be referenced correctly (I tried running it experimentally with 4.0. )

If it helps, I can provide the error log when loading the basic model of mmd.

[nagadomi]

Not sure if this is related, all hidden materials are visible when loaded (Alpha is 1 in all mmd_shader nodes).

works fine with the following changes

diff --git a/mmd_tools/core/material.py b/mmd_tools/core/material.py
index c98a4a5..ffbf741 100644
--- a/mmd_tools/core/material.py
+++ b/mmd_tools/core/material.py
@@ -728,7 +728,7 @@ class _FnMaterialCycles(_FnMaterialBI):
             input_socket = shader.node_tree.interface.items_tree[name]
             if hasattr(input_socket, 'min_value'):
                 val = min(max(val, input_socket.min_value), input_socket.max_value)
-            input_socket.default_value = val
+            shader.inputs[name].default_value = val

     def __update_shader_nodes(self):
         mat = self.material

[UuuNyaa]

@97lily @nagadomi Thanks for the reports 😀 Node API is changing destructively. And I still don't understand it properly....

https://github.com/UuuNyaa/blender_mmd_tools/pull/117/commits/7ce9364c1039e9a834856c0de94be2a789233eb7

[emendez17]

how long mmd will be fix?

[UuuNyaa]

how long mmd will be fix?

According to MMD Tools support policy, only Blender LTS releases will be supported. So, we are developing MMD Tools to meet the Blender 4.3 LTS release milestone, targeting November 12, 2024.

[emendez17]

mmd tool not work!? I Don't know how long with blender will be done online?

[UuuNyaa]

mmd tool not work!? I Don't know how long with blender will be done online?

MMD Tools works on Blender 3.6 LTS. But MMD Tools does not work on Blender 4.0, 4.1 and 4.2. In the future, MMD Tools will work on Blender 4.3.

[UuuNyaa]

Blender 4.2 will be released on July 16, 2024 as the next LTS. So I plan to release MMD Tools for Blender 4.2 LTS on July 16, 2024.

see: Blender 4.2 LTS release milestone

[97lily]

@UuuNyaa There are still people who file issues without reading the explanation if it doesn't work on 4.0, (sadly like this https://github.com/UuuNyaa/blender_mmd_tools/issues/126) so it might be better to highlight it by writing something like (Releasethe module version [version of Blender that works]) like with other add-on release name. I think this is an unnecessary inconvenience, but I hope it will help reduce stress for developers.