Trollpaxton wrote:
"Assumption failed" means that there was an error reading a particular "view" of the model. w0w character models have 4 (some have 2) different views. To my knowledge, every character model has at least 1 working view. (Usually #0, but for
nelf females it seems to be #1.) The solution is to tell the tool to strip out all the failed views. I forget what the option is but I'm sure I've explained this before somewhere in this thread.

[*]
.
Yes, well, I read the thread carefully so I was aware of that and the descriptions in the INI file made this clear (Or so I thaught).
Still, it says "ASSUMPTION FAILED: View 1" regarding geoset 5 to 55 plus a few sporadic "ASSUMPTION FAILED: NO 1-to-1" here and there.
This should give me an Obj-file with higher polycount, once edited, to fuse with a new M2-output with the same poly increase, right?
It still writes an output Obj-file though, and it would write a new M2 but nothing will happen without errors in view 1.
I can't see how I could specify my instructions in the INI any further, yet not get this right.
Here's what I set it up to do in the INI :
inputFile = I:\
OrcFemale.m2
objOutputFile = I:\NewOrcFemale.obj
bIncreasePolyCount = true
bLimitToOneView = true
bVerbose = true
bAffectAllGeosets = true
viewToUse = 0
viewCount = 1
I haven't tried any big-boobs mpq arround here yet, I wanted to design my own pair, hehe. At least to begin with.
But by the way , you'd kinda figure this to be a noob question, but since they are referred to as 'views', common sense tells me they are LOD (Level Of Detail) replications, defined by the distance you'd view the models ingame, degrees of model simplification regarding skeleton structure, polycount, animation bounding and mip-mapping, right?
Since wow isn't happy with all four of theese being identical, and if DX can manage theese four reduced to a number of two, how do this affect the models in-game ?
A.Will a player fade out or blink to invisibile when going further way?
B.Will the game try to render one of the two existing views at greater distances and how does it affect performance?
Rendering a far greater deal of full-res models, and above all, with increased polygons.
C.Will the M2 keep the other two views (view 2 and 3) and render them, thus not only making the boobs appear as if, but infact they WILL be smaller in proportion to our edits at greater distances?
How does this work?
Anyway, back to topic.
I hope I can get some help regarding the INI configuration.
Let's say I want to import the whole model with increased polycounts and with all geosets thrugh 3dsMax09 in OBJ format, export to 3ds, import that to be exported as obj thrugh Milkshape, and finally injected to the model.
How should I set it up ?
Thanks!
EDIT:I got it working with the 2.4 tool now, what an extremely helpful thing this tool is, thanks!