Compeller
i've looked at the scaling code for the MDL:
it's done using the same method but, unlike CVH file, there is no OriginalRadius value in the MDL file so this value is actually computed from the actual mesh data.
so if the CVH OriginalRadius (1st number in the file) is different from MDL OriginalRadius (computed from actual mesh data) i guess the scaling of the MDL and the CVH should mismatch at some point...
it's done using the same method but, unlike CVH file, there is no OriginalRadius value in the MDL file so this value is actually computed from the actual mesh data.
so if the CVH OriginalRadius (1st number in the file) is different from MDL OriginalRadius (computed from actual mesh data) i guess the scaling of the MDL and the CVH should mismatch at some point...
Could we change it that if there is a cvh for that model that it's original radius gets used for the model too? (or make it optional by say only having it if the cvh origilan radius is preceded with a * or some other character or something)KGJV wrote:QUOTE (KGJV @ Sep 24 2009, 03:17 PM) i've looked at the scaling code for the MDL:
it's done using the same method but, unlike CVH file, there is no OriginalRadius value in the MDL file so this value is actually computed from the actual mesh data.
so if the CVH OriginalRadius (1st number in the file) is different from MDL OriginalRadius (computed from actual mesh data) i guess the scaling of the MDL and the CVH should mismatch at some point...
same way. Actually all MDL 3D scaling is performed with same code whatever the object is (station, ship,...).Andon wrote:QUOTE (Andon @ Sep 24 2009, 05:08 PM) That makes sense. Are ship CVHs handled differently than base CVHs, by any chance?
QUOTE (madpeople)Could we change it that if there is a cvh for that model that it's original radius gets used for the model too? (or make it optional by say only having it if the cvh origilan radius is preceded with a * or some other character or something)[/quote]
why would we want to do such a tricky thing ?!
the issue is in generating 'good' CVH files, no point solving this by modifying the code to handle 'bad' CVH files...it's kinda bizarre.
can't you get this info in MS3D after importing the MDL ?Ramaglor wrote:QUOTE (Ramaglor @ Sep 24 2009, 08:22 PM) Well, then could we get a utility to read the mesh radius off the mdl so we can then apply it to the cvh?
I don't have MS3D installed so i can verify but IIRC there was some 'info' tool in MS3D that can do this.
Otherwise i guess we could modify mdlc or MDLView to compute the radius.
Maximum dimension would be the appropriate value? (it gives x-span, y-span, z-span)KGJV wrote:QUOTE (KGJV @ Sep 24 2009, 12:28 PM) can't you get this info in MS3D after importing the MDL ?
I don't have MS3D installed so i can verify but IIRC there was some 'info' tool in MS3D that can do this.
Otherwise i guess we could modify mdlc or MDLView to compute the radius.
Spidey's tactical advice on TS during Tourny game
QUOTE We don't need to save our thingy.[/quote]
QUOTE We don't need to save our thingy.[/quote]





