Effacer Posted April 23, 2019 Share Posted April 23, 2019 Hello JKHub. I've been attempting to merge DT85's First Order Stormtrooper and his Captain Phasma into one model with Blender so I can easily replace the models on Movie Battles II with a project I'm working on. I was going off of an example from one of Peneke's models where he managed to merge three different models together and I copied exactly how he sorted his but I'm getting the hierarchy error when I put it through Modview. Model has 121 surfaces, but only 149 of them are connected up through the heirarchy, the rest will never be recursed into. This model needs rebuilding, guys.. I've had this error before but have since learned how to solve the problem with some help from the community here and my own intuition. The problem here is I've never merged two models together successfully. I have tried before relatively the same way and failed. Any help on how to approach this or how I should specifically construct the model would be very appreciated. Link to comment
Jeff Posted April 23, 2019 Share Posted April 23, 2019 Make sure nothing is named the same. You can't have for example two "torso_0" the ones that are causing the problem will be named as such "torso_0.001". Search through your hierarchy and renamed all the parts with the "_0.001" extension. Link to comment
Effacer Posted April 23, 2019 Author Share Posted April 23, 2019 I've gone through every single part and renamed everything accordingly but to no avail. Link to comment
Solution Tompa9 Posted April 23, 2019 Solution Share Posted April 23, 2019 I've gone through every single part and renamed everything accordingly but to no avail.Ok so 2nd fix is to check all parentage of all meshes if they are parented well. Usually it is parented like this: hands --) armshead, arms, cape/robe --) torsotorso, belt, legs ---) hipships --) stupidtriangle This tutorial should help you with whole process (merging Rosh with Desann into one model.glm):https://www.youtube.com/watch?v=bUEHJWBodG4&feature=youtu.be Effacer likes this Link to comment
Ramikad Posted April 23, 2019 Share Posted April 23, 2019 Aside from Modview, did you test it in-game? Sometimes I had models that caused this problem in Modview, but (at least apparently) worked fine in-game. Not sure what kind of horrible thing I may have done, but if there are no apparent problems, anything goes. Link to comment
Effacer Posted April 23, 2019 Author Share Posted April 23, 2019 I haven't tested it out in-game but I got it to work on Modview. I was trying some things out and I came across it sort of by accident. If anyone else has this problem I'd be willing to help them out if requested. Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now