how fix?

[BossZe]

[powroupi]

Well, I am curious how this error happened. :thinking: Please go to Blender's [Python Console] window (hotkey [Shift]+F4) and paste the result of the following commands:

>>> import mmd_tools
>>> mmd_tools.__file__
>>> len(mmd_tools.__bl_classes)
>>> import os
>>> [os.path.join(os.path.basename(r),n) for r,d,f in os.walk(os.path.dirname(mmd_tools.__file__)) for n in f if str(n).lower().endswith('py')]
>>> 

Or copy the commands and paste them in Blender's [Python Console] at once:

import mmd_tools
mmd_tools.__file__
len(mmd_tools.__bl_classes)
import os
[os.path.join(os.path.basename(r),n) for r,d,f in os.walk(os.path.dirname(mmd_tools.__file__)) for n in f if str(n).lower().endswith('py')]

[shankarsivarajan]

I had the same problem after upgrading to Blender 2.93. Uninstall the addon, delete the installed mmd_tools folder (probably ~\AppData\Roaming\Blender Foundation\Blender\2.93\scripts\addons\mmd_tools), and reinstall the latest version, NOT the release 0.7.0.

[broken-gage]

I had the same problem after upgrading to Blender 2.93. Uninstall the addon, delete the installed mmd_tools folder (probably ~\AppData\Roaming\Blender Foundation\Blender\2.93\scripts\addons\mmd_tools), and reinstall the latest version, NOT the release 0.7.0.

I got the same error. What do you mean by not the 0.7.0? Is there any newer version after 0.7.0?

[shankarsivarajan]

Download the current "dev_test" branch as .zip (Code > Download ZIP), extract it, zip the mmd_tools folder, and install that.

[powroupi]

For people who have issues when installing mmd_tools, please see issue powroupi#98 (or powroupi#91, powroupi#92). Sorry, I don't see any other possibility that cause the installation error. :cry:

[nagadomi]

I think the best way to avoid installation problems is to create an installable addon zip file.

If it is acceptable to make major changes to the repository, use git mv to change the directory hierarchy, making the mmd_tools directory the top-level directory. You can create a temporary repository or branch to test it.

Alternatively, one could use https://download-directory.github.io/ or something similar to have it download the mmd_tools subdirectory. If you have some experience in web programming, you can fork it and create a dedicated download website for mmd_tools.

Although it will take time period to get rid of the old mmd_tools installed environment.

[shankarsivarajan]

It would be far simpler to leave the repo as is and just include the installable .zip (i.e., just the mmd_tools folder zipped) with the releases.

[nagadomi]

I am guessing it is not done because it takes a lot of work to deploy a small commit.

Aside from that, an installable zip file can be created with the gitarchive command.

git archive --prefix mmd_tools/ -o ./mmd_tools.zip HEAD:mmd_tools

Also, releases can be created from the command line using the Github CLI.

gh release create <tag> [<files>...]

Document: https://cli.github.com/manual/gh_release_create

[SonicVegeta]

what about this then?

[powroupi]

@SonicVegeta, please see issue powroupi#253.

[BossZe]

Thanks everyone for helping is now fixed

Im try to Closed comments :)