Are you using the version of DBpro available on Github here?
https://github.com/LeeBamberTGC/Dark-Basic-Pro
I cannot seem to be able to get anything other than a very dark object using the code provided in any version of DBpro other than that version, if not using that version then what version are you using? I tried the other free version available through this sites home page u7.5, followed by most of the only upgrades I could find available - upgrades 6.7, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.61, 7.62, and 7.7rc7. Upgrade 6.9, 6.8 and earlier than 6.7 all have broken links as best I can tell
It could be there is something wrong with my installations of DBPro but I don't think so on account everything else(my own projects and Evolveds AL) all work just fine.
Adding
gets rid of the flickering but there is a transparency issue with the mesh itself that I can't find a way of controlling, changing ghost/transparency values. It is almost as if its locked from standard DBPro commands accessing it. Even grabbing the mesh off each limb and making an object of them inherits the same transparency issue which to me suggests there is something unusual in the FVF data and converting the fvf has no effect either!
AndrewT wrote a model viewer in DBPro here
https://forum.thegamecreators.com/thread/124936 which loads the model perfectly(don't bother exporting the .dbo from it as it inherits same results). Given the date of the post he obviously must have been using an upgrade earlier than that date and it could be quite an old one for all we know. So I suspect it is one of the upgrades no longer available that he used
Therefore I can only deduce that Leadworks support for DBPro with 3DWS doesn't stretch beyond a certain date around this time. I think I recall GreenGandalf(a very well known user here) may have wrote some sort of shader for an export of 3DWS for a particular user he was helping out, but there may exist a specific way to setup your 3DWS model that is the same way that user had used prior to export. I could be wrong though as my memory is hazy.
Even if going down the route of grabbing meshes and reconstructing the model within DBPro is done and you ignore the transparency issue(which seems to cause the overlapping the same as in your screen shot), well there is no way of telling what limb has what texture as every limb reads the same texture data using DBPro's "Limb Texture Name()" command for each texture stage and the limbs themselves are not separately named either, so all the work of matching limb to texture would have to be done manually which would prove harsh for a complex 3DWS export. I don't have 3DWS to play with so I can only suggest uploading the .x version of export to see if we can load it into blender and re-export it to something DBPro can use. Other than that I can't think of an easy way round this.
