Mdlvis_Normals_Bug

mdlvis defense force here
what if it's virgin blizzard who messed up the normals and then tried covering it up by rotating them, but chad mdlvis is having none of it and just exposes their mistakes, reverting normals to their messed up state
but seriously, just make all meshes from scratch and you're good, mdlvis won't mess those up

Exactly why I didn't have trouble, I created my own mesh

you can fix it, its just tedious, export the face, delete it, edit it, re import it.

rotate normals is really buggy, reverse normals will give you more success. In my opinion.

remember to use magos for the geoset imports and exports, it may seem silly, but somtimes a ''transition'' model is needed, so take jainas face, export the geoset with magos, import it into another blank empty model (sometimes items can work) with magos, save it with magos, but then open that model with mdlvis and change the normals, save as, and then use magos to export that face to the original model.

I know it seems silly to do the same thing over and over but when I was attempting to import the world of warcaft deep sea murloc face onto the warcraft3 murgul slave with the help of minimage I had to try with 7 attempts because of the normals bug. each try had a different look, normals wise.

normals are unpredictable, im sorry to tell you that, but sometimes one attempt that looks the same as the last has glitches and bugs the other does not. the more tries you make the more likely youll find a result you can work with.

ahhh I forgot about the non save bug. that happens to models occasionally for virtually any reason, and can affect more then just normals.

its similar to the magos bug that wont save animated textures, forcing you to hard code them your self manually in the mdl format to make tracks and water elemental like effects. I think if you try a few more times or go back wards a few model versions you'll find one that will let you save your normals, if the bug persists.