Dragon Age Toolset Wiki - User contributions [en]

Extending GDAs tutorial

2016-08-03T11:33:39Z

DarthParametric:

Dragon Age makes extensive use of [[2DA|2DAs]] to define things. As such, a fundamental requirement for many mods is editing the information contained within one or more 2DAs, be it changing existing values or adding additional content. As the game can only address a single copy of any one file, problems would occur if multiple mods each included edited copies of the same 2DA. Fortunately, the 2DA system makes provision for this via [[2DA#Extending_the_game_via_M2DAs|M2DAs]] (Multiple 2DA). This system allows most 2DAs to be ''extended'' (only replacing specific content/adding new content) rather than ''overridden'' (replacing the entire file). In this way, edits of a single 2DA across multiple mods can effectively stack without conflicting with one another.

A note on file formats/nomenclature. Whilst 2DAs are essentially just simple spreadsheets and the source files are provided in XLS (Excel) format, the game (and toolset) requires that they be encapsulated in the [[GFF]] formatted version known as [[GDA|GDAs]] in order to be useable.

== Overview ==

In order to illustrate the process of extending a GDA, we will use a set of armour as an example. Weapons and armour collectively are one of the most common types of mod, and both are functionally identical in terms of GDA extension. The general principles are also applicable to all other types of GDA extension.

In this particular instance, we will make a new set of massive armour comprising the chest piece, gloves, and boots. Rather than override the appearance of existing items, we will take advantage of GDA extension to add these to the game as an additional set of item appearances. In terms of DA items, this is referred to as adding a new variation. Note that a variation is just a physical appearance (i.e. a specific model and texture combination) and separate from the concept of an item in its in-game usage (i.e. stats and properties). A single item can use any of the different variations that have been defined for that particular item type by the appropriate GDA.

==Source File Preparation==
To begin with, we need the model files and associated textures. Models may be custom made, or, as in this example, simply renamed copies of base game models. In either case, it is important to follow the appropriate [[Naming_conventions#Items|DA naming conventions]]. The Human male models for our example will be named as follows:

{|
| Chest piece: || hm_arm_goldena_0
|-
| Boots: || hm_boo_goldena_0
|-
| Gloves: || hm_glv_goldena_0
|}

Models for LODs and other sex/races should follow the same format.

Now we need to obtain the relevant 2DAs. The source files for the game’s 2DAs are located in <DA install dir>\tools\Source\2DA\ and its sub-folders. For M2DAs, a list is given in the [[M2DA_base_2da|M2DA_base]] sheet of [[2DA_base.xls]]. Note that M2DA_base only lists the ''worksheet'' name, not the ''file'' name. As many 2DAs are often stored together as separate worksheets in a single file, particular 2DAs are sometimes difficult to locate due to obscure/unintuitive file naming on Bioware’s part. In these instances it may be more expedient to simply extract the compiled GDA version of the 2DA from the game files and convert it to an XLS using [http://social.bioware.com/project/755/ GDApp]. Alternatively, refer to this [[2da_matrix|table of 2DA files/worksheets]].

In this case we are interested in the worksheets armor_massive_variation, boots_massive_variation and gloves_heavy_variation. These can be found in [[ItemVariations.xls]], located in <DA install dir>\tools\Source\2DA\rules\. Rather than editing the source file, copy these 3 worksheets to a new file (keeping each to their own worksheet).

==2DA Editing==
Using the existing rows as a guide, add a new row to each sheet with the pertinent info for the corresponding model. This is why following the proper file naming convention is important. You can duplicate the cell values of the existing rows for the icon, material and sound columns. The label column dictates what name for the variation will appear in the toolset, so use a value in this cell that is descriptive enough to recognise later. Finally, we need to add a custom ID number for each row. The original intention for this system was to allow IDs to range up into the billions, thereby reducing the likelihood of incompatibilities between mods due to ID clashes. Unfortunately, due to the [[Bug:_High_M2DA_ID_ranges_might_work_in_the_toolset,_but_not_in_game|presence of a bug]] in the GFF item file format (UTI), items can only use IDs up to 255. '''''Therefore, if you are releasing your mod publicly there is a high likelihood of it being incompatible with some other mods due to ID clashes.''''' Bearing this in mind, choose a suitable ID higher than the existing values but below 255 for each sheet. These don’t have to be the same – each ID number is only relevant to the specific item class of its associated variation 2DA.

Once each worksheet has a fully filled out row for each of your new item variations, you can delete the other existing rows ''except for the two header rows''. You should be left with something like this:

{| class="wikitable"
|+ Extended armor_massive_variation Worksheet
! scope="col" | ID
! scope="col" | LABEL
! scope="col" | MODELTYPE
! scope="col" | MODELSUBTYPE
! scope="col" | MODELVARIATION
! scope="col" | ICONNAME
! scope="col" | DEFAULTMATERIAL
! scope="col" | SoundMatType
|-
| int
| string
| string
| string
| string
| string
| int
| int
|-
| 105
| Golden Armour
| arm
| golden
| a
| ****
| 2
| 13
|}

{| class="wikitable"
|+ Extended gloves_massive_variation Worksheet
! scope="col" | ID
! scope="col" | LABEL
! scope="col" | MODELTYPE
! scope="col" | MODELSUBTYPE
! scope="col" | MODELVARIATION
! scope="col" | ICONNAME
! scope="col" | DEFAULTMATERIAL
|-
| int
| string
| string
| string
| string
| string
| int
|-
| 105
| Golden Gloves
| glv
| golden
| a
| ****
| 2
|}

{| class="wikitable"
|+ Extended boots_massive_variation Worksheet
! scope="col" | ID
! scope="col" | LABEL
! scope="col" | MODELTYPE
! scope="col" | MODELSUBTYPE
! scope="col" | MODELVARIATION
! scope="col" | ICONNAME
! scope="col" | DEFAULTMATERIAL
|-
| int
| string
| string
| string
| string
| string
| int
|-
| 105
| Golden Boots
| boo
| golden
| a
| ****
| 2
|}

The final remaining step is to give each worksheet an appropriate name. In accordance with the M2DA system, each worksheet name must have a unique epithet appended to it. However, the character limit for the full worksheet name is capped at 27. Because the epithet must be prefixed with an underscore, many extended variation GDAs only have room for extremely short epithets. In the case of the current example, the chest piece and boots worksheet names both have 23 characters, whilst the gloves worksheet has 24. With 1 character lost to the underscore, that leaves 3 characters available for the former and only 2 for the latter. In the current example, the following was chosen:

armor_massive_variation_gld

boots_massive_variation_gld

gloves_massive_variation_gd

'''''N.B. As with the ID number bug, the restrictions of the epithet length greatly increase the likelihood of clashes in some instances, so keep this in mind if publicly releasing a mod.'''''

== Compiling GDAs ==

With the 2DA worksheet editing finished, they now need to be compiled into the GDA format so that they are useable by the game and toolset. Move/paste a copy of the XLS into <DA install dir>\tools\ResourceBuild\Processors\ and then drag and drop it over ExcelProcessor.exe. A command-line window (i.e. DOS box) will briefly appear. If there are no problems, the window will close and one GDA for each worksheet will appear in the folder. If the window stays open, there has been some sort of error, which the processor should detail (commonly worksheet names longer than 27 characters). If this is the case, fix the XLS and try again.

The GDAs can now be moved to the appropriate folder for your Addin. You may first wish to check them with [http://social.bioware.com/project/755/ GDApp] to confirm all the values are correct. GDApp will allow you to edit GDAs directly, saving the need for recompiling from source XLS files.

== Testing ==

With the toolset open and your module loaded, either open an existing item or create a new one. In either case, make sure it is the appropriate type for the variation/s you have created. Now you should be able to go to the Item Variation section and select your newly added variation from the drop-down list. If all went to plan, you should get something like this:

[[File:Extending_GDA_Toolset.jpg|500 px]]

If everything works as expected then you can export your items/module for use in the game. Make sure you test any content in the game before releasing it publicly.

[[File:Extending_GDA_Game_Test.jpg|500 px]]

== Troubleshooting ==

The two most likely issues to occur are either your variation not appearing in the drop-down list, or when selecting it for there to be no model present. Both can be caused by GDA issues, but the latter may also be caused by problems with the model/s.

If the variation doesn’t appear in the list, check that the GDA filename (i.e. 2DA worksheet name) is correct. Also check if there is a clash between your chosen ID number and those of any other mods you may have installed.

If there is no model visible when you select your variation in the toolset, ensure that your GDA specifies the correct model name/s. Also make sure that you have models for the specific race/sex combination you are making an item for. As you will have noticed, when adding the filename information to the 2DA, you don’t enter any MainClass (i.e. race/sex) detail. Thus, a single row makes provision for all race/sex combinations. Therefore the toolset will apply your variation to any item of that class, expecting there to be a model present. Additionally, when extending GDAs outside of items, be aware that you may have to extend multiple GDAs to get the toolset to recognise your custom content. This is primarily the case in instances such as custom monsters/races, where specific creature/part variation GDAs may need to be extended as well as the appearance GDA.

If your item appears in the toolset but not in the game, it is almost always due to the aforementioned high ID bug. Check your GDA and lower the ID number under 255 if necessary.

== Resources ==

The source material used for the above example is available [http://dpmods.wheb.org/files/dao/DAO_GDA_Extension_Example.7z here].

[[Category:Tutorials|Extending GDAs]]
[[Category:2DAs]]

Extending GDAs tutorial

2012-02-23T09:49:31Z

DarthParametric: Created page with "Dragon Age makes extensive use of 2DAs to define things. As such, a fundamental requirement for many mods is editing the information contained within one or more 2DAs, be..."

Dragon Age makes extensive use of [[2DA|2DAs]] to define things. As such, a fundamental requirement for many mods is editing the information contained within one or more 2DAs, be it changing existing values or adding additional content. As the game can only address a single copy of any one file, problems would occur if multiple mods each included edited copies of the same 2DA. Fortunately, the 2DA system makes provision for this via [[2DA#Extending_the_game_via_M2DAs|M2DAs]] (Multiple 2DA). This system allows most 2DAs to be ''extended'' (only replacing specific content/adding new content) rather than ''overridden'' (replacing the entire file). In this way, edits of a single 2DA across multiple mods can effectively stack without conflicting with one another.

A note on file formats/nomenclature. Whilst 2DAs are essentially just simple spreadsheets and the source files are provided in XLS (Excel) format, the game (and toolset) requires that they be encapsulated in the [[GFF]] formatted version known as [[GDA|GDAs]] in order to be useable.

__TOC__

==Overview==
In order to illustrate the process of extending a GDA, we will use a set of armour as an example. Weapons and armour collectively are one of the most common types of mod, and both are functionally identical in terms of GDA extension. The general principles are also applicable to all other types of GDA extension.

In this particular instance, we will make a new set of massive armour comprising the chest piece, gloves, and boots. Rather than override the appearance of existing items, we will take advantage of GDA extension to add these to the game as an additional set of item appearances. In terms of DA items, this is referred to as adding a new variation. Note that a variation is just a physical appearance (i.e. a specific model and texture combination) and separate from the concept of an item in its in-game usage (i.e. stats and properties). A single item can use any of the different variations that have been defined for that particular item type by the appropriate GDA.

==Source File Preparation==
To begin with, we need the model files and associated textures. Models may be custom made, or, as in this example, simply renamed copies of base game models. In either case, it is important to follow the appropriate [[Naming_conventions#Items|DA naming conventions]]. The Human male models for our example will be named as follows:

{|
| Chest piece: || hm_arm_goldena_0
|-
| Boots: || hm_boo_goldena_0
|-
| Gloves: || hm_glv_goldena_0
|}

Models for LODs and other sex/races should follow the same format.

Now we need to obtain the relevant 2DAs. The source files for the game’s 2DAs are located in <DA install dir>\tools\Source\2DA\ and its sub-folders. For M2DAs, a list is given in the [[M2DA_base_2da|M2DA_base]] sheet of [[2DA_base.xls]]. Note that M2DA_base only lists the ''worksheet'' name, not the ''file'' name. As many 2DAs are often stored together as separate worksheets in a single file, particular 2DAs are sometimes difficult to locate due to obscure/unintuitive file naming on Bioware’s part. In these instances it may be more expedient to simply extract the compiled GDA version of the 2DA from the game files and convert it to an XLS using [http://social.bioware.com/project/755/ GDApp]. Alternatively, refer to this [[2da_matrix|table of 2DA files/worksheets]].

In this case we are interested in the worksheets armor_massive_variation, boots_massive_variation and gloves_heavy_variation. These can be found in [[ItemVariations.xls]], located in <DA install dir>\tools\Source\2DA\rules\. Rather than editing the source file, copy these 3 worksheets to a new file (keeping each to their own worksheet).

==2DA Editing==
Using the existing rows as a guide, add a new row to each sheet with the pertinent info for the corresponding model. This is why following the proper file naming convention is important. You can duplicate the cell values of the existing rows for the icon, material and sound columns. The label column dictates what name for the variation will appear in the toolset, so use a value in this cell that is descriptive enough to recognise later. Finally, we need to add a custom ID number for each row. The original intention for this system was to allow IDs to range up into the billions, thereby reducing the likelihood of incompatibilities between mods due to ID clashes. Unfortunately, due to the [[Bug:_High_M2DA_ID_ranges_might_work_in_the_toolset,_but_not_in_game|presence of a bug]] in the GFF item file format (UTI), items can only use IDs up to 255. '''''Therefore, if you are releasing your mod publicly there is a high likelihood of it being incompatible with some other mods due to ID clashes.''''' Bearing this in mind, choose a suitable ID higher than the existing values but below 255 for each sheet. These don’t have to be the same – each ID number is only relevant to the specific item class of its associated variation 2DA.

Once each worksheet has a fully filled out row for each of your new item variations, you can delete the other existing rows ''except for the two header rows''. You should be left with something like this:

{| border="1" cellpadding="5"
|+ Extended armor_massive_variation Worksheet
! scope="col" | ID
! scope="col" | LABEL
! scope="col" | MODELTYPE
! scope="col" | MODELSUBTYPE
! scope="col" | MODELVARIATION
! scope="col" | ICONNAME
! scope="col" | DEFAULTMATERIAL
! scope="col" | SoundMatType
|-
| int
| string
| string
| string
| string
| string
| int
| int
|-
| 105
| Golden Armour
| arm
| golden
| a
| ****
| 2
| 13
|}

{| border="1" cellpadding="5"
|+ Extended gloves_massive_variation Worksheet
! scope="col" | ID
! scope="col" | LABEL
! scope="col" | MODELTYPE
! scope="col" | MODELSUBTYPE
! scope="col" | MODELVARIATION
! scope="col" | ICONNAME
! scope="col" | DEFAULTMATERIAL
|-
| int
| string
| string
| string
| string
| string
| int
|-
| 105
| Golden Gloves
| glv
| golden
| a
| ****
| 2
|}

{| border="1" cellpadding="5"
|+ Extended boots_massive_variation Worksheet
! scope="col" | ID
! scope="col" | LABEL
! scope="col" | MODELTYPE
! scope="col" | MODELSUBTYPE
! scope="col" | MODELVARIATION
! scope="col" | ICONNAME
! scope="col" | DEFAULTMATERIAL
|-
| int
| string
| string
| string
| string
| string
| int
|-
| 105
| Golden Boots
| boo
| golden
| a
| ****
| 2
|}

The final remaining step is to give each worksheet an appropriate name. In accordance with the M2DA system, each worksheet name must have a unique epithet appended to it. However, the character limit for the full worksheet name is capped at 27. Because the epithet must be prefixed with an underscore, many extended variation GDAs only have room for extremely short epithets. In the case of the current example, the chest piece and boots worksheet names both have 23 characters, whilst the gloves worksheet has 24. With 1 character lost to the underscore, that leaves 3 characters available for the former and only 2 for the latter. In the current example, the following was chosen:

armor_massive_variation_gld

boots_massive_variation_gld

gloves_massive_variation_gd

'''''N.B. As with the ID number bug, the restrictions of the epithet length greatly increase the likelihood of clashes in some instances, so keep this in mind if publicly releasing a mod.'''''

==Compiling GDAs==
With the 2DA worksheet editing finished, they now need to be compiled into the GDA format so that they are useable by the game and toolset. Move/paste a copy of the XLS into <DA install dir>\tools\ResourceBuild\Processors\ and then drag and drop it over ExcelProcessor.exe. A command-line window (i.e. DOS box) will briefly appear. If there are no problems, the window will close and one GDA for each worksheet will appear in the folder. If the window stays open, there has been some sort of error, which the processor should detail (commonly worksheet names longer than 27 characters). If this is the case, fix the XLS and try again.

The GDAs can now be moved to the appropriate folder for your Addin. You may first wish to check them with [http://social.bioware.com/project/755/ GDApp] to confirm all the values are correct. GDApp will allow you to edit GDAs directly, saving the need for recompiling from source XLS files.

==Testing==
With the toolset open and your module loaded, either open an existing item or create a new one. In either case, make sure it is the appropriate type for the variation/s you have created. Now you should be able to go to the Item Variation section and select your newly added variation from the drop-down list. If all went to plan, you should get something like this:

[[File:Extending_GDA_Toolset.jpg|500 px]]

If everything works as expected then you can export your items/module for use in the game. Make sure you test any content in the game before releasing it publicly.

[[File:Extending_GDA_Game_Test.jpg|500 px]]

==Troubleshooting==
The two most likely issues to occur are either your variation not appearing in the drop-down list, or when selecting it for there to be no model present. Both can be caused by GDA issues, but the latter may also be caused by problems with the model/s.

If the variation doesn’t appear in the list, check that the GDA filename (i.e. 2DA worksheet name) is correct. Also check if there is a clash between your chosen ID number and those of any other mods you may have installed.

If there is no model visible when you select your variation in the toolset, ensure that your GDA specifies the correct model name/s. Also make sure that you have models for the specific race/sex combination you are making an item for. As you will have noticed, when adding the filename information to the 2DA, you don’t enter any MainClass (i.e. race/sex) detail. Thus, a single row makes provision for all race/sex combinations. Therefore the toolset will apply your variation to any item of that class, expecting there to be a model present. Additionally, when extending GDAs outside of items, be aware that you may have to extend multiple GDAs to get the toolset to recognise your custom content. This is primarily the case in instances such as custom monsters/races, where specific creature/part variation GDAs may need to be extended as well as the appearance GDA.

If your item appears in the toolset but not in the game, it is almost always due to the aforementioned high ID bug. Check your GDA and lower the ID number under 255 if necessary.

==Resources==
The source material used for the above example is available [http://social.bioware.com/bw_projects_file_download.php?project_file_id=11633 here].

File:Extending GDA Game Test.jpg

2012-02-23T09:23:40Z

DarthParametric: In-game testing of an item using a custom variation

In-game testing of an item using a custom variation

File:Extending GDA Toolset.jpg

2012-02-23T07:40:38Z

DarthParametric: Result of an extended variation GDA in the toolset

Result of an extended variation GDA in the toolset

PRCSCR Script Templates

2011-09-04T08:03:50Z

DarthParametric: Added missing quotation marks around $ContainerTag$ in existing vendor/container script

This page serves as a repository for ready to use M2DA's and Scripts to use in conjunction with [[PRCSCR]] M2DA's when adding custom content to the game.

References:
*See Main Article: ''[[PRCSCR]]''
*See ''[[PRCSCR.xls]]'' for details about that M2DA, or ''[[2DA]]'' for an explanation of 2DA's as a whole
*To create a Script, right click in the Resourcepalette and select "New/Script" , or see ''[[Designer Resources]]'' for such Resources as a whole.


__NOTOC__
'''Contents:'''
{| style="background-color:#eeeeee; border:2px #999999 solid; padding:4px; margin:4px" border="3"
| width=300 |[[PRCSCR Script Templates#Adding a placeable into an existing Area|1. Adding a placeable into an existing Area]]
| width=800 |This Script serves to add a placeable of your choice into an Area of choice. ''(non removable)''
|-
| [[PRCSCR Script Templates#Adding a NPC into an existing Area|2. Adding a NPC into an existing Area]]
| This Script serves to any custom NPC or Creature to a Area of choice. ''(removable)''
|-
| [[PRCSCR Script Templates#Activating a Waypoint on the Worldmap|3. Activating a Waypoint on the Worldmap]]
| This Script serves to activate a custom Waypoint (Map Pin) of choice ,when leaving Lothering or at any other time into the Game.
|-
| [[PRCSCR Script Templates#Adding an Item into the Players Inventory|4. Adding an Item into the Players Inventory]]
| This Script serves to instantly add an Item into the Players Inventory.
|-
| [[PRCSCR Script Templates#Adding an Item to an existing Vendor or Container|5. Adding an Item to an existing Vendor or Container]]
| This Script serves to add any Item into a existing Vendors Inventory, as long the Vendor exists.
|-
| 6. Adding a Working Door into an existing Area
| This Script serves to add a custom Door into a existing Area, that the Player can enter into a custom Area.
|-
| 7. Adding a Quest to an existing Chanters Board
| This Script serves to add a new Quest to a existing Chanters Board, at any chosen time into the Game.
|-
| 8. ...
| ...
|}

== Adding a placeable into an existing Area ==

'''M2DA Setup:'''

#AreaListName must not be "any". Chose a specific one.
#Copy the GDA into your modules override folder.

'''Script:''' (As taken from the Storage Chest mod a kind Bioware employee made :o)

<dascript>
//const string TAL_STORAGE_CHEST_SPAWNED = "TAL_STORAGE_CHEST_SPAWNED";
const string TAL_IP_STORAGE_CHEST = "tal_ip_storage_chest";
const resource TAL_RESOURCE_IP_STORAGE_CHEST = R"tal_ip_storage_chest.utp";

void main()
{
object oMainControlled = GetMainControlled();
object oChest = UT_GetNearestObjectByTag(oMainControlled, TAL_IP_STORAGE_CHEST);

//DisplayFloatyMessage(oMainControlled, "storage script working", FLOATY_MESSAGE, 16777215, 30.0);

if (!IsObjectValid(oChest))
{
location lSpawn = Location(GetArea(oMainControlled), Vector(148.77, 117.68, -0.94), 0.0);
CreateObject(OBJECT_TYPE_PLACEABLE, TAL_RESOURCE_IP_STORAGE_CHEST, lSpawn);

//DisplayFloatyMessage(oMainControlled, "storage chest created", FLOATY_MESSAGE, 16777215, 30.0);
}
}
</dascript>

#Replace "tal_ip_storage_chest" in the 2nd line with the "Tag" of your own placeable. (only small letters allowed)
#Replace "tal_ip_storage_chest.utp" in 3rd line with the Resources Filename of your placable.
#Exchange the (4) numbers after it sais "Vector" ,which should be the location of your placable. How to determine?
#Create a temporary duplicate of the specific Area, and add the placeable until you see fit. (delete this Area afterwards, do not export)
#Note down the numbers in the Object Inspector, and get the first 3 numbers of Position, and the 4rth Number from Rotation. (only 1 number, the first)
#Rotation needs to be recalculated before entering it into the script. For positive angles do (180-angle). For negative angles do (-180-(-angle)).

Export the script, the placeable ,and start the game. When you arrive at the specific Area in game, the Placeable will be there.

'''Note:''' This method prevents removal of the placable. Check out a Plot driven method.

== Adding a NPC into an existing Area ==

'''M2DA Setup:'''

#AreaListName must be "any". This Script is Plot driven.
#Copy the GDA into your modules override folder.

'''Script:'''

<dascript>
// this is the name of a precreated plot file "joblos_quest" prefixed with the special "plt_"
// "plt_" + quest name allows you to reference the flag names as constants.
#include "plt_joblos_quest"
#include "wrappers_h"

void main()
{
//Check whether we've added Joblo already.
if (WR_GetPlotFlag(PLT_JOBLOS_QUEST, JOBLO_ADDED_TO_TOWN) == FALSE)
{
object oTown = GetObjectByTag("lot100ar_lothering"); //An area's tag is the same as its resource name
vector vJobloLocation = Vector(126.745f, 120.724f, 0.460568f); // See below for how to get these coordinates

CreateObject(
OBJECT_TYPE_CREATURE,
R"joblo.utc",
Location(oTown, vJobloLocation, 180.0f) //See below for how to get the value for orientation
); //this semicolom was missing and caused errors

WR_SetPlotFlag("joblos_quest", JOBLO_ADDED_TO_TOWN, TRUE);
}
}
</dascript>

#Replace "joblos_quest" (3x) with the name of your Plot.
#Replace "JOBLO_ADDED_TO_TOWN" (2x) with a custom Flag you create in your Plot.
#Replace "lot100ar_lothering" with the Tag of an Area ,the NPC should spawn in.
#Replace "joblo.utc" with the filename of your [[Creature]].
#Exchange the (4) numbers ,which should be the location of your placable. How to determine?
#Create a temporary duplicate of the specific Area, and add the NPC until you see fit. (delete this Area afterwards, do not export)
#Note down the numbers in the Object Inspector, and get the first 3 numbers of Position, and the 4rth Number from Rotation. (only 1 number, the first)
#Rotation needs to be recalculated before entering it into the script. For positive angles do (180-angle). For negative angles do (-180-(-angle)).

Export the script, the creature ,and start the game. When you arrive at the specific Area in game, the [[Creature]] (Monsters or NPCs alike) will be there.

== Activating a Waypoint on the Worldmap ==

'''Requirements:''' Your module must extend Single Player.

'''M2DA Setup:'''

#AreaListName must be "any". Because Waypoint activation should be universal and it is Plot driven.
#Copy the GDA into your modules override folder.

'''Script:'''
<dascript>
const string WML_WOW_Custom = "eshmeswp";
#include "plt_mnp000pt_main_events"
#include "wrappers_h"
void main()
{
if(WR_GetPlotFlag( PLT_MNP000PT_MAIN_EVENTS, ARCHDEMON_EVENT_ONE) == TRUE )
{
WR_SetWorldMapLocationStatus(GetObjectByTag(WML_WOW_Custom), WM_LOCATION_ACTIVE);
}
}
</dascript>

#Replace "eshmeswp" in the 1st line with the "Tag" of your Waypoint (Map Pin) which u created. That Map Pin can be greyed out or inactive or so. Map Pin information can be found at: [[Map]].

Export the script, the Map ,and start the game. The Waypoint will now be activated once you leave Lothering, just like the other main Waypoints. This is to get in line with the Story. However to change the time of it happening..

#Choose which [[Plot]] should activate the Waypoint. The above example uses the Archdemon quest, when your nightmare triggers for example.
#Exchange "mnp000pt_main_events" in the 2nd and 6th line with the name of that other [[Plot]]. Leaving the "plt_" there.
#Exchange "ARCHDEMON_EVENT_ONE" with a "Flag" of your choice from that Plot.

This "should" work for any plot. Actually, waypoints dont need all this PRCSCR stuff and can be set "Active" in the first place. But the above example is to get in line with the Main Campaign, and potential gamebreaking Plot conflicts if able to leave Lothering too early.

== Adding an Item into the Players Inventory ==

'''Requirements:'''

'''M2DA Setup:'''
#AreaListName is "any".
#Copy the GDA into your modules override folder.

'''Script:'''
<dascript>
//include utility_h for the UT_AddItemToInventory() function.
#include "utility_h"
//include the custom made plot file
#include "plt_$plot_file_name$"

void main()
{
// If plot flag is TRUE then item already given.
// Otherwise add item to inventory.
if ( WR_GetPlotFlag( PLT_$plot_file_name$, $check_flag_name$ ) == FALSE )
{
UT_AddItemToInventory(R"$item_file_name$.uti");
//Set the plot flag to TRUE to indicate that the item was given.
WR_SetPlotFlag( PLT_$plot_file_name$, $check_flag_name$, TRUE );
}
}
</dascript>
# Replace everything between and including the $ signs with appropriate names (without the file extensions).

== Adding an Item to an existing Vendor or Container ==

'''Requirements:'''

'''M2DA Setup:'''

{| border="1"
! Campaign !! Container !! ContainerTag !! AreaListName
|-
|Origins || Bodahn || store_camp_bodahn || cam100ar_camp_plains
|-
|Origins || daytime King's Camp quartermaster || pre100sr_quartermaster || pre01al_kings_camp
|-
|Awakening || Yuriah || store_vgk100cr_merchant || vgk210ar_throne_room
|-
|Awakening || Party Chest in Vigil's Keep || vgk210ip_party_chest || vgk210ar_throne_room
|-
|Leliana's Song || first Lem encounter || store_lel00cr_lem || lel100ar_market
|}

#Create a [[PRCSCR.xls|PRCSCR M2DA override]] using the desired AreaListName from the above table
#Copy this new PRCSCR M2DA into your module's override folder (AddIns\{YourMod}\core\override)

'''Script:'''

<dascript>
#include "wrappers_h"
#include "plt_$plot_file_name$" // include your custom plot

void main()
{
if ( WR_GetPlotFlag( PLT_$plot_file_name$, $check_flag_name$ ) == TRUE ) return;

object oContainer = GetObjectByTag("$ContainerTag$");

if (IsObjectValid(oContainer))
{
CreateItemOnObject(R"$resource_name$.uti", oContainer, 1, "", TRUE); // repeat this for each item

WR_SetPlotFlag( PLT_$plot_file_name$, $check_flag_name$, TRUE );
}
}
</dascript>

#Replace "$plot_file_name$" and "$check_flag_name$" with the custom [[Plot#Scripting|plot and plot flags]] you create for your module.
#Replace "$resource_name$" with the resource name of your custom item.
#Replace "$ContainerTag$" with the desired container tag from the table in the M2DA setup section.
#The very first time you go to the party camp in Origins (after leaving Lothering) and view the Archdemon cutscene, this script will NOT run when using "cam100ar_camp_plains" as the AreaListName. This is because the cutscene version of the camp is actually a different area. In this case you must exit and return to the "normal" (non-cutscene) party camp for the script to run for the first time.

== Adding a Working Door into an existing Area ==

'''Requirements:'''

'''M2DA Setup:'''

'''Script:''' {{undocumented}}

== Adding a Quest to an existing Chanters Board ==

'''Requirements:'''

'''M2DA Setup:'''

'''Script:''' {{undocumented}}

[[category:tutorials]]
[[Category:Scripts]]
[[Category:Pages with example scripts]]

Talk:Chargenmorphcfg.xml

2010-12-24T09:56:43Z

DarthParametric:

The mod conflicts section appears to assume that mods should go in packages override. Is that a technical requirement here? See Compatibility page for a discussion of this issue [[User:Proleric1|Proleric1]] 09:44, 23 December 2010 (UTC)

Where anyone thinks mods should go is irrelevant (not to mention debatable in the first place). The simple fact is that the overwhelming majority of mods utilise the Override folder and will continue to do so, therefore there will be conflicts in cases where chargenmorphcfg.xml is utilised. There's no point just telling people to make Addins. [[User:DarthParametric|DarthParametric]] 17:40, 23 December 2010

OK, so there's no hard technical requirement to use packages override. Pragmatically, in this particular case, I see the argument that compatibility can be achieved by merging what other people have done in packages override. Presumably, the same result could be achieved by building a merged mod as an add-in which follows compatibility guidelines. Incidentally, I'd be interested to hear why you think the use of the folders which the toolset uses by default is questionable. Isn't this largely a matter of evidence rather than opinion? [[User:Proleric1|Proleric1]] 06:52, 24 December 2010 (UTC)

If a modder releases a single head morph preset, you're going to have a hard sell convincing them to spend time setting it up as an Addin for something so minor, not to mention that most end-users seem to baulk at the complexity of installing Addin-based mods anyway, judging from certain threads on the Social site. As long as a modder informs their end-users of the need to merge multiple chargenmorphcfg.xml files and how to do so, I see no issue with Override-based mods of this nature. If you want to add a section to the end telling people how to do it "properly", then do so. That's the whole point of a wiki, is it not? [[User:DarthParametric|DarthParametric]] 09:56, 24 December 2010

Talk:Chargenmorphcfg.xml

2010-12-23T17:42:00Z

DarthParametric:

Talk:Chargenmorphcfg.xml

2010-12-23T17:41:41Z

DarthParametric:

Talk:Chargenmorphcfg.xml

2010-12-23T17:40:00Z

DarthParametric:

Chargenmorphcfg.xml

2010-05-03T11:52:52Z

DarthParametric: /* Mod Conflicts */

Chargenmorphcfg.xml is the configuration file for the in-game character creator. It dictates what head [[morph]] presets ([[MOP]]), hairstyles, beards, tattoos, makeup and colour tints (for skin, hair, etc.) are available as selectable options. It is located in <install directory>\packages\core\data\misc.erf

=File Structure=

The contents of the default file are as follows:

<pre>
<?xml version="1.0" encoding="utf-8"?>
<morph_config>
<heads>
<human_male>
<resource name="HM_CPS_P01.mop"/>
<resource name="HM_CPS_P02.mop"/>
<resource name="HM_CPS_P03.mop"/>
<resource name="HM_CPS_P04.mop"/>
<resource name="HM_CPS_P05.mop"/>
<resource name="HM_CPS_P06.mop"/>
<resource name="HM_CPS_P07.mop"/>
<resource name="HM_CPS_P08.mop"/>
<resource name="HM_PCC_B01.mop"/>
</human_male>
<human_female>
<resource name="HF_CPS_P01.mop"/>
<resource name="HF_CPS_P02.mop"/>
<resource name="HF_CPS_P03.mop"/>
<resource name="HF_CPS_P04.mop"/>
<resource name="HF_CPS_P05.mop"/>
<resource name="HF_CPS_P06.mop"/>
<resource name="HF_CPS_P07.mop"/>
<resource name="HF_CPS_P08.mop"/>
<resource name="HF_PCC_B01.mop"/>
</human_female>
<dwarf_male>
<resource name="DM_CPS_P01.mop"/>
<resource name="DM_CPS_P02.mop"/>
<resource name="DM_CPS_P03.mop"/>
<resource name="DM_CPS_P04.mop"/>
<resource name="DM_CPS_P05.mop"/>
<resource name="DM_CPS_P06.mop"/>
<resource name="DM_CPS_P07.mop"/>
<resource name="DM_CPS_P08.mop"/>
<resource name="DM_PCC_B01.mop"/>
</dwarf_male>
<dwarf_female>
<resource name="DF_CPS_P01.mop"/>
<resource name="DF_CPS_P02.mop"/>
<resource name="DF_CPS_P03.mop"/>
<resource name="DF_CPS_P04.mop"/>
<resource name="DF_CPS_P05.mop"/>
<resource name="DF_CPS_P06.mop"/>
<resource name="DF_CPS_P07.mop"/>
<resource name="DF_CPS_P08.mop"/>
<resource name="DF_PCC_B01.mop"/>
</dwarf_female>
<elf_male>
<resource name="EM_CPS_P01.mop"/>
<resource name="EM_CPS_P02.mop"/>
<resource name="EM_CPS_P03.mop"/>
<resource name="EM_CPS_P04.mop"/>
<resource name="EM_CPS_P05.mop"/>
<resource name="EM_CPS_P06.mop"/>
<resource name="EM_CPS_P07.mop"/>
<resource name="EM_CPS_P08.mop"/>
<resource name="EM_PCC_B01.mop"/>
</elf_male>
<elf_female>
<resource name="EF_CPS_P01.mop"/>
<resource name="EF_CPS_P02.mop"/>
<resource name="EF_CPS_P03.mop"/>
<resource name="EF_CPS_P04.mop"/>
<resource name="EF_CPS_P05.mop"/>
<resource name="EF_CPS_P06.mop"/>
<resource name="EF_CPS_P07.mop"/>
<resource name="EF_CPS_P08.mop"/>
<resource name="EF_PCC_B01.mop"/>
</elf_female>
</heads>

<hairs>
<human_male>
<resource name="hm_har_blda_0" cut="0234"/>
<resource name="hm_har_ha1a_0" cut="1"/>
<resource name="hm_har_ha2a_0" cut="1"/>
<resource name="hm_har_ha3a_0" cut="1"/>
<resource name="hm_har_hb1a_0" cut="1"/>
<resource name="hm_har_hb2a_0" cut="1"/>
<resource name="hm_har_hb3a_0" cut="1"/>
<resource name="hm_har_hb4a_0" cut="1"/>
<resource name="hm_har_hc1a_0" cut="1"/>
<resource name="hm_har_hc2a_0" cut="1"/>
<resource name="hm_har_hc3a_0" cut="1"/>
<resource name="hm_har_hc4a_0" cut="1"/>
<resource name="hm_har_hd1a_0" cut="1"/>
<resource name="hm_har_hd2a_0" cut="1"/>
<resource name="hm_har_hd3a_0" cut="1"/>
<resource name="hm_har_hd4a_0" cut="0"/>
</human_male>
<human_female>
<resource name="hf_har_blda_0" cut="02"/>
<resource name="hf_har_ha1a_0" cut="1"/>
<resource name="hf_har_ha2a_0" cut="1"/>
<resource name="hf_har_ha3a_0" cut="1"/>
<resource name="hf_har_ha4a_0" cut="1"/>
<resource name="hf_har_hb1a_0" cut="1"/>
<resource name="hf_har_hb2a_0" cut="1"/>
<resource name="hf_har_hb3a_0" cut="1"/>
<resource name="hf_har_hb4a_0" cut="1"/>
<resource name="hf_har_hc1a_0" cut="1"/>
<resource name="hf_har_hc2a_0" cut="1"/>
<resource name="hf_har_hc3a_0" cut="1"/>
<resource name="hf_har_hc4a_0" cut="1"/>
<resource name="hf_har_hd1a_0" cut="1"/>
<resource name="hf_har_hd2a_0" cut="1"/>
<resource name="hf_har_hd3a_0" cut="1"/>
<resource name="hf_har_hd4a_0" cut="1"/>
</human_female>
<dwarf_male>
<resource name="dm_har_blda_0" cut="0234"/>
<resource name="dm_har_ha1a_0" cut="1"/>
<resource name="dm_har_ha2a_0" cut="1"/>
<resource name="dm_har_ha3a_0" cut="1"/>
<resource name="dm_har_hb1a_0" cut="1"/>
<resource name="dm_har_hb2a_0" cut="1"/>
<resource name="dm_har_hb3a_0" cut="1"/>
<resource name="dm_har_hb4a_0" cut="1"/>
<resource name="dm_har_hc1a_0" cut="1"/>
<resource name="dm_har_hc2a_0" cut="1"/>
<resource name="dm_har_hc3a_0" cut="1"/>
<resource name="dm_har_hc4a_0" cut="1"/>
<resource name="dm_har_hd1a_0" cut="1"/>
<resource name="dm_har_hd2a_0" cut="1"/>
<resource name="dm_har_hd3a_0" cut="1"/>
<resource name="dm_har_hd4a_0" cut="0"/>
</dwarf_male> 1
<dwarf_female>
<resource name="df_har_blda_0" cut="02"/>
<resource name="df_har_ha1a_0" cut="1"/>
<resource name="df_har_ha2a_0" cut="1"/>
<resource name="df_har_ha3a_0" cut="1"/>
<resource name="df_har_ha4a_0" cut="1"/>
<resource name="df_har_hb1a_0" cut="1"/>
<resource name="df_har_hb2a_0" cut="1"/>
<resource name="df_har_hb3a_0" cut="1"/>
<resource name="df_har_hb4a_0" cut="1"/>
<resource name="df_har_hc1a_0" cut="1"/>
<resource name="df_har_hc2a_0" cut="1"/>
<resource name="df_har_hc3a_0" cut="1"/>
<resource name="df_har_hc4a_0" cut="1"/>
<resource name="df_har_hd1a_0" cut="1"/>
<resource name="df_har_hd2a_0" cut="1"/>
<resource name="df_har_hd3a_0" cut="1"/>
<resource name="df_har_hd4a_0" cut="1"/>
</dwarf_female>
<elf_male>
<resource name="em_har_blda_0" cut="0234"/>
<resource name="em_har_ha1a_0" cut="1"/>
<resource name="em_har_ha2a_0" cut="1"/>
<resource name="em_har_ha3a_0" cut="1"/>
<resource name="em_har_hb1a_0" cut="1"/>
<resource name="em_har_hb2a_0" cut="1"/>
<resource name="em_har_hb3a_0" cut="1"/>
<resource name="em_har_hb4a_0" cut="1"/>
<resource name="em_har_hc1a_0" cut="1"/>
<resource name="em_har_hc2a_0" cut="1"/>
<resource name="em_har_hc3a_0" cut="1"/>
<resource name="em_har_hc4a_0" cut="1"/>
<resource name="em_har_hd1a_0" cut="1"/>
<resource name="em_har_hd2a_0" cut="1"/>
<resource name="em_har_hd3a_0" cut="1"/>
<resource name="em_har_hd4a_0" cut="0"/>
</elf_male>
<elf_female>
<resource name="ef_har_blda_0" cut="02"/>
<resource name="ef_har_ha1a_0" cut="1"/>
<resource name="ef_har_ha2a_0" cut="1"/>
<resource name="ef_har_ha3a_0" cut="1"/>
<resource name="ef_har_ha4a_0" cut="1"/>
<resource name="ef_har_hb1a_0" cut="1"/>
<resource name="ef_har_hb2a_0" cut="1"/>
<resource name="ef_har_hb3a_0" cut="1"/>
<resource name="ef_har_hb4a_0" cut="1"/>
<resource name="ef_har_hc1a_0" cut="1"/>
<resource name="ef_har_hc2a_0" cut="1"/>
<resource name="ef_har_hc3a_0" cut="1"/>
<resource name="ef_har_hc4a_0" cut="1"/>
<resource name="ef_har_hd1a_0" cut="1"/>
<resource name="ef_har_hd2a_0" cut="1"/>
<resource name="ef_har_hd3a_0" cut="1"/>
<resource name="ef_har_hd4a_0" cut="1"/>
</elf_female>
</hairs>

<beards>
<human_male>
<resource name=""/>
<resource name="hm_brd_b1a_0"/>
<resource name="hm_brd_b2a_0"/>
<resource name="hm_brd_b3a_0"/>
<resource name="hm_brd_b4a_0"/>
<resource name="hm_brd_b5a_0"/>
<resource name="hm_brd_b6a_0"/>
</human_male>
<dwarf_male>
<resource name=""/>
<resource name="dm_brd_b1a_0"/>
<resource name="dm_brd_b2a_0"/>
<resource name="dm_brd_b3a_0"/>
<resource name="dm_brd_b4a_0"/>
<resource name="dm_brd_b5a_0"/>
<resource name="dm_brd_b6a_0"/>
</dwarf_male>
</beards>

<hair_colors>
<resource name ="t3_har_wht"/>
<resource name ="t3_har_bln"/>
<resource name ="t3_har_dbl"/>
<resource name ="t3_har_org"/>
<resource name ="t3_har_red"/>
<resource name ="t3_har_lbr"/>
<resource name ="t3_har_rbr"/>
<resource name ="t3_har_dbr"/>
<resource name ="t3_har_blk"/>
</hair_colors>

<skin_colors>
<resource name="t1_skn_001"/>
<resource name="t1_skn_002"/>
<resource name="t1_skn_003"/>
<resource name="t1_skn_004"/>
<resource name="t1_skn_006"/>
<resource name="t1_skn_005"/>
<resource name="t1_skn_007"/>
</skin_colors>

<eyes_colors>
<resource name="t3_eye_ice"/>
<resource name="t3_eye_lbl"/>
<resource name="t3_eye_dbl"/>
<resource name="t3_eye_tea"/>
<resource name="t3_eye_grn"/>
<resource name="t3_eye_hzl"/>
<resource name="t3_eye_lbr"/>
<resource name="t3_eye_amb"/>
<resource name="t3_eye_dbr"/>
<resource name="t3_eye_gry"/>
<resource name="t3_eye_blk"/>
</eyes_colors>

<eyes_makeup_colors>
<resource name=""/>
<resource name="t1_mue_bl1"/>
<resource name="t1_mue_bl2"/>
<resource name="t1_mue_bl3"/>
<resource name="t1_mue_gn1"/>
<resource name="t1_mue_gn2"/>
<resource name="t1_mue_gn3"/>
<resource name="t1_mue_gr1"/>
<resource name="t1_mue_gr2"/>
<resource name="t1_mue_gr3"/>
<resource name="t1_mue_or1"/>
<resource name="t1_mue_or2"/>
<resource name="t1_mue_or3"/>
<resource name="t1_mue_pi1"/>
<resource name="t1_mue_pi2"/>
<resource name="t1_mue_pi3"/>
<resource name="t1_mue_pu1"/>
<resource name="t1_mue_pu2"/>
<resource name="t1_mue_pu3"/>
<resource name="t1_mue_re1"/>
<resource name="t1_mue_re2"/>
<resource name="t1_mue_re3"/>
<resource name="t1_mue_ro1"/>
<resource name="t1_mue_ro2"/>
<resource name="t1_mue_ro3"/>
<resource name="t1_mue_te1"/>
<resource name="t1_mue_te2"/>
<resource name="t1_mue_te3"/>
<resource name="t1_mue_ye1"/>
<resource name="t1_mue_ye2"/>
<resource name="t1_mue_ye3"/>
</eyes_makeup_colors>

<blush_makeup_colors>
<resource name=""/>
<resource name="t1_mub_br1"/>
<resource name="t1_mub_br2"/>
<resource name="t1_mub_br3"/>
<resource name="t1_mub_or1"/>
<resource name="t1_mub_or2"/>
<resource name="t1_mub_or3"/>
<resource name="t1_mub_pi1"/>
<resource name="t1_mub_pi2"/>
<resource name="t1_mub_pi3"/>
<resource name="t1_mub_pu1"/>
<resource name="t1_mub_pu2"/>
<resource name="t1_mub_pu3"/>
<resource name="t1_mub_re1"/>
<resource name="t1_mub_re2"/>
<resource name="t1_mub_re3"/>
<resource name="t1_mub_ro1"/>
<resource name="t1_mub_ro2"/>
<resource name="t1_mub_ro3"/>
<resource name="t1_mub_ta1"/>
<resource name="t1_mub_ta2"/>
<resource name="t1_mub_ta3"/>
<resource name="t1_mub_te1"/>
<resource name="t1_mub_te2"/>
<resource name="t1_mub_te3"/>
</blush_makeup_colors>

<lip_makeup_colors>
<resource name=""/>
<resource name="t1_mul_bk1"/>
<resource name="t1_mul_bk2"/>
<resource name="t1_mul_bk3"/>
<resource name="t1_mul_br1"/>
<resource name="t1_mul_br2"/>
<resource name="t1_mul_br3"/>
<resource name="t1_mul_pi1"/>
<resource name="t1_mul_pi2"/>
<resource name="t1_mul_pi3"/>
<resource name="t1_mul_pu1"/>
<resource name="t1_mul_pu2"/>
<resource name="t1_mul_pu3"/>
<resource name="t1_mul_re1"/>
<resource name="t1_mul_re2"/>
<resource name="t1_mul_re3"/>
<resource name="t1_mul_ro1"/>
<resource name="t1_mul_ro2"/>
<resource name="t1_mul_ro3"/>
<resource name="t1_mul_ta1"/>
<resource name="t1_mul_ta2"/>
<resource name="t1_mul_ta3"/>
<resource name="t1_mul_te1"/>
<resource name="t1_mul_te2"/>
<resource name="t1_mul_te3"/>
</lip_makeup_colors>

<brow_stubble_colors>
<resource name="t1_stb_wht"/>
<resource name="t1_stb_bln"/>
<resource name="t1_stb_dbl"/>
<resource name="t1_stb_org"/>
<resource name="t1_stb_red"/>
<resource name="t1_stb_lbr"/>
<resource name="t1_stb_rbr"/>
<resource name="t1_stb_dbr"/>
<resource name="t1_stb_blk"/>
</brow_stubble_colors>

<crew_cut_colors>
<resource name="t1_stb_wht"/>
<resource name="t1_stb_bln"/>
<resource name="t1_stb_dbl"/>
<resource name="t1_stb_org"/>
<resource name="t1_stb_red"/>
<resource name="t1_stb_lbr"/>
<resource name="t1_stb_rbr"/>
<resource name="t1_stb_dbr"/>
<resource name="t1_stb_blk"/>
</crew_cut_colors>

<tattoo_colors>
<resource name="T1_TAT_BLK"/>
<resource name="T1_TAT_GRY"/>
<resource name="T1_TAT_BRN"/>
<resource name="T1_TAT_DBR"/>
<resource name="T1_TAT_GRN"/>
<resource name="T1_TAT_DGN"/>
<resource name="T1_TAT_BLU"/>
<resource name="T1_TAT_DBL"/>
<resource name="T1_TAT_PUR"/>
<resource name="T1_TAT_DPU"/>
<resource name="T1_TAT_RED"/>
<resource name="T1_TAT_DRD"/>
<resource name="T1_TAT_ORG"/>
<resource name="T1_TAT_YEL"/>
<resource name="T1_TAT_PNK"/>
</tattoo_colors>

<tattoos>
<resource name="uh_tat_av1_0t"/>
<resource name="uh_tat_av2_0t"/>
<resource name="uh_tat_av3_0t"/>
<resource name="uh_tat_da1_0t"/>
<resource name="uh_tat_da2_0t"/>
<resource name="uh_tat_da3_0t"/>
<resource name="uh_tat_dw1_0t"/>
<resource name="uh_tat_dw2_0t"/>
<resource name="uh_tat_p01_0t"/>
</tattoos>

<skins>
<resource name="uh_hed_fema_0d"/>
<resource name="uh_hed_elfa_0d"/>
<resource name="uh_hed_kida_0d"/>
<resource name="uh_hed_masa_0d"/>
<resource name="uh_hed_dwfa_0d"/>
<resource name="uh_hed_quna_0d"/>
</skins>
</morph_config>
</pre>

==Section <heads>==
This section defines all of the head morph presets for each race and gender. Additional custom presets can be appended to the relevant list. The MOP file should be placed in the Override folder.

==Section <hairs>==
This section defines the various hair meshes for each race and gender. As with morph presets, additional custom hair meshes can be appended. The mesh files should be placed in the Override folder.

==Section <beards>==
This section defines the various beard meshes for each race (males only). Additional custom beard meshes can be appended. The mesh files should be placed in the Override folder.

==Section <xxx_colors>==
These sections define the tint files ([[TNT]]) used for hair, skin, eye, makeup and tattoo colours. Additional custom tints can be appended. The [[TNT]] files should be placed in the Override folder.

==Section <tattoos>==
This section appears to define the [[Texture_Formats#Tint_Map|tint maps]] used for facial tattoos. However, the files listed are not those actually used by the character creator. Thus, it is not possible to append or replace these with custom files. It would appear that tattoos are hardcoded or specified elsewhere and that this section is unused.

At this time the only known method to achieve custom tattoos in the in-game character generator is either through the use of custom head morph presets or by overriding the default [[Texture_Formats#Tint_Map|tint maps]] (by placing a custom [[Texture_Formats#Tint_Map|tint map]] of the appropriate file name in the Override folder). If you wish to override the defaults, the races/origins that the [[Texture_Formats#Tint_Map|tint maps]] are used for are as follows:

uh_pct_dc1_0t.dds - Dwarf Commoner 
uh_pmt_001_0t.dds - Dwarf Commoner 
uh_pct_dn1_0t.dds - Dwarf Noble 
uh_pct_h01_0t.dds - Human, Elf City/Mage 
uh_pct_h02_0t.dds - Human, Elf City/Mage 
uh_tat_ed1_0t.dds - Elf Dalish 
uh_tat_ed2_0t.dds - Elf Dalish 
uh_tat_ed3_0t.dds - Elf Dalish 
uh_tat_ed4_0t.dds - Elf Dalish 

==Section <skins>==
This section defines the skin [[Texture_Formats#Diffuse_Map|diffuse maps]]. Custom skin textures for each head morph are achieved by blending two skin textures together in amounts adjusted via sliders. Where the specific combinations of these skins for each race and gender are specified is unknown. Possibly it is hardcoded. Because of this, appending additional skin [[Texture_Formats#Diffuse_Map|diffuse maps]] is unlikely to have any effect. They can be overridden however, as described previously for [[Texture_Formats#Tint_Map|tint maps]].

=Mod Conflicts=
To avoid conflicts, there should only ever be one copy of chargenmorphcfg.xml in the Override folder. The game will ignore additional copies. A number of popular mods make edits to chargenmorphcfg.xml (e.g. Pineappletree's Vibrant Colors, Bidelle's Makeup Studio, CC Tints and Tones, More Hairstyles, etc.). If you install two or more of these mods you will need to delete extra copies of chargenmorphcfg.xml and edit the remaining copy to include the necessary additions for the other mods. To avoid having to manually edit the file, Terra_Ex created a program called [http://social.bioware.com/project/2440/ CharGenMorph Compiler]. This tool will search for multiple instances of chargenmorphcfg.xml in the user's Override folder and condense them into a single file.

[[Category:Character generation]]

Chargenmorphcfg.xml

2010-02-18T12:58:48Z

DarthParametric: /* Mod Conflicts */

Chargenmorphcfg.xml is the configuration file for the in-game character creator. It dictates what head [[morph]] presets ([[MOP]]), hairstyles, beards, tattoos, makeup and colour tints (for skin, hair, etc.) are available as selectable options. It is located in <install directory>\packages\core\data\misc.erf

=File Structure=

The contents of the default file are as follows:

<pre>
<?xml version="1.0" encoding="utf-8"?>
<morph_config>
<heads>
<human_male>
<resource name="HM_CPS_P01.mop"/>
<resource name="HM_CPS_P02.mop"/>
<resource name="HM_CPS_P03.mop"/>
<resource name="HM_CPS_P04.mop"/>
<resource name="HM_CPS_P05.mop"/>
<resource name="HM_CPS_P06.mop"/>
<resource name="HM_CPS_P07.mop"/>
<resource name="HM_CPS_P08.mop"/>
<resource name="HM_PCC_B01.mop"/>
</human_male>
<human_female>
<resource name="HF_CPS_P01.mop"/>
<resource name="HF_CPS_P02.mop"/>
<resource name="HF_CPS_P03.mop"/>
<resource name="HF_CPS_P04.mop"/>
<resource name="HF_CPS_P05.mop"/>
<resource name="HF_CPS_P06.mop"/>
<resource name="HF_CPS_P07.mop"/>
<resource name="HF_CPS_P08.mop"/>
<resource name="HF_PCC_B01.mop"/>
</human_female>
<dwarf_male>
<resource name="DM_CPS_P01.mop"/>
<resource name="DM_CPS_P02.mop"/>
<resource name="DM_CPS_P03.mop"/>
<resource name="DM_CPS_P04.mop"/>
<resource name="DM_CPS_P05.mop"/>
<resource name="DM_CPS_P06.mop"/>
<resource name="DM_CPS_P07.mop"/>
<resource name="DM_CPS_P08.mop"/>
<resource name="DM_PCC_B01.mop"/>
</dwarf_male>
<dwarf_female>
<resource name="DF_CPS_P01.mop"/>
<resource name="DF_CPS_P02.mop"/>
<resource name="DF_CPS_P03.mop"/>
<resource name="DF_CPS_P04.mop"/>
<resource name="DF_CPS_P05.mop"/>
<resource name="DF_CPS_P06.mop"/>
<resource name="DF_CPS_P07.mop"/>
<resource name="DF_CPS_P08.mop"/>
<resource name="DF_PCC_B01.mop"/>
</dwarf_female>
<elf_male>
<resource name="EM_CPS_P01.mop"/>
<resource name="EM_CPS_P02.mop"/>
<resource name="EM_CPS_P03.mop"/>
<resource name="EM_CPS_P04.mop"/>
<resource name="EM_CPS_P05.mop"/>
<resource name="EM_CPS_P06.mop"/>
<resource name="EM_CPS_P07.mop"/>
<resource name="EM_CPS_P08.mop"/>
<resource name="EM_PCC_B01.mop"/>
</elf_male>
<elf_female>
<resource name="EF_CPS_P01.mop"/>
<resource name="EF_CPS_P02.mop"/>
<resource name="EF_CPS_P03.mop"/>
<resource name="EF_CPS_P04.mop"/>
<resource name="EF_CPS_P05.mop"/>
<resource name="EF_CPS_P06.mop"/>
<resource name="EF_CPS_P07.mop"/>
<resource name="EF_CPS_P08.mop"/>
<resource name="EF_PCC_B01.mop"/>
</elf_female>
</heads>

<hairs>
<human_male>
<resource name="hm_har_blda_0" cut="0234"/>
<resource name="hm_har_ha1a_0" cut="1"/>
<resource name="hm_har_ha2a_0" cut="1"/>
<resource name="hm_har_ha3a_0" cut="1"/>
<resource name="hm_har_hb1a_0" cut="1"/>
<resource name="hm_har_hb2a_0" cut="1"/>
<resource name="hm_har_hb3a_0" cut="1"/>
<resource name="hm_har_hb4a_0" cut="1"/>
<resource name="hm_har_hc1a_0" cut="1"/>
<resource name="hm_har_hc2a_0" cut="1"/>
<resource name="hm_har_hc3a_0" cut="1"/>
<resource name="hm_har_hc4a_0" cut="1"/>
<resource name="hm_har_hd1a_0" cut="1"/>
<resource name="hm_har_hd2a_0" cut="1"/>
<resource name="hm_har_hd3a_0" cut="1"/>
<resource name="hm_har_hd4a_0" cut="0"/>
</human_male>
<human_female>
<resource name="hf_har_blda_0" cut="02"/>
<resource name="hf_har_ha1a_0" cut="1"/>
<resource name="hf_har_ha2a_0" cut="1"/>
<resource name="hf_har_ha3a_0" cut="1"/>
<resource name="hf_har_ha4a_0" cut="1"/>
<resource name="hf_har_hb1a_0" cut="1"/>
<resource name="hf_har_hb2a_0" cut="1"/>
<resource name="hf_har_hb3a_0" cut="1"/>
<resource name="hf_har_hb4a_0" cut="1"/>
<resource name="hf_har_hc1a_0" cut="1"/>
<resource name="hf_har_hc2a_0" cut="1"/>
<resource name="hf_har_hc3a_0" cut="1"/>
<resource name="hf_har_hc4a_0" cut="1"/>
<resource name="hf_har_hd1a_0" cut="1"/>
<resource name="hf_har_hd2a_0" cut="1"/>
<resource name="hf_har_hd3a_0" cut="1"/>
<resource name="hf_har_hd4a_0" cut="1"/>
</human_female>
<dwarf_male>
<resource name="dm_har_blda_0" cut="0234"/>
<resource name="dm_har_ha1a_0" cut="1"/>
<resource name="dm_har_ha2a_0" cut="1"/>
<resource name="dm_har_ha3a_0" cut="1"/>
<resource name="dm_har_hb1a_0" cut="1"/>
<resource name="dm_har_hb2a_0" cut="1"/>
<resource name="dm_har_hb3a_0" cut="1"/>
<resource name="dm_har_hb4a_0" cut="1"/>
<resource name="dm_har_hc1a_0" cut="1"/>
<resource name="dm_har_hc2a_0" cut="1"/>
<resource name="dm_har_hc3a_0" cut="1"/>
<resource name="dm_har_hc4a_0" cut="1"/>
<resource name="dm_har_hd1a_0" cut="1"/>
<resource name="dm_har_hd2a_0" cut="1"/>
<resource name="dm_har_hd3a_0" cut="1"/>
<resource name="dm_har_hd4a_0" cut="0"/>
</dwarf_male> 1
<dwarf_female>
<resource name="df_har_blda_0" cut="02"/>
<resource name="df_har_ha1a_0" cut="1"/>
<resource name="df_har_ha2a_0" cut="1"/>
<resource name="df_har_ha3a_0" cut="1"/>
<resource name="df_har_ha4a_0" cut="1"/>
<resource name="df_har_hb1a_0" cut="1"/>
<resource name="df_har_hb2a_0" cut="1"/>
<resource name="df_har_hb3a_0" cut="1"/>
<resource name="df_har_hb4a_0" cut="1"/>
<resource name="df_har_hc1a_0" cut="1"/>
<resource name="df_har_hc2a_0" cut="1"/>
<resource name="df_har_hc3a_0" cut="1"/>
<resource name="df_har_hc4a_0" cut="1"/>
<resource name="df_har_hd1a_0" cut="1"/>
<resource name="df_har_hd2a_0" cut="1"/>
<resource name="df_har_hd3a_0" cut="1"/>
<resource name="df_har_hd4a_0" cut="1"/>
</dwarf_female>
<elf_male>
<resource name="em_har_blda_0" cut="0234"/>
<resource name="em_har_ha1a_0" cut="1"/>
<resource name="em_har_ha2a_0" cut="1"/>
<resource name="em_har_ha3a_0" cut="1"/>
<resource name="em_har_hb1a_0" cut="1"/>
<resource name="em_har_hb2a_0" cut="1"/>
<resource name="em_har_hb3a_0" cut="1"/>
<resource name="em_har_hb4a_0" cut="1"/>
<resource name="em_har_hc1a_0" cut="1"/>
<resource name="em_har_hc2a_0" cut="1"/>
<resource name="em_har_hc3a_0" cut="1"/>
<resource name="em_har_hc4a_0" cut="1"/>
<resource name="em_har_hd1a_0" cut="1"/>
<resource name="em_har_hd2a_0" cut="1"/>
<resource name="em_har_hd3a_0" cut="1"/>
<resource name="em_har_hd4a_0" cut="0"/>
</elf_male>
<elf_female>
<resource name="ef_har_blda_0" cut="02"/>
<resource name="ef_har_ha1a_0" cut="1"/>
<resource name="ef_har_ha2a_0" cut="1"/>
<resource name="ef_har_ha3a_0" cut="1"/>
<resource name="ef_har_ha4a_0" cut="1"/>
<resource name="ef_har_hb1a_0" cut="1"/>
<resource name="ef_har_hb2a_0" cut="1"/>
<resource name="ef_har_hb3a_0" cut="1"/>
<resource name="ef_har_hb4a_0" cut="1"/>
<resource name="ef_har_hc1a_0" cut="1"/>
<resource name="ef_har_hc2a_0" cut="1"/>
<resource name="ef_har_hc3a_0" cut="1"/>
<resource name="ef_har_hc4a_0" cut="1"/>
<resource name="ef_har_hd1a_0" cut="1"/>
<resource name="ef_har_hd2a_0" cut="1"/>
<resource name="ef_har_hd3a_0" cut="1"/>
<resource name="ef_har_hd4a_0" cut="1"/>
</elf_female>
</hairs>

<beards>
<human_male>
<resource name=""/>
<resource name="hm_brd_b1a_0"/>
<resource name="hm_brd_b2a_0"/>
<resource name="hm_brd_b3a_0"/>
<resource name="hm_brd_b4a_0"/>
<resource name="hm_brd_b5a_0"/>
<resource name="hm_brd_b6a_0"/>
</human_male>
<dwarf_male>
<resource name=""/>
<resource name="dm_brd_b1a_0"/>
<resource name="dm_brd_b2a_0"/>
<resource name="dm_brd_b3a_0"/>
<resource name="dm_brd_b4a_0"/>
<resource name="dm_brd_b5a_0"/>
<resource name="dm_brd_b6a_0"/>
</dwarf_male>
</beards>

<hair_colors>
<resource name ="t3_har_wht"/>
<resource name ="t3_har_bln"/>
<resource name ="t3_har_dbl"/>
<resource name ="t3_har_org"/>
<resource name ="t3_har_red"/>
<resource name ="t3_har_lbr"/>
<resource name ="t3_har_rbr"/>
<resource name ="t3_har_dbr"/>
<resource name ="t3_har_blk"/>
</hair_colors>

<skin_colors>
<resource name="t1_skn_001"/>
<resource name="t1_skn_002"/>
<resource name="t1_skn_003"/>
<resource name="t1_skn_004"/>
<resource name="t1_skn_006"/>
<resource name="t1_skn_005"/>
<resource name="t1_skn_007"/>
</skin_colors>

<eyes_colors>
<resource name="t3_eye_ice"/>
<resource name="t3_eye_lbl"/>
<resource name="t3_eye_dbl"/>
<resource name="t3_eye_tea"/>
<resource name="t3_eye_grn"/>
<resource name="t3_eye_hzl"/>
<resource name="t3_eye_lbr"/>
<resource name="t3_eye_amb"/>
<resource name="t3_eye_dbr"/>
<resource name="t3_eye_gry"/>
<resource name="t3_eye_blk"/>
</eyes_colors>

<eyes_makeup_colors>
<resource name=""/>
<resource name="t1_mue_bl1"/>
<resource name="t1_mue_bl2"/>
<resource name="t1_mue_bl3"/>
<resource name="t1_mue_gn1"/>
<resource name="t1_mue_gn2"/>
<resource name="t1_mue_gn3"/>
<resource name="t1_mue_gr1"/>
<resource name="t1_mue_gr2"/>
<resource name="t1_mue_gr3"/>
<resource name="t1_mue_or1"/>
<resource name="t1_mue_or2"/>
<resource name="t1_mue_or3"/>
<resource name="t1_mue_pi1"/>
<resource name="t1_mue_pi2"/>
<resource name="t1_mue_pi3"/>
<resource name="t1_mue_pu1"/>
<resource name="t1_mue_pu2"/>
<resource name="t1_mue_pu3"/>
<resource name="t1_mue_re1"/>
<resource name="t1_mue_re2"/>
<resource name="t1_mue_re3"/>
<resource name="t1_mue_ro1"/>
<resource name="t1_mue_ro2"/>
<resource name="t1_mue_ro3"/>
<resource name="t1_mue_te1"/>
<resource name="t1_mue_te2"/>
<resource name="t1_mue_te3"/>
<resource name="t1_mue_ye1"/>
<resource name="t1_mue_ye2"/>
<resource name="t1_mue_ye3"/>
</eyes_makeup_colors>

<blush_makeup_colors>
<resource name=""/>
<resource name="t1_mub_br1"/>
<resource name="t1_mub_br2"/>
<resource name="t1_mub_br3"/>
<resource name="t1_mub_or1"/>
<resource name="t1_mub_or2"/>
<resource name="t1_mub_or3"/>
<resource name="t1_mub_pi1"/>
<resource name="t1_mub_pi2"/>
<resource name="t1_mub_pi3"/>
<resource name="t1_mub_pu1"/>
<resource name="t1_mub_pu2"/>
<resource name="t1_mub_pu3"/>
<resource name="t1_mub_re1"/>
<resource name="t1_mub_re2"/>
<resource name="t1_mub_re3"/>
<resource name="t1_mub_ro1"/>
<resource name="t1_mub_ro2"/>
<resource name="t1_mub_ro3"/>
<resource name="t1_mub_ta1"/>
<resource name="t1_mub_ta2"/>
<resource name="t1_mub_ta3"/>
<resource name="t1_mub_te1"/>
<resource name="t1_mub_te2"/>
<resource name="t1_mub_te3"/>
</blush_makeup_colors>

<lip_makeup_colors>
<resource name=""/>
<resource name="t1_mul_bk1"/>
<resource name="t1_mul_bk2"/>
<resource name="t1_mul_bk3"/>
<resource name="t1_mul_br1"/>
<resource name="t1_mul_br2"/>
<resource name="t1_mul_br3"/>
<resource name="t1_mul_pi1"/>
<resource name="t1_mul_pi2"/>
<resource name="t1_mul_pi3"/>
<resource name="t1_mul_pu1"/>
<resource name="t1_mul_pu2"/>
<resource name="t1_mul_pu3"/>
<resource name="t1_mul_re1"/>
<resource name="t1_mul_re2"/>
<resource name="t1_mul_re3"/>
<resource name="t1_mul_ro1"/>
<resource name="t1_mul_ro2"/>
<resource name="t1_mul_ro3"/>
<resource name="t1_mul_ta1"/>
<resource name="t1_mul_ta2"/>
<resource name="t1_mul_ta3"/>
<resource name="t1_mul_te1"/>
<resource name="t1_mul_te2"/>
<resource name="t1_mul_te3"/>
</lip_makeup_colors>

<brow_stubble_colors>
<resource name="t1_stb_wht"/>
<resource name="t1_stb_bln"/>
<resource name="t1_stb_dbl"/>
<resource name="t1_stb_org"/>
<resource name="t1_stb_red"/>
<resource name="t1_stb_lbr"/>
<resource name="t1_stb_rbr"/>
<resource name="t1_stb_dbr"/>
<resource name="t1_stb_blk"/>
</brow_stubble_colors>

<crew_cut_colors>
<resource name="t1_stb_wht"/>
<resource name="t1_stb_bln"/>
<resource name="t1_stb_dbl"/>
<resource name="t1_stb_org"/>
<resource name="t1_stb_red"/>
<resource name="t1_stb_lbr"/>
<resource name="t1_stb_rbr"/>
<resource name="t1_stb_dbr"/>
<resource name="t1_stb_blk"/>
</crew_cut_colors>

<tattoo_colors>
<resource name="T1_TAT_BLK"/>
<resource name="T1_TAT_GRY"/>
<resource name="T1_TAT_BRN"/>
<resource name="T1_TAT_DBR"/>
<resource name="T1_TAT_GRN"/>
<resource name="T1_TAT_DGN"/>
<resource name="T1_TAT_BLU"/>
<resource name="T1_TAT_DBL"/>
<resource name="T1_TAT_PUR"/>
<resource name="T1_TAT_DPU"/>
<resource name="T1_TAT_RED"/>
<resource name="T1_TAT_DRD"/>
<resource name="T1_TAT_ORG"/>
<resource name="T1_TAT_YEL"/>
<resource name="T1_TAT_PNK"/>
</tattoo_colors>

<tattoos>
<resource name="uh_tat_av1_0t"/>
<resource name="uh_tat_av2_0t"/>
<resource name="uh_tat_av3_0t"/>
<resource name="uh_tat_da1_0t"/>
<resource name="uh_tat_da2_0t"/>
<resource name="uh_tat_da3_0t"/>
<resource name="uh_tat_dw1_0t"/>
<resource name="uh_tat_dw2_0t"/>
<resource name="uh_tat_p01_0t"/>
</tattoos>

<skins>
<resource name="uh_hed_fema_0d"/>
<resource name="uh_hed_elfa_0d"/>
<resource name="uh_hed_kida_0d"/>
<resource name="uh_hed_masa_0d"/>
<resource name="uh_hed_dwfa_0d"/>
<resource name="uh_hed_quna_0d"/>
</skins>
</morph_config>
</pre>

==Section <heads>==
This section defines all of the head morph presets for each race and gender. Additional custom presets can be appended to the relevant list. The MOP file should be placed in the Override folder.

==Section <hairs>==
This section defines the various hair meshes for each race and gender. As with morph presets, additional custom hair meshes can be appended. The mesh files should be placed in the Override folder.

==Section <beards>==
This section defines the various beard meshes for each race (males only). Additional custom beard meshes can be appended. The mesh files should be placed in the Override folder.

==Section <xxx_colors>==
These sections define the tint files ([[TNT]]) used for hair, skin, eye, makeup and tattoo colours. Additional custom tints can be appended. The [[TNT]] files should be placed in the Override folder.

==Section <tattoos>==
This section appears to define the [[Texture_Formats#Tint_Map|tint maps]] used for facial tattoos. However, the files listed are not those actually used by the character creator. Thus, it is not possible to append or replace these with custom files. It would appear that tattoos are hardcoded or specified elsewhere and that this section is unused.

At this time the only known method to achieve custom tattoos in the in-game character generator is either through the use of custom head morph presets or by overriding the default [[Texture_Formats#Tint_Map|tint maps]] (by placing a custom [[Texture_Formats#Tint_Map|tint map]] of the appropriate file name in the Override folder). If you wish to override the defaults, the races/origins that the [[Texture_Formats#Tint_Map|tint maps]] are used for are as follows:

uh_pct_dc1_0t.dds - Dwarf Commoner 
uh_pmt_001_0t.dds - Dwarf Commoner 
uh_pct_dn1_0t.dds - Dwarf Noble 
uh_pct_h01_0t.dds - Human, Elf City/Mage 
uh_pct_h02_0t.dds - Human, Elf City/Mage 
uh_tat_ed1_0t.dds - Elf Dalish 
uh_tat_ed2_0t.dds - Elf Dalish 
uh_tat_ed3_0t.dds - Elf Dalish 
uh_tat_ed4_0t.dds - Elf Dalish 

==Section <skins>==
This section defines the skin [[Texture_Formats#Diffuse_Map|diffuse maps]]. Custom skin textures for each head morph are achieved by blending two skin textures together in amounts adjusted via sliders. Where the specific combinations of these skins for each race and gender are specified is unknown. Possibly it is hardcoded. Because of this, appending additional skin [[Texture_Formats#Diffuse_Map|diffuse maps]] is unlikely to have any effect. They can be overridden however, as described previously for [[Texture_Formats#Tint_Map|tint maps]].

=Mod Conflicts=
To avoid conflicts, there should only ever be one copy of chargenmorphcfg.xml in the Override folder. The game will ignore additional copies. A number of mods make edits to chargenmorphcfg.xml (e.g. Pineappletree's Vibrant Colors, Bidelle's Makeup Studio, CC Tints and Tones, More Hairstyles, etc.). If you install two or more of these mods you will need to delete extra copies of chargenmorphcfg.xml and edit the remaining copy to include the necessary additions for the other mods. Many mods now make pre-edited copies of chargenmorphcfg.xml available that encompass all the major appearance mods that require this file.

Chargenmorphcfg.xml

2010-02-18T12:56:56Z

DarthParametric: /* Section */

Chargenmorphcfg.xml is the configuration file for the in-game character creator. It dictates what head [[morph]] presets ([[MOP]]), hairstyles, beards, tattoos, makeup and colour tints (for skin, hair, etc.) are available as selectable options. It is located in <install directory>\packages\core\data\misc.erf

=File Structure=

The contents of the default file are as follows:

<pre>
<?xml version="1.0" encoding="utf-8"?>
<morph_config>
<heads>
<human_male>
<resource name="HM_CPS_P01.mop"/>
<resource name="HM_CPS_P02.mop"/>
<resource name="HM_CPS_P03.mop"/>
<resource name="HM_CPS_P04.mop"/>
<resource name="HM_CPS_P05.mop"/>
<resource name="HM_CPS_P06.mop"/>
<resource name="HM_CPS_P07.mop"/>
<resource name="HM_CPS_P08.mop"/>
<resource name="HM_PCC_B01.mop"/>
</human_male>
<human_female>
<resource name="HF_CPS_P01.mop"/>
<resource name="HF_CPS_P02.mop"/>
<resource name="HF_CPS_P03.mop"/>
<resource name="HF_CPS_P04.mop"/>
<resource name="HF_CPS_P05.mop"/>
<resource name="HF_CPS_P06.mop"/>
<resource name="HF_CPS_P07.mop"/>
<resource name="HF_CPS_P08.mop"/>
<resource name="HF_PCC_B01.mop"/>
</human_female>
<dwarf_male>
<resource name="DM_CPS_P01.mop"/>
<resource name="DM_CPS_P02.mop"/>
<resource name="DM_CPS_P03.mop"/>
<resource name="DM_CPS_P04.mop"/>
<resource name="DM_CPS_P05.mop"/>
<resource name="DM_CPS_P06.mop"/>
<resource name="DM_CPS_P07.mop"/>
<resource name="DM_CPS_P08.mop"/>
<resource name="DM_PCC_B01.mop"/>
</dwarf_male>
<dwarf_female>
<resource name="DF_CPS_P01.mop"/>
<resource name="DF_CPS_P02.mop"/>
<resource name="DF_CPS_P03.mop"/>
<resource name="DF_CPS_P04.mop"/>
<resource name="DF_CPS_P05.mop"/>
<resource name="DF_CPS_P06.mop"/>
<resource name="DF_CPS_P07.mop"/>
<resource name="DF_CPS_P08.mop"/>
<resource name="DF_PCC_B01.mop"/>
</dwarf_female>
<elf_male>
<resource name="EM_CPS_P01.mop"/>
<resource name="EM_CPS_P02.mop"/>
<resource name="EM_CPS_P03.mop"/>
<resource name="EM_CPS_P04.mop"/>
<resource name="EM_CPS_P05.mop"/>
<resource name="EM_CPS_P06.mop"/>
<resource name="EM_CPS_P07.mop"/>
<resource name="EM_CPS_P08.mop"/>
<resource name="EM_PCC_B01.mop"/>
</elf_male>
<elf_female>
<resource name="EF_CPS_P01.mop"/>
<resource name="EF_CPS_P02.mop"/>
<resource name="EF_CPS_P03.mop"/>
<resource name="EF_CPS_P04.mop"/>
<resource name="EF_CPS_P05.mop"/>
<resource name="EF_CPS_P06.mop"/>
<resource name="EF_CPS_P07.mop"/>
<resource name="EF_CPS_P08.mop"/>
<resource name="EF_PCC_B01.mop"/>
</elf_female>
</heads>

<hairs>
<human_male>
<resource name="hm_har_blda_0" cut="0234"/>
<resource name="hm_har_ha1a_0" cut="1"/>
<resource name="hm_har_ha2a_0" cut="1"/>
<resource name="hm_har_ha3a_0" cut="1"/>
<resource name="hm_har_hb1a_0" cut="1"/>
<resource name="hm_har_hb2a_0" cut="1"/>
<resource name="hm_har_hb3a_0" cut="1"/>
<resource name="hm_har_hb4a_0" cut="1"/>
<resource name="hm_har_hc1a_0" cut="1"/>
<resource name="hm_har_hc2a_0" cut="1"/>
<resource name="hm_har_hc3a_0" cut="1"/>
<resource name="hm_har_hc4a_0" cut="1"/>
<resource name="hm_har_hd1a_0" cut="1"/>
<resource name="hm_har_hd2a_0" cut="1"/>
<resource name="hm_har_hd3a_0" cut="1"/>
<resource name="hm_har_hd4a_0" cut="0"/>
</human_male>
<human_female>
<resource name="hf_har_blda_0" cut="02"/>
<resource name="hf_har_ha1a_0" cut="1"/>
<resource name="hf_har_ha2a_0" cut="1"/>
<resource name="hf_har_ha3a_0" cut="1"/>
<resource name="hf_har_ha4a_0" cut="1"/>
<resource name="hf_har_hb1a_0" cut="1"/>
<resource name="hf_har_hb2a_0" cut="1"/>
<resource name="hf_har_hb3a_0" cut="1"/>
<resource name="hf_har_hb4a_0" cut="1"/>
<resource name="hf_har_hc1a_0" cut="1"/>
<resource name="hf_har_hc2a_0" cut="1"/>
<resource name="hf_har_hc3a_0" cut="1"/>
<resource name="hf_har_hc4a_0" cut="1"/>
<resource name="hf_har_hd1a_0" cut="1"/>
<resource name="hf_har_hd2a_0" cut="1"/>
<resource name="hf_har_hd3a_0" cut="1"/>
<resource name="hf_har_hd4a_0" cut="1"/>
</human_female>
<dwarf_male>
<resource name="dm_har_blda_0" cut="0234"/>
<resource name="dm_har_ha1a_0" cut="1"/>
<resource name="dm_har_ha2a_0" cut="1"/>
<resource name="dm_har_ha3a_0" cut="1"/>
<resource name="dm_har_hb1a_0" cut="1"/>
<resource name="dm_har_hb2a_0" cut="1"/>
<resource name="dm_har_hb3a_0" cut="1"/>
<resource name="dm_har_hb4a_0" cut="1"/>
<resource name="dm_har_hc1a_0" cut="1"/>
<resource name="dm_har_hc2a_0" cut="1"/>
<resource name="dm_har_hc3a_0" cut="1"/>
<resource name="dm_har_hc4a_0" cut="1"/>
<resource name="dm_har_hd1a_0" cut="1"/>
<resource name="dm_har_hd2a_0" cut="1"/>
<resource name="dm_har_hd3a_0" cut="1"/>
<resource name="dm_har_hd4a_0" cut="0"/>
</dwarf_male> 1
<dwarf_female>
<resource name="df_har_blda_0" cut="02"/>
<resource name="df_har_ha1a_0" cut="1"/>
<resource name="df_har_ha2a_0" cut="1"/>
<resource name="df_har_ha3a_0" cut="1"/>
<resource name="df_har_ha4a_0" cut="1"/>
<resource name="df_har_hb1a_0" cut="1"/>
<resource name="df_har_hb2a_0" cut="1"/>
<resource name="df_har_hb3a_0" cut="1"/>
<resource name="df_har_hb4a_0" cut="1"/>
<resource name="df_har_hc1a_0" cut="1"/>
<resource name="df_har_hc2a_0" cut="1"/>
<resource name="df_har_hc3a_0" cut="1"/>
<resource name="df_har_hc4a_0" cut="1"/>
<resource name="df_har_hd1a_0" cut="1"/>
<resource name="df_har_hd2a_0" cut="1"/>
<resource name="df_har_hd3a_0" cut="1"/>
<resource name="df_har_hd4a_0" cut="1"/>
</dwarf_female>
<elf_male>
<resource name="em_har_blda_0" cut="0234"/>
<resource name="em_har_ha1a_0" cut="1"/>
<resource name="em_har_ha2a_0" cut="1"/>
<resource name="em_har_ha3a_0" cut="1"/>
<resource name="em_har_hb1a_0" cut="1"/>
<resource name="em_har_hb2a_0" cut="1"/>
<resource name="em_har_hb3a_0" cut="1"/>
<resource name="em_har_hb4a_0" cut="1"/>
<resource name="em_har_hc1a_0" cut="1"/>
<resource name="em_har_hc2a_0" cut="1"/>
<resource name="em_har_hc3a_0" cut="1"/>
<resource name="em_har_hc4a_0" cut="1"/>
<resource name="em_har_hd1a_0" cut="1"/>
<resource name="em_har_hd2a_0" cut="1"/>
<resource name="em_har_hd3a_0" cut="1"/>
<resource name="em_har_hd4a_0" cut="0"/>
</elf_male>
<elf_female>
<resource name="ef_har_blda_0" cut="02"/>
<resource name="ef_har_ha1a_0" cut="1"/>
<resource name="ef_har_ha2a_0" cut="1"/>
<resource name="ef_har_ha3a_0" cut="1"/>
<resource name="ef_har_ha4a_0" cut="1"/>
<resource name="ef_har_hb1a_0" cut="1"/>
<resource name="ef_har_hb2a_0" cut="1"/>
<resource name="ef_har_hb3a_0" cut="1"/>
<resource name="ef_har_hb4a_0" cut="1"/>
<resource name="ef_har_hc1a_0" cut="1"/>
<resource name="ef_har_hc2a_0" cut="1"/>
<resource name="ef_har_hc3a_0" cut="1"/>
<resource name="ef_har_hc4a_0" cut="1"/>
<resource name="ef_har_hd1a_0" cut="1"/>
<resource name="ef_har_hd2a_0" cut="1"/>
<resource name="ef_har_hd3a_0" cut="1"/>
<resource name="ef_har_hd4a_0" cut="1"/>
</elf_female>
</hairs>

<beards>
<human_male>
<resource name=""/>
<resource name="hm_brd_b1a_0"/>
<resource name="hm_brd_b2a_0"/>
<resource name="hm_brd_b3a_0"/>
<resource name="hm_brd_b4a_0"/>
<resource name="hm_brd_b5a_0"/>
<resource name="hm_brd_b6a_0"/>
</human_male>
<dwarf_male>
<resource name=""/>
<resource name="dm_brd_b1a_0"/>
<resource name="dm_brd_b2a_0"/>
<resource name="dm_brd_b3a_0"/>
<resource name="dm_brd_b4a_0"/>
<resource name="dm_brd_b5a_0"/>
<resource name="dm_brd_b6a_0"/>
</dwarf_male>
</beards>

<hair_colors>
<resource name ="t3_har_wht"/>
<resource name ="t3_har_bln"/>
<resource name ="t3_har_dbl"/>
<resource name ="t3_har_org"/>
<resource name ="t3_har_red"/>
<resource name ="t3_har_lbr"/>
<resource name ="t3_har_rbr"/>
<resource name ="t3_har_dbr"/>
<resource name ="t3_har_blk"/>
</hair_colors>

<skin_colors>
<resource name="t1_skn_001"/>
<resource name="t1_skn_002"/>
<resource name="t1_skn_003"/>
<resource name="t1_skn_004"/>
<resource name="t1_skn_006"/>
<resource name="t1_skn_005"/>
<resource name="t1_skn_007"/>
</skin_colors>

<eyes_colors>
<resource name="t3_eye_ice"/>
<resource name="t3_eye_lbl"/>
<resource name="t3_eye_dbl"/>
<resource name="t3_eye_tea"/>
<resource name="t3_eye_grn"/>
<resource name="t3_eye_hzl"/>
<resource name="t3_eye_lbr"/>
<resource name="t3_eye_amb"/>
<resource name="t3_eye_dbr"/>
<resource name="t3_eye_gry"/>
<resource name="t3_eye_blk"/>
</eyes_colors>

<eyes_makeup_colors>
<resource name=""/>
<resource name="t1_mue_bl1"/>
<resource name="t1_mue_bl2"/>
<resource name="t1_mue_bl3"/>
<resource name="t1_mue_gn1"/>
<resource name="t1_mue_gn2"/>
<resource name="t1_mue_gn3"/>
<resource name="t1_mue_gr1"/>
<resource name="t1_mue_gr2"/>
<resource name="t1_mue_gr3"/>
<resource name="t1_mue_or1"/>
<resource name="t1_mue_or2"/>
<resource name="t1_mue_or3"/>
<resource name="t1_mue_pi1"/>
<resource name="t1_mue_pi2"/>
<resource name="t1_mue_pi3"/>
<resource name="t1_mue_pu1"/>
<resource name="t1_mue_pu2"/>
<resource name="t1_mue_pu3"/>
<resource name="t1_mue_re1"/>
<resource name="t1_mue_re2"/>
<resource name="t1_mue_re3"/>
<resource name="t1_mue_ro1"/>
<resource name="t1_mue_ro2"/>
<resource name="t1_mue_ro3"/>
<resource name="t1_mue_te1"/>
<resource name="t1_mue_te2"/>
<resource name="t1_mue_te3"/>
<resource name="t1_mue_ye1"/>
<resource name="t1_mue_ye2"/>
<resource name="t1_mue_ye3"/>
</eyes_makeup_colors>

<blush_makeup_colors>
<resource name=""/>
<resource name="t1_mub_br1"/>
<resource name="t1_mub_br2"/>
<resource name="t1_mub_br3"/>
<resource name="t1_mub_or1"/>
<resource name="t1_mub_or2"/>
<resource name="t1_mub_or3"/>
<resource name="t1_mub_pi1"/>
<resource name="t1_mub_pi2"/>
<resource name="t1_mub_pi3"/>
<resource name="t1_mub_pu1"/>
<resource name="t1_mub_pu2"/>
<resource name="t1_mub_pu3"/>
<resource name="t1_mub_re1"/>
<resource name="t1_mub_re2"/>
<resource name="t1_mub_re3"/>
<resource name="t1_mub_ro1"/>
<resource name="t1_mub_ro2"/>
<resource name="t1_mub_ro3"/>
<resource name="t1_mub_ta1"/>
<resource name="t1_mub_ta2"/>
<resource name="t1_mub_ta3"/>
<resource name="t1_mub_te1"/>
<resource name="t1_mub_te2"/>
<resource name="t1_mub_te3"/>
</blush_makeup_colors>

<lip_makeup_colors>
<resource name=""/>
<resource name="t1_mul_bk1"/>
<resource name="t1_mul_bk2"/>
<resource name="t1_mul_bk3"/>
<resource name="t1_mul_br1"/>
<resource name="t1_mul_br2"/>
<resource name="t1_mul_br3"/>
<resource name="t1_mul_pi1"/>
<resource name="t1_mul_pi2"/>
<resource name="t1_mul_pi3"/>
<resource name="t1_mul_pu1"/>
<resource name="t1_mul_pu2"/>
<resource name="t1_mul_pu3"/>
<resource name="t1_mul_re1"/>
<resource name="t1_mul_re2"/>
<resource name="t1_mul_re3"/>
<resource name="t1_mul_ro1"/>
<resource name="t1_mul_ro2"/>
<resource name="t1_mul_ro3"/>
<resource name="t1_mul_ta1"/>
<resource name="t1_mul_ta2"/>
<resource name="t1_mul_ta3"/>
<resource name="t1_mul_te1"/>
<resource name="t1_mul_te2"/>
<resource name="t1_mul_te3"/>
</lip_makeup_colors>

<brow_stubble_colors>
<resource name="t1_stb_wht"/>
<resource name="t1_stb_bln"/>
<resource name="t1_stb_dbl"/>
<resource name="t1_stb_org"/>
<resource name="t1_stb_red"/>
<resource name="t1_stb_lbr"/>
<resource name="t1_stb_rbr"/>
<resource name="t1_stb_dbr"/>
<resource name="t1_stb_blk"/>
</brow_stubble_colors>

<crew_cut_colors>
<resource name="t1_stb_wht"/>
<resource name="t1_stb_bln"/>
<resource name="t1_stb_dbl"/>
<resource name="t1_stb_org"/>
<resource name="t1_stb_red"/>
<resource name="t1_stb_lbr"/>
<resource name="t1_stb_rbr"/>
<resource name="t1_stb_dbr"/>
<resource name="t1_stb_blk"/>
</crew_cut_colors>

<tattoo_colors>
<resource name="T1_TAT_BLK"/>
<resource name="T1_TAT_GRY"/>
<resource name="T1_TAT_BRN"/>
<resource name="T1_TAT_DBR"/>
<resource name="T1_TAT_GRN"/>
<resource name="T1_TAT_DGN"/>
<resource name="T1_TAT_BLU"/>
<resource name="T1_TAT_DBL"/>
<resource name="T1_TAT_PUR"/>
<resource name="T1_TAT_DPU"/>
<resource name="T1_TAT_RED"/>
<resource name="T1_TAT_DRD"/>
<resource name="T1_TAT_ORG"/>
<resource name="T1_TAT_YEL"/>
<resource name="T1_TAT_PNK"/>
</tattoo_colors>

<tattoos>
<resource name="uh_tat_av1_0t"/>
<resource name="uh_tat_av2_0t"/>
<resource name="uh_tat_av3_0t"/>
<resource name="uh_tat_da1_0t"/>
<resource name="uh_tat_da2_0t"/>
<resource name="uh_tat_da3_0t"/>
<resource name="uh_tat_dw1_0t"/>
<resource name="uh_tat_dw2_0t"/>
<resource name="uh_tat_p01_0t"/>
</tattoos>

<skins>
<resource name="uh_hed_fema_0d"/>
<resource name="uh_hed_elfa_0d"/>
<resource name="uh_hed_kida_0d"/>
<resource name="uh_hed_masa_0d"/>
<resource name="uh_hed_dwfa_0d"/>
<resource name="uh_hed_quna_0d"/>
</skins>
</morph_config>
</pre>

==Section <heads>==
This section defines all of the head morph presets for each race and gender. Additional custom presets can be appended to the relevant list. The MOP file should be placed in the Override folder.

==Section <hairs>==
This section defines the various hair meshes for each race and gender. As with morph presets, additional custom hair meshes can be appended. The mesh files should be placed in the Override folder.

==Section <beards>==
This section defines the various beard meshes for each race (males only). Additional custom beard meshes can be appended. The mesh files should be placed in the Override folder.

==Section <xxx_colors>==
These sections define the tint files ([[TNT]]) used for hair, skin, eye, makeup and tattoo colours. Additional custom tints can be appended. The [[TNT]] files should be placed in the Override folder.

==Section <tattoos>==
This section appears to define the [[Texture_Formats#Tint_Map|tint maps]] used for facial tattoos. However, the files listed are not those actually used by the character creator. Thus, it is not possible to append or replace these with custom files. It would appear that tattoos are hardcoded or specified elsewhere and that this section is unused.

At this time the only known method to achieve custom tattoos in the in-game character generator is either through the use of custom head morph presets or by overriding the default [[Texture_Formats#Tint_Map|tint maps]] (by placing a custom [[Texture_Formats#Tint_Map|tint map]] of the appropriate file name in the Override folder). If you wish to override the defaults, the races/origins that the [[Texture_Formats#Tint_Map|tint maps]] are used for are as follows:

uh_pct_dc1_0t.dds - Dwarf Commoner 
uh_pmt_001_0t.dds - Dwarf Commoner 
uh_pct_dn1_0t.dds - Dwarf Noble 
uh_pct_h01_0t.dds - Human, Elf City/Mage 
uh_pct_h02_0t.dds - Human, Elf City/Mage 
uh_tat_ed1_0t.dds - Elf Dalish 
uh_tat_ed2_0t.dds - Elf Dalish 
uh_tat_ed3_0t.dds - Elf Dalish 
uh_tat_ed4_0t.dds - Elf Dalish 

==Section <skins>==
This section defines the skin [[Texture_Formats#Diffuse_Map|diffuse maps]]. Custom skin textures for each head morph are achieved by blending two skin textures together in amounts adjusted via sliders. Where the specific combinations of these skins for each race and gender are specified is unknown. Possibly it is hardcoded. Because of this, appending additional skin [[Texture_Formats#Diffuse_Map|diffuse maps]] is unlikely to have any effect. They can be overridden however, as described previously for [[Texture_Formats#Tint_Map|tint maps]].

=Mod Conflicts=
To avoid conflicts, there should only ever be one copy of chargenmorphcfg.xml in the Override folder. The game will ignore additional copies. A number of mods make edits to chargenmorphcfg.xml (e.g. Pineappletree's Vibrant Colors, Bidelle's Makeup Studio, CC Tints and Tones,More Hairstyles, etc.). If you install two or more of these mods you will need to delete extra copies of chargenmorphcfg.xml and edit the remaining copy to include the necessary additions for the other mods. Many mods now make pre-edited copies of chargenmorphcfg.xml available that encompass all the major appearance mods that require this file.

Chargenmorphcfg.xml

2010-02-18T12:52:37Z

DarthParametric: /* Section */

Chargenmorphcfg.xml is the configuration file for the in-game character creator. It dictates what head [[morph]] presets ([[MOP]]), hairstyles, beards, tattoos, makeup and colour tints (for skin, hair, etc.) are available as selectable options. It is located in <install directory>\packages\core\data\misc.erf

=File Structure=

The contents of the default file are as follows:

<pre>
<?xml version="1.0" encoding="utf-8"?>
<morph_config>
<heads>
<human_male>
<resource name="HM_CPS_P01.mop"/>
<resource name="HM_CPS_P02.mop"/>
<resource name="HM_CPS_P03.mop"/>
<resource name="HM_CPS_P04.mop"/>
<resource name="HM_CPS_P05.mop"/>
<resource name="HM_CPS_P06.mop"/>
<resource name="HM_CPS_P07.mop"/>
<resource name="HM_CPS_P08.mop"/>
<resource name="HM_PCC_B01.mop"/>
</human_male>
<human_female>
<resource name="HF_CPS_P01.mop"/>
<resource name="HF_CPS_P02.mop"/>
<resource name="HF_CPS_P03.mop"/>
<resource name="HF_CPS_P04.mop"/>
<resource name="HF_CPS_P05.mop"/>
<resource name="HF_CPS_P06.mop"/>
<resource name="HF_CPS_P07.mop"/>
<resource name="HF_CPS_P08.mop"/>
<resource name="HF_PCC_B01.mop"/>
</human_female>
<dwarf_male>
<resource name="DM_CPS_P01.mop"/>
<resource name="DM_CPS_P02.mop"/>
<resource name="DM_CPS_P03.mop"/>
<resource name="DM_CPS_P04.mop"/>
<resource name="DM_CPS_P05.mop"/>
<resource name="DM_CPS_P06.mop"/>
<resource name="DM_CPS_P07.mop"/>
<resource name="DM_CPS_P08.mop"/>
<resource name="DM_PCC_B01.mop"/>
</dwarf_male>
<dwarf_female>
<resource name="DF_CPS_P01.mop"/>
<resource name="DF_CPS_P02.mop"/>
<resource name="DF_CPS_P03.mop"/>
<resource name="DF_CPS_P04.mop"/>
<resource name="DF_CPS_P05.mop"/>
<resource name="DF_CPS_P06.mop"/>
<resource name="DF_CPS_P07.mop"/>
<resource name="DF_CPS_P08.mop"/>
<resource name="DF_PCC_B01.mop"/>
</dwarf_female>
<elf_male>
<resource name="EM_CPS_P01.mop"/>
<resource name="EM_CPS_P02.mop"/>
<resource name="EM_CPS_P03.mop"/>
<resource name="EM_CPS_P04.mop"/>
<resource name="EM_CPS_P05.mop"/>
<resource name="EM_CPS_P06.mop"/>
<resource name="EM_CPS_P07.mop"/>
<resource name="EM_CPS_P08.mop"/>
<resource name="EM_PCC_B01.mop"/>
</elf_male>
<elf_female>
<resource name="EF_CPS_P01.mop"/>
<resource name="EF_CPS_P02.mop"/>
<resource name="EF_CPS_P03.mop"/>
<resource name="EF_CPS_P04.mop"/>
<resource name="EF_CPS_P05.mop"/>
<resource name="EF_CPS_P06.mop"/>
<resource name="EF_CPS_P07.mop"/>
<resource name="EF_CPS_P08.mop"/>
<resource name="EF_PCC_B01.mop"/>
</elf_female>
</heads>

<hairs>
<human_male>
<resource name="hm_har_blda_0" cut="0234"/>
<resource name="hm_har_ha1a_0" cut="1"/>
<resource name="hm_har_ha2a_0" cut="1"/>
<resource name="hm_har_ha3a_0" cut="1"/>
<resource name="hm_har_hb1a_0" cut="1"/>
<resource name="hm_har_hb2a_0" cut="1"/>
<resource name="hm_har_hb3a_0" cut="1"/>
<resource name="hm_har_hb4a_0" cut="1"/>
<resource name="hm_har_hc1a_0" cut="1"/>
<resource name="hm_har_hc2a_0" cut="1"/>
<resource name="hm_har_hc3a_0" cut="1"/>
<resource name="hm_har_hc4a_0" cut="1"/>
<resource name="hm_har_hd1a_0" cut="1"/>
<resource name="hm_har_hd2a_0" cut="1"/>
<resource name="hm_har_hd3a_0" cut="1"/>
<resource name="hm_har_hd4a_0" cut="0"/>
</human_male>
<human_female>
<resource name="hf_har_blda_0" cut="02"/>
<resource name="hf_har_ha1a_0" cut="1"/>
<resource name="hf_har_ha2a_0" cut="1"/>
<resource name="hf_har_ha3a_0" cut="1"/>
<resource name="hf_har_ha4a_0" cut="1"/>
<resource name="hf_har_hb1a_0" cut="1"/>
<resource name="hf_har_hb2a_0" cut="1"/>
<resource name="hf_har_hb3a_0" cut="1"/>
<resource name="hf_har_hb4a_0" cut="1"/>
<resource name="hf_har_hc1a_0" cut="1"/>
<resource name="hf_har_hc2a_0" cut="1"/>
<resource name="hf_har_hc3a_0" cut="1"/>
<resource name="hf_har_hc4a_0" cut="1"/>
<resource name="hf_har_hd1a_0" cut="1"/>
<resource name="hf_har_hd2a_0" cut="1"/>
<resource name="hf_har_hd3a_0" cut="1"/>
<resource name="hf_har_hd4a_0" cut="1"/>
</human_female>
<dwarf_male>
<resource name="dm_har_blda_0" cut="0234"/>
<resource name="dm_har_ha1a_0" cut="1"/>
<resource name="dm_har_ha2a_0" cut="1"/>
<resource name="dm_har_ha3a_0" cut="1"/>
<resource name="dm_har_hb1a_0" cut="1"/>
<resource name="dm_har_hb2a_0" cut="1"/>
<resource name="dm_har_hb3a_0" cut="1"/>
<resource name="dm_har_hb4a_0" cut="1"/>
<resource name="dm_har_hc1a_0" cut="1"/>
<resource name="dm_har_hc2a_0" cut="1"/>
<resource name="dm_har_hc3a_0" cut="1"/>
<resource name="dm_har_hc4a_0" cut="1"/>
<resource name="dm_har_hd1a_0" cut="1"/>
<resource name="dm_har_hd2a_0" cut="1"/>
<resource name="dm_har_hd3a_0" cut="1"/>
<resource name="dm_har_hd4a_0" cut="0"/>
</dwarf_male> 1
<dwarf_female>
<resource name="df_har_blda_0" cut="02"/>
<resource name="df_har_ha1a_0" cut="1"/>
<resource name="df_har_ha2a_0" cut="1"/>
<resource name="df_har_ha3a_0" cut="1"/>
<resource name="df_har_ha4a_0" cut="1"/>
<resource name="df_har_hb1a_0" cut="1"/>
<resource name="df_har_hb2a_0" cut="1"/>
<resource name="df_har_hb3a_0" cut="1"/>
<resource name="df_har_hb4a_0" cut="1"/>
<resource name="df_har_hc1a_0" cut="1"/>
<resource name="df_har_hc2a_0" cut="1"/>
<resource name="df_har_hc3a_0" cut="1"/>
<resource name="df_har_hc4a_0" cut="1"/>
<resource name="df_har_hd1a_0" cut="1"/>
<resource name="df_har_hd2a_0" cut="1"/>
<resource name="df_har_hd3a_0" cut="1"/>
<resource name="df_har_hd4a_0" cut="1"/>
</dwarf_female>
<elf_male>
<resource name="em_har_blda_0" cut="0234"/>
<resource name="em_har_ha1a_0" cut="1"/>
<resource name="em_har_ha2a_0" cut="1"/>
<resource name="em_har_ha3a_0" cut="1"/>
<resource name="em_har_hb1a_0" cut="1"/>
<resource name="em_har_hb2a_0" cut="1"/>
<resource name="em_har_hb3a_0" cut="1"/>
<resource name="em_har_hb4a_0" cut="1"/>
<resource name="em_har_hc1a_0" cut="1"/>
<resource name="em_har_hc2a_0" cut="1"/>
<resource name="em_har_hc3a_0" cut="1"/>
<resource name="em_har_hc4a_0" cut="1"/>
<resource name="em_har_hd1a_0" cut="1"/>
<resource name="em_har_hd2a_0" cut="1"/>
<resource name="em_har_hd3a_0" cut="1"/>
<resource name="em_har_hd4a_0" cut="0"/>
</elf_male>
<elf_female>
<resource name="ef_har_blda_0" cut="02"/>
<resource name="ef_har_ha1a_0" cut="1"/>
<resource name="ef_har_ha2a_0" cut="1"/>
<resource name="ef_har_ha3a_0" cut="1"/>
<resource name="ef_har_ha4a_0" cut="1"/>
<resource name="ef_har_hb1a_0" cut="1"/>
<resource name="ef_har_hb2a_0" cut="1"/>
<resource name="ef_har_hb3a_0" cut="1"/>
<resource name="ef_har_hb4a_0" cut="1"/>
<resource name="ef_har_hc1a_0" cut="1"/>
<resource name="ef_har_hc2a_0" cut="1"/>
<resource name="ef_har_hc3a_0" cut="1"/>
<resource name="ef_har_hc4a_0" cut="1"/>
<resource name="ef_har_hd1a_0" cut="1"/>
<resource name="ef_har_hd2a_0" cut="1"/>
<resource name="ef_har_hd3a_0" cut="1"/>
<resource name="ef_har_hd4a_0" cut="1"/>
</elf_female>
</hairs>

<beards>
<human_male>
<resource name=""/>
<resource name="hm_brd_b1a_0"/>
<resource name="hm_brd_b2a_0"/>
<resource name="hm_brd_b3a_0"/>
<resource name="hm_brd_b4a_0"/>
<resource name="hm_brd_b5a_0"/>
<resource name="hm_brd_b6a_0"/>
</human_male>
<dwarf_male>
<resource name=""/>
<resource name="dm_brd_b1a_0"/>
<resource name="dm_brd_b2a_0"/>
<resource name="dm_brd_b3a_0"/>
<resource name="dm_brd_b4a_0"/>
<resource name="dm_brd_b5a_0"/>
<resource name="dm_brd_b6a_0"/>
</dwarf_male>
</beards>

<hair_colors>
<resource name ="t3_har_wht"/>
<resource name ="t3_har_bln"/>
<resource name ="t3_har_dbl"/>
<resource name ="t3_har_org"/>
<resource name ="t3_har_red"/>
<resource name ="t3_har_lbr"/>
<resource name ="t3_har_rbr"/>
<resource name ="t3_har_dbr"/>
<resource name ="t3_har_blk"/>
</hair_colors>

<skin_colors>
<resource name="t1_skn_001"/>
<resource name="t1_skn_002"/>
<resource name="t1_skn_003"/>
<resource name="t1_skn_004"/>
<resource name="t1_skn_006"/>
<resource name="t1_skn_005"/>
<resource name="t1_skn_007"/>
</skin_colors>

<eyes_colors>
<resource name="t3_eye_ice"/>
<resource name="t3_eye_lbl"/>
<resource name="t3_eye_dbl"/>
<resource name="t3_eye_tea"/>
<resource name="t3_eye_grn"/>
<resource name="t3_eye_hzl"/>
<resource name="t3_eye_lbr"/>
<resource name="t3_eye_amb"/>
<resource name="t3_eye_dbr"/>
<resource name="t3_eye_gry"/>
<resource name="t3_eye_blk"/>
</eyes_colors>

<eyes_makeup_colors>
<resource name=""/>
<resource name="t1_mue_bl1"/>
<resource name="t1_mue_bl2"/>
<resource name="t1_mue_bl3"/>
<resource name="t1_mue_gn1"/>
<resource name="t1_mue_gn2"/>
<resource name="t1_mue_gn3"/>
<resource name="t1_mue_gr1"/>
<resource name="t1_mue_gr2"/>
<resource name="t1_mue_gr3"/>
<resource name="t1_mue_or1"/>
<resource name="t1_mue_or2"/>
<resource name="t1_mue_or3"/>
<resource name="t1_mue_pi1"/>
<resource name="t1_mue_pi2"/>
<resource name="t1_mue_pi3"/>
<resource name="t1_mue_pu1"/>
<resource name="t1_mue_pu2"/>
<resource name="t1_mue_pu3"/>
<resource name="t1_mue_re1"/>
<resource name="t1_mue_re2"/>
<resource name="t1_mue_re3"/>
<resource name="t1_mue_ro1"/>
<resource name="t1_mue_ro2"/>
<resource name="t1_mue_ro3"/>
<resource name="t1_mue_te1"/>
<resource name="t1_mue_te2"/>
<resource name="t1_mue_te3"/>
<resource name="t1_mue_ye1"/>
<resource name="t1_mue_ye2"/>
<resource name="t1_mue_ye3"/>
</eyes_makeup_colors>

<blush_makeup_colors>
<resource name=""/>
<resource name="t1_mub_br1"/>
<resource name="t1_mub_br2"/>
<resource name="t1_mub_br3"/>
<resource name="t1_mub_or1"/>
<resource name="t1_mub_or2"/>
<resource name="t1_mub_or3"/>
<resource name="t1_mub_pi1"/>
<resource name="t1_mub_pi2"/>
<resource name="t1_mub_pi3"/>
<resource name="t1_mub_pu1"/>
<resource name="t1_mub_pu2"/>
<resource name="t1_mub_pu3"/>
<resource name="t1_mub_re1"/>
<resource name="t1_mub_re2"/>
<resource name="t1_mub_re3"/>
<resource name="t1_mub_ro1"/>
<resource name="t1_mub_ro2"/>
<resource name="t1_mub_ro3"/>
<resource name="t1_mub_ta1"/>
<resource name="t1_mub_ta2"/>
<resource name="t1_mub_ta3"/>
<resource name="t1_mub_te1"/>
<resource name="t1_mub_te2"/>
<resource name="t1_mub_te3"/>
</blush_makeup_colors>

<lip_makeup_colors>
<resource name=""/>
<resource name="t1_mul_bk1"/>
<resource name="t1_mul_bk2"/>
<resource name="t1_mul_bk3"/>
<resource name="t1_mul_br1"/>
<resource name="t1_mul_br2"/>
<resource name="t1_mul_br3"/>
<resource name="t1_mul_pi1"/>
<resource name="t1_mul_pi2"/>
<resource name="t1_mul_pi3"/>
<resource name="t1_mul_pu1"/>
<resource name="t1_mul_pu2"/>
<resource name="t1_mul_pu3"/>
<resource name="t1_mul_re1"/>
<resource name="t1_mul_re2"/>
<resource name="t1_mul_re3"/>
<resource name="t1_mul_ro1"/>
<resource name="t1_mul_ro2"/>
<resource name="t1_mul_ro3"/>
<resource name="t1_mul_ta1"/>
<resource name="t1_mul_ta2"/>
<resource name="t1_mul_ta3"/>
<resource name="t1_mul_te1"/>
<resource name="t1_mul_te2"/>
<resource name="t1_mul_te3"/>
</lip_makeup_colors>

<brow_stubble_colors>
<resource name="t1_stb_wht"/>
<resource name="t1_stb_bln"/>
<resource name="t1_stb_dbl"/>
<resource name="t1_stb_org"/>
<resource name="t1_stb_red"/>
<resource name="t1_stb_lbr"/>
<resource name="t1_stb_rbr"/>
<resource name="t1_stb_dbr"/>
<resource name="t1_stb_blk"/>
</brow_stubble_colors>

<crew_cut_colors>
<resource name="t1_stb_wht"/>
<resource name="t1_stb_bln"/>
<resource name="t1_stb_dbl"/>
<resource name="t1_stb_org"/>
<resource name="t1_stb_red"/>
<resource name="t1_stb_lbr"/>
<resource name="t1_stb_rbr"/>
<resource name="t1_stb_dbr"/>
<resource name="t1_stb_blk"/>
</crew_cut_colors>

<tattoo_colors>
<resource name="T1_TAT_BLK"/>
<resource name="T1_TAT_GRY"/>
<resource name="T1_TAT_BRN"/>
<resource name="T1_TAT_DBR"/>
<resource name="T1_TAT_GRN"/>
<resource name="T1_TAT_DGN"/>
<resource name="T1_TAT_BLU"/>
<resource name="T1_TAT_DBL"/>
<resource name="T1_TAT_PUR"/>
<resource name="T1_TAT_DPU"/>
<resource name="T1_TAT_RED"/>
<resource name="T1_TAT_DRD"/>
<resource name="T1_TAT_ORG"/>
<resource name="T1_TAT_YEL"/>
<resource name="T1_TAT_PNK"/>
</tattoo_colors>

<tattoos>
<resource name="uh_tat_av1_0t"/>
<resource name="uh_tat_av2_0t"/>
<resource name="uh_tat_av3_0t"/>
<resource name="uh_tat_da1_0t"/>
<resource name="uh_tat_da2_0t"/>
<resource name="uh_tat_da3_0t"/>
<resource name="uh_tat_dw1_0t"/>
<resource name="uh_tat_dw2_0t"/>
<resource name="uh_tat_p01_0t"/>
</tattoos>

<skins>
<resource name="uh_hed_fema_0d"/>
<resource name="uh_hed_elfa_0d"/>
<resource name="uh_hed_kida_0d"/>
<resource name="uh_hed_masa_0d"/>
<resource name="uh_hed_dwfa_0d"/>
<resource name="uh_hed_quna_0d"/>
</skins>
</morph_config>
</pre>

==Section <heads>==
This section defines all of the head morph presets for each race and gender. Additional custom presets can be appended to the relevant list. The MOP file should be placed in the Override folder.

==Section <hairs>==
This section defines the various hair meshes for each race and gender. As with morph presets, additional custom hair meshes can be appended. The mesh files should be placed in the Override folder.

==Section <beards>==
This section defines the various beard meshes for each race (males only). Additional custom beard meshes can be appended. The mesh files should be placed in the Override folder.

==Section <xxx_colors>==
These sections define the tint files ([[TNT]]) used for hair, skin, eye, makeup and tattoo colours. Additional custom tints can be appended. The [[TNT]] files should be placed in the Override folder.

==Section <tattoos>==
This section defines the [[Texture_Formats#Tint_Map|tint maps]] used for facial tattoos. It is not possible to append or replace these with custom files.

At this time the only known method to achieve custom tattoos in the in-game character generator is either through the use of custom head morph presets or by overriding the default [[Texture_Formats#Tint_Map|tint maps]] (by placing a custom [[Texture_Formats#Tint_Map|tint map]] of the appropriate file name in the Override folder). If you wish to override the defaults, the races/origins that the [[Texture_Formats#Tint_Map|tint maps]] are used for are as follows:

uh_pct_dc1_0t.dds - Dwarf Commoner 
uh_pmt_001_0t.dds - Dwarf Commoner 
uh_pct_dn1_0t.dds - Dwarf Noble 
uh_pct_h01_0t.dds - Human, Elf City/Mage 
uh_pct_h02_0t.dds - Human, Elf City/Mage 
uh_tat_ed1_0t.dds - Elf Dalish 
uh_tat_ed2_0t.dds - Elf Dalish 
uh_tat_ed3_0t.dds - Elf Dalish 
uh_tat_ed4_0t.dds - Elf Dalish 

==Section <skins>==
This section defines the skin [[Texture_Formats#Diffuse_Map|diffuse maps]]. Custom skin textures for each head morph are achieved by blending two skin textures together in amounts adjusted via sliders. Where the specific combinations of these skins for each race and gender are specified is unknown. Possibly it is hardcoded. Because of this, appending additional skin [[Texture_Formats#Diffuse_Map|diffuse maps]] is unlikely to have any effect. They can be overridden however, as described previously for [[Texture_Formats#Tint_Map|tint maps]].

=Mod Conflicts=
To avoid conflicts, there should only ever be one copy of chargenmorphcfg.xml in the Override folder. The game will ignore additional copies. A number of mods make edits to chargenmorphcfg.xml (e.g. Pineappletree's Vibrant Colors, Bidelle's Makeup Studio, CC Tints and Tones,More Hairstyles, etc.). If you install two or more of these mods you will need to delete extra copies of chargenmorphcfg.xml and edit the remaining copy to include the necessary additions for the other mods. Many mods now make pre-edited copies of chargenmorphcfg.xml available that encompass all the major appearance mods that require this file.

Chargenmorphcfg.xml

2010-02-18T12:51:16Z

DarthParametric: Created page with 'Chargenmorphcfg.xml is the configuration file for the in-game character creator. It dictates what head morph presets (MOP), hairstyles, beards, tattoos, makeup and colour...'

Chargenmorphcfg.xml is the configuration file for the in-game character creator. It dictates what head [[morph]] presets ([[MOP]]), hairstyles, beards, tattoos, makeup and colour tints (for skin, hair, etc.) are available as selectable options. It is located in <install directory>\packages\core\data\misc.erf

=File Structure=

The contents of the default file are as follows:

<pre>
<?xml version="1.0" encoding="utf-8"?>
<morph_config>
<heads>
<human_male>
<resource name="HM_CPS_P01.mop"/>
<resource name="HM_CPS_P02.mop"/>
<resource name="HM_CPS_P03.mop"/>
<resource name="HM_CPS_P04.mop"/>
<resource name="HM_CPS_P05.mop"/>
<resource name="HM_CPS_P06.mop"/>
<resource name="HM_CPS_P07.mop"/>
<resource name="HM_CPS_P08.mop"/>
<resource name="HM_PCC_B01.mop"/>
</human_male>
<human_female>
<resource name="HF_CPS_P01.mop"/>
<resource name="HF_CPS_P02.mop"/>
<resource name="HF_CPS_P03.mop"/>
<resource name="HF_CPS_P04.mop"/>
<resource name="HF_CPS_P05.mop"/>
<resource name="HF_CPS_P06.mop"/>
<resource name="HF_CPS_P07.mop"/>
<resource name="HF_CPS_P08.mop"/>
<resource name="HF_PCC_B01.mop"/>
</human_female>
<dwarf_male>
<resource name="DM_CPS_P01.mop"/>
<resource name="DM_CPS_P02.mop"/>
<resource name="DM_CPS_P03.mop"/>
<resource name="DM_CPS_P04.mop"/>
<resource name="DM_CPS_P05.mop"/>
<resource name="DM_CPS_P06.mop"/>
<resource name="DM_CPS_P07.mop"/>
<resource name="DM_CPS_P08.mop"/>
<resource name="DM_PCC_B01.mop"/>
</dwarf_male>
<dwarf_female>
<resource name="DF_CPS_P01.mop"/>
<resource name="DF_CPS_P02.mop"/>
<resource name="DF_CPS_P03.mop"/>
<resource name="DF_CPS_P04.mop"/>
<resource name="DF_CPS_P05.mop"/>
<resource name="DF_CPS_P06.mop"/>
<resource name="DF_CPS_P07.mop"/>
<resource name="DF_CPS_P08.mop"/>
<resource name="DF_PCC_B01.mop"/>
</dwarf_female>
<elf_male>
<resource name="EM_CPS_P01.mop"/>
<resource name="EM_CPS_P02.mop"/>
<resource name="EM_CPS_P03.mop"/>
<resource name="EM_CPS_P04.mop"/>
<resource name="EM_CPS_P05.mop"/>
<resource name="EM_CPS_P06.mop"/>
<resource name="EM_CPS_P07.mop"/>
<resource name="EM_CPS_P08.mop"/>
<resource name="EM_PCC_B01.mop"/>
</elf_male>
<elf_female>
<resource name="EF_CPS_P01.mop"/>
<resource name="EF_CPS_P02.mop"/>
<resource name="EF_CPS_P03.mop"/>
<resource name="EF_CPS_P04.mop"/>
<resource name="EF_CPS_P05.mop"/>
<resource name="EF_CPS_P06.mop"/>
<resource name="EF_CPS_P07.mop"/>
<resource name="EF_CPS_P08.mop"/>
<resource name="EF_PCC_B01.mop"/>
</elf_female>
</heads>

<hairs>
<human_male>
<resource name="hm_har_blda_0" cut="0234"/>
<resource name="hm_har_ha1a_0" cut="1"/>
<resource name="hm_har_ha2a_0" cut="1"/>
<resource name="hm_har_ha3a_0" cut="1"/>
<resource name="hm_har_hb1a_0" cut="1"/>
<resource name="hm_har_hb2a_0" cut="1"/>
<resource name="hm_har_hb3a_0" cut="1"/>
<resource name="hm_har_hb4a_0" cut="1"/>
<resource name="hm_har_hc1a_0" cut="1"/>
<resource name="hm_har_hc2a_0" cut="1"/>
<resource name="hm_har_hc3a_0" cut="1"/>
<resource name="hm_har_hc4a_0" cut="1"/>
<resource name="hm_har_hd1a_0" cut="1"/>
<resource name="hm_har_hd2a_0" cut="1"/>
<resource name="hm_har_hd3a_0" cut="1"/>
<resource name="hm_har_hd4a_0" cut="0"/>
</human_male>
<human_female>
<resource name="hf_har_blda_0" cut="02"/>
<resource name="hf_har_ha1a_0" cut="1"/>
<resource name="hf_har_ha2a_0" cut="1"/>
<resource name="hf_har_ha3a_0" cut="1"/>
<resource name="hf_har_ha4a_0" cut="1"/>
<resource name="hf_har_hb1a_0" cut="1"/>
<resource name="hf_har_hb2a_0" cut="1"/>
<resource name="hf_har_hb3a_0" cut="1"/>
<resource name="hf_har_hb4a_0" cut="1"/>
<resource name="hf_har_hc1a_0" cut="1"/>
<resource name="hf_har_hc2a_0" cut="1"/>
<resource name="hf_har_hc3a_0" cut="1"/>
<resource name="hf_har_hc4a_0" cut="1"/>
<resource name="hf_har_hd1a_0" cut="1"/>
<resource name="hf_har_hd2a_0" cut="1"/>
<resource name="hf_har_hd3a_0" cut="1"/>
<resource name="hf_har_hd4a_0" cut="1"/>
</human_female>
<dwarf_male>
<resource name="dm_har_blda_0" cut="0234"/>
<resource name="dm_har_ha1a_0" cut="1"/>
<resource name="dm_har_ha2a_0" cut="1"/>
<resource name="dm_har_ha3a_0" cut="1"/>
<resource name="dm_har_hb1a_0" cut="1"/>
<resource name="dm_har_hb2a_0" cut="1"/>
<resource name="dm_har_hb3a_0" cut="1"/>
<resource name="dm_har_hb4a_0" cut="1"/>
<resource name="dm_har_hc1a_0" cut="1"/>
<resource name="dm_har_hc2a_0" cut="1"/>
<resource name="dm_har_hc3a_0" cut="1"/>
<resource name="dm_har_hc4a_0" cut="1"/>
<resource name="dm_har_hd1a_0" cut="1"/>
<resource name="dm_har_hd2a_0" cut="1"/>
<resource name="dm_har_hd3a_0" cut="1"/>
<resource name="dm_har_hd4a_0" cut="0"/>
</dwarf_male> 1
<dwarf_female>
<resource name="df_har_blda_0" cut="02"/>
<resource name="df_har_ha1a_0" cut="1"/>
<resource name="df_har_ha2a_0" cut="1"/>
<resource name="df_har_ha3a_0" cut="1"/>
<resource name="df_har_ha4a_0" cut="1"/>
<resource name="df_har_hb1a_0" cut="1"/>
<resource name="df_har_hb2a_0" cut="1"/>
<resource name="df_har_hb3a_0" cut="1"/>
<resource name="df_har_hb4a_0" cut="1"/>
<resource name="df_har_hc1a_0" cut="1"/>
<resource name="df_har_hc2a_0" cut="1"/>
<resource name="df_har_hc3a_0" cut="1"/>
<resource name="df_har_hc4a_0" cut="1"/>
<resource name="df_har_hd1a_0" cut="1"/>
<resource name="df_har_hd2a_0" cut="1"/>
<resource name="df_har_hd3a_0" cut="1"/>
<resource name="df_har_hd4a_0" cut="1"/>
</dwarf_female>
<elf_male>
<resource name="em_har_blda_0" cut="0234"/>
<resource name="em_har_ha1a_0" cut="1"/>
<resource name="em_har_ha2a_0" cut="1"/>
<resource name="em_har_ha3a_0" cut="1"/>
<resource name="em_har_hb1a_0" cut="1"/>
<resource name="em_har_hb2a_0" cut="1"/>
<resource name="em_har_hb3a_0" cut="1"/>
<resource name="em_har_hb4a_0" cut="1"/>
<resource name="em_har_hc1a_0" cut="1"/>
<resource name="em_har_hc2a_0" cut="1"/>
<resource name="em_har_hc3a_0" cut="1"/>
<resource name="em_har_hc4a_0" cut="1"/>
<resource name="em_har_hd1a_0" cut="1"/>
<resource name="em_har_hd2a_0" cut="1"/>
<resource name="em_har_hd3a_0" cut="1"/>
<resource name="em_har_hd4a_0" cut="0"/>
</elf_male>
<elf_female>
<resource name="ef_har_blda_0" cut="02"/>
<resource name="ef_har_ha1a_0" cut="1"/>
<resource name="ef_har_ha2a_0" cut="1"/>
<resource name="ef_har_ha3a_0" cut="1"/>
<resource name="ef_har_ha4a_0" cut="1"/>
<resource name="ef_har_hb1a_0" cut="1"/>
<resource name="ef_har_hb2a_0" cut="1"/>
<resource name="ef_har_hb3a_0" cut="1"/>
<resource name="ef_har_hb4a_0" cut="1"/>
<resource name="ef_har_hc1a_0" cut="1"/>
<resource name="ef_har_hc2a_0" cut="1"/>
<resource name="ef_har_hc3a_0" cut="1"/>
<resource name="ef_har_hc4a_0" cut="1"/>
<resource name="ef_har_hd1a_0" cut="1"/>
<resource name="ef_har_hd2a_0" cut="1"/>
<resource name="ef_har_hd3a_0" cut="1"/>
<resource name="ef_har_hd4a_0" cut="1"/>
</elf_female>
</hairs>

<beards>
<human_male>
<resource name=""/>
<resource name="hm_brd_b1a_0"/>
<resource name="hm_brd_b2a_0"/>
<resource name="hm_brd_b3a_0"/>
<resource name="hm_brd_b4a_0"/>
<resource name="hm_brd_b5a_0"/>
<resource name="hm_brd_b6a_0"/>
</human_male>
<dwarf_male>
<resource name=""/>
<resource name="dm_brd_b1a_0"/>
<resource name="dm_brd_b2a_0"/>
<resource name="dm_brd_b3a_0"/>
<resource name="dm_brd_b4a_0"/>
<resource name="dm_brd_b5a_0"/>
<resource name="dm_brd_b6a_0"/>
</dwarf_male>
</beards>

<hair_colors>
<resource name ="t3_har_wht"/>
<resource name ="t3_har_bln"/>
<resource name ="t3_har_dbl"/>
<resource name ="t3_har_org"/>
<resource name ="t3_har_red"/>
<resource name ="t3_har_lbr"/>
<resource name ="t3_har_rbr"/>
<resource name ="t3_har_dbr"/>
<resource name ="t3_har_blk"/>
</hair_colors>

<skin_colors>
<resource name="t1_skn_001"/>
<resource name="t1_skn_002"/>
<resource name="t1_skn_003"/>
<resource name="t1_skn_004"/>
<resource name="t1_skn_006"/>
<resource name="t1_skn_005"/>
<resource name="t1_skn_007"/>
</skin_colors>

<eyes_colors>
<resource name="t3_eye_ice"/>
<resource name="t3_eye_lbl"/>
<resource name="t3_eye_dbl"/>
<resource name="t3_eye_tea"/>
<resource name="t3_eye_grn"/>
<resource name="t3_eye_hzl"/>
<resource name="t3_eye_lbr"/>
<resource name="t3_eye_amb"/>
<resource name="t3_eye_dbr"/>
<resource name="t3_eye_gry"/>
<resource name="t3_eye_blk"/>
</eyes_colors>

<eyes_makeup_colors>
<resource name=""/>
<resource name="t1_mue_bl1"/>
<resource name="t1_mue_bl2"/>
<resource name="t1_mue_bl3"/>
<resource name="t1_mue_gn1"/>
<resource name="t1_mue_gn2"/>
<resource name="t1_mue_gn3"/>
<resource name="t1_mue_gr1"/>
<resource name="t1_mue_gr2"/>
<resource name="t1_mue_gr3"/>
<resource name="t1_mue_or1"/>
<resource name="t1_mue_or2"/>
<resource name="t1_mue_or3"/>
<resource name="t1_mue_pi1"/>
<resource name="t1_mue_pi2"/>
<resource name="t1_mue_pi3"/>
<resource name="t1_mue_pu1"/>
<resource name="t1_mue_pu2"/>
<resource name="t1_mue_pu3"/>
<resource name="t1_mue_re1"/>
<resource name="t1_mue_re2"/>
<resource name="t1_mue_re3"/>
<resource name="t1_mue_ro1"/>
<resource name="t1_mue_ro2"/>
<resource name="t1_mue_ro3"/>
<resource name="t1_mue_te1"/>
<resource name="t1_mue_te2"/>
<resource name="t1_mue_te3"/>
<resource name="t1_mue_ye1"/>
<resource name="t1_mue_ye2"/>
<resource name="t1_mue_ye3"/>
</eyes_makeup_colors>

<blush_makeup_colors>
<resource name=""/>
<resource name="t1_mub_br1"/>
<resource name="t1_mub_br2"/>
<resource name="t1_mub_br3"/>
<resource name="t1_mub_or1"/>
<resource name="t1_mub_or2"/>
<resource name="t1_mub_or3"/>
<resource name="t1_mub_pi1"/>
<resource name="t1_mub_pi2"/>
<resource name="t1_mub_pi3"/>
<resource name="t1_mub_pu1"/>
<resource name="t1_mub_pu2"/>
<resource name="t1_mub_pu3"/>
<resource name="t1_mub_re1"/>
<resource name="t1_mub_re2"/>
<resource name="t1_mub_re3"/>
<resource name="t1_mub_ro1"/>
<resource name="t1_mub_ro2"/>
<resource name="t1_mub_ro3"/>
<resource name="t1_mub_ta1"/>
<resource name="t1_mub_ta2"/>
<resource name="t1_mub_ta3"/>
<resource name="t1_mub_te1"/>
<resource name="t1_mub_te2"/>
<resource name="t1_mub_te3"/>
</blush_makeup_colors>

<lip_makeup_colors>
<resource name=""/>
<resource name="t1_mul_bk1"/>
<resource name="t1_mul_bk2"/>
<resource name="t1_mul_bk3"/>
<resource name="t1_mul_br1"/>
<resource name="t1_mul_br2"/>
<resource name="t1_mul_br3"/>
<resource name="t1_mul_pi1"/>
<resource name="t1_mul_pi2"/>
<resource name="t1_mul_pi3"/>
<resource name="t1_mul_pu1"/>
<resource name="t1_mul_pu2"/>
<resource name="t1_mul_pu3"/>
<resource name="t1_mul_re1"/>
<resource name="t1_mul_re2"/>
<resource name="t1_mul_re3"/>
<resource name="t1_mul_ro1"/>
<resource name="t1_mul_ro2"/>
<resource name="t1_mul_ro3"/>
<resource name="t1_mul_ta1"/>
<resource name="t1_mul_ta2"/>
<resource name="t1_mul_ta3"/>
<resource name="t1_mul_te1"/>
<resource name="t1_mul_te2"/>
<resource name="t1_mul_te3"/>
</lip_makeup_colors>

<brow_stubble_colors>
<resource name="t1_stb_wht"/>
<resource name="t1_stb_bln"/>
<resource name="t1_stb_dbl"/>
<resource name="t1_stb_org"/>
<resource name="t1_stb_red"/>
<resource name="t1_stb_lbr"/>
<resource name="t1_stb_rbr"/>
<resource name="t1_stb_dbr"/>
<resource name="t1_stb_blk"/>
</brow_stubble_colors>

<crew_cut_colors>
<resource name="t1_stb_wht"/>
<resource name="t1_stb_bln"/>
<resource name="t1_stb_dbl"/>
<resource name="t1_stb_org"/>
<resource name="t1_stb_red"/>
<resource name="t1_stb_lbr"/>
<resource name="t1_stb_rbr"/>
<resource name="t1_stb_dbr"/>
<resource name="t1_stb_blk"/>
</crew_cut_colors>

<tattoo_colors>
<resource name="T1_TAT_BLK"/>
<resource name="T1_TAT_GRY"/>
<resource name="T1_TAT_BRN"/>
<resource name="T1_TAT_DBR"/>
<resource name="T1_TAT_GRN"/>
<resource name="T1_TAT_DGN"/>
<resource name="T1_TAT_BLU"/>
<resource name="T1_TAT_DBL"/>
<resource name="T1_TAT_PUR"/>
<resource name="T1_TAT_DPU"/>
<resource name="T1_TAT_RED"/>
<resource name="T1_TAT_DRD"/>
<resource name="T1_TAT_ORG"/>
<resource name="T1_TAT_YEL"/>
<resource name="T1_TAT_PNK"/>
</tattoo_colors>

<tattoos>
<resource name="uh_tat_av1_0t"/>
<resource name="uh_tat_av2_0t"/>
<resource name="uh_tat_av3_0t"/>
<resource name="uh_tat_da1_0t"/>
<resource name="uh_tat_da2_0t"/>
<resource name="uh_tat_da3_0t"/>
<resource name="uh_tat_dw1_0t"/>
<resource name="uh_tat_dw2_0t"/>
<resource name="uh_tat_p01_0t"/>
</tattoos>

<skins>
<resource name="uh_hed_fema_0d"/>
<resource name="uh_hed_elfa_0d"/>
<resource name="uh_hed_kida_0d"/>
<resource name="uh_hed_masa_0d"/>
<resource name="uh_hed_dwfa_0d"/>
<resource name="uh_hed_quna_0d"/>
</skins>
</morph_config>
</pre>

==Section <heads>==
This section defines all of the head morph presets for each race and gender. Additional custom presets can be appended to the relevant list. The MOP file should be placed in the Override folder.

==Section <hairs>==
This section defines the various hair meshes for each race and gender. As with morph presets, additional custom hair meshes can be appended. The mesh files should be placed in the Override folder.

==Section <beards>==
This section defines the various beard meshes for each race (males only). Additional custom beard meshes can be appended. The mesh files should be placed in the Override folder.

==Section <xxx_colors>==
These sections define the tint files ([[TNT]]) used for hair, skin, eye, makeup and tattoo colours. Additional custom tints can be appended. The [[TNT]] files should be placed in the Override folder.

==Section <tattoos>==
This section defines the [[Texture_Formats#Tint_Map|tint maps]] used for facial tattoos. It is not possible to append or replace these with custom files.

At this time the only known method to achieve custom tattoos in the in-game character generator is either through the use of custom head morph presets or by overriding the default [[Texture_Formats#Tint_Map|tint maps]] (by placing a custom [[Texture_Formats#Tint_Map|tint map]] of the appropriate file name in the Override folder). If you wish to override the defaults, the races/origins that the [[Texture_Formats#Tint_Map|tint maps]] are used for are as follows:

uh_pct_dc1_0t.dds - Dwarf Commoner
uh_pmt_001_0t.dds - Dwarf Commoner
uh_pct_dn1_0t.dds - Dwarf Noble
uh_pct_h01_0t.dds - Human, Elf City/Mage
uh_pct_h02_0t.dds - Human, Elf City/Mage
uh_tat_ed1_0t.dds - Elf Dalish
uh_tat_ed2_0t.dds - Elf Dalish
uh_tat_ed3_0t.dds - Elf Dalish
uh_tat_ed4_0t.dds - Elf Dalish

==Section <skins>==
This section defines the skin [[Texture_Formats#Diffuse_Map|diffuse maps]]. Custom skin textures for each head morph are achieved by blending two skin textures together in amounts adjusted via sliders. Where the specific combinations of these skins for each race and gender are specified is unknown. Possibly it is hardcoded. Because of this, appending additional skin [[Texture_Formats#Diffuse_Map|diffuse maps]] is unlikely to have any effect. They can be overridden however, as described previously for [[Texture_Formats#Tint_Map|tint maps]].

=Mod Conflicts=
To avoid conflicts, there should only ever be one copy of chargenmorphcfg.xml in the Override folder. The game will ignore additional copies. A number of mods make edits to chargenmorphcfg.xml (e.g. Pineappletree's Vibrant Colors, Bidelle's Makeup Studio, CC Tints and Tones,More Hairstyles, etc.). If you install two or more of these mods you will need to delete extra copies of chargenmorphcfg.xml and edit the remaining copy to include the necessary additions for the other mods. Many mods now make pre-edited copies of chargenmorphcfg.xml available that encompass all the major appearance mods that require this file.

Overriding and creating tints tutorial

2010-01-17T10:19:22Z

DarthParametric:

The [[Material Tint System|tint system]] is potentially very powerful, but its results are not always pleasing to everyone. One example in the base game that a number of people dislike is the number of armour and weapon material types (like Red Steel) that are a pinkish-red colour. The colour of a particular material is tied to its tint. What follows is a revised and enhanced version of several forum posts by DarthParametric on how to make armour and weapons more of a traditional metal colour by both replacing default tints with alternative ones that already exist in the game and using completely custom tints.

__TOC__

= Basic Override: Replacing One Set of Tints with Another =

The first thing is to open materialtypes.xls located in <install directory>\tools\Source\2DA\rules\ Change to the materialtypes tab. Here you’ll see all the armour and weapon material types and their associated tints. You'll want to find the entries for metal armour, metal weapons, and metal shields. For easy reference, here are the specific rows of interest (click for larger):

{| class="wikitable" border="1"
|-valign="top"
|[[Image:ArmTnt_2DA_Armour.jpg|200px]]
|[[Image:ArmTnt_2DA_Weapon.jpg|200px]]
|[[Image:ArmTnt_2DA_Shield.jpg|200px]]
|-align="center"
|Metal Armour Material Tints
|Metal Weapon Material Tints
|Metal Shield Material Tints
|}

Red Steel is obviously going to be the major offender in terms of pink/red colouration, but we’ll extract them all just to be safe. In the toolset directory, run ErfEditor.exe. Go to File->Open File and navigate to <install directory>\packages\core\data\ and select tints.erf and click Open. You’ll see all the game’s tint files. As seen in the 2DA, the tint files we want are prefaced T3_ARM_, T3_WPN_ and T3_SHD_, so scroll down until you find them all. Select (CTRL + left click) the 20 (there is no veridium shield) files we want, then right click and choose Extract Resource. In the pop-up folder browser, just choose somewhere easy to find like the Desktop and click OK.

Now what we are going to do is choose the tint file for one material type that looks appropriately metal-like and overwrite the others with copies of it. Before we do that though we need to see what colours each tint file has. Open the toolset. Go to File->New->Material. This is the [[Material editor|material editor]]. Right click on the Root object and choose Insert->Insert New Tint Library. Right click on the new tint library and choose Insert->Insert New Tint Object. Click on the new tint object and then in the Object Inspector (if it isn’t already open go to View->Other Windows->Object Inspector) look for the Import [[TNT]] File line and click the button to the right. Navigate to where you extracted the tint files and load one.

You’ll see in the Object Inspector a whole series of colours, labelled diffuse and specular for the red, green and blue channels. Diffuse is the actual base colour, and specular is the highlights. The channels it is referring to is of the [[Texture_Formats#Tint_Map|tint map]]. This has 4 channels (RGB plus Alpha), each of which is a greyscale image that is used to define the area its related tint colour is applied. Refer to the other relevant wiki tint and texture topics for more info.

If you load the tint files for all 7 different material types in turn, you’ll see a number of them have reddish colours. There are two which would be suitable replacements. The first is silverite, the second is steel. Both have bluish grey colours for the most part:

[[image:ArmTnt_Tnt_Stl_Sil.jpg|thumb|none|Silverite and Steel Tints]]

What you want to do is select one of those and make additional copies of the TNT file, then rename them appropriately (after deleting the originals) to replace the Iron, Grey Iron, Red Steel and Dragonbone tint files. Additionally, you may also choose to replace the Veridium tint file (for armour and weapons), which is a greenish tint, if that is not to your taste. Make sure you only replace a tint file with one of the same type, i.e. only replace armour tints with another armour tint, not a weapon or shield tint (the reason for this is detailed later). Once that is done, create a new folder in My Documents\BioWare\Dragon Age\packages\core\override\ and call it something appropriate (Armour & Weapon Tint Mod for example). Place your tint files in there. Load up the game and try out a formally pink suit of armour. You should get something like this:

[[image:ArmTnt_Arm_Tint_Edit.jpg|thumb|none|Before and After Tint Override]]

You can see there that Alistair has gone from the original red armour to a proper metal colour.

There are also some additional tints that you may want to look at. If you peruse the rest of materialtypes.xls you'll see that Templar armour uses T3_ARM_TMP.tnt and the king's armour uses T3_ARM_GLD.tnt.

= Advanced Tinting 101: Overriding with Custom Tints =

As alluded to previously, tint files hold a series of colours that are applied to a model in a manner that is defined by a [[Texture_Formats#Tint_Map|tint map]]. Each channel of the tint map is used as a mask to define a specific area of the parent texture to apply the associated tint. While tint maps have four channels (RGB+A), it’s mostly only face textures and related things like tattoos that use all four. Everything else tends just to use the RGB channels.

As you would have seen, the metal material tints extracted previously have a pair of colours, diffuse and specular, for each of the three tint map channels (thus 6 colours in total). The diffuse is what actually colours the base texture, the specular is the “shininess” – the colour of highlights caused by light reflection. A specific type of armour generally shares a single model (well, one model per sex per race, not counting scaled [[Texture_Formats#Level_of_Detail|LOD]] variants). There are usually 4 (occasionally 5) texture variants, and these are diversified further into actual item variations through the use of tints, the colour of which are determined by material type. As an example, I’ll use two texture variants of male medium armour (as with faces, armour models share a common UV map across races, although armour is split into male and female variants, aside from massive armour).

If you haven’t previously unpacked or browsed through the armour textures, you can find them in <install directory>\packages\core\textures\high\texturepack.erf. We’ll use variant A, pm_arm_meda_0d.dds, and variant D, pm_arm_medd_0d.dds. Notice the _0d suffix. This denotes the [[Texture_Formats#Diffuse_Map|diffuse map]]. You’ll see a number of associated textures with the same base filename as the diffuse maps. Those with the _0n suffix are the [[Texture_Formats#Normal_Map|normal maps]], those with _0s are the [[Texture_Formats#Specular_Map|specular maps]], and the ones we want, _0t, the [[Texture_Formats#Tint_Map|tint maps]]. Refer to the [[Texture_Formats|texture formats]] page for more info on texture types and filename conventions. Extract the two diffuse maps and the two tint maps to a working directory and open them with something that can handle [[DDS]] files.

You’ll see that the diffuse maps are just standard colour textures, albeit a tad dull. The tint maps, at first impression, look to be horrible technicolour nightmares. Change to the channels tab however and you’ll see how they work. Think of each channel as a separate alpha mask. Black is 100% transparency, white is 100% opacity, and shades of grey denote values in between. If we lay out the channels of the tint map as 3 separate images and compare them to the parent diffuse map, we get the following for the two texture variants:

[[image:ArmTnt_Med_Arm_Tint_Example_01.jpg|thumb|left|Male Medium Armour Texture A Plus Tint Masks]] [[image:ArmTnt_Med_Arm_Tint_Example_02.jpg|thumb|none|Male Medium Armour Texture D Plus Tint Masks]]
 If you look at the first image, variant A, you’ll see that the red channel of the tint mask is confined to areas of metal banding, the green channel to other metal areas like buckles and trim, and the blue channel to areas of leather. Variant D is a similar story, the red and green channels being confined to metal, the blue to leather. Because all three classes of metal armour (medium, heavy, massive) use a universal set of tints based on material type, if you look at the other metal armour tint masks you’ll see that this is the pattern that they all more or less conform to – the red channel is the primary metal area tint, the green channel the secondary metal area tint, the blue channel the leather/cloth/misc area tint (the "misc" mostly refers to the massive armours, which don’t have much leather or cloth and mainly use the blue channel for filigree patterns and other decorative effects).

Now that we know what each channel of the tint mask does, we can edit our tint file appropriately. Load the tint file you want to edit into the material editor. I’ll use the dragonbone tint, T3_ARM_DRB.tnt, for this example. Creating tints in the toolset's [[material editor]] has already been [[Tutorial:_Creating_recolors_of_existing_items|covered previously]], so I won't recount the process here. Instead, I'll cover editing [[TNT]] files directly in the GFF editor. You can do this in the toolset (by just going to File->Open and loading the TNT file) but I prefer to use the standalone GFF editor in the toolset directory, GffEditor.exe. You may find it handy to associate this program with all GFF file types so that you can quickly edit a particular file just by double clicking on it. With the TNT file open in the GFF editor, you’ll see something like this:

[[image:ArmTnt_TNT_GFF_Editor.jpg|thumb|none|Dragonbone Tint File in GFF Editor]]

Although it’s confusing at first, you’ll see it’s conveying the same basic information as that in the material editor, just in a more concise (and less visually intuitive) format. For a breakdown of the file structure and significance of the values, refer to the [[TNT]] page.

Now let’s look at the tint file in the material editor. We’ll use this to tweak the colours to our liking, then copy the values across to the file in the GFF editor. If you click on each colour you’ll get a button on the right that pops up a colour picker for easy tweaking. If you are using the Dragonbone tint file from earlier, it will be using the colour values from the Silverite or Steel tints, which are bluish grey. I don’t know what colour Dragonbone is supposed to be, but for this example I’ll change it to some brownish colours, as follows:

[[image:ArmTnt_Tint_Col_Dragonbone.jpg|thumb|none|Custom Dragonbone Tint Colours]]

So now we have our set of colours. You’ll see next to the little colour square, the material editor gives you the RGB V4 values. We need to copy and paste these into the appropriate rows in the GFF editor, remembering to append a 1 to the end. So for example the Red channel value of 0.75,0.74,0.44 gets pasted as 0.75,0.74,0.44,1. If you try and paste just the 3 values, the editor will complain about it not being a proper V4 array. Based on our exploration of the tint masks earlier, we know that the Red and Green channels are for metal, so these get the boney colour we want along with a fairly bright colour for specular. Given that this is supposed to be bone and not metal, I probably should have used a darker colour instead which would give a flatter specular highlight, as opposed to the sharp, close to white, specular highly reflective materials like metal have. However the fact that the intensity value is being reduced to 1 (by just pasting the RGB values directly) should counteract this. The Blue channel gets a darkish brown with a dark specular, as that is for any leather and cloth. Save the TNT file and we are ready to test it in the game. Reusing the example scene from the original tint override:

[[image:ArmTnt_Dragonbone_Tint_Game.jpg|thumb|none|Custom Dragonbone Tint In-Game]]

OK, so not exactly the most thrilling tint in the world, but hopefully it demonstrates the principle. In particular, notice the reduction in the specular highlights between the two tints as a result of dropping the intensity. If you are trying to make a shiny metal then crank the intensity up, if making cloth, leather or some other flat, dull material (bone?) then crank it down. Adjust your specular colours to suit as well. Generally you want to make it some lighter shade of your diffuse colour, but the more reflective the object and the higher the intensity, the closer to white it should be.

[[Category:Tutorials]]

Overriding and creating tints tutorial

2010-01-17T10:15:21Z

DarthParametric: /* Advanced Tinting 101: Overriding with Custom Tints */

The [[Material Tint System|tint system]] is potentially very powerful, but its results are not always pleasing to everyone. One example in the base game that a number of people dislike is the number of armour and weapon material types (like Red Steel) that are a pinkish-red colour. The colour of a particular material is tied to its tint. What follows is a revised and enhanced version of several forum posts by DarthParametric on how to make armour and weapons more of a traditional metal colour by both replacing default tints with alternative ones that already exist in the game and using completely custom tints.

= Basic Override: Replacing One Set of Tints with Another =

The first thing is to open materialtypes.xls located in <install directory>\tools\Source\2DA\rules\ Change to the materialtypes tab. Here you’ll see all the armour and weapon material types and their associated tints. You'll want to find the entries for metal armour, metal weapons, and metal shields. For easy reference, here are the specific rows of interest (click for larger):

{| class="wikitable" border="1"
|-valign="top"
|[[Image:ArmTnt_2DA_Armour.jpg|200px]]
|[[Image:ArmTnt_2DA_Weapon.jpg|200px]]
|[[Image:ArmTnt_2DA_Shield.jpg|200px]]
|-align="center"
|Metal Armour Material Tints
|Metal Weapon Material Tints
|Metal Shield Material Tints
|}

Red Steel is obviously going to be the major offender in terms of pink/red colouration, but we’ll extract them all just to be safe. In the toolset directory, run ErfEditor.exe. Go to File->Open File and navigate to <install directory>\packages\core\data\ and select tints.erf and click Open. You’ll see all the game’s tint files. As seen in the 2DA, the tint files we want are prefaced T3_ARM_, T3_WPN_ and T3_SHD_, so scroll down until you find them all. Select (CTRL + left click) the 20 (there is no veridium shield) files we want, then right click and choose Extract Resource. In the pop-up folder browser, just choose somewhere easy to find like the Desktop and click OK.

Now what we are going to do is choose the tint file for one material type that looks appropriately metal-like and overwrite the others with copies of it. Before we do that though we need to see what colours each tint file has. Open the toolset. Go to File->New->Material. This is the [[Material editor|material editor]]. Right click on the Root object and choose Insert->Insert New Tint Library. Right click on the new tint library and choose Insert->Insert New Tint Object. Click on the new tint object and then in the Object Inspector (if it isn’t already open go to View->Other Windows->Object Inspector) look for the Import [[TNT]] File line and click the button to the right. Navigate to where you extracted the tint files and load one.

You’ll see in the Object Inspector a whole series of colours, labelled diffuse and specular for the red, green and blue channels. Diffuse is the actual base colour, and specular is the highlights. The channels it is referring to is of the [[Texture_Formats#Tint_Map|tint map]]. This has 4 channels (RGB plus Alpha), each of which is a greyscale image that is used to define the area its related tint colour is applied. Refer to the other relevant wiki tint and texture topics for more info.

If you load the tint files for all 7 different material types in turn, you’ll see a number of them have reddish colours. There are two which would be suitable replacements. The first is silverite, the second is steel. Both have bluish grey colours for the most part:

[[image:ArmTnt_Tnt_Stl_Sil.jpg|thumb|none|Silverite and Steel Tints]]

What you want to do is select one of those and make additional copies of the TNT file, then rename them appropriately (after deleting the originals) to replace the Iron, Grey Iron, Red Steel and Dragonbone tint files. Additionally, you may also choose to replace the Veridium tint file (for armour and weapons), which is a greenish tint, if that is not to your taste. Make sure you only replace a tint file with one of the same type, i.e. only replace armour tints with another armour tint, not a weapon or shield tint (the reason for this is detailed later). Once that is done, create a new folder in My Documents\BioWare\Dragon Age\packages\core\override\ and call it something appropriate (Armour & Weapon Tint Mod for example). Place your tint files in there. Load up the game and try out a formally pink suit of armour. You should get something like this:

[[image:ArmTnt_Arm_Tint_Edit.jpg|thumb|none|Before and After Tint Override]]

You can see there that Alistair has gone from the original red armour to a proper metal colour.

There are also some additional tints that you may want to look at. If you peruse the rest of materialtypes.xls you'll see that Templar armour uses T3_ARM_TMP.tnt and the king's armour uses T3_ARM_GLD.tnt.

= Advanced Tinting 101: Overriding with Custom Tints =

As alluded to previously, tint files hold a series of colours that are applied to a model in a manner that is defined by a [[Texture_Formats#Tint_Map|tint map]]. Each channel of the tint map is used as a mask to define a specific area of the parent texture to apply the associated tint. While tint maps have four channels (RGB+A), it’s mostly only face textures and related things like tattoos that use all four. Everything else tends just to use the RGB channels.

As you would have seen, the metal material tints extracted previously have a pair of colours, diffuse and specular, for each of the three tint map channels (thus 6 colours in total). The diffuse is what actually colours the base texture, the specular is the “shininess” – the colour of highlights caused by light reflection. A specific type of armour generally shares a single model (well, one model per sex per race, not counting scaled [[Texture_Formats#Level_of_Detail|LOD]] variants). There are usually 4 (occasionally 5) texture variants, and these are diversified further into actual item variations through the use of tints, the colour of which are determined by material type. As an example, I’ll use two texture variants of male medium armour (as with faces, armour models share a common UV map across races, although armour is split into male and female variants, aside from massive armour).

If you haven’t previously unpacked or browsed through the armour textures, you can find them in <install directory>\packages\core\textures\high\texturepack.erf. We’ll use variant A, pm_arm_meda_0d.dds, and variant D, pm_arm_medd_0d.dds. Notice the _0d suffix. This denotes the [[Texture_Formats#Diffuse_Map|diffuse map]]. You’ll see a number of associated textures with the same base filename as the diffuse maps. Those with the _0n suffix are the [[Texture_Formats#Normal_Map|normal maps]], those with _0s are the [[Texture_Formats#Specular_Map|specular maps]], and the ones we want, _0t, the [[Texture_Formats#Tint_Map|tint maps]]. Refer to the [[Texture_Formats|texture formats]] page for more info on texture types and filename conventions. Extract the two diffuse maps and the two tint maps to a working directory and open them with something that can handle [[DDS]] files.

You’ll see that the diffuse maps are just standard colour textures, albeit a tad dull. The tint maps, at first impression, look to be horrible technicolour nightmares. Change to the channels tab however and you’ll see how they work. Think of each channel as a separate alpha mask. Black is 100% transparency, white is 100% opacity, and shades of grey denote values in between. If we lay out the channels of the tint map as 3 separate images and compare them to the parent diffuse map, we get the following for the two texture variants:

[[image:ArmTnt_Med_Arm_Tint_Example_01.jpg|thumb|left|Male Medium Armour Texture A Plus Tint Masks]] [[image:ArmTnt_Med_Arm_Tint_Example_02.jpg|thumb|none|Male Medium Armour Texture D Plus Tint Masks]]
 If you look at the first image, variant A, you’ll see that the red channel of the tint mask is confined to areas of metal banding, the green channel to other metal areas like buckles and trim, and the blue channel to areas of leather. Variant D is a similar story, the red and green channels being confined to metal, the blue to leather. Because all three classes of metal armour (medium, heavy, massive) use a universal set of tints based on material type, if you look at the other metal armour tint masks you’ll see that this is the pattern that they all more or less conform to – the red channel is the primary metal area tint, the green channel the secondary metal area tint, the blue channel the leather/cloth/misc area tint (the "misc" mostly refers to the massive armours, which don’t have much leather or cloth and mainly use the blue channel for filigree patterns and other decorative effects).

Now that we know what each channel of the tint mask does, we can edit our tint file appropriately. Load the tint file you want to edit into the material editor. I’ll use the dragonbone tint, T3_ARM_DRB.tnt, for this example. Creating tints in the toolset's [[material editor]] has already been [[Tutorial:_Creating_recolors_of_existing_items|covered previously]], so I won't recount the process here. Instead, I'll cover editing [[TNT]] files directly in the GFF editor. You can do this in the toolset (by just going to File->Open and loading the TNT file) but I prefer to use the standalone GFF editor in the toolset directory, GffEditor.exe. You may find it handy to associate this program with all GFF file types so that you can quickly edit a particular file just by double clicking on it. With the TNT file open in the GFF editor, you’ll see something like this:

[[image:ArmTnt_TNT_GFF_Editor.jpg|thumb|none|Dragonbone Tint File in GFF Editor]]

Although it’s confusing at first, you’ll see it’s conveying the same basic information as that in the material editor, just in a more concise (and less visually intuitive) format. For a breakdown of the file structure and significance of the values, refer to the [[TNT]] page.

Now let’s look at the tint file in the material editor. We’ll use this to tweak the colours to our liking, then copy the values across to the file in the GFF editor. If you click on each colour you’ll get a button on the right that pops up a colour picker for easy tweaking. If you are using the Dragonbone tint file from earlier, it will be using the colour values from the Silverite or Steel tints, which are bluish grey. I don’t know what colour Dragonbone is supposed to be, but for this example I’ll change it to some brownish colours, as follows:

[[image:ArmTnt_Tint_Col_Dragonbone.jpg|thumb|none|Custom Dragonbone Tint Colours]]

So now we have our set of colours. You’ll see next to the little colour square, the material editor gives you the RGB V4 values. We need to copy and paste these into the appropriate rows in the GFF editor, remembering to append a 1 to the end. So for example the Red channel value of 0.75,0.74,0.44 gets pasted as 0.75,0.74,0.44,1. If you try and paste just the 3 values, the editor will complain about it not being a proper V4 array. Based on our exploration of the tint masks earlier, we know that the Red and Green channels are for metal, so these get the boney colour we want along with a fairly bright colour for specular. Given that this is supposed to be bone and not metal, I probably should have used a darker colour instead which would give a flatter specular highlight, as opposed to the sharp, close to white, specular highly reflective materials like metal have. However the fact that the intensity value is being reduced to 1 (by just pasting the RGB values directly) should counteract this. The Blue channel gets a darkish brown with a dark specular, as that is for any leather and cloth. Save the TNT file and we are ready to test it in the game. Reusing the example scene from the original tint override:

[[image:ArmTnt_Dragonbone_Tint_Game.jpg|thumb|none|Custom Dragonbone Tint In-Game]]

OK, so not exactly the most thrilling tint in the world, but hopefully it demonstrates the principle. In particular, notice the reduction in the specular highlights between the two tints as a result of dropping the intensity. If you are trying to make a shiny metal then crank the intensity up, if making cloth, leather or some other flat, dull material (bone?) then crank it down. Adjust your specular colours to suit as well. Generally you want to make it some lighter shade of your diffuse colour, but the more reflective the object and the higher the intensity, the closer to white it should be.

[[Category:Tutorials]]

Tutorials

2010-01-17T10:12:13Z

DarthParametric: /* Custom content tutorials */

==Introductory tutorials ==

In the course of these tutorials we'll go through all the steps needed to create a basic adventure.

{{sidebox|
*Boxes like this contain a checklist of important steps.
*They're intended as a reminder and as a navigational aid.
}}

*[[Introductory tutorial]] - An overview of the toolset as a whole
*[[Module tutorial]] - how to create a module to work in.

This set of tutorials forms a series, each building on or filling in omissions by the last:
*[[Area tutorial]]
*[[Placeable tutorial]]
*[[Item tutorial]]
*[[Creature tutorial]]
*[[Conversation tutorial]]

Once you've become familiar with the basics introduced on those tutorials you might have a better grounding for:
*[[Cutscene tutorial]]
*[[Map tutorial]] (which also introduces you to [[2DA]] editing)
*[[Level Editor Tutorial]]
*[[Scripting tutorial]]

== Demo module ==

The toolset currently ships with a simple demo module pre-loaded into its database.

*[[Demo module]] - how to export and run the demo module.

== Custom content tutorials ==
*[[Tutorial: Idiots guide to make special objects]]
*[[Tutorial: idiots guide to adding custom items to singleplayer]]
*[[Tutorial: Adding a Custom Model to Toolset]]
*[[Tutorial: Creating a custom placeable from a model]]
*[[Tutorial: Reskinning an Item]]
*[[Tutorial: Creating recolors of existing items]]
*[[Tutorial: Understanding Tints: Overriding Defaults & Creating New Ones]]
*[[Adding a New Spell Tutorial]]

== Character generation tutorials ==
*[[Backgrounds tutorial]]
*[[Add A New Class Tutorial]]

== Other Tutorials ==
*[[ToolSet: Area Layouts]]
*[[Adding a Location to the Single Player Campaign Tutorial]]
*[[Follower tutorial]] (Simple and advanced, requires scripting knowledge)

== External Tutorials ==
*[http://lerlek.se/Video+Tutorials Lerlek Dragon Age Origins Toolset Video Tutorials Collection] has collected many in-depth video tutorials.
*[http://dragonagemodding.wordpress.com Beyond Ferelden] has many in-depth tutorials by jwvanderbeck.
*[http://www.youtube.com/watch?v=TwQNRBFLhrE Playable Area and Conversation] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=CaHldJcUTz8 Simple Conversation Cameras] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=QOQJ2heQto4 Cutscene and Trigger] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=szWKgj2ZuXo Custom Level and Room Building] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=DKJ7F14n8o8 Downloading and Installing the Toolset] video tutorial by [http://social.bioware.com/74287/ DragonAge22].
*[http://www.youtube.com/watch?v=iMPBsulv9xI Creating a Room] video tutorial by [http://social.bioware.com/74287/ DragonAge22].
*[http://www.youtube.com/watch?v=g3kx2CaarHo How to Make an Interior Level with Lighting] video tutorial by [http://social.bioware.com/group/60/ Darkworld Development Team].
*[http://www.youtube.com/watch?v=O6TeZeE1Lc8 Making a Room] video tutorial by BigDrip681.
*[http://social.bioware.com/5339/blog/576/ Custom Player Items In Single Player] by [http://social.bioware.com/5339/ weriK].
*[http://social.bioware.com/5339/blog/651/ The Secret Behind Item Statistics] by [http://social.bioware.com/5339/ weriK].
*[http://social.bioware.com/project/923/ Guide for installing/uninstalling/updating Mods] Beginner Guide to get started with using Mods by [http://social.bioware.com/237411/ Alexspeed].
*[http://www.jezelf.co.uk/tutorials.htm Photoshop Map making tutorials] Credits to Jason Elford, brought to DAT wiki by [http://social.bioware.com/48156/ Arixsus]
*[http://social.bioware.com/project/527/ Video Tutorials by SilentCid] Multiple in-depth video tutorials of the DA Toolset
*[http://www.youtube.com/view_play_list?p=EF29DD1AACEBA92A Qkrch's Video Tutorials] Toolset tutorial complete series for the experienced builder (Spanish & English)
[[Category:Tutorials| ]]

Overriding and creating tints tutorial

2010-01-17T10:11:18Z

DarthParametric: moved Understanding Tints: Overriding Defaults & Creating New Ones to Tutorial: Understanding Tints: Overriding Defaults & Creating New Ones

The [[Material Tint System|tint system]] is potentially very powerful, but its results are not always pleasing to everyone. One example in the base game that a number of people dislike is the number of armour and weapon material types (like Red Steel) that are a pinkish-red colour. The colour of a particular material is tied to its tint. What follows is a revised and enhanced version of several forum posts by DarthParametric on how to make armour and weapons more of a traditional metal colour by both replacing default tints with alternative ones that already exist in the game and using completely custom tints.

= Basic Override: Replacing One Set of Tints with Another =

The first thing is to open materialtypes.xls located in <install directory>\tools\Source\2DA\rules\ Change to the materialtypes tab. Here you’ll see all the armour and weapon material types and their associated tints. You'll want to find the entries for metal armour, metal weapons, and metal shields. For easy reference, here are the specific rows of interest (click for larger):

{| class="wikitable" border="1"
|-valign="top"
|[[Image:ArmTnt_2DA_Armour.jpg|200px]]
|[[Image:ArmTnt_2DA_Weapon.jpg|200px]]
|[[Image:ArmTnt_2DA_Shield.jpg|200px]]
|-align="center"
|Metal Armour Material Tints
|Metal Weapon Material Tints
|Metal Shield Material Tints
|}

Red Steel is obviously going to be the major offender in terms of pink/red colouration, but we’ll extract them all just to be safe. In the toolset directory, run ErfEditor.exe. Go to File->Open File and navigate to <install directory>\packages\core\data\ and select tints.erf and click Open. You’ll see all the game’s tint files. As seen in the 2DA, the tint files we want are prefaced T3_ARM_, T3_WPN_ and T3_SHD_, so scroll down until you find them all. Select (CTRL + left click) the 20 (there is no veridium shield) files we want, then right click and choose Extract Resource. In the pop-up folder browser, just choose somewhere easy to find like the Desktop and click OK.

Now what we are going to do is choose the tint file for one material type that looks appropriately metal-like and overwrite the others with copies of it. Before we do that though we need to see what colours each tint file has. Open the toolset. Go to File->New->Material. This is the [[Material editor|material editor]]. Right click on the Root object and choose Insert->Insert New Tint Library. Right click on the new tint library and choose Insert->Insert New Tint Object. Click on the new tint object and then in the Object Inspector (if it isn’t already open go to View->Other Windows->Object Inspector) look for the Import [[TNT]] File line and click the button to the right. Navigate to where you extracted the tint files and load one.

You’ll see in the Object Inspector a whole series of colours, labelled diffuse and specular for the red, green and blue channels. Diffuse is the actual base colour, and specular is the highlights. The channels it is referring to is of the [[Texture_Formats#Tint_Map|tint map]]. This has 4 channels (RGB plus Alpha), each of which is a greyscale image that is used to define the area its related tint colour is applied. Refer to the other relevant wiki tint and texture topics for more info.

If you load the tint files for all 7 different material types in turn, you’ll see a number of them have reddish colours. There are two which would be suitable replacements. The first is silverite, the second is steel. Both have bluish grey colours for the most part:

[[image:ArmTnt_Tnt_Stl_Sil.jpg|thumb|none|Silverite and Steel Tints]]

What you want to do is select one of those and make additional copies of the TNT file, then rename them appropriately (after deleting the originals) to replace the Iron, Grey Iron, Red Steel and Dragonbone tint files. Additionally, you may also choose to replace the Veridium tint file (for armour and weapons), which is a greenish tint, if that is not to your taste. Make sure you only replace a tint file with one of the same type, i.e. only replace armour tints with another armour tint, not a weapon or shield tint (the reason for this is detailed later). Once that is done, create a new folder in My Documents\BioWare\Dragon Age\packages\core\override\ and call it something appropriate (Armour & Weapon Tint Mod for example). Place your tint files in there. Load up the game and try out a formally pink suit of armour. You should get something like this:

[[image:ArmTnt_Arm_Tint_Edit.jpg|thumb|none|Before and After Tint Override]]

You can see there that Alistair has gone from the original red armour to a proper metal colour.

There are also some additional tints that you may want to look at. If you peruse the rest of materialtypes.xls you'll see that Templar armour uses T3_ARM_TMP.tnt and the king's armour uses T3_ARM_GLD.tnt.

= Advanced Tinting 101: Overriding with Custom Tints =

As alluded to previously, tint files hold a series of colours that are applied to a model in a manner that is defined by a [[Texture_Formats#Tint_Map|tint map]]. Each channel of the tint map is used as a mask to define a specific area of the parent texture to apply the associated tint. While tint maps have four channels (RGB+A), it’s mostly only face textures and related things like tattoos that use all four. Everything else tends just to use the RGB channels.

As you would have seen, the metal material tints extracted previously have a pair of colours, diffuse and specular, for each of the three tint map channels (thus 6 colours in total). The diffuse is what actually colours the base texture, the specular is the “shininess” – the colour of highlights caused by light reflection. A specific type of armour generally shares a single model (well, one model per sex per race, not counting scaled [[Texture_Formats#Level_of_Detail|LOD]] variants). There are usually 4 (occasionally 5) texture variants, and these are diversified further into actual item variations through the use of tints, the colour of which are determined by material type. As an example, I’ll use two texture variants of male medium armour (as with faces, armour models share a common UV map across races, although armour is split into male and female variants, aside from massive armour).

If you haven’t previously unpacked or browsed through the armour textures, you can find them in <install directory>\packages\core\textures\high\texturepack.erf. We’ll use variant A, pm_arm_meda_0d.dds, and variant D, pm_arm_medd_0d.dds. Notice the _0d suffix. This denotes the [[Texture_Formats#Diffuse_Map|diffuse map]]. You’ll see a number of associated textures with the same base filename as the diffuse maps. Those with the _0n suffix are the [[Texture_Formats#Normal_Map|normal maps]], those with _0s are the [[Texture_Formats#Specular_Map|specular maps]], and the ones we want, _0t, the [[Texture_Formats#Tint_Map|tint maps]]. Refer to the [[Texture_Formats|texture formats]] page for more info on texture types and filename conventions. Extract the two diffuse maps and the two tint maps to a working directory and open them with something that can handle [[DDS]] files.

You’ll see that the diffuse maps are just standard colour textures, albeit a tad dull. The tint maps, at first impression, look to be horrible technicolour nightmares. Change to the channels tab however and you’ll see how they work. Think of each channel as a separate alpha mask. Black is 100% transparency, white is 100% opacity, and shades of grey denote values in between. If we lay out the channels of the tint map as 3 separate images and compare them to the parent diffuse map, we get the following for the two texture variants:

[[image:ArmTnt_Med_Arm_Tint_Example_01.jpg|thumb|left|Male Medium Armour Texture A Plus Tint Masks]] [[image:ArmTnt_Med_Arm_Tint_Example_02.jpg|thumb|none|Male Medium Armour Texture D Plus Tint Masks]]

If you look at the first image, variant A, you’ll see that the red channel of the tint mask is confined to areas of metal banding, the green channel to other metal areas like buckles and trim, and the blue channel to areas of leather. Variant D is a similar story, the red and green channels being confined to metal, the blue to leather. Because all three classes of metal armour (medium, heavy, massive) use a universal set of tints based on material type, if you look at the other metal armour tint masks you’ll see that this is the pattern that they all more or less conform to – the red channel is the primary metal area tint, the green channel the secondary metal area tint, the blue channel the leather/cloth/misc area tint (the "misc" mostly refers to the massive armours, which don’t have much leather or cloth and mainly use the blue channel for filigree patterns and other decorative effects).

Now that we know what each channel of the tint mask does, we can edit our tint file appropriately. Load the tint file you want to edit into the material editor. I’ll use the dragonbone tint, T3_ARM_DRB.tnt, for this example. Creating tints in the toolset's [[material editor]] has already been [[Tutorial:_Creating_recolors_of_existing_items|covered previously]], so I won't recount the process here. Instead, I'll cover editing [[TNT]] files directly in the GFF editor. You can do this in the toolset (by just going to File->Open and loading the TNT file) but I prefer to use the standalone GFF editor in the toolset directory, GffEditor.exe. You may find it handy to associate this program with all GFF file types so that you can quickly edit a particular file just by double clicking on it. With the TNT file open in the GFF editor, you’ll see something like this:

[[image:ArmTnt_TNT_GFF_Editor.jpg|thumb|none|Dragonbone Tint File in GFF Editor]]

Although it’s confusing at first, you’ll see it’s conveying the same basic information as that in the material editor, just in a more concise (and less visually intuitive) format. For a breakdown of the file structure and significance of the values, refer to the [[TNT]] page.

Now let’s look at the tint file in the material editor. We’ll use this to tweak the colours to our liking, then copy the values across to the file in the GFF editor. If you click on each colour you’ll get a button on the right that pops up a colour picker for easy tweaking. If you are using the Dragonbone tint file from earlier, it will be using the colour values from the Silverite or Steel tints, which are bluish grey. I don’t know what colour Dragonbone is supposed to be, but for this example I’ll change it to some brownish colours, as follows:

[[image:ArmTnt_Tint_Col_Dragonbone.jpg|thumb|none|Custom Dragonbone Tint Colours]]

So now we have our set of colours. You’ll see next to the little colour square, the material editor gives you the RGB V4 values. We need to copy and paste these into the appropriate rows in the GFF editor, remembering to append a 1 to the end. So for example the Red channel value of 0.75,0.74,0.44 gets pasted as 0.75,0.74,0.44,1. If you try and paste just the 3 values, the editor will complain about it not being a proper V4 array. Based on our exploration of the tint masks earlier, we know that the Red and Green channels are for metal, so these get the boney colour we want along with a fairly bright colour for specular. Given that this is supposed to be bone and not metal, I probably should have used a darker colour instead which would give a flatter specular highlight, as opposed to the sharp, close to white, specular highly reflective materials like metal have. However the fact that the intensity value is being reduced to 1 (by just pasting the RGB values directly) should counteract this. The Blue channel gets a darkish brown with a dark specular, as that is for any leather and cloth. Save the TNT file and we are ready to test it in the game. Reusing the example scene from the original tint override:

[[image:ArmTnt_Dragonbone_Tint_Game.jpg|thumb|none|Custom Dragonbone Tint In-Game]]

OK, so not exactly the most thrilling tint in the world, but hopefully it demonstrates the principle. In particular, notice the reduction in the specular highlights between the two tints as a result of dropping the intensity. If you are trying to make a shiny metal then crank the intensity up, if making cloth, leather or some other flat, dull material (bone?) then crank it down. Adjust your specular colours to suit as well. Generally you want to make it some lighter shade of your diffuse colour, but the more reflective the object and the higher the intensity, the closer to white it should be.

[[Category:Tutorials]]

Overriding and creating tints tutorial

2010-01-17T10:10:50Z

DarthParametric: Created page with 'The tint system is potentially very powerful, but its results are not always pleasing to everyone. One example in the base game that a number of people d...'

The [[Material Tint System|tint system]] is potentially very powerful, but its results are not always pleasing to everyone. One example in the base game that a number of people dislike is the number of armour and weapon material types (like Red Steel) that are a pinkish-red colour. The colour of a particular material is tied to its tint. What follows is a revised and enhanced version of several forum posts by DarthParametric on how to make armour and weapons more of a traditional metal colour by both replacing default tints with alternative ones that already exist in the game and using completely custom tints.

= Basic Override: Replacing One Set of Tints with Another =

The first thing is to open materialtypes.xls located in <install directory>\tools\Source\2DA\rules\ Change to the materialtypes tab. Here you’ll see all the armour and weapon material types and their associated tints. You'll want to find the entries for metal armour, metal weapons, and metal shields. For easy reference, here are the specific rows of interest (click for larger):

{| class="wikitable" border="1"
|-valign="top"
|[[Image:ArmTnt_2DA_Armour.jpg|200px]]
|[[Image:ArmTnt_2DA_Weapon.jpg|200px]]
|[[Image:ArmTnt_2DA_Shield.jpg|200px]]
|-align="center"
|Metal Armour Material Tints
|Metal Weapon Material Tints
|Metal Shield Material Tints
|}

Red Steel is obviously going to be the major offender in terms of pink/red colouration, but we’ll extract them all just to be safe. In the toolset directory, run ErfEditor.exe. Go to File->Open File and navigate to <install directory>\packages\core\data\ and select tints.erf and click Open. You’ll see all the game’s tint files. As seen in the 2DA, the tint files we want are prefaced T3_ARM_, T3_WPN_ and T3_SHD_, so scroll down until you find them all. Select (CTRL + left click) the 20 (there is no veridium shield) files we want, then right click and choose Extract Resource. In the pop-up folder browser, just choose somewhere easy to find like the Desktop and click OK.

Now what we are going to do is choose the tint file for one material type that looks appropriately metal-like and overwrite the others with copies of it. Before we do that though we need to see what colours each tint file has. Open the toolset. Go to File->New->Material. This is the [[Material editor|material editor]]. Right click on the Root object and choose Insert->Insert New Tint Library. Right click on the new tint library and choose Insert->Insert New Tint Object. Click on the new tint object and then in the Object Inspector (if it isn’t already open go to View->Other Windows->Object Inspector) look for the Import [[TNT]] File line and click the button to the right. Navigate to where you extracted the tint files and load one.

You’ll see in the Object Inspector a whole series of colours, labelled diffuse and specular for the red, green and blue channels. Diffuse is the actual base colour, and specular is the highlights. The channels it is referring to is of the [[Texture_Formats#Tint_Map|tint map]]. This has 4 channels (RGB plus Alpha), each of which is a greyscale image that is used to define the area its related tint colour is applied. Refer to the other relevant wiki tint and texture topics for more info.

If you load the tint files for all 7 different material types in turn, you’ll see a number of them have reddish colours. There are two which would be suitable replacements. The first is silverite, the second is steel. Both have bluish grey colours for the most part:

[[image:ArmTnt_Tnt_Stl_Sil.jpg|thumb|none|Silverite and Steel Tints]]

What you want to do is select one of those and make additional copies of the TNT file, then rename them appropriately (after deleting the originals) to replace the Iron, Grey Iron, Red Steel and Dragonbone tint files. Additionally, you may also choose to replace the Veridium tint file (for armour and weapons), which is a greenish tint, if that is not to your taste. Make sure you only replace a tint file with one of the same type, i.e. only replace armour tints with another armour tint, not a weapon or shield tint (the reason for this is detailed later). Once that is done, create a new folder in My Documents\BioWare\Dragon Age\packages\core\override\ and call it something appropriate (Armour & Weapon Tint Mod for example). Place your tint files in there. Load up the game and try out a formally pink suit of armour. You should get something like this:

[[image:ArmTnt_Arm_Tint_Edit.jpg|thumb|none|Before and After Tint Override]]

You can see there that Alistair has gone from the original red armour to a proper metal colour.

There are also some additional tints that you may want to look at. If you peruse the rest of materialtypes.xls you'll see that Templar armour uses T3_ARM_TMP.tnt and the king's armour uses T3_ARM_GLD.tnt.

= Advanced Tinting 101: Overriding with Custom Tints =

As alluded to previously, tint files hold a series of colours that are applied to a model in a manner that is defined by a [[Texture_Formats#Tint_Map|tint map]]. Each channel of the tint map is used as a mask to define a specific area of the parent texture to apply the associated tint. While tint maps have four channels (RGB+A), it’s mostly only face textures and related things like tattoos that use all four. Everything else tends just to use the RGB channels.

As you would have seen, the metal material tints extracted previously have a pair of colours, diffuse and specular, for each of the three tint map channels (thus 6 colours in total). The diffuse is what actually colours the base texture, the specular is the “shininess” – the colour of highlights caused by light reflection. A specific type of armour generally shares a single model (well, one model per sex per race, not counting scaled [[Texture_Formats#Level_of_Detail|LOD]] variants). There are usually 4 (occasionally 5) texture variants, and these are diversified further into actual item variations through the use of tints, the colour of which are determined by material type. As an example, I’ll use two texture variants of male medium armour (as with faces, armour models share a common UV map across races, although armour is split into male and female variants, aside from massive armour).

If you haven’t previously unpacked or browsed through the armour textures, you can find them in <install directory>\packages\core\textures\high\texturepack.erf. We’ll use variant A, pm_arm_meda_0d.dds, and variant D, pm_arm_medd_0d.dds. Notice the _0d suffix. This denotes the [[Texture_Formats#Diffuse_Map|diffuse map]]. You’ll see a number of associated textures with the same base filename as the diffuse maps. Those with the _0n suffix are the [[Texture_Formats#Normal_Map|normal maps]], those with _0s are the [[Texture_Formats#Specular_Map|specular maps]], and the ones we want, _0t, the [[Texture_Formats#Tint_Map|tint maps]]. Refer to the [[Texture_Formats|texture formats]] page for more info on texture types and filename conventions. Extract the two diffuse maps and the two tint maps to a working directory and open them with something that can handle [[DDS]] files.

You’ll see that the diffuse maps are just standard colour textures, albeit a tad dull. The tint maps, at first impression, look to be horrible technicolour nightmares. Change to the channels tab however and you’ll see how they work. Think of each channel as a separate alpha mask. Black is 100% transparency, white is 100% opacity, and shades of grey denote values in between. If we lay out the channels of the tint map as 3 separate images and compare them to the parent diffuse map, we get the following for the two texture variants:

[[image:ArmTnt_Med_Arm_Tint_Example_01.jpg|thumb|left|Male Medium Armour Texture A Plus Tint Masks]] [[image:ArmTnt_Med_Arm_Tint_Example_02.jpg|thumb|none|Male Medium Armour Texture D Plus Tint Masks]]

If you look at the first image, variant A, you’ll see that the red channel of the tint mask is confined to areas of metal banding, the green channel to other metal areas like buckles and trim, and the blue channel to areas of leather. Variant D is a similar story, the red and green channels being confined to metal, the blue to leather. Because all three classes of metal armour (medium, heavy, massive) use a universal set of tints based on material type, if you look at the other metal armour tint masks you’ll see that this is the pattern that they all more or less conform to – the red channel is the primary metal area tint, the green channel the secondary metal area tint, the blue channel the leather/cloth/misc area tint (the "misc" mostly refers to the massive armours, which don’t have much leather or cloth and mainly use the blue channel for filigree patterns and other decorative effects).

Now that we know what each channel of the tint mask does, we can edit our tint file appropriately. Load the tint file you want to edit into the material editor. I’ll use the dragonbone tint, T3_ARM_DRB.tnt, for this example. Creating tints in the toolset's [[material editor]] has already been [[Tutorial:_Creating_recolors_of_existing_items|covered previously]], so I won't recount the process here. Instead, I'll cover editing [[TNT]] files directly in the GFF editor. You can do this in the toolset (by just going to File->Open and loading the TNT file) but I prefer to use the standalone GFF editor in the toolset directory, GffEditor.exe. You may find it handy to associate this program with all GFF file types so that you can quickly edit a particular file just by double clicking on it. With the TNT file open in the GFF editor, you’ll see something like this:

[[image:ArmTnt_TNT_GFF_Editor.jpg|thumb|none|Dragonbone Tint File in GFF Editor]]

Although it’s confusing at first, you’ll see it’s conveying the same basic information as that in the material editor, just in a more concise (and less visually intuitive) format. For a breakdown of the file structure and significance of the values, refer to the [[TNT]] page.

Now let’s look at the tint file in the material editor. We’ll use this to tweak the colours to our liking, then copy the values across to the file in the GFF editor. If you click on each colour you’ll get a button on the right that pops up a colour picker for easy tweaking. If you are using the Dragonbone tint file from earlier, it will be using the colour values from the Silverite or Steel tints, which are bluish grey. I don’t know what colour Dragonbone is supposed to be, but for this example I’ll change it to some brownish colours, as follows:

[[image:ArmTnt_Tint_Col_Dragonbone.jpg|thumb|none|Custom Dragonbone Tint Colours]]

So now we have our set of colours. You’ll see next to the little colour square, the material editor gives you the RGB V4 values. We need to copy and paste these into the appropriate rows in the GFF editor, remembering to append a 1 to the end. So for example the Red channel value of 0.75,0.74,0.44 gets pasted as 0.75,0.74,0.44,1. If you try and paste just the 3 values, the editor will complain about it not being a proper V4 array. Based on our exploration of the tint masks earlier, we know that the Red and Green channels are for metal, so these get the boney colour we want along with a fairly bright colour for specular. Given that this is supposed to be bone and not metal, I probably should have used a darker colour instead which would give a flatter specular highlight, as opposed to the sharp, close to white, specular highly reflective materials like metal have. However the fact that the intensity value is being reduced to 1 (by just pasting the RGB values directly) should counteract this. The Blue channel gets a darkish brown with a dark specular, as that is for any leather and cloth. Save the TNT file and we are ready to test it in the game. Reusing the example scene from the original tint override:

[[image:ArmTnt_Dragonbone_Tint_Game.jpg|thumb|none|Custom Dragonbone Tint In-Game]]

OK, so not exactly the most thrilling tint in the world, but hopefully it demonstrates the principle. In particular, notice the reduction in the specular highlights between the two tints as a result of dropping the intensity. If you are trying to make a shiny metal then crank the intensity up, if making cloth, leather or some other flat, dull material (bone?) then crank it down. Adjust your specular colours to suit as well. Generally you want to make it some lighter shade of your diffuse colour, but the more reflective the object and the higher the intensity, the closer to white it should be.

[[Category:Tutorials]]

File:ArmTnt Dragonbone Tint Game.jpg

2010-01-17T10:07:56Z

DarthParametric:

File:ArmTnt Tint Col Dragonbone.jpg

2010-01-17T10:04:26Z

DarthParametric:

File:ArmTnt TNT GFF Editor.jpg

2010-01-17T09:56:08Z

DarthParametric:

File:ArmTnt Med Arm Tint Example 02.jpg

2010-01-17T09:42:59Z

DarthParametric:

File:ArmTnt Med Arm Tint Example 01.jpg

2010-01-17T09:40:29Z

DarthParametric:

File:ArmTnt Tnt Stl Sil.jpg

2010-01-17T08:44:23Z

DarthParametric:

File:ArmTnt Arm Tint Edit.jpg

2010-01-17T08:14:37Z

DarthParametric:

File:ArmTnt 2DA Armour.jpg

2010-01-17T07:38:49Z

DarthParametric: uploaded a new version of "File:ArmTnt 2DA Armour.jpg"

File:ArmTnt 2DA Weapon.jpg

2010-01-17T07:38:13Z

DarthParametric: uploaded a new version of "File:ArmTnt 2DA Weapon.jpg"

File:ArmTnt 2DA Shield.jpg

2010-01-17T07:37:29Z

DarthParametric: uploaded a new version of "File:ArmTnt 2DA Shield.jpg"

File:ArmTnt 2DA Shield.jpg

2010-01-17T07:35:44Z

DarthParametric:

File:ArmTnt 2DA Weapon.jpg

2010-01-17T07:35:26Z

DarthParametric:

File:ArmTnt 2DA Armour.jpg

2010-01-17T07:33:20Z

DarthParametric:

Texture Formats

2010-01-16T13:38:43Z

DarthParametric: /* Diffuse Map */

Textures in DAO are stored in the [[DDS]] format. Native support of this file type can be added to a graphics package such as Adobe Photoshop or GIMP via the use of plugins. Alternatively, a DDS can be converted into a more universal format such as TGA or JPG using 3rd party tools.

== Texture Types ==

Dragon Age uses a number of different texture types. While all are in the [[DDS]] format, they have different purposes. The filename scheme differentiates these types with a suffix. Typically, a texture set for a particular model consists of 4 different types. These are as follows, using the deer model as an example:

c_deera_0d.dds - Diffuse map (''d'' suffix)

c_deera_0n.dds - Normal map (''n'' suffix)

c_deera_0s.dds - Specular map (''s'' suffix)

c_deera_0t.dds - Tint map (''t'' suffix)

Additional texture types are used on some models. The most common type is a height map used on static objects like floors and walls, designated with the ''h'' suffix.

=== Diffuse Map ===

This texture holds the base colour information for the model. Diffuse maps are commonly referred to as "skins" in other games. Diffuse maps can be enhanced through the use of the [[Material Tint System|tint system]], which overlays a series of colours (defined by the [[TNT]] file) on the diffuse map in a pattern defined by the associated tint map.

RGB channels - These hold the colour information, as with any standard image.

Alpha channel - The alpha channel is multi-purpose. Typically it holds transparency information (black is 100% transparency, white is 100% opacity, shades of grey denote values in between), however in some cases, such as face textures, it holds the specular map instead. In these instances there is no separate specular map.

Special cases: Some diffuse maps, notably for hair, do not follow the standard arrangement and are instead what is known as a "packed texture". In these instances, the image is essentially a container for 4 separate greyscale texture maps, one in each channel. These are used in conjunction with the [[Material Tint System|tint system]] when full colour diffuse maps are not necessary. For example, the hair diffuse map is a packed texture that appears to have the normal map in the red channel, the specular map in the green channel, the alpha map in the blue channel, and the diffuse map in the alpha channel.

DDS Compression: [[DDS Export Settings]]

[[image:TexFor_Deer_Dif_Map.jpg|thumb|none|Deer diffuse map]]

=== Normal Map ===

Normal maps are an enhanced version of bump maps, and are used to fake the appearance of additional geometry on a low polygon mesh. They work by providing information on how light would be reflected from a polygon's surface normal (hence the name normal map) as if it were part of a more detailed model. This provides the optical illusion of extra height and depth to otherwise flat geometry. It is typically used to provide roughness to surfaces like rock, or intricate detail like raised filigree patterns on armour and weapons. It is a way of providing highly detailed models without the use of a large number of polygons.

Normal maps used by Dragon Age differ from the typical tangent-space normal maps used in other games. A tangent-space normal map holds X information in the red channel, Y information in the green channel, and Z information in the blue channel. DA normal maps are RGBA with only X and Y information. Z information is interpolated on the fly.

R = Y (same as G channel in regular normal maps)

G = Y (same as G channel in regular normal maps)

B = Y (same as G channel in regular normal maps)

Alpha = X (same as R channel in regular normal maps)

DDS Compression: [[DDS Export Settings]]

[[image:TexFor_Deer_Nml_Map_DA.jpg|thumb|left|Deer normal map in DA format]] [[image:TexFor_Deer_Nml_Map_Reg.jpg|thumb|none|Deer normal map converted to typical RGB format]]

=== Specular Map ===

Specular maps hold information on how an object reflects light. It is sometimes also referred to as a gloss map. Lighting is games does not reflect the true behaviour of light in the real world, thus specular highlights are used to give the illusion of light reflecting off a surface. In simplest terms, it denotes the size and intensity of bright spots on an object, places where light would reflect back in the real world. Objects that should appear very shiny, like polished metal, have high sharp specular highlights, objects that should appear fairly dull, like cloth, have low flat specular highlights.

Specular maps function in a manner not dissimilar to alpha masks, in that the closer to white an area it is, the brighter the highlight. They appear to function as a container file, holding 4 greyscale specular maps, one in each channel.

DDS Compression: [[DDS Export Settings]]

[[image:TexFor_Deer_Spec_Map_4ch.jpg|thumb|none|Deer specular map]]

=== Tint Map ===

Tint maps are another container texture, holding a series of greyscale images. Each channel is actually an alpha mask. They denote areas of the associated diffuse texture that will be affected by the corresponding tint colour defined in the [[TNT]] file.

DDS Compression: [[DDS Export Settings]]

[[image:TexFor_Deer_Tint_Map.jpg|thumb|none|RGB channels for deer tint map]]

== Material Object ==

A texture set for a model is defined in the model's material object or [[MAO]]. See the [[MAO]] page for more info.

== Level of Detail ==

Most complex models (such as NPCs and creatures) have a scaling level of detail (LOD). As a player moves further away from an object, the LOD is progressively scaled down to reduce system overhead. Both the geometry and textures of a model may have LOD variants. DA uses three LOD levels, denoted by the suffix. The three levels are 0 (highest), 2 and 3 (lowest). For LOD0, the suffix is simply _0''x'' (where ''x'' denotes texture type). For LOD2, the suffix is _0''x''l2 and for LOD3, it is _0''x''l3. For example, c_deera_0d.dds is a diffuse texture at the highest LOD, c_deera_0dl2.dds and c_deera_0dl3.dds are the LOD2 and LOD3 diffuse textures, respectively. Each LOD texture level is generally 25% the size of the preceding level. For instance, for a LOD0 texture that is 1024x1024, the LOD2 texture will be 512x512 and the LOD3 texture will be 256x256. As well as diffuse maps, LOD is also used for specular and tint maps. Normal maps have no scaling LOD, as they are only used for LOD0.

[[image:TexFor_Deer_LOD.jpg|thumb|none|Scaling LOD for deer diffuse map]]

== Related Links ==

[[Tutorial: Reskinning an Item]]

[[Material editor|Material Editor]]

[[Material Tint System]]

=== External Links ===

nVidia DDS Plugin for Adobe Photoshop (32bit only)
http://developer.nvidia.com/object/photoshop_dds_plugins.html

DDS Plugin for GIMP
http://nifelheim.dyndns.org/~cocidius/dds/

DDS Converter v2.1 (DDS conversion tool)
http://eliteforce2.filefront.com/file/DDS_Converter;29412

nVidia DDS Utilities (includes DDS conversion tool)
http://developer.nvidia.com/object/dds_utilities_legacy.html

[[Category:Textures]]

Texture Formats

2010-01-16T13:38:27Z

DarthParametric: /* Diffuse Map */

Textures in DAO are stored in the [[DDS]] format. Native support of this file type can be added to a graphics package such as Adobe Photoshop or GIMP via the use of plugins. Alternatively, a DDS can be converted into a more universal format such as TGA or JPG using 3rd party tools.

== Texture Types ==

Dragon Age uses a number of different texture types. While all are in the [[DDS]] format, they have different purposes. The filename scheme differentiates these types with a suffix. Typically, a texture set for a particular model consists of 4 different types. These are as follows, using the deer model as an example:

c_deera_0d.dds - Diffuse map (''d'' suffix)

c_deera_0n.dds - Normal map (''n'' suffix)

c_deera_0s.dds - Specular map (''s'' suffix)

c_deera_0t.dds - Tint map (''t'' suffix)

Additional texture types are used on some models. The most common type is a height map used on static objects like floors and walls, designated with the ''h'' suffix.

=== Diffuse Map ===

This texture holds the base colour information for the model. Diffuse maps are commonly referred to as "skins" in other games. Diffuse maps can be enhanced through the use of the [[Material Tint System|tint system], which overlays a series of colours (defined by the [[TNT]] file) on the diffuse map in a pattern defined by the associated tint map.

RGB channels - These hold the colour information, as with any standard image.

Alpha channel - The alpha channel is multi-purpose. Typically it holds transparency information (black is 100% transparency, white is 100% opacity, shades of grey denote values in between), however in some cases, such as face textures, it holds the specular map instead. In these instances there is no separate specular map.

Special cases: Some diffuse maps, notably for hair, do not follow the standard arrangement and are instead what is known as a "packed texture". In these instances, the image is essentially a container for 4 separate greyscale texture maps, one in each channel. These are used in conjunction with the [[Material Tint System|tint system]] when full colour diffuse maps are not necessary. For example, the hair diffuse map is a packed texture that appears to have the normal map in the red channel, the specular map in the green channel, the alpha map in the blue channel, and the diffuse map in the alpha channel.

DDS Compression: [[DDS Export Settings]]

[[image:TexFor_Deer_Dif_Map.jpg|thumb|none|Deer diffuse map]]

=== Normal Map ===

Normal maps are an enhanced version of bump maps, and are used to fake the appearance of additional geometry on a low polygon mesh. They work by providing information on how light would be reflected from a polygon's surface normal (hence the name normal map) as if it were part of a more detailed model. This provides the optical illusion of extra height and depth to otherwise flat geometry. It is typically used to provide roughness to surfaces like rock, or intricate detail like raised filigree patterns on armour and weapons. It is a way of providing highly detailed models without the use of a large number of polygons.

Normal maps used by Dragon Age differ from the typical tangent-space normal maps used in other games. A tangent-space normal map holds X information in the red channel, Y information in the green channel, and Z information in the blue channel. DA normal maps are RGBA with only X and Y information. Z information is interpolated on the fly.

R = Y (same as G channel in regular normal maps)

G = Y (same as G channel in regular normal maps)

B = Y (same as G channel in regular normal maps)

Alpha = X (same as R channel in regular normal maps)

DDS Compression: [[DDS Export Settings]]

[[image:TexFor_Deer_Nml_Map_DA.jpg|thumb|left|Deer normal map in DA format]] [[image:TexFor_Deer_Nml_Map_Reg.jpg|thumb|none|Deer normal map converted to typical RGB format]]

=== Specular Map ===

Specular maps hold information on how an object reflects light. It is sometimes also referred to as a gloss map. Lighting is games does not reflect the true behaviour of light in the real world, thus specular highlights are used to give the illusion of light reflecting off a surface. In simplest terms, it denotes the size and intensity of bright spots on an object, places where light would reflect back in the real world. Objects that should appear very shiny, like polished metal, have high sharp specular highlights, objects that should appear fairly dull, like cloth, have low flat specular highlights.

Specular maps function in a manner not dissimilar to alpha masks, in that the closer to white an area it is, the brighter the highlight. They appear to function as a container file, holding 4 greyscale specular maps, one in each channel.

DDS Compression: [[DDS Export Settings]]

[[image:TexFor_Deer_Spec_Map_4ch.jpg|thumb|none|Deer specular map]]

=== Tint Map ===

Tint maps are another container texture, holding a series of greyscale images. Each channel is actually an alpha mask. They denote areas of the associated diffuse texture that will be affected by the corresponding tint colour defined in the [[TNT]] file.

DDS Compression: [[DDS Export Settings]]

[[image:TexFor_Deer_Tint_Map.jpg|thumb|none|RGB channels for deer tint map]]

== Material Object ==

A texture set for a model is defined in the model's material object or [[MAO]]. See the [[MAO]] page for more info.

== Level of Detail ==

Most complex models (such as NPCs and creatures) have a scaling level of detail (LOD). As a player moves further away from an object, the LOD is progressively scaled down to reduce system overhead. Both the geometry and textures of a model may have LOD variants. DA uses three LOD levels, denoted by the suffix. The three levels are 0 (highest), 2 and 3 (lowest). For LOD0, the suffix is simply _0''x'' (where ''x'' denotes texture type). For LOD2, the suffix is _0''x''l2 and for LOD3, it is _0''x''l3. For example, c_deera_0d.dds is a diffuse texture at the highest LOD, c_deera_0dl2.dds and c_deera_0dl3.dds are the LOD2 and LOD3 diffuse textures, respectively. Each LOD texture level is generally 25% the size of the preceding level. For instance, for a LOD0 texture that is 1024x1024, the LOD2 texture will be 512x512 and the LOD3 texture will be 256x256. As well as diffuse maps, LOD is also used for specular and tint maps. Normal maps have no scaling LOD, as they are only used for LOD0.

[[image:TexFor_Deer_LOD.jpg|thumb|none|Scaling LOD for deer diffuse map]]

== Related Links ==

[[Tutorial: Reskinning an Item]]

[[Material editor|Material Editor]]

[[Material Tint System]]

=== External Links ===

nVidia DDS Plugin for Adobe Photoshop (32bit only)
http://developer.nvidia.com/object/photoshop_dds_plugins.html

DDS Plugin for GIMP
http://nifelheim.dyndns.org/~cocidius/dds/

DDS Converter v2.1 (DDS conversion tool)
http://eliteforce2.filefront.com/file/DDS_Converter;29412

nVidia DDS Utilities (includes DDS conversion tool)
http://developer.nvidia.com/object/dds_utilities_legacy.html

[[Category:Textures]]

Texture Formats

2010-01-16T13:36:41Z

DarthParametric:

Textures in DAO are stored in the [[DDS]] format. Native support of this file type can be added to a graphics package such as Adobe Photoshop or GIMP via the use of plugins. Alternatively, a DDS can be converted into a more universal format such as TGA or JPG using 3rd party tools.

== Texture Types ==

Dragon Age uses a number of different texture types. While all are in the [[DDS]] format, they have different purposes. The filename scheme differentiates these types with a suffix. Typically, a texture set for a particular model consists of 4 different types. These are as follows, using the deer model as an example:

c_deera_0d.dds - Diffuse map (''d'' suffix)

c_deera_0n.dds - Normal map (''n'' suffix)

c_deera_0s.dds - Specular map (''s'' suffix)

c_deera_0t.dds - Tint map (''t'' suffix)

Additional texture types are used on some models. The most common type is a height map used on static objects like floors and walls, designated with the ''h'' suffix.

=== Diffuse Map ===

This texture holds the base colour information for the model. Diffuse maps are commonly referred to as "skins" in other games. Diffuse maps can be enhanced through the use of the tint system, which overlays a series of colours (defined by the [[TNT]] file) on the diffuse map in a pattern defined by the associated tint map.

RGB channels - These hold the colour information, as with any standard image.

Alpha channel - The alpha channel is multi-purpose. Typically it holds transparency information (black is 100% transparency, white is 100% opacity, shades of grey denote values in between), however in some cases, such as face textures, it holds the specular map instead. In these instances there is no separate specular map.

Special cases: Some diffuse maps, notably for hair, do not follow the standard arrangement and are instead what is known as a "packed texture". In these instances, the image is essentially a container for 4 separate greyscale texture maps, one in each channel. These are used in conjunction with the [[Material Tint System|tint system]] when full colour diffuse maps are not necessary. For example, the hair diffuse map is a packed texture that appears to have the normal map in the red channel, the specular map in the green channel, the alpha map in the blue channel, and the diffuse map in the alpha channel.

DDS Compression: [[DDS Export Settings]]

[[image:TexFor_Deer_Dif_Map.jpg|thumb|none|Deer diffuse map]]

=== Normal Map ===

Normal maps are an enhanced version of bump maps, and are used to fake the appearance of additional geometry on a low polygon mesh. They work by providing information on how light would be reflected from a polygon's surface normal (hence the name normal map) as if it were part of a more detailed model. This provides the optical illusion of extra height and depth to otherwise flat geometry. It is typically used to provide roughness to surfaces like rock, or intricate detail like raised filigree patterns on armour and weapons. It is a way of providing highly detailed models without the use of a large number of polygons.

Normal maps used by Dragon Age differ from the typical tangent-space normal maps used in other games. A tangent-space normal map holds X information in the red channel, Y information in the green channel, and Z information in the blue channel. DA normal maps are RGBA with only X and Y information. Z information is interpolated on the fly.

R = Y (same as G channel in regular normal maps)

G = Y (same as G channel in regular normal maps)

B = Y (same as G channel in regular normal maps)

Alpha = X (same as R channel in regular normal maps)

DDS Compression: [[DDS Export Settings]]

[[image:TexFor_Deer_Nml_Map_DA.jpg|thumb|left|Deer normal map in DA format]] [[image:TexFor_Deer_Nml_Map_Reg.jpg|thumb|none|Deer normal map converted to typical RGB format]]

=== Specular Map ===

Specular maps hold information on how an object reflects light. It is sometimes also referred to as a gloss map. Lighting is games does not reflect the true behaviour of light in the real world, thus specular highlights are used to give the illusion of light reflecting off a surface. In simplest terms, it denotes the size and intensity of bright spots on an object, places where light would reflect back in the real world. Objects that should appear very shiny, like polished metal, have high sharp specular highlights, objects that should appear fairly dull, like cloth, have low flat specular highlights.

Specular maps function in a manner not dissimilar to alpha masks, in that the closer to white an area it is, the brighter the highlight. They appear to function as a container file, holding 4 greyscale specular maps, one in each channel.

DDS Compression: [[DDS Export Settings]]

[[image:TexFor_Deer_Spec_Map_4ch.jpg|thumb|none|Deer specular map]]

=== Tint Map ===

Tint maps are another container texture, holding a series of greyscale images. Each channel is actually an alpha mask. They denote areas of the associated diffuse texture that will be affected by the corresponding tint colour defined in the [[TNT]] file.

DDS Compression: [[DDS Export Settings]]

[[image:TexFor_Deer_Tint_Map.jpg|thumb|none|RGB channels for deer tint map]]

== Material Object ==

A texture set for a model is defined in the model's material object or [[MAO]]. See the [[MAO]] page for more info.

== Level of Detail ==

Most complex models (such as NPCs and creatures) have a scaling level of detail (LOD). As a player moves further away from an object, the LOD is progressively scaled down to reduce system overhead. Both the geometry and textures of a model may have LOD variants. DA uses three LOD levels, denoted by the suffix. The three levels are 0 (highest), 2 and 3 (lowest). For LOD0, the suffix is simply _0''x'' (where ''x'' denotes texture type). For LOD2, the suffix is _0''x''l2 and for LOD3, it is _0''x''l3. For example, c_deera_0d.dds is a diffuse texture at the highest LOD, c_deera_0dl2.dds and c_deera_0dl3.dds are the LOD2 and LOD3 diffuse textures, respectively. Each LOD texture level is generally 25% the size of the preceding level. For instance, for a LOD0 texture that is 1024x1024, the LOD2 texture will be 512x512 and the LOD3 texture will be 256x256. As well as diffuse maps, LOD is also used for specular and tint maps. Normal maps have no scaling LOD, as they are only used for LOD0.

[[image:TexFor_Deer_LOD.jpg|thumb|none|Scaling LOD for deer diffuse map]]

== Related Links ==

[[Tutorial: Reskinning an Item]]

[[Material editor|Material Editor]]

[[Material Tint System]]

=== External Links ===

nVidia DDS Plugin for Adobe Photoshop (32bit only)
http://developer.nvidia.com/object/photoshop_dds_plugins.html

DDS Plugin for GIMP
http://nifelheim.dyndns.org/~cocidius/dds/

DDS Converter v2.1 (DDS conversion tool)
http://eliteforce2.filefront.com/file/DDS_Converter;29412

nVidia DDS Utilities (includes DDS conversion tool)
http://developer.nvidia.com/object/dds_utilities_legacy.html

[[Category:Textures]]

File:TexFor Deer Spec Map 4ch.jpg

2010-01-16T13:36:21Z

DarthParametric:

File:TexFor Deer Dif Map.jpg

2010-01-16T13:25:41Z

DarthParametric:

File:TexFor Deer Nml Map DA.jpg

2010-01-16T13:23:10Z

DarthParametric:

File:TexFor Deer Nml Map Reg.jpg

2010-01-16T13:21:45Z

DarthParametric:

File:TexFor Deer Spec Map.jpg

2010-01-16T13:20:50Z

DarthParametric:

File:TexFor Deer Tint Map.jpg

2010-01-16T13:18:27Z

DarthParametric:

Creating recolors of existing items tutorial

2010-01-16T13:04:44Z

DarthParametric: /* Related Links */

This tutorial describes how to create a custom [[Item]] by recoloring an existing item. It is assumed that the reader is familiar with the Toolset. These instructions are based on a forum post by Dylbot.

__TOC__

=Getting Started=

Open the item you want to recolor. For the purposes of this tutorial, we're going to go for heavy chainmail.

[[File:HeavyChainmail.jpg]]

=Create a new material=

[[File:CreateNewMaterial.jpg]]

=Add a new tint library to Root=

[[File:NewTintLibrary.jpg]]

=Add a new tint object to that library=

[[File:NewTintObject.jpg]]

=Enable the red, green and blue channels=

[[File:EnableRGBChannels.jpg]]

=Open the tint file for the object you are recoloring=

You'll need to know what you're changing when you color the channels. If you don't have a [[DDS]] viewing program, now might be a good time to grab one. Windows Texture Viewer - http://developer.nvidia.com/object/windows_texture_viewer.html - is good for the purpose, and free.

Using the Toolset, open up texturepack.erf in (Dragon Age directory)/core/packages/textures/high/, and scroll down to the texture you need (in this case, it's pm_arm_hvyc_0t.dds, signifying male, armor, heavy, type c, tint map). Right-click and open resource. At this point, you may want to hide the alpha channel in WTV, or all you're going to see is a pink square.

[[File:RedGreenBlueChannels.jpg]]

What you're seeing is the armor texture, divided into three channels; red, blue, and green. As you may have guessed, each of the channels corresponds to the equivalent colored area on the tint map.

=Change the colors as desired=

If you do this:

[[File:ChangeGreenChannel.jpg]]

All of the green areas on the tint map (the chainmail and the belts) will become red on the model when you apply the tint. A little tip: the Diffuse color changes the base color, and the Specular color changes the reflection color. Change colors as you please.

=Name and save the tint file=

Once you're happy, give your texture a name (I'd suggest sticking to the naming convention of the game, so something like arm_xyz, it'll add the T3 itself) save the matproj, and right click on Root - Post Selection to Local.

=Add the new tint to your tint_override m2da=

Now, the next bit is a bit more complicated. In the item settings, you may notice an option called Tint Override.

[[File:TintOverride.jpg]]

What we're going to do now is tell the game that our new tint is one of these overrides. This comes with the added bonus that the armor can be set as any material and still have the custom color. You'll need a spreadsheet program, so if you don't have MS Office, go pick up OpenOffice (if you don't have it already, naturally). Done? Right. Navigate to (Dragon Age directory)/tools/Source/2DA, and copy Tints.xls to your documents area, or wherever. Open up the copy, and choose the tint_override sheet. Add your new tint in at the next available blank line (put whatever you want as the label, something like "My Custom Tint 1" or something that makes it obvious what it is, and the file name in the tintfile box, which, in the case of our example, would be t3_arm_xyz. Star out the last column like the other tints). Save the worksheet and close it. Now, you're going to need to export that to the 2DA format. There's a handy tutorial over at the DA Builder wiki - http://social.bioware.com/wiki/datoolset/index.php/2DA - which looks a bit scary at first, but is nothing to be worried about. If you don't know how to create a batch file, all you do is create a new text document, and change the extension from .txt to .bat. Once you've exported, chuck the tint_override.gda file into the game's override folder, as described in the 2da tutorial.
Now, close the toolset and open it again. Check out your piece of armor, and check the tint overrides. Lo and behold, your new tint is there. Apply that sucker and admire your handiwork.

[[File:RecoloredItem.jpg]]

Save, check in, and export the armor. If you've got gloves and boots (and you should have, we're going for a matching set here), check them out and apply the tint too. You can even apply it to weapons and shields if you want. Once everything is checked out and exported, load up your game and take a look at your shiny new equipment (if you've set up your loading script, or already have the equipment. If not, check the custom item tutorial, it'll tell you what you need to know).

[[File:AlistairInArmor.jpg]]

Alastair wearing the new armor.

= Related Links =

[[Material editor|Material Editor]]

[[Texture Formats]]

[[Material Tint System]]

[[Category:Textures]]
[[Category:Tutorials]]

Creating recolors of existing items tutorial

2010-01-16T13:04:26Z

DarthParametric: /* Related Links */

This tutorial describes how to create a custom [[Item]] by recoloring an existing item. It is assumed that the reader is familiar with the Toolset. These instructions are based on a forum post by Dylbot.

__TOC__

=Getting Started=

Open the item you want to recolor. For the purposes of this tutorial, we're going to go for heavy chainmail.

[[File:HeavyChainmail.jpg]]

=Create a new material=

[[File:CreateNewMaterial.jpg]]

=Add a new tint library to Root=

[[File:NewTintLibrary.jpg]]

=Add a new tint object to that library=

[[File:NewTintObject.jpg]]

=Enable the red, green and blue channels=

[[File:EnableRGBChannels.jpg]]

=Open the tint file for the object you are recoloring=

You'll need to know what you're changing when you color the channels. If you don't have a [[DDS]] viewing program, now might be a good time to grab one. Windows Texture Viewer - http://developer.nvidia.com/object/windows_texture_viewer.html - is good for the purpose, and free.

Using the Toolset, open up texturepack.erf in (Dragon Age directory)/core/packages/textures/high/, and scroll down to the texture you need (in this case, it's pm_arm_hvyc_0t.dds, signifying male, armor, heavy, type c, tint map). Right-click and open resource. At this point, you may want to hide the alpha channel in WTV, or all you're going to see is a pink square.

[[File:RedGreenBlueChannels.jpg]]

What you're seeing is the armor texture, divided into three channels; red, blue, and green. As you may have guessed, each of the channels corresponds to the equivalent colored area on the tint map.

=Change the colors as desired=

If you do this:

[[File:ChangeGreenChannel.jpg]]

All of the green areas on the tint map (the chainmail and the belts) will become red on the model when you apply the tint. A little tip: the Diffuse color changes the base color, and the Specular color changes the reflection color. Change colors as you please.

=Name and save the tint file=

Once you're happy, give your texture a name (I'd suggest sticking to the naming convention of the game, so something like arm_xyz, it'll add the T3 itself) save the matproj, and right click on Root - Post Selection to Local.

=Add the new tint to your tint_override m2da=

Now, the next bit is a bit more complicated. In the item settings, you may notice an option called Tint Override.

[[File:TintOverride.jpg]]

What we're going to do now is tell the game that our new tint is one of these overrides. This comes with the added bonus that the armor can be set as any material and still have the custom color. You'll need a spreadsheet program, so if you don't have MS Office, go pick up OpenOffice (if you don't have it already, naturally). Done? Right. Navigate to (Dragon Age directory)/tools/Source/2DA, and copy Tints.xls to your documents area, or wherever. Open up the copy, and choose the tint_override sheet. Add your new tint in at the next available blank line (put whatever you want as the label, something like "My Custom Tint 1" or something that makes it obvious what it is, and the file name in the tintfile box, which, in the case of our example, would be t3_arm_xyz. Star out the last column like the other tints). Save the worksheet and close it. Now, you're going to need to export that to the 2DA format. There's a handy tutorial over at the DA Builder wiki - http://social.bioware.com/wiki/datoolset/index.php/2DA - which looks a bit scary at first, but is nothing to be worried about. If you don't know how to create a batch file, all you do is create a new text document, and change the extension from .txt to .bat. Once you've exported, chuck the tint_override.gda file into the game's override folder, as described in the 2da tutorial.
Now, close the toolset and open it again. Check out your piece of armor, and check the tint overrides. Lo and behold, your new tint is there. Apply that sucker and admire your handiwork.

[[File:RecoloredItem.jpg]]

Save, check in, and export the armor. If you've got gloves and boots (and you should have, we're going for a matching set here), check them out and apply the tint too. You can even apply it to weapons and shields if you want. Once everything is checked out and exported, load up your game and take a look at your shiny new equipment (if you've set up your loading script, or already have the equipment. If not, check the custom item tutorial, it'll tell you what you need to know).

[[File:AlistairInArmor.jpg]]

Alastair wearing the new armor.

= Related Links =

[[Material editor|Material Editor]]
[[Texture Formats]]
[[Material Tint System]]

[[Category:Textures]]
[[Category:Tutorials]]

Creating recolors of existing items tutorial

2010-01-16T13:03:24Z

DarthParametric:

This tutorial describes how to create a custom [[Item]] by recoloring an existing item. It is assumed that the reader is familiar with the Toolset. These instructions are based on a forum post by Dylbot.

__TOC__

=Getting Started=

Open the item you want to recolor. For the purposes of this tutorial, we're going to go for heavy chainmail.

[[File:HeavyChainmail.jpg]]

=Create a new material=

[[File:CreateNewMaterial.jpg]]

=Add a new tint library to Root=

[[File:NewTintLibrary.jpg]]

=Add a new tint object to that library=

[[File:NewTintObject.jpg]]

=Enable the red, green and blue channels=

[[File:EnableRGBChannels.jpg]]

=Open the tint file for the object you are recoloring=

You'll need to know what you're changing when you color the channels. If you don't have a [[DDS]] viewing program, now might be a good time to grab one. Windows Texture Viewer - http://developer.nvidia.com/object/windows_texture_viewer.html - is good for the purpose, and free.

Using the Toolset, open up texturepack.erf in (Dragon Age directory)/core/packages/textures/high/, and scroll down to the texture you need (in this case, it's pm_arm_hvyc_0t.dds, signifying male, armor, heavy, type c, tint map). Right-click and open resource. At this point, you may want to hide the alpha channel in WTV, or all you're going to see is a pink square.

[[File:RedGreenBlueChannels.jpg]]

What you're seeing is the armor texture, divided into three channels; red, blue, and green. As you may have guessed, each of the channels corresponds to the equivalent colored area on the tint map.

=Change the colors as desired=

If you do this:

[[File:ChangeGreenChannel.jpg]]

All of the green areas on the tint map (the chainmail and the belts) will become red on the model when you apply the tint. A little tip: the Diffuse color changes the base color, and the Specular color changes the reflection color. Change colors as you please.

=Name and save the tint file=

Once you're happy, give your texture a name (I'd suggest sticking to the naming convention of the game, so something like arm_xyz, it'll add the T3 itself) save the matproj, and right click on Root - Post Selection to Local.

=Add the new tint to your tint_override m2da=

Now, the next bit is a bit more complicated. In the item settings, you may notice an option called Tint Override.

[[File:TintOverride.jpg]]

What we're going to do now is tell the game that our new tint is one of these overrides. This comes with the added bonus that the armor can be set as any material and still have the custom color. You'll need a spreadsheet program, so if you don't have MS Office, go pick up OpenOffice (if you don't have it already, naturally). Done? Right. Navigate to (Dragon Age directory)/tools/Source/2DA, and copy Tints.xls to your documents area, or wherever. Open up the copy, and choose the tint_override sheet. Add your new tint in at the next available blank line (put whatever you want as the label, something like "My Custom Tint 1" or something that makes it obvious what it is, and the file name in the tintfile box, which, in the case of our example, would be t3_arm_xyz. Star out the last column like the other tints). Save the worksheet and close it. Now, you're going to need to export that to the 2DA format. There's a handy tutorial over at the DA Builder wiki - http://social.bioware.com/wiki/datoolset/index.php/2DA - which looks a bit scary at first, but is nothing to be worried about. If you don't know how to create a batch file, all you do is create a new text document, and change the extension from .txt to .bat. Once you've exported, chuck the tint_override.gda file into the game's override folder, as described in the 2da tutorial.
Now, close the toolset and open it again. Check out your piece of armor, and check the tint overrides. Lo and behold, your new tint is there. Apply that sucker and admire your handiwork.

[[File:RecoloredItem.jpg]]

Save, check in, and export the armor. If you've got gloves and boots (and you should have, we're going for a matching set here), check them out and apply the tint too. You can even apply it to weapons and shields if you want. Once everything is checked out and exported, load up your game and take a look at your shiny new equipment (if you've set up your loading script, or already have the equipment. If not, check the custom item tutorial, it'll tell you what you need to know).

[[File:AlistairInArmor.jpg]]

Alastair wearing the new armor.

== Related Links ==

[[Material editor|Material Editor]]
[[Texture Formats]]
[[Material Tint System]]

[[Category:Textures]]
[[Category:Tutorials]]

File:TexFor Deer LOD.jpg

2010-01-16T13:02:13Z

DarthParametric:

Texture Formats

2010-01-16T12:38:37Z

DarthParametric: /* Diffuse Map */

Textures in DAO are stored in the [[DDS]] format. Native support of this file type can be added to a graphics package such as Adobe Photoshop or GIMP via the use of plugins. Alternatively, a DDS can be converted into a more universal format such as TGA or JPG using 3rd party tools.

== Texture Types ==

Dragon Age uses a number of different texture types. While all are in the [[DDS]] format, they have different purposes. The filename scheme differentiates these types with a suffix. Typically, a texture set for a particular model consists of 4 different types. These are as follows, using the deer model as an example:

c_deera_0d.dds - Diffuse map (''d'' suffix)

c_deera_0n.dds - Normal map (''n'' suffix)

c_deera_0s.dds - Specular map (''s'' suffix)

c_deera_0t.dds - Tint map (''t'' suffix)

Additional texture types are used on some models. The most common type is a height map used on static objects like floors and walls, designated with the ''h'' suffix.

=== Diffuse Map ===

This texture holds the base colour information for the model. Diffuse maps are commonly referred to as "skins" in other games. Diffuse maps can be enhanced through the use of the tint system, which overlays a series of colours (defined by the [[TNT]] file) on the diffuse map in a pattern defined by the associated tint map.

RGB channels - These hold the colour information, as with any standard image.

Alpha channel - The alpha channel is multi-purpose. Typically it holds transparency information (black is 100% transparency, white is 100% opacity, shades of grey denote values in between), however in some cases, such as face textures, it holds the specular map instead. In these instances there is no separate specular map.

Special cases: Some diffuse maps, notably for hair, do not follow the standard arrangement and are instead what is known as a "packed texture". In these instances, the image is essentially a container for 4 separate greyscale texture maps, one in each channel. These are used in conjunction with the [[Material Tint System|tint system]] when full colour diffuse maps are not necessary. For example, the hair diffuse map is a packed texture that appears to have the normal map in the red channel, the specular map in the green channel, the alpha map in the blue channel, and the diffuse map in the alpha channel.

DDS Compression: [[DDS Export Settings]]

=== Normal Map ===

Normal maps are an enhanced version of bump maps, and are used to fake the appearance of additional geometry on a low polygon mesh. They work by providing information on how light would be reflected from a polygon's surface normal (hence the name normal map) as if it were part of a more detailed model. This provides the optical illusion of extra height and depth to otherwise flat geometry. It is typically used to provide roughness to surfaces like rock, or intricate detail like raised filigree patterns on armour and weapons. It is a way of providing highly detailed models without the use of a large number of polygons.

Normal maps used by Dragon Age differ from the typical tangent-space normal maps used in other games. A tangent-space normal map holds X information in the red channel, Y information in the green channel, and Z information in the blue channel. DA normal maps are RGBA with only X and Y information. Z information is interpolated on the fly.

R = Y (same as G channel in regular normal maps)

G = Y (same as G channel in regular normal maps)

B = Y (same as G channel in regular normal maps)

Alpha = X (same as R channel in regular normal maps)

DDS Compression: [[DDS Export Settings]]

=== Specular Map ===

Specular maps hold information on how an object reflects light. It is sometimes also referred to as a gloss map. Lighting is games does not reflect the true behaviour of light in the real world, thus specular highlights are used to give the illusion of light reflecting off a surface. In simplest terms, it denotes the size and intensity of bright spots on an object, places where light would reflect back in the real world. Objects that should appear very shiny, like polished metal, have high sharp specular highlights, objects that should appear fairly dull, like cloth, have low flat specular highlights.

Specular maps function in a manner not dissimilar to alpha masks, in that the closer to white an area it is, the brighter the highlight. The RGB channels hold the specular information in greyscale, the alpha channel is a standard alpha mask.

DDS Compression: [[DDS Export Settings]]

=== Tint Map ===

Tint maps are another container texture, holding a series of greyscale images. Each channel is actually an alpha mask. They denote areas of the associated diffuse texture that will be affected by the corresponding tint colour defined in the [[TNT]] file.

DDS Compression: [[DDS Export Settings]]

== Material Object ==

A texture set for a model is defined in the model's material object or [[MAO]]. See the [[MAO]] page for more info.

== Level of Detail ==

Most complex models (such as NPCs and creatures) have a scaling level of detail (LOD). As a player moves further away from an object, the LOD is progressively scaled down to reduce system overhead. Both the geometry and textures of a model may have LOD variants. DA uses three LOD levels, denoted by the suffix. The three levels are 0 (highest), 2 and 3 (lowest). For LOD0, the suffix is simply _0''x'' (where ''x'' denotes texture type). For LOD2, the suffix is _0''x''l2 and for LOD3, it is _0''x''l3. For example, c_deera_0d.dds is a diffuse texture at the highest LOD, c_deera_0dl2.dds and c_deera_0dl3.dds are the LOD2 and LOD3 diffuse textures, respectively. Each LOD texture level is generally 25% the size of the preceding level. For instance, for a LOD0 texture that is 1024x1024, the LOD2 texture will be 512x512 and the LOD3 texture will be 256x256. As well as diffuse maps, LOD is also used for specular and tint maps. Normal maps have no scaling LOD, as they are only used for LOD0.

== Related Links ==

[[Tutorial: Reskinning an Item]]

[[Material editor|Material Editor]]

[[Material Tint System]]

=== External Links ===

nVidia DDS Plugin for Adobe Photoshop (32bit only)
http://developer.nvidia.com/object/photoshop_dds_plugins.html

DDS Plugin for GIMP
http://nifelheim.dyndns.org/~cocidius/dds/

DDS Converter v2.1 (DDS conversion tool)
http://eliteforce2.filefront.com/file/DDS_Converter;29412

nVidia DDS Utilities (includes DDS conversion tool)
http://developer.nvidia.com/object/dds_utilities_legacy.html

[[Category:Textures]]

Texture Formats

2010-01-16T12:36:47Z

DarthParametric: /* Diffuse Map */

Textures in DAO are stored in the [[DDS]] format. Native support of this file type can be added to a graphics package such as Adobe Photoshop or GIMP via the use of plugins. Alternatively, a DDS can be converted into a more universal format such as TGA or JPG using 3rd party tools.

== Texture Types ==

Dragon Age uses a number of different texture types. While all are in the [[DDS]] format, they have different purposes. The filename scheme differentiates these types with a suffix. Typically, a texture set for a particular model consists of 4 different types. These are as follows, using the deer model as an example:

c_deera_0d.dds - Diffuse map (''d'' suffix)

c_deera_0n.dds - Normal map (''n'' suffix)

c_deera_0s.dds - Specular map (''s'' suffix)

c_deera_0t.dds - Tint map (''t'' suffix)

Additional texture types are used on some models. The most common type is a height map used on static objects like floors and walls, designated with the ''h'' suffix.

=== Diffuse Map ===

This texture holds the base colour information for the model. Diffuse maps are commonly referred to as "skins" in other games. Diffuse maps can be enhanced through the use of the tint system, which overlays a series of colours (defined by the [[TNT]] file) on the diffuse map in a pattern defined by the associated tint map.

RGB channels - These hold the colour information, as with any standard image.

Alpha channel - The alpha channel is multi-purpose. Typically it holds transparency information (black is 100% transparency, white is 100% opacity, shades of grey denote values in between), however in some cases, such as face textures, it holds the specular map instead. In these instances there is no separate specular map.

Special cases: Some diffuse maps, notably for hair, do not follow the standard arrangement and are instead what is known as a "packed texture". In these instances, the image is essentially a container for 4 separate greyscale texture maps, one in each channel. These are used in conjunction with the [[Material Tint System|tint system]]. For example the hair diffuse map is a packed texture that appears to have the normal map in the red channel, the specular map in the green channel, the alpha map in the blue channel, and the diffuse map in the alpha channel.

DDS Compression: [[DDS Export Settings]]

=== Normal Map ===

Normal maps are an enhanced version of bump maps, and are used to fake the appearance of additional geometry on a low polygon mesh. They work by providing information on how light would be reflected from a polygon's surface normal (hence the name normal map) as if it were part of a more detailed model. This provides the optical illusion of extra height and depth to otherwise flat geometry. It is typically used to provide roughness to surfaces like rock, or intricate detail like raised filigree patterns on armour and weapons. It is a way of providing highly detailed models without the use of a large number of polygons.

Normal maps used by Dragon Age differ from the typical tangent-space normal maps used in other games. A tangent-space normal map holds X information in the red channel, Y information in the green channel, and Z information in the blue channel. DA normal maps are RGBA with only X and Y information. Z information is interpolated on the fly.

R = Y (same as G channel in regular normal maps)

G = Y (same as G channel in regular normal maps)

B = Y (same as G channel in regular normal maps)

Alpha = X (same as R channel in regular normal maps)

DDS Compression: [[DDS Export Settings]]

=== Specular Map ===

Specular maps hold information on how an object reflects light. It is sometimes also referred to as a gloss map. Lighting is games does not reflect the true behaviour of light in the real world, thus specular highlights are used to give the illusion of light reflecting off a surface. In simplest terms, it denotes the size and intensity of bright spots on an object, places where light would reflect back in the real world. Objects that should appear very shiny, like polished metal, have high sharp specular highlights, objects that should appear fairly dull, like cloth, have low flat specular highlights.

Specular maps function in a manner not dissimilar to alpha masks, in that the closer to white an area it is, the brighter the highlight. The RGB channels hold the specular information in greyscale, the alpha channel is a standard alpha mask.

DDS Compression: [[DDS Export Settings]]

=== Tint Map ===

Tint maps are another container texture, holding a series of greyscale images. Each channel is actually an alpha mask. They denote areas of the associated diffuse texture that will be affected by the corresponding tint colour defined in the [[TNT]] file.

DDS Compression: [[DDS Export Settings]]

== Material Object ==

A texture set for a model is defined in the model's material object or [[MAO]]. See the [[MAO]] page for more info.

== Level of Detail ==

Most complex models (such as NPCs and creatures) have a scaling level of detail (LOD). As a player moves further away from an object, the LOD is progressively scaled down to reduce system overhead. Both the geometry and textures of a model may have LOD variants. DA uses three LOD levels, denoted by the suffix. The three levels are 0 (highest), 2 and 3 (lowest). For LOD0, the suffix is simply _0''x'' (where ''x'' denotes texture type). For LOD2, the suffix is _0''x''l2 and for LOD3, it is _0''x''l3. For example, c_deera_0d.dds is a diffuse texture at the highest LOD, c_deera_0dl2.dds and c_deera_0dl3.dds are the LOD2 and LOD3 diffuse textures, respectively. Each LOD texture level is generally 25% the size of the preceding level. For instance, for a LOD0 texture that is 1024x1024, the LOD2 texture will be 512x512 and the LOD3 texture will be 256x256. As well as diffuse maps, LOD is also used for specular and tint maps. Normal maps have no scaling LOD, as they are only used for LOD0.

== Related Links ==

[[Tutorial: Reskinning an Item]]

[[Material editor|Material Editor]]

[[Material Tint System]]

=== External Links ===

nVidia DDS Plugin for Adobe Photoshop (32bit only)
http://developer.nvidia.com/object/photoshop_dds_plugins.html

DDS Plugin for GIMP
http://nifelheim.dyndns.org/~cocidius/dds/

DDS Converter v2.1 (DDS conversion tool)
http://eliteforce2.filefront.com/file/DDS_Converter;29412

nVidia DDS Utilities (includes DDS conversion tool)
http://developer.nvidia.com/object/dds_utilities_legacy.html

[[Category:Textures]]

Texture Formats

2010-01-16T12:34:39Z

DarthParametric: /* Texture Types */

Textures in DAO are stored in the [[DDS]] format. Native support of this file type can be added to a graphics package such as Adobe Photoshop or GIMP via the use of plugins. Alternatively, a DDS can be converted into a more universal format such as TGA or JPG using 3rd party tools.

== Texture Types ==

Dragon Age uses a number of different texture types. While all are in the [[DDS]] format, they have different purposes. The filename scheme differentiates these types with a suffix. Typically, a texture set for a particular model consists of 4 different types. These are as follows, using the deer model as an example:

c_deera_0d.dds - Diffuse map (''d'' suffix)

c_deera_0n.dds - Normal map (''n'' suffix)

c_deera_0s.dds - Specular map (''s'' suffix)

c_deera_0t.dds - Tint map (''t'' suffix)

Additional texture types are used on some models. The most common type is a height map used on static objects like floors and walls, designated with the ''h'' suffix.

=== Diffuse Map ===

This texture holds the base colour information for the model. Diffuse maps are commonly referred to as "skins" in other games. Diffuse maps can be enhanced through the use of the tint system, which overlays a series of colours (defined by the [[TNT]] file) on the diffuse map in a pattern defined by the associated tint map.

RGB channels - These hold the colour information, as with any standard image.

Alpha channel - The alpha channel is multi-purpose. Typically it holds transparency information (black is 100% transparency, white is 100% opacity, shades of grey denote values in between), however in some cases, such as face textures, it holds the specular map instead. In these instances there is no separate specular map.

Special cases: Some diffuse maps, notably for hair, do not follow the standard arrangement and are instead what is known as a "packed texture". In these instances, the image is essentially a container for 4 separate greyscale texture maps, one in each channel. These are used in conjunction with the tint system. For example the hair diffuse map is a packed texture that appears to have the normal map in the red channel, the specular map in the green channel, the alpha map in the blue channel, and the diffuse map in the alpha channel.

DDS Compression: [[DDS Export Settings]]

=== Normal Map ===

Normal maps are an enhanced version of bump maps, and are used to fake the appearance of additional geometry on a low polygon mesh. They work by providing information on how light would be reflected from a polygon's surface normal (hence the name normal map) as if it were part of a more detailed model. This provides the optical illusion of extra height and depth to otherwise flat geometry. It is typically used to provide roughness to surfaces like rock, or intricate detail like raised filigree patterns on armour and weapons. It is a way of providing highly detailed models without the use of a large number of polygons.

Normal maps used by Dragon Age differ from the typical tangent-space normal maps used in other games. A tangent-space normal map holds X information in the red channel, Y information in the green channel, and Z information in the blue channel. DA normal maps are RGBA with only X and Y information. Z information is interpolated on the fly.

R = Y (same as G channel in regular normal maps)

G = Y (same as G channel in regular normal maps)

B = Y (same as G channel in regular normal maps)

Alpha = X (same as R channel in regular normal maps)

DDS Compression: [[DDS Export Settings]]

=== Specular Map ===

Specular maps hold information on how an object reflects light. It is sometimes also referred to as a gloss map. Lighting is games does not reflect the true behaviour of light in the real world, thus specular highlights are used to give the illusion of light reflecting off a surface. In simplest terms, it denotes the size and intensity of bright spots on an object, places where light would reflect back in the real world. Objects that should appear very shiny, like polished metal, have high sharp specular highlights, objects that should appear fairly dull, like cloth, have low flat specular highlights.

Specular maps function in a manner not dissimilar to alpha masks, in that the closer to white an area it is, the brighter the highlight. The RGB channels hold the specular information in greyscale, the alpha channel is a standard alpha mask.

DDS Compression: [[DDS Export Settings]]

=== Tint Map ===

Tint maps are another container texture, holding a series of greyscale images. Each channel is actually an alpha mask. They denote areas of the associated diffuse texture that will be affected by the corresponding tint colour defined in the [[TNT]] file.

DDS Compression: [[DDS Export Settings]]

== Material Object ==

A texture set for a model is defined in the model's material object or [[MAO]]. See the [[MAO]] page for more info.

== Level of Detail ==

Most complex models (such as NPCs and creatures) have a scaling level of detail (LOD). As a player moves further away from an object, the LOD is progressively scaled down to reduce system overhead. Both the geometry and textures of a model may have LOD variants. DA uses three LOD levels, denoted by the suffix. The three levels are 0 (highest), 2 and 3 (lowest). For LOD0, the suffix is simply _0''x'' (where ''x'' denotes texture type). For LOD2, the suffix is _0''x''l2 and for LOD3, it is _0''x''l3. For example, c_deera_0d.dds is a diffuse texture at the highest LOD, c_deera_0dl2.dds and c_deera_0dl3.dds are the LOD2 and LOD3 diffuse textures, respectively. Each LOD texture level is generally 25% the size of the preceding level. For instance, for a LOD0 texture that is 1024x1024, the LOD2 texture will be 512x512 and the LOD3 texture will be 256x256. As well as diffuse maps, LOD is also used for specular and tint maps. Normal maps have no scaling LOD, as they are only used for LOD0.

== Related Links ==

[[Tutorial: Reskinning an Item]]

[[Material editor|Material Editor]]

[[Material Tint System]]

=== External Links ===

nVidia DDS Plugin for Adobe Photoshop (32bit only)
http://developer.nvidia.com/object/photoshop_dds_plugins.html

DDS Plugin for GIMP
http://nifelheim.dyndns.org/~cocidius/dds/

DDS Converter v2.1 (DDS conversion tool)
http://eliteforce2.filefront.com/file/DDS_Converter;29412

nVidia DDS Utilities (includes DDS conversion tool)
http://developer.nvidia.com/object/dds_utilities_legacy.html

[[Category:Textures]]

Texture Formats

2010-01-16T12:33:37Z

DarthParametric: /* Links */

Textures in DAO are stored in the [[DDS]] format. Native support of this file type can be added to a graphics package such as Adobe Photoshop or GIMP via the use of plugins. Alternatively, a DDS can be converted into a more universal format such as TGA or JPG using 3rd party tools.

== Texture Types ==

Dragon Age uses a number of different texture types. While all are in the [[DDS]] format, they have different purposes. The filename scheme differentiates these types with a suffix. Typically, a texture set for a particular model consists of 4 different types. These are as follows, using the deer model as an example:

c_deera_0d.dds - Diffuse (colour) map (''d'' suffix)

c_deera_0n.dds - Normal map (''n'' suffix)

c_deera_0s.dds - Specular map (''s'' suffix)

c_deera_0t.dds - Tint map (''t'' suffix)

Additional texture types are used on some models. The most common type is a height map used on static objects like floors and walls, designated with the ''h'' suffix.

=== Diffuse Map ===

This texture holds the base colour information for the model. Diffuse maps are commonly referred to as "skins" in other games. Diffuse maps can be enhanced through the use of the tint system, which overlays a series of colours (defined by the [[TNT]] file) on the diffuse map in a pattern defined by the associated tint map.

RGB channels - These hold the colour information, as with any standard image.

Alpha channel - The alpha channel is multi-purpose. Typically it holds transparency information (black is 100% transparency, white is 100% opacity, shades of grey denote values in between), however in some cases, such as face textures, it holds the specular map instead. In these instances there is no separate specular map.

Special cases: Some diffuse maps, notably for hair, do not follow the standard arrangement and are instead what is known as a "packed texture". In these instances, the image is essentially a container for 4 separate greyscale texture maps, one in each channel. These are used in conjunction with the tint system. For example the hair diffuse map is a packed texture that appears to have the normal map in the red channel, the specular map in the green channel, the alpha map in the blue channel, and the diffuse map in the alpha channel.

DDS Compression: [[DDS Export Settings]]

=== Normal Map ===

Normal maps are an enhanced version of bump maps, and are used to fake the appearance of additional geometry on a low polygon mesh. They work by providing information on how light would be reflected from a polygon's surface normal (hence the name normal map) as if it were part of a more detailed model. This provides the optical illusion of extra height and depth to otherwise flat geometry. It is typically used to provide roughness to surfaces like rock, or intricate detail like raised filigree patterns on armour and weapons. It is a way of providing highly detailed models without the use of a large number of polygons.

Normal maps used by Dragon Age differ from the typical tangent-space normal maps used in other games. A tangent-space normal map holds X information in the red channel, Y information in the green channel, and Z information in the blue channel. DA normal maps are RGBA with only X and Y information. Z information is interpolated on the fly.

R = Y (same as G channel in regular normal maps)

G = Y (same as G channel in regular normal maps)

B = Y (same as G channel in regular normal maps)

Alpha = X (same as R channel in regular normal maps)

DDS Compression: [[DDS Export Settings]]

=== Specular Map ===

Specular maps hold information on how an object reflects light. It is sometimes also referred to as a gloss map. Lighting is games does not reflect the true behaviour of light in the real world, thus specular highlights are used to give the illusion of light reflecting off a surface. In simplest terms, it denotes the size and intensity of bright spots on an object, places where light would reflect back in the real world. Objects that should appear very shiny, like polished metal, have high sharp specular highlights, objects that should appear fairly dull, like cloth, have low flat specular highlights.

Specular maps function in a manner not dissimilar to alpha masks, in that the closer to white an area it is, the brighter the highlight. The RGB channels hold the specular information in greyscale, the alpha channel is a standard alpha mask.

DDS Compression: [[DDS Export Settings]]

=== Tint Map ===

Tint maps are another container texture, holding a series of greyscale images. Each channel is actually an alpha mask. They denote areas of the associated diffuse texture that will be affected by the corresponding tint colour defined in the [[TNT]] file.

DDS Compression: [[DDS Export Settings]]

== Material Object ==

A texture set for a model is defined in the model's material object or [[MAO]]. See the [[MAO]] page for more info.

== Level of Detail ==

Most complex models (such as NPCs and creatures) have a scaling level of detail (LOD). As a player moves further away from an object, the LOD is progressively scaled down to reduce system overhead. Both the geometry and textures of a model may have LOD variants. DA uses three LOD levels, denoted by the suffix. The three levels are 0 (highest), 2 and 3 (lowest). For LOD0, the suffix is simply _0''x'' (where ''x'' denotes texture type). For LOD2, the suffix is _0''x''l2 and for LOD3, it is _0''x''l3. For example, c_deera_0d.dds is a diffuse texture at the highest LOD, c_deera_0dl2.dds and c_deera_0dl3.dds are the LOD2 and LOD3 diffuse textures, respectively. Each LOD texture level is generally 25% the size of the preceding level. For instance, for a LOD0 texture that is 1024x1024, the LOD2 texture will be 512x512 and the LOD3 texture will be 256x256. As well as diffuse maps, LOD is also used for specular and tint maps. Normal maps have no scaling LOD, as they are only used for LOD0.

== Related Links ==

[[Tutorial: Reskinning an Item]]

[[Material editor|Material Editor]]

[[Material Tint System]]

=== External Links ===

nVidia DDS Plugin for Adobe Photoshop (32bit only)
http://developer.nvidia.com/object/photoshop_dds_plugins.html

DDS Plugin for GIMP
http://nifelheim.dyndns.org/~cocidius/dds/

DDS Converter v2.1 (DDS conversion tool)
http://eliteforce2.filefront.com/file/DDS_Converter;29412

nVidia DDS Utilities (includes DDS conversion tool)
http://developer.nvidia.com/object/dds_utilities_legacy.html

[[Category:Textures]]

Creating recolors of existing items tutorial

2010-01-16T12:25:09Z

DarthParametric: /* Open the tint file for the object you are recoloring */