The main reason your having problems is all down to DA and the software they used. The CMP's & 3DB's have different internal compositions depending on 1) what part of FL thier in, 2) What software version was used & 3) who built and exported the model.
Most of the older tools that we use were designed primarily for the player usable ships, and as such only really work well with those models but they can still edit some of the other models.
The CMPImporter (a pet hate of mine) will import a custom model without any problem, but vanilla models are a different story (for me at least). If the VMeshLibrary's sub node ends in "data.blah.blah.blah.lod0-112.vms" then it will import with only minor problems, animated parts are normally twisted out of allignment. 212.vms or any of the other numbers result in either garbage being loaded, error messages or milkshape crashes.
**shuffles of with a new headache**![](smilies/icon_smile_wink.gif)
Most of the older tools that we use were designed primarily for the player usable ships, and as such only really work well with those models but they can still edit some of the other models.
The CMPImporter (a pet hate of mine) will import a custom model without any problem, but vanilla models are a different story (for me at least). If the VMeshLibrary's sub node ends in "data.blah.blah.blah.lod0-112.vms" then it will import with only minor problems, animated parts are normally twisted out of allignment. 212.vms or any of the other numbers result in either garbage being loaded, error messages or milkshape crashes.
**shuffles of with a new headache**
![](smilies/icon_smile_wink.gif)