[XodusArt2]

I've spent money and time trying to replace a cloak geoset on the Male HD human, it was working good before Legion, now I'm not so sure. I've tried the following methods to edit Legion M2s.

 

Removing the prefix/chunk before the MD20 chunk/prefix (MD21.:À.)  and changing the first byte after MD20 to 10 instead of 12.

This let's m2modredux 4.6.1 read it and convert it, It converts fine, then I open the m2i in blender.

I remove the cloak geoset as a test, and all references to it, then I convert it to m2, add the chunk/prefix; MD21.:À. back in, change the byte after MD20 to 12 again, and place it in my patch.

The model works, but is missing several geosets, almost all.

How can removing one geoset remove MANY others?

[XodusArt2]

GOT THIS WORKING. But bone names changed in legion, how do I keep the weights I had, but change the names of the bones?

 

 

[XodusArt2]

Seriously, this is confusing as hell, there's apparently two bones with the exact same name, in the exact same location? HUH?

 

I even went through the trouble of naming the bones.

with the prefix (Same as Legion)

Because there's apparently 13 bones that are the exact same in name and position in Legion.

The fashion at the moment is, Legion switched names with the bone below it, 14 becomes 13, 15 becomes 14, etc, etc...

 

But we have bones that stayed the same name, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13.

So by that logic, a WoD bone by 15 would go down to 14, to be called upon in the exact same location and name. It's HARD to explain this, you really have to experience it for yourself, check any WoD character model / creature model in Legion, bones have changed names.

 

I REALLY DONT WANT TO WEIGHT EVERYTHING AGAIN, if it's possible to just change the bone names (In the vertex groups) I'd opt for that instead, PLEASE HELP!

[XodusArt2]

I suppose why I'm so confused is, sure you can rename every single bone with an interval above the Legion intervals name DOWN an interval, eg; bone 12 becomes bone 11.

WHAT HAPPENS WHEN YOU GET TO 0? You can't rename the bone below it, because it doesn't exist.

[XodusArt2]

So basically I need to redo all my weights, just because they added two new bones in legion, fuck that noise.

 

Also, I understand how stupid it is to expect the WoWmodding community to want to move forward and do things with Legion, but I guess I tricked myself for a moment into thinking there would be a few who were interested. 

Also, I understand I haven't explained myself perfectly, but I am not even sure what's wrong.

There's either too many bones, or not enough, and the naming is out of whack.

 

[XodusArt2]

Maybe I found a solution, maybe I didn't, it isn't optimal in the least, but what has worked for me was renaming the bone in the WoD M2 (at the exact same location as it is in the Legion M2) to fit the Legion M2 bone name, then transfering weights.

[XodusArt2]

Well, from one problem to another, such is my life modding anything above 3.3.5.. 

 

All I did was delete a cloak geoset, Ha ha hah ahah aha.

 

[Amaroth]

My friend, you excel at talking to yourself :D. Good luck, I wish I could help you somehow.

[XodusArt2]

I mean, I ended up helping myself, so you know? Whatever works.

Maybe you can help me, I'm sure your knowledge is more vast than my own.