How to fix MMD models? How can I troubleshoot MMD models? How can get help with an MMD model? How can I contact LearnMMD for help?
How to Troubleshoot MMD Models
If you ever try to make a model, there’s going to be a time when you run headlong into a wall. Something isn’t going to work right. Guess what? There was a time when none of the LearnMMD authors knew how to do anything with MMD. Just like everyone!
It’s easy to believe that we all know how to think well. After all, like walking, we spend all of our lives doing it. But just like you’re going to need a coach to run at a competitive level, there are a few tricks you can learn to troubleshoot MMD models. And they’re the same tricks you can use to improve your thinking about fixing anything else.
When you do run into a problem, there are four techniques you should use to get through it:
- … and Waiting
Let me Google that for you. You want to get to the solution as quickly as possible, don’t you? Luckily for you, there are seven billion other people, and the odds are pretty good that one of them has run into the same issue as you. Maybe they’ve already described what you need to troubleshoot MMD models!
Just like anything else, searching the web is a skill that you can improve. Googling MMD pictures don’t match isn’t going to give useful results. It’s too vague. Googling MMD texture seams normals is much better, assuming that the problem has something to do with sharp edges in textures and something to do with normals.
The key to Google-Fu is vocabulary. Luckily, it’s not too hard to improve your vocabulary. All it takes is reading. Here, let me Google that for you!
Searching isn’t robotic. It’s empathic and imaginative. Try to think about what words somebody would use if they were answering your question. Imagine being an expert on 3D modelling. Put yourselves in their shoes. What would they say? It’s not necessarily what you would say.
Videos vs Text
I saw a Youtube video tutorial for MMD that said it had a new technique for PMXE that would simplify weight painting. It was ten minutes long. The technique was introduced about five minutes in. And I already knew the technique.
If that video was text instead, I could have figured it out in under a minute. In the time it took me to discover that video wasn’t useful, I could have read about five different techniques.
That’s why I almost always prefer text to videos. Whenever I can choose between a text tutorial or a video tutorial, I always choose the text. That way, I can learn five times as much in the same time!
Even if you find it difficult to read, or perhaps just difficult to read English, consider text tutorials as an investment. The more that you read, the easier it will get.
Tutorials with pictures are even better than text. They’re not like videos, because you can skip around easily and quickly. And pictures are great for finding your way through tricky interfaces.
That doesn’t mean don’t look at videos. It just means use them as a last resort, after you’ve already checked the text tutorials.
When you Google, don’t expect the answer to be the first link Google provides. Don’t even expect it to be on the first page. Look at a lot of different pages. For my searches, I usually look at four or five different sources over the first three pages of results.
Google didn’t help? That happens. For every solved problem, somebody solved it first without any help from Google. Your problem might be like that. You need to experiment to troubleshoot MMD models.
Experimentation is just focused play. It’s like being a toddler again, seeing which blocks go through which holes. It can be directed or aimless or anything between. But when you have a problem, you want to pick at it from as many different angles as you can.
When Galileo tested gravity, he didn’t compare a feather to an anvil. He didn’t drop one weight from his rooftop and one from the Empire State Building. Because he wanted to reduce the number of variables. So he simplified.
And that’s the first thing that you should do with any problem. How can you simplify it? How many parts of your model can you remove before the problem goes away? For example, does your model need physics? Delete all joints and bodies and see if that fixes the problem. Do you have a bone problem? Try deleting other bones and seeing how they affect your problem. Delete delete delete! (Just don’t forget to back up your model first.)
Reproduce– and fail to reproduce
Can you reliably recreate the problem? If not, there might not be any problem at all! If nobody else can reproduce the problem, they’re going to have a hard time fixing it– or if they do, they won’t even know that they did.
So start fresh. Restart your computer. If you downloaded a model, delete it, and download it fresh. Whatever your problem, see if it happens when you do the same thing the second time. I know, there’s that popular definition of insanity. That definition ignores the fact that the definition of science is also doing the same thing, multiple times, with an open mind about getting different results.
Then, look for situations where the problem doesn’t reproduce. That’s going to be key to figuring out what’s happening. If you’re having trouble loading a pose with a model– try it on a different model. Try it on a modified model. Try it in MMM instead of MMD. Try it in as many different ways as possible. Do you have a different computer? Try it on a different computer!
When you can both reproduce the problem with one set of steps, and fail to reproduce it with another set of steps, start blending those steps to identify exactly which steps are associated with the problem.
One of the most important things to do to troubleshoot MMD models is to look at it from different perspectives. I’m not talking about rotating the model (although sometimes that’s enough!)
When I get stuck on a problem, I know there are a lot of different ways to investigate the problem. I can look at a morph in MMD. I can look at in the PMXE transform window. And I can look at the morph’s detailed data on the PMXE tabbed view.
But another thing I can do is export the morph to a .csv file and look at that in Excel or a text editor. Recently, doing exactly that helped me solve one user’s problem, by showing me parts of the morph that weren’t apparent even in PMXE.
And there are other ways to look at things. Different display modes in PMXE can show me a lot of problems. I open models up in Blender sometimes. I can create custom effects to make visual defects plain (like by displaying normals, and enhancing contrast). KillerBeer recently solved a problem by looking at a pose file in a text editor. Each of these are different perspectives we can take on problems, depending on where our skills lay.
Another set of eyes
We all make dumb mistakes. We all get stuck with tunnel vision. Sometimes, it just takes a different person to help us notice. There’s no shame in making those dumb mistakes, only shame in being too stubborn to admit them.
If you have any friends that make models or use MMD, those friends are great resources for dealing with problems. Invite them over to take a look. If you’re part of any MMD communities, see if you can post a model file someplace for people to help, or send a private message to one of the members asking if they’d take a look.
Of course, if you want to keep your friends, be a good friend yourself. When it comes to fixing problems, that means putting effort into fixing the problem first, before you ask for help.
Another set of 両目
You don’t always need a friend to get another set of eyes. Whenever you download a model, you’re getting a fresh set! One of the best ways to learn about any problem is to open up a similar model, one that you know works, and see how the modeller solved the problem for that model. Trace out the way that a good model works, by opening it up and examining it in detail, and you should be able to learn enough to deal with your own problem.
“I tried everything!”
When you ask another person to look at your problem, that person will want to know a few things. First, they’ll want to know how to reproduce the problem, in as much detail as possible. You’ve already done that, right?
Another thing they’ll want to know is how you’ve tried to troubleshoot MMD models already– and what those attempts did. That can save them some time. (It’s also proof that you put some work into trying to fix it, so your friends don’t feel like you’re taking advantage of them!)
At LearnMMD, we hear a lot of people say, “I tried everything!” But that’s not an answer. If you really tried everything, then what else can we try? If somebody actually tried everything, and nothing fixed the problem, then the problem cannot be fixed, right?
What people usually mean is, “I tried everything that I know to try.” But we don’t know what you know. That’s why it’s important to be specific about what you tried. If there were ten things you tried, talk about them! If you can’t remember, try again, and keep a pen and piece of paper handy to write down what you tried and what happened.
Are you still banging your head into the wall? It’s time for the easiest step to troubleshoot MMD models: go to bed. Our problem solving abilities work in strange ways, not always conscious, not always at the pace we’d prefer. The best way to solve some difficult problems is to spend some time not thinking about them.
Sometimes, that means taking a walk and letting your mind wander. Sometimes, it just means getting a good night’s rest. Troubleshooting is like cooking a good stew. It takes longer than you’d like. But you don’t have to be stirring the pot the whole time.
This is not a flowchart
Even though I talked about these problems like they’re four steps to troubleshoot
MMD models, they’re not really. You can do them in any order. And no step is ever complete! You can experiment, wait, experiment, wait, and then research.
Did somebody tell you there’s no failure, only death? There’s a reason bushido is dead. If people never gave up, we’d all be stuck on whatever problem we first failed to solve. There comes a time to admit that a problem may be beyond us. That’s okay.
Especially when you get started, you’re going to run into problems that you just can’t solve, no matter how hard you try. It’s okay to give up and do something else instead.
But trying to fix these problems is how we learn– how we gain expertise. And any time you spend in experimentation or research is going to help you become better at making models in the future, even if it doesn’t solve your problem this time.
And you never know! Even when you give up, that problem may sit in the back of your head while you work on other problems. As you gain experience, you may find that you learn what you need to solve the problem you gave up on so long ago. From this perspective, there’s no such thing as giving up– it’s just an extended waiting period.
Remember when I talked about the value of an extra set of eyes? If you’re still having difficulty, you can contact us at LearnMMD. We can help you troubleshoot MMD models!
Just as with any other friend, if you want to stay on our good side, we expect that you’ve put some work into the problem before hand. That includes all of these other techniques: some experimentation, some research, and sleeping on the problem for at least one day. Solving problems isn’t easy for us, either, so put the work in yourself first.
And we’ll want to know everything that any other friend would want to know. How can we reproduce the problem? And what, specifically, did you try to do to fix it? Not, “I tried everything!”
Show me the model!
If you need help to troubleshoot MMD models, we’re probably going to need the model to figure out what’s happening. Screenshots are not going to be good enough. There are a number of hosting sites where you can upload your model– try Mega, Dropbox, or Mediafire. If you’re using something that shouldn’t be redistributed, provide us a public link (not one that requires a password or registration or else we probably can’t get the model!) Remember, you can write the model author to request special permission to redistribute. Tell them you want to send it to LearnMMD for troubleshooting help. Most modellers will happily give permission for that.
Maybe you’re working on a model yourself and don’t want it to be redistributed. Remember, if you’re running into a problem that you can’t solve, you probably need to improve before people will want to use your model in the first place. And if you’re asking for help, it’s a good reminder that modelling is a group effort where we all pitch in, rather than a situation where any single person could claim exclusive credit. I feel much more comfortable helping when people intend to share their model with everyone. However, you can still be sure that we won’t use your work-in-progress in our own work without asking your permission. We’ll happily delete it when we’re done. (I have way too many models anyways, I can’t even keep track anymore!)
So if you still need help to troubleshoot MMD models, feel free to write ReggieDentmore@aol.com with a link to your model, a description of the problem and how to reproduce it, and the steps you’ve already tried.
Just as with everything else, people have already put the work into learning how to learn. And for more useful information about the techniques people use to fix anything, check out Art of Troubleshooting or Universal Troubleshooting Process.
Keep the Faith and credit your sources! I’m using my own Tda 0401 Bliss, wearing edited versions of UnluckyCandyFox’s MMD Coat and SkinnyMandria’s shoes from Shoe Pack 1! For accessories, I used my own laptop, glasses, and chair models.
– SEE BELOW for MORE MMD TUTORIALS…
— — —
– _ — –