What happened to the MMD modules? I recently updated to version 1.80, and I was terribly surprised to find that it no longer loads the MMD modules, which my projects completely depend on.
Have I changed anything? Am I doing something wrong?
1 Like
Did you have a look at the migration guide? It shows the following for MMD modulesā¦
It does say āuntil r172ā, maybe it was put back to be re-introduced?
2 Likes
Just learned something. (migration guide)
When working with vite import three , is it considered making as a fork*of github?
Or the opposite āyou have time until r172 to migrate, afterwards it would be gone, so r172 would the last release with MMD loaderā
1 Like
Yeah I think youāre right, itās seems quite confusing in that case, what would make more sense isā¦
āThe MMD modules have been deprecated and will be removed in r172. Please migrate toā¦ā
The MMD modules donāt seem to exist in or after r172, does this break the ā10 revision deprecationā rule? 
GitHub - takahirox/three-mmd-loader looks like an empty repo also.
@ADI3DXP you could stay at r171 until the suggested repo above is updated, otherwise you could look into pulling all the MMD modules into a new separate repo yourself and and try to make the necessary changes to be compatible with the latest three.js
1 Like
The MMD code base was huge and we wanted to get rid of it as soon as possible. Hence, the shorter deprecation window.
The original author of MMDLoader has planned to maintain the files in a new third-party repository but it looks like he did not find the time to do so. In the meanwhile, developers that use MMD must move the loader code into their app.
3 Likes