Search the Community

Hey everyone, ive been learning a lot recently specifically with converting some MDX files made for Warcraft 3. To preface, im starting this guide with an already-converted .m2 file from a source .mdx, i used the Lazy Converter and assigned animation ids by hand. So you've managed to convert your model, but now all its animations are jittery and look like garbage! Well not a problem, this is something we can *somewhat* easily fix on our own, without the help of something like Blender or other Model Editors. To start, choose a specific animation you want to clean up first, in this tutorial ill be using my models "Attack Unarmed" animation, locate the animation ID using 010 and a matching .m2 template from the Animations block, refer to the animation by the ID referenced here: We can see here, my animation ID is 17, with that in mind we can move on to the Bones We need to pick out specific bones based on the animation itself, use Wow Model Viewer and find the animation you selected previously. In the below gifs, you'll see the offending animation in all its glory, ill be specifically targeting the leg bones for this tutorial Now in WMV go to View>Show Model Control, uncheck "render" and check the "bones" box until you can see a visualization of the bone structure: The given render of only the bone connections is useful in finding specific bones in the structure Picking out the right bone can be difficult, but usually you can use the parent structure to find the bone you want In my case, the legs are connected directly to the waist, and visibly we see 4-5 bones in each leg chain With the given image, we can see that bone #2 is the waist, we can see all the bones connected to bone #2 in the image as well, with smaller offshoots being bones 8-11 That being said, we have two chains of 5 bones each starting at bone 2, those ranges in my case are: Bone #3-#7 and Bone #12-#16 Now that we've narrowed down where we need to make changes, lets open up a bone and see whats inside. 9/10 times the corrupted data is within the Rotation data for the animation. Bones store each animation separately in its own block like this: Right here we've located the anim id #17 data for a specific bones rotation data. Not all data is corrupted, but some definitely is let dig a little deeper to see exactly what the problem is: As you can see by the giant red boxes, some of the data here does not follow a regular "pattern", specifically, look at the 4th value in each line, these are labeled as the "W" value. These values should always line up near each other, at least with the same polarity. In order to fix this, we simply need to target the corrupted lines (the ones in boxes) and swap their negative and positive values. Heres the end result here: Now my data is following a regular pattern, with emphasis on the W values being in-line Congratulations! If you've made it this far, you just repaired the animation data for a single animation on a single bone! Great job! Lets keep working through each leg bone, fixing each set of corrupted values so that the "pattern" is intact: This bit of data corruption follows a different pattern. You'll notice some 0 values and some that are .000061, these are essentially null values, we need to leave them alone, that being said, the W and Y values here are corrupted. Lets fix them like this: Looks much better now, keep working through the structure until you finish all the bones in the set. Now we should be good to go, lets save the .m2 and try it out in-game or in the model viewer. Excellent! Were on our way to a fully working model! This process takes absolute ages, and is a bit tedious for beginners. I strongly suggest enlisting some help, perhaps 2 could split animation data down the middle and merge corrected data together when finished Thats all for now, happy editing!

Sorry for the beginner question here, but. After setting up Noggit, I have run into an issue where it can't seem to read my WMV's log and can't place an object into the game because there are is no model data in my log, while the log shows that I have been looking at models. Here's my path to the WMV log folder. And here's my WMV log - as you can see, it has opened everything successfully and is looking at the model. Am I doing something dumb or is this a bug?

First of all, why the heck do I even bother with something what seems to be so basic? Well, apparently it is not, because there are a few tips and tricks which aren't very commonly known, at least beginners don't know them and there's no tutorial really describing them. I will also link my simple WIP tool which can be very usefull for you here. I will start with things you probably do already know, if that bothers you, just skip to the last heading. First of all, how can we get models into our map in Noggit? A short list of possibilities: Ctrl+c and ctrl+v. No magic hidden here. Import from MV. Import from a text file (Import.txt). Import from MV MV is a model viewer. WoW Model Viewer is an application which enables you to browse WoW models. Great thing, but here comes a problem - current Noggit's import functions aren't compatible with quite a lot of WMV's versions. As far as I know, importing WMOs in general tends to work. In order to import models from WMV, simply change ImportPath in noggit.conf, so it points to log.txt file in userSettings folder in your WMV's folder. An example follows.: ImportFile = D:\Modding\Projekty\Arathor\WMV\userSettings\log.txt When you have this set, you can simply open a WMV, select a model, then go to Noggit and shift+c to import M2, alt+c to import WMO. There were slightly bugged versions of Noggit where both shortcuts actually imported M2, keep this on mind please. The newest version should have this fixed by now. If your import functions don't work (mostly M2 tends to not), you can try a different version of WMV. Version which is definitely compatible with Noggit's import function for M2s can be downloaded on Modcraft.: http://modcraft.superparanoid.de/viewtopic.php?f=48&t=4797 The problem is, that this version is really an ancient one, and tends to crash frequently, especially when it comes to retro-ported stuff. Import from text file Import.txt is a file located in Noggit's installation folder. It contains paths to models separeted by line breaks. You can delete models from here simply by opening a file and deleting them. To reload a file, just deselect any model you may have selected in Noggit and go to Assist menu, choose To Text File function, and here you go, Import file is reloaded. If you have any model selected while clicking on To Text File button, its path will be written at the end of the file. This can be very useful when you need to copy a model from different map, or when you need to copy multiple models. To acces list of models in your Import.txt, simply go to Assist menu and click on From Text File. Then you can just start clicking on model names and models will appear on your mouse cursor or in model you have currently selected, or on selected coordinates, if Auto select mode in Edit menu is turned off (does anyone even use this thing?). So, why this tutorial? Where are those secret tips? Yep, its a little bit strange to write them at the end of tutorial which was supposed to be dedicated to this, but I needed to explain stuff above. Import.txt is actually quite a powerful thing to use, as long as you can get list of models you want to import into Noggit, separated by line breaks, and filter them. Such lists do exist in WoW - they are called listfiles. In each MPQ, you can find (listfile) (as long as it wasn't made as listfile-free MPQ). (listfile) is a list of all file paths to all files in MPQ. And we will make a good use of this. First of all, download my Toolkit. Its a WIP application and poorly written, I've got to admit, but it works for what we are going to do with it absolutely fine. There's also a simple .bat included.: https://www.dropbox.com/s/hh8i859hb9ebxve/AmarothsToolkit.rar?dl=0 Open your WMV. Go to File menu and select Export textures... option. In new panel which appears, make sure that Path preserved option is checked. Then just browse M2s. Everytime you find some you want to use, just click on Export all button in panel which have appeared. In the end, you will have model files in Export folder in WMV's directory, and they will be all in paths into which they belong. Now, you have basically two options. You can either place cleanup.bat script into Export folder and run it. It will delete all .skin and .blp files in all directories in Export folder. If you want to change list of extensions which should be deleted, simply right-click that cleanup.bat, click on Edit and you surely will figure out how to change it on your own. Then create a new, empty MPQ and place all folders in Export directory into it. The second option is skipping whole cleanup.bat part and continuing to another paragraph of this tutorial. When you have any sort of MPQ with (listfile) which contains files you don't want to use in Import.txt (like BLPs, SKINs or maybe even more stuff, it may be your server's patch you are giving to players or whatever else), you need to clean that (listfile) from all things you don't want to have there. To do this, just extract (listfile) from that MPQ and place it whenever you like. Then run my Toolkit application and set extracted (listfile) as input file. For this purpouse, you will want to use cleanup filter, which is that big panel on the left. Select extensions you want to keep in listfile (most likely .M2 and Root-only .WMO). You can also select path prefixes to keep only models from certain directory, for example, you can keep only files from World folders. You can also modify filters by using those 2 buttons and text input under filters, so you can add filter to World\Expansion02\ directory, for example. For more info, follow a Manual. When all your settings are done, just click on Cleanup Listfile button and save cleaned listfile whenever you want. If you have made a MPQ which already contains only M2 files, its (listfile) will, obviously, contain also only M2s (and (listfile) and (attributes) most likely), so you can basically use that (listfile)'s content without even filtering it by my Toolkit. Now just open that cleaned and filtered listfile, press ctrl+a (or select just some particular models you wanted to use), ctrl+c, open Import.txt, ctrl+v, ctrl+s, use To Text File function in Noggit to reload import file and you are done, you have your models in Noggit. This all can seem a little bit complicated, but when you learn how to do this and won't need to look any manual up for that, you will actually be able to quickly get lists of even hundreds or thousands file paths and filter them by using my Toolbox to get files you wanted, the only problem is exporting model files via WMV, if you need to do that (so, if you need to select just a few certain models rather then just use whole folder for example). One final tip. You can also create a (listfile) of all file paths in WoW and then just always get only models from some certain directories by using my Toolbox. Lets say you want all World\Expansion02\Coldarra\ models. If you already have prepared merged (listfile) of all WoW files, my Toolkit is actually very fast and easy way of getting all those models directly into Import.txt. Just open Toolkit, choose merged (listfile) as an input file, write World\Expansion02\Coldarra\ under filters, click on Add path prefix button, make that filter checked, click on Cleanup Listfile and... done. And one now really final tip. Extensions filter may be actually used also for ends of file names (like keg.m2, instead of just .m2). Path prefix filter can, on the other hand, be also used for name prefixes, like World/Custom/am_. Sadly, its (for now) limited for use on only one directory. This will get all am_ files, but only in World/Custom/ folder. Both extension and prefix filters aren't case-sensitive.