I think you will be better off doing a Google search...you should be able to find tutorials in whatever your preferred language is. _________________ Skins: Links:
Trollpaxton wrote: tancients wrote: Would I be able to take current .m2 files and just drop them into the application and have it 'smooth' out things? I don't have access to a model editing program, but I'd like to keep the model change sizes etc the same, but smooth them out more.
No...here's a picture of a poly in profile:
O O / / / -> O / / O O
Since the added vert is exactly along the edge of the poly the models shape stays exactly the same.
So basically it cuts up the vertices, allowing model editors more flexibility in what they can bend/stretch. Now I understand a bit better how WoW model edits work I suppose, though I can't do anything with the information. haha
ScDK wrote: Didn't touch it since it only states that it works with Blender, and i'm using 3ds Max myself. XD
Wich one? I was using 2009 and couldn't export back the objects, every time I tried I get pop-up of visual basic debugger.
Edit: Holy Cow!! It worked with 3ds max 9. Well this is tha shit, now that I can remove those ugly eyebrows from the bloodelves, I can continue on my own custom character, It should look like this after a while :
Zilem wrote: Trollpaxton wrote: What's wrong with those races? i have no clue, i just know that i can't get any Models propper Converted to OBJ with Glitchy's MES...
didn't read the whole topic, but maybe i can help. i use that GMES myself, it has a "bug".
at first i couldn't export files properly and then couldn't import them back. spent like 3 hours on the matter.
Glichy's MES requires u to change the language of your computer to US english, i guess a regional setting affects the output and input of files. that's the fix suggested for it.
after changing the language/regional settings of my computer i repeated the process (exported the model from mywarcraftstudio, converted with GMES and importing in 3ds9) and it worked fine.
i've edited draenei, tauren, dwarven and orc females, and hi-res dwarf and orc. since changing the language never had a problem.
Isn't it just the " bLimitToOneView = true " line that needs to be active, i.e. not commented out? To reduce views I mean.
EDIT: I forgot to add that I do end up with just 1 .skin file, so I kinda thought I did everything right :d _________________ Visit for BIG higher-res boobs
Last edited by on Thu Oct 23, 2008 8:21 pm, edited 1 time in total.
I don't have a lot of time right now but here is a first draft: ---------------------------------------------------------------
[Settings] File Input/Output
inputFile - The m2 file to load. outputFile - The m2 file to save to. No matter what else is set, a file is only saved if outputFile is given and either an operation changed something in the file or bForceSave is set to true. objOutputFile - The OBJ file to output. The program outputs vertex data to the OBJ -AFTER- all other operations are performed. That means that objOutputFile will match outputFile. If no operations are performed, objOutputFile will match inputFile. Remember that you always need an M2 file to match your exported OBJ file so that you can merge them with objInputFile. objInputFile - The OBJ file to input vertex data from. This OBJ must be matched with the inputFile. The importing happens -BEFORE- all other operations.
Operations These represent the major changes the program can make to a model. Operation-specific settings are specified in their own [Sections] later in the file.
bIncreasePolyCount - Subdivides polygons, increasing the poly and vert count. The polygons it effects can be restricted by geoset and or ranges. bRemoveOptionalClothingGeosets - Makes the model's headers tell the game that it has no geosets for capes, flared sleeves/cuffs, flared pants, boots, or dresses. Doesn't actually remove them so no memory is saved. Option was added to solve a wierd problem with turning a creature model into a player model. bRemoveHairGeosets - Removes all hair geosets, making the model totally bald. May not work on all models. Was used to make custom female Orcfrog models. bBigTexture - Tells player model to use the texture you specify instead of the usual skin+clothing system. The texture can be 512x512 (like the EredarFemale creature skin), but no clothing (except shoulders & helms) will be shown on the player after this. bAddEnvMap - Adds an environment map to the model. Env. maps make models look sort of shiny--it is the effect seen on Naga, for example. The effect is always on whether the model has clothes on or not. bGhostify - This tells the model to render it's first texture with additive blending. On some creature models this can make a ghost-like effect. Work in progress. bTransparentDress - This tells the model to draw it's dress geoset transparently and to leave legs on. Work in progress. bEnableSkirtGeosets - This tells the player model to show it's mini-skirt geosets instead of it's flared leg geoset. This is how I made the models for the mini-skirt pack. bChangeTabardUVs - Normal tabard UVs are such that it takes their texture from the side of the character's torso. This setting makes it take it from a small area on the side of the breast. Work in progress. bComputeNormals - This tells the program to analyze it's normals and attempt to smooth them out. Overall, it doesn't do a very good job, though it can be used with the bDebugNormals option to give you a visual representation of your Ranges settings.
General Options bMakeDefaultDestFileName - If this is set, outputFile will be set to "<inputFile>_HiRes". Added by request, not much general use for this. bVerbose - Makes the program output additional information for debugging. Not as useful as the Print options. bDontPauseAtEnd - Makes the program not pause when it is done, handy for batch files. bForceSave - Makes the program save outputFile even if no changes were made to inputFile. Mostly used for debugging.
[Geosets] This section is used to define a set of Geosets. These operations use this defined set: bIncreasePolyCount.
bAffectAllGeosets - This adds all of the model's geosets to the set, effectively overriding any set with geosetID. geosetID - This adds a single geoset ID to the set. This line can be added to the ini file multiple times.
[Ranges] These specify the limits of a 3-dimensional box, within which some operations operate. Mostly used to define a region of the model to subdivide with bIncreasePolyCount. If commented out, -infinity is used for min values and +infinity used for max. Used by: bIncreasePolyCount, bComputeNormals. xmin - xmax - The center of the character is at X=0, with negative X values being behind the character and positive being in front. ymin - ymax - The y-axis passes through character models left-to-right, so normally you want ymin = ymax for symmetric edits. zmin - zmax - Character models tend to start at around Z=0 and go up to Z=2.0 or so.
[PrePrint] and [PostPrint] PrePrint options print right after inputFile is loaded. PostPrint options print right before outputFile is saved. Useful for getting detailed information about a model, and for checking your changes.
VIEWS - Prints view information. Character models seem to consist of 4 views, which contain slightly different data. All 4 views seem to be important, though it's unknown what exactly they are for. TEXLOOKUPS - A look-up table for texture IDs. TEXTURELIST - The textures used by the model. Some textures have no filename--these are things like character skins, the exact texture of which is determined by the character's in-game options. RENDERFLAGS - TexUnits assign these flags to a given texture to specify how the texture is rendered. For example, elf eye glow textures have different flags to make them glowy. TEXUNITLOOKUPS - Another look-up table. TEXUNITS - Each view consists of a list of TexUnits. Each TexUnit says "render -this- texture onto -this- geoset using -these- flags". WowModelViewer's "Show Geosets" control actually doesn't show geosets, it shows view #0's TexUnits. GEOSETDETAILS - Shows detailed geoset information. A geoset is a collection of polygons. Each geoset is given an ID which specifies what it does (for example, if it models the dress). The engine turns geosets on and off according to what armor a character is wearing, what it's hair and jewelry options are, etc. GEOSETEXTENTS - Outputs the x,y,z min and maxes for each geoset. GEOSETUNKNOWNS - There are a number of values in each geoset which I don't know the purpose of. This lists them.
Operation-specific Options
[IncreasePolyCount] viewCount - This specifies how many views to save. Default is 2, which seems to be the minimum that the game requires when using DirectX rendering. OpenGL rendering requires 4, it seems, but the program doesn't yet know how to save the 3rd and 4th geosets in a way that OGL likes. Best to leave this option alone until that problem gets resolved. bDivideEdges - If this is true, edges of geosets will have extra verts inserted into them. If the geosets on the other side of the edge are -not- subdivided the same number of times you will probably see a seam. Best to leave this off.
[ComputeNormals] bDontSmoothNormals - If true, computes normals without extra smoothing. Tends to look blocky. bDebugNormals - If true, sets all normals to 0, which ruins the model for rendering in-game but makes the affected polys look black in WMV. This option can be then used to visualize your Ranges settings.
[OBJImport] bImportNormalsFromObj - Imports vertex normal information when importing an OBJ. bImportTexCoordsFromObj - Imports vertex texture coordinates when importing an OBJ.
[EnvMap] mapFileName - The name of the texture to use for the environment map. Defaults to the naga environment map, but you can use this option to set your own.
[EnableSkirtGeosets] skirtSwapGeosetID - The ID of the geoset which is to be swapped with the mini-skirt geoset. Defaults to 902, which is the ID of pants with flared legs.
[RenameTextures] texture0 = ... texture7 = You can use these options to change (or set) the path of given textures in the model file. Use the TEXTURELIST Print option to see what the current texture paths are. This is mostly for use when you swap around creature models. Note that there is no operation associated with this: if the texture names are set then the renaming will occur.
[BigTexture] bigTextureName - The name of the texture to use. _________________ Skins: Links:
Trollpaxton wrote: Oh...yeah, that'll do it. To keep poly's down you can use the Range options, especially if you are just updating one area of the model (ie. the breasts). It's good to use the range to tell the tool to not subdivide anything from the neck up, in any case: all the hair options really add up, and the face is the highest poly part of most (all?) character's bodies.
Ah, so that's what range does... lol...
Another question, been trying to find the geoset number for the alternate set of upper legs. They are the ones with built in armor plates protruding from each side. The list in the ini was really useful, but I can't find that particular set number. Help?
As for the range, what values you recommend for the human model? I didn't use range parameters, so the face poly count was doubled, it would be cool to do as you mention and leave the head out next time. The rest of the body needs the increase though.
grin wrote: What I meant was obtaining in the created obj a group layout that combines body groups. Unfortunately that isn't as easy as it sounds. Right now the obj importer/exporter assumes all the vertices are going to be in the same order as they are in the file, but in order to make a group that is made of multiple geosets that are scattered throughout the file I'd have to reorder the vertices.
grin wrote: In other words, obtain directly in the output .obj what you get when you uncheck body geosets while importing into max (which as far as I know renders the max processed .obj not reinjectable as it doesn't contain the same grouping info as the original). Yeah, that messes everything up, you definitely don't want to do that.
Why all these limitations? Here is the problem: vertices in M2 files have a lot of data associated with them (things like bone weights) that can't be stored in an OBJ file. In neither file format do vertices have a unique identifier. So, the only way to find out which vertex is which so that the extra data can be reassigned to the right vertex when importing an OBJ is if the vertices are all listed in the exact same order in both files.
grin wrote: Then you can modify multiple element meshes at the same time... Can't that be done already? What I do is use the Layers window to hide everything but the body, and that's pretty much it.
Isn't that what you are trying to do? Or am I missing something? _________________ Skins: Links:
Quick question, I tried to use the "bAffectAllGeosets = true" option and I'm getting an error on a couple of geosets:
ERROR: Vert indexes (66681) in geoset 53 exceeded maximum of 65535.
I think this is probably due to some variable being too small to hold the value, but is there anything we can do short of changing the code? The reason I am doing this is that I want to find the geosetID for the alternate set of armored legs. They don't seem to follow convention (it is not 1300 nor 1303). Rather than guess I was trying to enhance it all (yeah and this is the price, lol). Am I missing a tool to identify the sets? Googling didn't reveal anything that isnt on the board, at least on the first few pages...
Do anyone know the geoset id for this particular mesh layer?
Pardon me if someone posted it and I couldn't find it.
Users browsing this forum: No registered users and 0 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum