^ . .^ noted.
Any interface changes? Did browser-integration with drag-drop work okay, or should I go to ugly-buggy common-dialogue controls?
this is a horizontal break wrote:<hr>
Just digging through mesher now...
adapted from converter 1.15 wrote:mesher
<inputfile>
<outputfile>
<command>
' [input format (BFXM,obj,Xmesh|
' |output format(BFXM,obj,Xmesh,mesh)|
' |action (append,create)]
[-flip]
[-flop]
[-flips]
[-flipt]
[-flipn]
[-autolod]
[-autoedge]
[-autotangent]
[-forceflatshade] (forcenormals=false)
[-basepath=##########]
[-dims#####] (BFXM)
<Translation Distance>
' [-x##|-y##|-z##]
Ok.
The base three formats (
BFXM,
obj and
Xmesh) all can be
created from each other, however,
ogre mesh format is from
BFXM input and cannot return to another format with mesher (yet).
Only
BFXM and
mesh files can be
appended to.
BFXM only from
Xmesh and
mesh only from
BFXM.
Further more
<dims> is only valid with
BFXM, and will 'discard' all other actions.
And finally when a
mesh file is
appended to with an
<input file name> of
- then "we're just postprocessing the .mesh file".
^- - ^ I forget what the other
[-arguments] do under what formats..
this is a line break wrote:<br>
(as in previous versions of Masher) To overcome this difficulty the generated script first
creates a buffer file of appropriate type and then takes the appropriate action(s) as needed. ^ - -^
For example:
say we have asked Masher to
append
Larry.BFXM,
Curly.obj and
Moe.Xmesh to
Stooges.Yes? Yes, yes? Yes, yes, yes? ...NOOO!.obj.
Now we want the Stooges
appended in that order therefore we Drag-Drop them into the append list in that order ending with the target file in the 'output file' box. If we don't have a file we can type a name, or Masher will assume that is is the first file specified. Don't worry too much about screwing this up, but remember to set an output type. How about
ogre mesh.
First thing Masher does is backup and abstract the input file(s) incase some chowderhead has named their file with some utter crazyness that will confuse Mesher. So
Larry.BFXM becomes
0.BFXM,
Curly.obj to
1.obj,
Moe.Xmesh 2.Xmesh and
Stooges.Yes? Yes, yes? Yes, yes, yes? ...NOOO!.obj becomes
~.obj if it exists.
Next thing is Masher (seeing the output format)
creates the necessary buffer files for the final
append actions. Therefore
Larry.BFXM who became
0.BFXM is let alone,
Curly.obj who is now
1.obj creates
1.BFXM which can be understood to be
Curly.BFXM,
Moe.Xmesh 2.Xmesh 2.BFXM in lieu of
Moe.BFXM and
Stooges.Yes? Yes, yes? Yes, yes, yes? ...NOOO!.obj as
~.
obj creates
~.BFXM becaue there is no direct link from
obj to
mesh.
Masher then instructs Mesher to turn the output-buffer file
~.BFXM (inlieu of a
Stooges.Yes? Yes, yes? Yes, yes, yes? ...NOOO!.BFXM) to
~.mesh in lieu of
Stooges.Yes? Yes, yes? Yes, yes, yes? ...NOOO!.mesh. And subsequently appends
0.BFXM,
1.BFXM and
2.BFXM resulting in the
~.mesh which is the bachard child of
Larry.BFXM,
Curly.obj and
Moe.Xmesh gettin
append with
Stooges.Yes? Yes, yes? Yes, yes, yes? ...NOOO!.obj.
Finally Masher returns the child
~.mesh as
Stooges.Yes? Yes, yes? Yes, yes, yes? ...NOOO!.mesh
^ - -^ wrote:<!--"meow."-->
Now had we no
Stooges.Yes? Yes, yes? Yes, yes, yes? ...NOOO!.obj but specified the file name Masher would have understood this to be the 'root' name and would have treated
Larry.BFXM and the mother to be
appended to and named the child
Stooges.Yes? Yes, yes? Yes, yes, yes? ...NOOO!.obj.mesh unless we did not specify a speific output file name then the child would be named
Larry.mesh after teh mother.
^- - ^ wrote:<!--"meow?"-->
^ - -^ Tell me I haven't forgotten anything else, and fill me in on the details.
BFXMobjXmeshmesh-