mdlc -optimize

Discussion area for user-created Allegiance models, textures, voicechats, music, and other ingame content.
Compellor
Posts: 994
Joined: Fri Jul 06, 2007 12:56 am
Location: Columbus, OH

Post by Compellor »

madpeople wrote:QUOTE (madpeople @ Nov 16 2008, 06:59 AM) do you have the texture files already as bmp.mdl in the same directory as the mdlc tool? It checks for their existance when converting
Yes, because mdlc refuses to work if the bmp.mdl isn't present.
QUOTE and attempts to convert any .bmp with the right name f they aren't there. (might be safer using non-text bmp.mdl here)[/quote]
This is false, see above. Perhaps you are using a different version. Does your version create hybrid MDLs?
Any job worth doing with a laser is worth doing with many, many lasers. -Khrima
Beyond a shadow of a doubt if you don't watch them like a hawk they will stack their collective balls off - MrChaos on Alleg players
madpeople
Posts: 4787
Joined: Tue Dec 16, 2003 8:00 am
Location: England

Post by madpeople »

don't think so, but i was using the whole tool chain and modifying it.
I did almost make a working redistribution of it, but then my comp crashed, and i haven't got it working properly since.
Here are the folders i experimented with the tools.
http://www.mesialonline.com/madpeople/AllegTools.exe <- self extracting rar file
you will probably want to look at what the .bat files are doing / using different tools for.

thhere are quite a few different versions of things in there, and a few pieces of art and converted art (I deleted all the big files to reduce the size, so if you see a flat_ model with no normal version then i've probably deleted the normal version in the archive - i deleted about 100MB of art in there to get the file size down)
this stuff may or may not be useful
Compellor
Posts: 994
Joined: Fri Jul 06, 2007 12:56 am
Location: Columbus, OH

Post by Compellor »

Hmm, just skimming through that rar, stuff I'm noticing:

MDLpackageR2\MDLpackageR4.zip/bin/output/fig04.mdl is a hybrid
MDLpackageR2\bin\output\fig04.mdl is also a hybrid

MDLpackageR2\bin\output\cap504.mdl is untextured, and lacks lights, etc. Just plain mesh data.

MDLpackageR2\bin\output\test.mdl appears to be an image with lights

MDLpackageR2\Copy of Copy of bin\finished\cap504.mdl has an image, lights, and frames, but no mesh data.

MDLpackageR2.zip/MDLpackageR2/bin/fig04.mdl is a hybrid
Last edited by Compellor on Wed Nov 19, 2008 1:10 pm, edited 1 time in total.
Any job worth doing with a laser is worth doing with many, many lasers. -Khrima
Beyond a shadow of a doubt if you don't watch them like a hawk they will stack their collective balls off - MrChaos on Alleg players
Compellor
Posts: 994
Joined: Fri Jul 06, 2007 12:56 am
Location: Columbus, OH

Post by Compellor »

I really think the key here is that the hybrid MDL files have:

Code: Select all

--Imported Libraries:2
     NameSpace:model
     NameSpace:effect
While on the other hand the mesh MDL files (my desired goal) have:

Code: Select all

--Imported Libraries:3
     NameSpace:model
     NameSpace:effect
     NameSpace:acs05bmp
acs05 being an example, of course.

I notice that the source.mdl file, which is read by mdlc, contains
use "effect";
I tried replacing that with
use "scorpionbmp";
or
use "scorpionbmp.mdl";
Sadly that doesn't appear to have any effect on the resulting file, it even still imports the "effect" library.
Any job worth doing with a laser is worth doing with many, many lasers. -Khrima
Beyond a shadow of a doubt if you don't watch them like a hawk they will stack their collective balls off - MrChaos on Alleg players
Post Reply