Documentation:File formats and extensions - Revision history

Grinsegold: /* Material files */

2017-03-17T20:40:18Z

‎Material files

Grinsegold: /* .mhmat file format Internals */

2017-03-17T20:34:32Z

‎.mhmat file format Internals

Grinsegold: /* .mhmat file format Internals */

2017-03-17T20:30:46Z

‎.mhmat file format Internals

Grinsegold: /* .mhclo files */

2017-03-17T20:25:43Z

‎.mhclo files

Grinsegold: /* .mhclo files */

2017-03-17T20:24:51Z

‎.mhclo files

Grinsegold: /* .mhclo files */

2017-03-17T20:09:41Z

‎.mhclo files

Grinsegold: /* .mhclo files */

2017-03-17T20:08:23Z

‎.mhclo files

Grinsegold: /* .mhclo files */

2017-03-17T20:04:43Z

‎.mhclo files

Grinsegold: /* .mhclo files */

2017-03-17T20:01:37Z

‎.mhclo files

Grinsegold: /* Material files */

2017-03-17T16:19:58Z

‎Material files

@@ Line 410: / Line 410: @@
 == Material files ==
-Here's a list of naming convention for the content of the mhmat-file
+You can store more than one material for an asset. To do so, create a folder named "material" inside of the folder which also contains the mhclo- and mhmat file of that asset. Put your alternative textures and mhmat-files in there.
-(floats are between 0.0 and 1.0):
-−
-"name": string
-−
-"tag": string
-−
-"description": string
-−
-"ambientColor": 3 x float
-−
-"diffuseColor": 3 x float
-−
-"specularColor": 3 x float
-−
-"shininess": 1 x float
-−
-"emissiveColor": 3 x float
-−
-"opacity": 1 x float
-−
-"translucency": 1 x float
-−
-"shadeless": bool
-−
-"wireframe": bool
-−
-"transparent": bool
-−
-"alphaToCoverage": bool
-−
-"backfaceCull": bool
-−
-"depthless": bool
-−
-"castShadows": bool
-−
-"receiveShadows": bool
-−
-"autoBlendSkin": bool
-−
-"diffuseTexture": filename
-−
-"bumpmapTexture": filename
-−
-"bumpmapIntensity": 1 x float
-−
-"normalmapTexture": filename
-−
-"normalmapIntensity": 1 x float
-−
-"displacementmapTexture": filename
-−
-"displacementmapIntensity": 1 x float
-−
-"specularmapTexture": filename
-−
-"specularmapIntensity": 1 x float
-−
-"transparencymapTexture": filename
-−
-"transparencymapIntensity": 1 x float
-−
-"aomapTexture": filename
-−
-"aomapIntensity": 1 x float
-−
-−
-−
-−
-"sssEnabled": bool
-−
-"sssRScale": 1 x float
-−
-"sssGScale": 1 x float
-−
-"sssBScale": 1 x float
-−
-−
-−
-−
-"shader": filename
-−
-"uvMap": filename
-−
-"shaderParam":
-−
-['diffuse', 'ambient', 'specular', 'emissive', 'diffuseTexture', 'bumpmapTexture', 'bumpmapIntensity', 'normalmapTexture', 'normalmapIntensity', 'displacementmapTexture', 'displacementmapTexture', 'specularmapTexture', 'specularmapIntensity', 'transparencymapTexture', 'transparencymapIntensity', 'aomapTexture', 'aomapIntensity']
-−
-"shaderDefine":
-−
-['BUMPMAP', 'NORMALMAP', 'DISPLACEMENT', 'SPECULARMAP', 'TRANSPARENCYMAP']
-−
-"shaderConfig"  "diffuse": bool
-−
-"shaderConfig"  "bump": bool
-−
-"shaderConfig"  "normal": bool
-−
-"shaderConfig"  "displacement": bool
-−
-"shaderConfig"  "spec": bool
-−
-"shaderConfig"  "vertexColors": bool
-−
-"shaderConfig"  "transparency": bool
-−
-"shaderConfig"  "ambientOcclusion": bool
 == Poseunit files ==

← Older revision		Revision as of 20:34, 17 March 2017
Line 234:		Line 234:

	"shaderConfig" "ambientOcclusion": bool		"shaderConfig" "ambientOcclusion": bool
		+
		+
		+	ambientColor, diffuseColor specularColor, emissiveColor are the standard colors as used in the rendering equation or in standard OpenGL. Their corresponding intensities are simple scalars with a value between 0 and 1 and are multiplied with the colors to dim them. Default these intensities are set to 1.
		+
		+	Colors are described as three floating point numbers, representing R G B, or red-green-blue values. 1 is the maximum, 0 the minimum. For example 1.0 0 0 means fully red, 1 1 1 means full white, 0 0 0 is full black. 0.5 0.5 0.5 will give you a grey middle color.
		+
		+	opacity determines the opaqueness of the object (alpha channel), with 1 being fully opaque, and 0 being fully transparent (invisible)
		+
		+	translucency is something that came from Blender but is unused
		+
		+	shininess or specular hardness is a number between 0 and 1 determining the shininess constant of the phong shading model.
		+	Texture maps
		+
		+	Various standard texture maps can be defined on the material, like diffuseTexture, bumpmapTexture, normalmapTexture, displacementmapTexture, specularmapTexture, transparencymapTexture, aomapTexture. Each of these also has an associated intensity value, which is a scalar from 0 to 1 multiplied with the pixel value of that texture (unless a specific shader implements it differently). These textures only have an effect if their corresponding shaderConfig feature has been defined (see the table in Shaders section).
		+	Render states
		+
		+	When wireframe is set to True, the model is drawn in wireframe mode. In this mode, most material properties have no effect, but you can enable the vertexColors shaderConfig to be able to change the color of the mesh using vertex colors (this requires access to the mesh programatically, obj meshes do not support vertex colors). This feature is used in some parts of MakeHuman, for example viewing bone weights in the skeleton debug plugin.
		+
		+	Set shadeless to True to disable shading, eg. the object is not affected by lights. Configured shader will have no effect
		+
		+	Set transparent to True to enable transparency rendering (usually needed when opacity is < 1) In itself this does not change the visual appearance of the model, but this setting should be enabled if your texture contains (semi-) transparent parts. This setting instructs the renderer to disable depth buffer writes (glDepthMask(false)) and enables alpha testing and blending so that transparent surfaces can overlap and to allow alpha blending.
		+
		+	alphaToCoverage Applies when transparent is set to True (otherwise does nothing). It requires that your GPU supports alpha to coverage (A2C) rendering. It enables the A2C feature which provides face order-independent alpha rendering. This works very well for complex transparent meshes, like hair. At the cost of a slightly dithered look, it solves all the problems with face sorting that are usually involved in rendering semi transparency. (This feature disables anti-aliasing for this object because the multisample buffer is used for alpha blending instead)
		+
		+	Set backfaceCull to False to disable backface culling (render the back side of polygons) By default, and in most cases, this should be set to True, but can be useful in some cases (for example, we disable back-face culling for the eyebrow materials).
		+
		+	Set depthless to True for depthless rendering (object is not occluded and does not occlude other objects). This disables OpenGL depth writes and tests. In practice, this makes object faces that should be occluded shine through others.
		+
		+	castShadows determines whether the object casts shadows on other objects.
		+
		+	receiveShadows determines whether the object receives shadows from other objects. For some features, like eyes, you probably want to disable shadow receiving.
		+
		+	Since MakeHuman does not (yet) implement shadow casting, the shadow settings have no effect in MakeHuman, but they do export to other engines.
		+
		+	Play around with these settings in the Material Editor plugin to see their effect, that's the best advise I can give you. The best way to find out which settings work for an asset, is simply to try them out.
		+	autoBlendSkin
		+
		+	If True MakeHuman will set the diffuse color based on the ethnix mix set for the character. Any diffuseColor set in the material file will be overridden by this. Also the shaderParam litsphereTexture will be automatically set to a dynamically blended litsphere texture, which is a mix of three litsphere materials (afro, asian, caucasian) depending on the ethnic mix of the character. This latter is specifically intended to be used with the litsphere shader, and it is what you see as default material when you start MakeHuman This overrides whatever shaderParam litsphereTexture was set in the material file. This setting is intended only for skin materials.
		+	shaderParam
		+
		+	Define a custom shader parameter (uniform), which might be required for some non-standard shaders. For example, the litsphere shader takes an extra type of texture map as input, a so-called litsphere texture. This generic system of mapping shader uniforms allows you to create specialised shaders that take new and different kind of inputs, and allow configuring the shader from the material file.
		+
		+	shaderParam can be a list of floating point numbers, in which case it will be interpreted as a vector, or it can be a file path, in which case it is assumed to be an image path. Internally in MakeHuman, shaderParams can also be assigned a texture object, which allows for dynamically passing a texture that is in memory, but perhaps not stored on disk.
		+
		+	Another example of a custom shaderParam is the X-ray shader that defines an edgefalloff and intensity uniform parameter. These could be changed from the material file with
		+
		+	shaderParam edgefalloff 0.8
		+	shaderParam intensity 0.77
		+
		+	shaderDefine
		+
		+	shaderDefines allow enabling or disabling custom shading techniques in shaders. These allow to define new shading techniques, apart from the pre-defined ones such as normal mapping, specularity mapping, ... It's a generic system that allows new shaders to be added and configured from the material file, or from the material editor (which nicely auto-detects these features in the shader and shows a set of checkboxes for them).
		+	uvMap
		+
		+	Load custom UV coordinates on the mesh to use this material. This makes the material completely dependent on the mesh it is used with.
		+
		+	Takes a path to a .mhuv file, which is actually just an .obj file, where the vertex positions can be deleted (they can remain in there, but they are ignored). Requirement for it to work is that the vertex order is the same as that of the mesh obj.
		+
		+	An example uv map for the basemesh can be found in data/uvs/a7.mhuv, which is a set of UV coordinates compatible with the old Alpha 7 mesh, allowing you to load A7 textures on the new basemesh used in MakeHuman v1+
		+	SSS properties
		+	These are the so-called sub-surface scattering shading properties, currently only used by the built-in offline renderer. They were decided on while trying to figure out the most generic way to define SSS shading properties, so that they could easily be translated into SSS properties for a different renderer (as no single renderer that I know of has a standard for these). It's uncertain whether the format we have landed on currently is the best, or whether this will remain permanently or is still likely to change. This setting should currently be considered experimental. The properties are sssEnabled, sssRScale, sssGScale and sssBScale.

	==== .mhuv files ====		==== .mhuv files ====

@@ Line 128: / Line 128: @@
    emissiveColor- The color of the light that the material seems to emit as if it's a glowing light source.
    shininess- The sharpness of the shine spots created by the reflection of a light source on the material, which is how glossy its surface is.
 ==== .mhuv files ====

← Older revision		Revision as of 20:25, 17 March 2017
Line 107:		Line 107:

	where r1,r2,r3 are locations of human vertices v1,v2,v3, and s1,s2,s3 are scale factors		where r1,r2,r3 are locations of human vertices v1,v2,v3, and s1,s2,s3 are scale factors
−
−
−	~~See also here:~~
−	~~http://www.makehumancommunity.org/wiki/Technical_notes_on_MakeHuman#The_Material_System~~

	==== .mhmat files ====		==== .mhmat files ====

← Older revision		Revision as of 20:24, 17 March 2017
Line 107:		Line 107:

	where r1,r2,r3 are locations of human vertices v1,v2,v3, and s1,s2,s3 are scale factors		where r1,r2,r3 are locations of human vertices v1,v2,v3, and s1,s2,s3 are scale factors
		+
		+
		+	See also here:
		+	http://www.makehumancommunity.org/wiki/Technical_notes_on_MakeHuman#The_Material_System

	==== .mhmat files ====		==== .mhmat files ====

@@ Line 92: / Line 92: @@
-The three first a human vertex numbers which define a triangle.
+The three first are human vertex numbers which define a triangle.
-The three in the middle are barycentric coordinates, which defines a point in the triangle.
+The three in the middle are barycentric coordinates, which define a point in the triangle.
 The three last is an offset from this point. However, the offset is scaled with factors determined by the x,y,z_scale lines in the header.

@@ Line 68: / Line 68: @@
   # starts a comment.
 The uuid is a unique identifier for this file.
 The basemesh is the version of the MH mesh. Today always hm08, but earlier versions of MC supported hm07 and alpha6.
 Name of clothing.
 Version of MC
 The obj file contains all information about the mesh in obj format: original vertex locations, faces, UVs.
 x_scale v1 v2 dist: Used for scaling of offsets (see below) in the x direction. dist is the distance between verts v1 and v2 in the character the clothes were made for.
 y_scale, z_scale analogous
 z_depth determines the render order in MH, I think. It was originally used in a different way by the MHX importer.
 max_pole is the maximal pole number of any vertex in this mesh. Affects how large arrays must be allocated in MH.
-verts 0. It was some kind of vertex number offset, but I don't quite remember how it worked.
 Then comes a bunch of lines which determine the vertex locations.
 16602 16605 -2.77529 -3.02614 6.80143 -0.56369 0.10852 -0.06174
@@ Line 90: / Line 98: @@
 If the n:th line reads
      v1 v2 v3 w1 w2 w3 d1 d2 d3
@@ Line 96: / Line 103: @@
 then the location of clothing vertex n is
      w1*r1 + w2*r2 + w3 *r3 + (s1*d1, s2*d2, s3*d3)

@@ Line 55: / Line 55: @@
      uuid 59985471-ab08-479f-a32d-2d88411714ef
      basemesh hm08
      name Helmet
      version 110
@@ Line 67: / Line 66: @@
-# starts a comment.
+ # starts a comment.
 The uuid is a unique identifier for this file.
 The basemesh is the version of the MH mesh. Today always hm08, but earlier versions of MC supported hm07 and alpha6.

@@ Line 44: / Line 44: @@
 A special empty MakeHuman clothes meta-file named clear.mhclo is is used to restore the default UV map that comes with the system.  In the lib folder, the filechooser.py module has a MhcloFileLoader.Refresh() method to clear materials when the refresh button is clicked.
 In the plugins folder,3_libraries_clothes_chooser.py, 3_libraries_eye_chooser.py, and 3_libraries_polygon_hair_chooser.py all access MHCLO files, but as of this writing, there are some file handling issues related to proxy clothes that means some of this code is commented out.  In the shared/export_utils folder, config.py accesses a cage.mhclo file.  In the tools folder, the tool ‘MakeClothes’ accesses MHCLO files in both the  makeclothes.py and material.py modules.  Similarly, the tool ‘MakeTarget‘ accesses MHCLO files in several of its modules:_init_.py, convert.py, import_obj.py, mt.py, ands ettings.py.  Finally, two experimental tools in the utils folder, the makeface.py and helpers.py modules access MCHO files.
 ==== .mhmat files ====