2010-04-15, 06:22 AM
Here (https://anon.swordofmoonlight.com/holy/S..._debug.exe) is a new version. I think this will be the last until I have some animations going.
I worked out the frame buffer mapping afaik. The files don't really seem consistent. I don't think the TIMs are limited to just the four "TIM Banks" I've seen ones which are not. But basically if a mapping to the framebuffer can't be made (a texture isn't where it should be) the first texture in the file seems to be used by default. This happens really fairly often. There aren't that many files with more than one texture and none with more than two afaik. Since there is no x2mdl program there's no way to know anything beyond what's in the mdl files themselves. We can test the limits of this sometime down the road I reckon.
I've also noticed enough of the TIMs have irregular coordinates in the frame buffer. Usually like they start on Y=1 instead of Y=0. If Som interprets this literally (or fails to -- if it was important to the modelers) it might explain the seams in the models. I will have to look into that further.
PS: If I get some of the transparency stuff working efficiently I will upload that / let you know. Assimp's transparency model is present overly conservative / probably broken. So it's more of a prob of leaning on Assimp's principal authors.
I worked out the frame buffer mapping afaik. The files don't really seem consistent. I don't think the TIMs are limited to just the four "TIM Banks" I've seen ones which are not. But basically if a mapping to the framebuffer can't be made (a texture isn't where it should be) the first texture in the file seems to be used by default. This happens really fairly often. There aren't that many files with more than one texture and none with more than two afaik. Since there is no x2mdl program there's no way to know anything beyond what's in the mdl files themselves. We can test the limits of this sometime down the road I reckon.
I've also noticed enough of the TIMs have irregular coordinates in the frame buffer. Usually like they start on Y=1 instead of Y=0. If Som interprets this literally (or fails to -- if it was important to the modelers) it might explain the seams in the models. I will have to look into that further.
PS: If I get some of the transparency stuff working efficiently I will upload that / let you know. Assimp's transparency model is present overly conservative / probably broken. So it's more of a prob of leaning on Assimp's principal authors.