Sorry for the tardy reply, Draygoth!
Okay
, as Amethyst Dragon indicated, the h_* supermodel sereis are going to need to be included. Their decompiled, ASCII forms. I believe they're natively compiled, anyway. That's going to be a bit of a pain in the butt for a couple of different reasons. Again, while it's preferred to have models compiled in advance nomatter what, the goal here is shaving off loading time. Any model which hooks into h_ba is going to cause at least a little hiccup because of the (relatively) enormous size fo the h_ba animations to begin with. However, if you already have mounts in your scene (which certainly already plug into h_ba), any additional loading time lag is probably due to on the fly compilation- because the animations are already in memory.
Just wanted to get that out of the way.
Crash course, two different routes.
First, give your model a shot with the Bioware compiler. The Bioware compiler will almost certainly bork it, but it's worth a shot. Just copy the model into the "in" directory, run the
processmodels.bat file and check in the "out" directory. Also look at processmodels.log. If there is any error at all, it'll probably be a "**MAJOR ERROR**". Fortunately, processmodels is very good at sniffing out any problems, inconsistencies or lack of "best practices" on any models it attempts ot compile. Unfortunately, it throws up its hands for pretty much the same way for major errors as well as minor ones, reporting the same inaccurate message in the log for both. If your model DOES compile, copy it to your override and test it out. If it works, you're lucky. There's a pretty good chance it won't, though. Processmodels and skin mesh (and some types of animation) don't seem to work right.
Second, adding the supermodel chain to either the Bioware processmodels "in" folder to the "DLA" model compiler's model folder. As Amethyst Dragon mentioned, you're going to need ASCII versions of the h_ba model series present at compile time. The reason for this is the deep down way supermodeling appears to work. More can be learned about that
here (from Torlack), BTW.
Here is a list of the h_ba supermodel chain:
h_ba.mdl
h_ba_casts.mdl
h_ba_coat.mdl
h_ba_custom.mdl
h_ba_med_weap.mdl
h_ba_non_combat.mdlI think that's it. This ful chain of models will likely have to be placed in the directory for compile. I had forgotten this appears to be the one time where compiling models in advance can get really...irritating. Usually it's so easy it's not even funny. On the assumption that the compile goes through with the DLA model compiler with these additional files, what you want to do is to test your compiled model (probably by copying it to the override directory) but
you do not want to test with the resulting compiled h_ba* models into your override or distribute them. Again, don't do that.
If all goes well, your fox model should compile fine and work well, standalone.
Modifié par OldTimeRadio, 19 mars 2013 - 12:54 .
