-
Posts
0 -
Joined
-
Last visited
Content Type
Profiles
Forums
Servers
Downloads
Gallery
Everything posted by XodusArt2
-
HOW THE HELL DO I DO IT THEN? The man is half right ,you definitely can't upconvert Objtom2 M2s to Legion....
-
Woah, what? Is it possible to do them with m2modder then? Even the static M2s?
-
As for the renderflag issue, it's just due to me combining a character M2 with an armor M2, anyway, fixed. I only needed a script because there was so many flags to tick. Well, I don't wanna toss away this thread, so let's change it into something useful for others too.. How do I make an ObjtoM2 M2 compatable with Legion? I've tried this ~ Convert Obj to M2 the same way as usual Open in 010 editor and run LKtoCata script on skin and m2, add legion prefix, open m2 template and set renderflags, open game and it crashes when I enter world.
-
Hi, to communicate my issue as best as I can, I'll start by saying this, I'm modding only the latest expansions every time, and that is because I believe progress is forward, not backward. This issue; ObjtoM2 used to convert Objects into Wrath of the Lich King M2 format, which it still does. All you had to do in 010 editor was use the LKtoCata script, and it would work with WoD, Cata, MoP etc. Not working with Legion, I've tried it, and yes I added the MD21 prefix, nothing works.
-
I guess what I'm asking is what those numbers look like in hex code. Just as an example, because I know you're trying to explain it, but for one, I don't even know what a *fid chunk is, I don't know how you translate 12.8mb to hex code, and I'm lost as hell.
-
If my file is 12.8mb, what should the chunk be?
-
Where in the wiki does it say how to tell what your M2s data size is? The only help I actually got was from running in circles asking my self questions. Why would I do a tut when I don't even know for sure how I fixed it? 16 hours of trial and error.
-
I solved it by myself through trial and error.
-
Please don't link me to Wowdev.wiki..
-
To what? I've added a whole new geoset, rather large in size, what would I change the chunk to?
-
This isn't an issue anymore, my issue now is getting custom M2s into legion, just adding the MD21àÍ chunk at the start and changing the 10 byte doesn't work (for going INTO) legion, but it works fine converting to WOTLK.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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!
-
GOT THIS WORKING. But bone names changed in legion, how do I keep the weights I had, but change the names of the bones?
-
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?
-
I made it myself, vert by vert, in blender.
-
pls help, i def cannot get this to work.
-
So I'm trying to create a creature model that has a properly flowing cloak, or atleast a cloak that moves with the bones. I've just uploaded my blend file, considering I'm not sure how to pack this into an M2 and still have all the geometry there, I'm assuming because I didn't name / parent shit properly it doesn't appear in the m2 when converted to M2i. Anyway, If anyone could look at this, get it working, feel free to keep it for yourself too. I'd very much appreciate any help you can offer. I understand that It's a bother for me to ask you to do shit like this for free, hopefully my 'work' is good enough to be considered payment, and make it worth your while, I haven't seen any other full body cloak patches anyway. HilltopBees.blend
-
It's WoD, so I guess no transparency on helmet models then?