Home General Discussion

Problem of bones influence (3DsMax - Babylon.js)

Hi Guys, I'm a 3D animation student in France (Sorry for my English x_x), and for school, I'm on a project of a video game (An FPS Bomberman like, in 3D).

I'm in front of a problem with my team, and we can't find from where it comes (my professor can't answer us too, cause he is just teaching us 3D animation, and don't know a thing about exporting and things like that).

I'll explain myself :

We have a rigged and skinned character we've done in 3DSmax, and we have to import it in babylon.js file. Each time we try, we have an error, that says some of our vertex have too many bones influence (5 bones), and that the babylon exporter accept only 4 bones.

The babylon exporter tells that the problem comes from the entire mesh of the character ; does it mean that the entire character must have only 4 bones to work ? Or is there something to do, like detach each part under influence of a different bone ? I don't think so (I hope not O_O).

Sorry again for my english. I tried to make the less mistake than possible :).

Thanks for your time ! I hope someone will know something about that :)

Replies

  • Popol
    Offline / Send Message
    Popol interpolator
    I've never heard of that babylon exporter but I can help you.

    The problem seem to be that each vertex can only be influenced by 4 different bones. Checking every vertex would be quite time consuming so an easy way to solve this would be to select the skin modifier, go into "advanced parameters", and select "remove zero weights" with a limit of like 1 or less. I don't know how you made your skinnig but I'm assuming you left very small influences on each vertex and that's why there's more than 4 bones influencing each vertex.

    Hope that will help.
  • Naekiah
    Sorry for the late, haven't saw your post before ! Thanks for answering :)
    There was a problem with my software, "remove 0 weights" didn't delete all the 0... And that was the problem, indeed :) The problem was solved by simply restarting 3Dsmax... should have done that before !

    Thanks again.
Sign In or Register to comment.