Frith5 wrote...
Is this a script issue, where some script is adding those additional wings to a model that already has wings built in, maybe? When Draygoth was asking how to 'keep wings' on the mountables, I told him about using the appropriate scripting to add the wings to the mounted model that needed them. It's possible that same script is adding wings to models with built in wings. Just a thought... does the model appearance show up with both sets of wings?
Yes, the wings are being added by me via script or in the toolset -- but to a model that
isn't supposed to already have wings.
I did a little more digging and I think I know what's going on. I think my confusion came partly from not clearly remembering what Hardpoints did. Looking over my haks again and the "Pegasus Node Change" hak that he provided, I realize that he didn't actually modify the underlying pegasus horse model (c_pegasus1.mdl) at all. (I must have noticed that at the time, but I guess I'd forgotten it.) His hak contains mostly phenotype changes and new models for the wings only. (What his hak does is move the wing nodes for the riding phenotype to appear on the horse body, so that if you put wings on a mounted character the result is that character riding a Pegasus.)
So logically, what CEP 2.4 must have done was to add these vestigal wings to the underlying c_pegasus1 model that I was using. It turns out that's exactly what happened. In CEP 2.2, c_pegasus1.mdl (which my ridable pegasi use) is in cep2_core0.hak, and of course it lacked these vestigal wings. It's still there and unchanged in CEP2.4, except that now another copy of c_pegasus1.mdl
also exists in cep2_core6.hak -- and which
does have these vestigal wings. And since core6 is supposed to come before core0 in the hak list, this new model with the vestigal wings was now overriding the one without them.
Now I have to say with all due respect that this is an astonishing failure of backward compatibility. The original pegasus model (c_pegasus1.mdl) does
not have wings --
precisely because it was designed and intended to be used in conjunction with adding wings in the wing slot, via script or in the toolset. Creating a new pegasus model with these vestigal wings would have been fine, as long as it had used a new name. By
overriding it with a model using the
same name, however, it could not have had any other result except to break every existing module that was already using it to create pegasi as originally designed and intended.
In any event, now that I know what's going on, I should be able to fix it easily by adding the original c_pegasus.mdl (in cep_core0.hak) into my module-specific hak (ahead of the CEP haks).
EDIT: I just did that, and confirmed that it fixes the problem.
Modifié par AndarianTD, 24 avril 2011 - 02:13 .
