Dragon Age Toolset Wiki - User contributions [en]

Database backup and restore

2010-03-31T08:45:35Z

JackFuzz: /* Troubles with sqlcmd */

The following commands can be used to backup and restore your database, assuming you're using the default database name (bw_dragonage_content):

== Restoring the Database if it failed after Installation ==

If you installed the Toolset, and receive an Error message "Unable to connect to Database", and have never made a Backup, this Solution helps. Although it is a batch file, and requires the users maintenance.

'''Note:''' Be aware that it will overwrite the old Database if it existed. Doesnt apply if you never used the Toolset before.

'''1.''' Create a file called "MyRestore.bat" anywhere in your system and edit it with a program like "Notepad"

'''2.''' Copy and paste the complete following lines into it:

<dascript>SET SOURCE=C:\Program Files\Dragon Age\tools\dbbak
SET TARGET=C:\Program Files\Dragon Age\tools\toolssql\Data

@Echo off
if not exist "%SOURCE%\bw_dragonage_content.bak" goto Sourcemiss
if not exist "%TARGET%" goto Targetmiss
:returnme
if not exist "%PROGRAMFILES(X86)%\Microsoft SQL Server\90\Tools\Binn\" goto SQLmiss64
SET varprogs=%PROGRAMFILES(X86)%
goto apply

:SQLmiss64
if not exist "%ProgramFiles%\Microsoft SQL Server\90\Tools\Binn\" goto SQLmiss32
SET varprogs=%ProgramFiles%
goto apply

:apply
Echo Running SQLcmd...
"%varprogs%\Microsoft SQL Server\90\Tools\Binn\"sqlcmd -S .\BWDATOOLSET -E -Q "RESTORE DATABASE bw_dragonage_content FROM DISK = '%SOURCE%\bw_dragonage_content.bak' WITH MOVE 'bw_dragonage_content' TO '%TARGET%\bw_dragonage_content.mdf', MOVE 'bw_dragonage_content_log' TO '%TARGET%\bw_dragonage_content.ldf'"
goto End

:Sourcemiss
Echo SOURCE not found. (bw_dragonage_content.bak) Please check.
Echo Edit this File with Notepad and reapply correct location.
goto End

:Targetmiss
Echo TARGET directory does not exist and will be created: %Target%
PAUSE
mkdir "%TARGET%"
if not exist "%TARGET%" goto Stillmiss
goto returnme

:Stillmiss
Echo TARGET Directory creation failed. Please check.
goto End

:SQLmiss32
Echo SQL is missing. Please check location (Windows 32bit): %PROGRAMFILES%\Microsoft SQL Server\90\Tools\Binn\
Echo SQL is missing. Please check location (Windows 64bit): %PROGRAMFILES(X86)%\Microsoft SQL Server\90\Tools\Binn\
Echo Edit this file with Notepad and apply correct location.
goto end

:End
PAUSE</dascript>

'''3.''' Change SET SOURCE and SET TARGET to the path of your Dragon Age installation folder as appropriate. Look it up if you dont know. The above example is default for english WindowsXP 32bit.

:'''3.1''' Common other default paths are ''C:\Program Files(x86)\Dragon Age\...'' for 64Bit Windows XP /Vista
:'''3.2''' ''C:\Programme\Dragon Age\...'' for 32bit Windows XP/Vista (german)
:'''3.3''' ''Archivos de Programa(x86)\Dragon Age\...'' for 64bit Windows XP/Vista (spanish)

'''4.''' Save and run the new "MyRestore.bat" file by doubleclicking. Make sure you are logged in as "Administrator".

'''5.''' Once finished with a short success message ,you can start the Toolset.

'''6.''' If an load of Errors occur, see Error Handling below. (The error might be somewhat hidden, but look for the first occurance first.)

=== Error Handling ===

'''Note:''' Be sure to try again with Administator rights. Especially on Vista and Windows 7. When you have ran the batch file above, note the first error which occured. Heres a list:

'''1.''' Among other messages, you get: "MSG 5133, Level 16, State1, Server ****\BWDATOOLSET, Line1" (Error, system cant find that file...)
:'''1.1''' The path to TARGET was incorrect and cant bee found. The SQL doesnt create paths on its own. Although the BAT file above will do and tell you anyway. Just in case.

'''2.''' Among other messages, you get: "Msg 3634, Level 16, State 1..." "The operating system returned the error (Access denied) while attempting..":
:'''2.1.''' SQL being picky about write access here. Workaround: Change the second line into SET TARGET=C:\DB , and rerun it. You may experiment with this.

'''3.''' Among other messages, you get: "Msg 262, Level 14, State 1, Server ****\BWDATOOLSET, Line 1"
:'''3.1''' Vista Problem. (Might apply to Windows 7 too, but it was not released in 2005) Please confirm.
:'''3.2''' Log in to Windows Vista using your administrative account
:'''3.3''' Open SQL Server Surface Area Configuration Application ( Start --> All Programs --> Microsoft SQL Server 2005 --> Configuration Tools -->SQL Server Surface Area Configuration)
:'''3.4''' Click on Add New Administrator
:'''3.5''' Select the Member of BWDATOOLSET, and click on the Add button to move it to the right. Then click OK, and run the bat file above again.
:'''3.6''' Source Link: http://blog.techdreams.org/2007/11/create-database-permission-denied-sql.html

'''4.''' Amonst other messages, you get: "HResult 0x2, Level16, State 1" Named Pipes Provider: Could not open a connection to SQL Server [2].
:'''4.1''' Link: http://www.cryer.co.uk/brian/sqlserver/hresult_0x2_npp_error_establishing_connection.htm

'''Search:''' Put the name of the error number into a searchengine. Errors seems to be very common here, and likely can be found.

'''Reinstall:''' If you customized the installation, you may want to reinstall the Toolset and try again. There can be errors if entering something out of the norm.

== Using the Backup and Restore batch files ==

'''Note:''' You may only use the following ,if you have <u>no</u> database problem. This section is meant to do backups from a working system!

A pair of batch files have been included with the toolset install to ease the process of making backups. They can be found at:

C:\Program Files\Dragon Age\tools\DatabaseUtilities\Backup_Restore

Both the "Backup" and "Restore" scripts are controlled by settings stored in the config.ini file. If you're using the default database location the only settings you'll need to change are the filenames that backups will be stored to or read from.

Use caution when restoring your database, as this will overwrite everything in your existing database.

Also note that SQL Server is very picky about directory access permissions, and may not be able to write to the directory of your choosing. Check to make sure that your backup file was actually created after doing a backup. A common way of ensuring that SQL Server will be able to write to the backup directory is to create the backup directory directly off of the root of your drive, such as C:\Backups\.

=== Backup ===

<tt>sqlcmd -S .\BWDATOOLSET -E -Q "BACKUP DATABASE <Database Name> TO DISK = '<Backup Directory><Backup Filename>'"</tt>

Where:

:''<Database Name>'' is the name of your database, typically bw_dragonage_content
:''<Backup Directory>'' is the name of the directory where you want to save the backup file (directory must exist, this process will not create it)
:''<Backup Filename>'' is what you are naming the backup file

an example:

<tt>sqlcmd -S .\BWDATOOLSET -E -Q "BACKUP DATABASE bw_dragonage_content TO DISK = 'C:\Backup\bw_dragonage_content.bak'"</tt>

=== Restore ===

<tt>sqlcmd -S .\BWDATOOLSET -E -Q "RESTORE DATABASE <Database Name> FROM DISK = '<Backup Directory><Backup Filename>' WITH REPLACE"</tt>

where:

:''<Database Name>'' is the name of your database, typically bw_dragonage_content
:''<Backup Directory>'' is the name of the directory where the backup file resides
:''<Backup Filename>'' is the name of backup file you wish to restore

an example:

<tt>sqlcmd -S .\BWDATOOLSET -E -Q "RESTORE DATABASE bw_dragonage_content FROM DISK = 'C:\Backup\bw_dragonage_content.bak' WITH REPLACE"</tt>

If you're restoring to a data store that's in a location other than the store you made the backup from (for example if you're moving your data from one computer to another and the toolset is installed in a different location on the destination machine) you can add the following to the restore command to restore to the new location. If you're restoring to the same place you made the backup from you can omit this.

<tt>WITH MOVE 'bw_da_content_euts_Data' TO 'C:\Program Files\Dragon Age\toolssql\Data\bw_dragonage_content.mdf', MOVE 'bw_da_content_euts_Log' TO 'C:\Program Files\Dragon Age\toolssql\Data\bw_dragonage_content.ldf'</tt>

== Troubles with sqlcmd ==

You may experience a strange occurrence where sqlcmd is not recognized as a dos command. You can try to download Microsoft SQL Server 2005 Command Line Query Utility at

http://www.microsoft.com/downloads/details.aspx?FamilyID=D09C1D60-A13C-4479-9B91-9E8B9D835CDC&displaylang=en (scroll down a bit)

Reboot your computer and try it again, it should work.

== Quick Backup & Restore ==

Before doing this tutorial I am going to assume you installed the toolset and sql server at the default settings.

Tutorial

1. create a folder called "Backups" in your C Drive.

2. navigate to the folder and make note of the files there.
C:\Program Files (x86)\Dragon Age\tools\DatabaseUtilities\Backup_Restore

3. go to start --> programs --> accessories --> and "right click" on "command prompt" then choose "Run as administrator"

4. A new window will come up and you'll notice in the top left it will say administrator and you should be at the windows\system32 directory

5. change directory to the backup_restore folder above.

6. run the backup.bat file and then type Backup to confirm .... This will backup your entire DA database to the backups folder. The file was around 783mb for me.

[[Category:Database]]

Compatibility

2010-03-25T11:13:04Z

JackFuzz: /* Module Scope */

DAO has an active modding community. Over time, players will accumulate many new campaigns and game mods. So, as a courtesy to players and other builders, it's helpful to try to make our mods mutually compatible.

From time to time, Bioware may well issue new releases, so it's good to reduce the risk of conflict in that respect, too.

== Disable Add-Ins ==

If the player disables all other add-ins on the in game DLC screen, no conflict should occur between them. Tedious, but effective.

This should rarely be necessary if the compatibility guidelines listed here are observed.

Exception : there is a [[Bug:_export_creates_unnecessary_core_override | toolset bug]] which produces content that persists in game, even when the add-in is disabled, unless the builder cleans it out before making the Builder-to-Player file. The same problem can occur if a builder has intentionally placed content in the packages\override folder.

== Module Scope ==

Setting the Extended Module in Module properties to "Core Game Resources" means that the add-in will change every campaign in game. If that's not intended, select the campaign you're trying to extend e.g. Single Player for the official campaign, (None) for a new standalone campaign.

In the case of Awakening, chances are you will want to extend into core game resources. (This tip needs more feedback from toolset modders).

== Resource Scope ==

The Owner Module resource property has a similar effect on individual design resources. It's easy to make a new core resource accidentally when copy-editing an official core resource, because the Owner Module defaults to core. This isn't obvious, but the resource will export to your module's core folder, where it will impact every campaign in game.

Placing resources in the packages folder should be avoided (unless you have a very good reason), because once a player has installed those resources, they persist, even when your add-in is disabled.

Unfortunately, the packages folder has to be used for resources that won't load from the addins folder, namely

* Core item overrides (.uti)
* Tintmaps
* Resources which are required for the standalone Character Creator program

Art resources posted to local are always sent to the module's core folder.

== Resource Conflict ==

Resource names need to be unique within type. For example, genpt_party.plt and genpt_party.nss are different resources, becasue the type is different. However, if two modules both have resources called genpt_party.plt, only one will load in game, following the [[Source directory priorities]].

Within the toolset database, duplicate resource names are forbidden, but there's nothing to stop different builders making resources which accidentally conflict, so it's wise to choose a unique range of names. Each builder can register the prefix they require. See [[Naming_conventions#Resource_Naming_Convention | Resource Naming Convention]].

It is possible to override a core resource intentionally, by editing a copy, exporting it, and renaming it in the export folder to the same name as the original. However, almost invariably there is a cleaner way of doing this - for example, by changing the 2DA which identifies which resource to use.

== 2DA Conflict ==

Conflict between 2DA mods can be reduced using the [[2DA#Extending_the_game_via_M2DAs | M2DA]] mechanism and [[2DA#Reserved_ID_Ranges_and_overriding_existing_rows | reserving ID ranges]].

== String Conflict ==

When a new module is created, its properties include a [[String ID]] range which starts at a very large random number. This makes it very unlikely that text created by one add-in will override another.

See [[String ID]] main article for a discussion of how this impacts sharing between Builders.

== Core Script Integrity ==

See [[Event_(dascript_type) | Event]] for a typical event-handling script which avoids overwriting the official core scripts.

Bear in mind that an add-in which impacts all campaigns could have undesirable consequences if it changes scripts or event-handling, given that custom campaigns may well have made changes of their own. If in doubt, consider modding the Single Player campaign only.

== Plot Property ==

Scripts that impact all campaigns should respect the plot property on resources. For example, if a campaign author has flagged an NPC as plot, it might not be helpful to change the creature AI.

Feature request: Know what cutscene is playing from your module event.

2010-01-24T07:19:02Z

JackFuzz: /* Know what cutscene is playing from your module event */

[[Category:Feature requests]]
I just want to know what cutscene is about to play so I can act accordingly. There must be another way but I can't figure it out. This is as close as I've gotten.

Example:

<pre>
case EVENT_TYPE_GAMEMODE_CHANGE:
{
int nNewGameMode = GetEventInteger(ev, 0);
int nOldGameMode = GetEventInteger(ev, 1);

if (nNewGameMode == 5)
{
//find out which cutscene is about to play from the local variable
//CURRENT_CUTSCENE which was set in CS_LoadCutscene

string sCutscene = GetLocalString(GetModule(), CURRENT_CUTSCENE);
}
}
</pre>

<pre>
utility_h.nss

void CS_LoadCutsceneWithReplacements(resource rCutscene,
string [] arActors,
object [] arReplacements,
string strPlot = "",
int nPlotFlag = -1,
string sTalkSpeaker = "")
{
object oModule = GetModule();

SetLocalString(oModule, CUTSCENE_SET_PLOT, strPlot);
SetLocalInt(oModule, CUTSCENE_SET_PLOT_FLAG, nPlotFlag);
SetLocalString(oModule, CUTSCENE_TALK_SPEAKER, sTalkSpeaker);

//=================================== NEW LINE OF CODE PLEASE ADD
SetLocalString(oModule, CURRENT_CUTSCENE, ResourceToString(rCutscene));
//=================================== /NEW LINE OF CODE PLEASE ADD

LoadCutscene(rCutscene, OBJECT_INVALID, TRUE, arActors, arReplacements, TRUE);
}

</pre>

== CURRENT PROBLEMS ==

I just found out that I have to add a single line to utility_h.nss but that means I have to compile every other script that uses it. That means I have to essentially modify so many core files.

All I want to know is what cutscene is going to play so I can act accordingly.

Feature request: Know what cutscene is playing from your module event.

2010-01-24T07:18:43Z

JackFuzz: Created page with 'Category:Feature requests = Know what cutscene is playing from your module event = I just want to know what cutscene is about to play so I can act accordingly. There must b...'

[[Category:Feature requests]]
= Know what cutscene is playing from your module event =

I just want to know what cutscene is about to play so I can act accordingly. There must be another way but I can't figure it out. This is as close as I've gotten.

Example:

<pre>
case EVENT_TYPE_GAMEMODE_CHANGE:
{
int nNewGameMode = GetEventInteger(ev, 0);
int nOldGameMode = GetEventInteger(ev, 1);

if (nNewGameMode == 5)
{
//find out which cutscene is about to play from the local variable
//CURRENT_CUTSCENE which was set in CS_LoadCutscene

string sCutscene = GetLocalString(GetModule(), CURRENT_CUTSCENE);
}
}
</pre>

<pre>
utility_h.nss

void CS_LoadCutsceneWithReplacements(resource rCutscene,
string [] arActors,
object [] arReplacements,
string strPlot = "",
int nPlotFlag = -1,
string sTalkSpeaker = "")
{
object oModule = GetModule();

SetLocalString(oModule, CUTSCENE_SET_PLOT, strPlot);
SetLocalInt(oModule, CUTSCENE_SET_PLOT_FLAG, nPlotFlag);
SetLocalString(oModule, CUTSCENE_TALK_SPEAKER, sTalkSpeaker);

//=================================== NEW LINE OF CODE PLEASE ADD
SetLocalString(oModule, CURRENT_CUTSCENE, ResourceToString(rCutscene));
//=================================== /NEW LINE OF CODE PLEASE ADD

LoadCutscene(rCutscene, OBJECT_INVALID, TRUE, arActors, arReplacements, TRUE);
}

</pre>

== CURRENT PROBLEMS ==

I just found out that I have to add a single line to utility_h.nss but that means I have to compile every other script that uses it. That means I have to essentially modify so many core files.

All I want to know is what cutscene is going to play so I can act accordingly.

Feature request: Creating a creature with the player's head morph

2010-01-18T22:45:15Z

JackFuzz: /* Custom Creature Head Mapped to Player */

[[Category:Feature requests]]

== Custom Creature Uses Player Head ==
I want my custom creature that I design to have the head of the player. So under "head morph" in creature creation I want to simply type PLAYER to have it use the players head morph.

* This creature will be customized to wear items and equipment the player does not have.

* Such cutscenes are past and future cutscenes that show the player from another point in time in the game.

* I will use the correct body type. If the player is a human I would naturally use a human body in the creature creation. The point is that the creature will have the look I want (via armor & items).

== Unfortunate Work Around ==

* Disassociate cutscene from conversation line and instead have the conversation line fire a custom script.

* Custom script adds the items and gear I want the player to wear in the cutscene. Custom script also remembers what the user was wearing previously. The script does all this then fires the cutscene so the player is wearing the intended armor and items ONLY needed for the cutscene.

* When the cutscene is finished, have the cutscene fire another custom script which restores the players original armor and deletes the new armor and items added that were only intended for the cutscene.

Feature request: Bone based keyframe animation

2010-01-18T22:44:39Z

JackFuzz: Created page with 'Category:Feature requests == Choose bone, move, rotate, set keyframe == This toolset is so impressive. I love it. It is my new favorite hobby. It has every aspect covered. ...'

[[Category:Feature requests]]

== Choose bone, move, rotate, set keyframe ==

This toolset is so impressive. I love it. It is my new favorite hobby. It has every aspect covered.

The ONLY thing the toolset is missing is the ability to create new animations. Is there anyway you can let us set keyframes for invidivual bones? That way we can just select the bone, move it around and rotate it, then set a keyframe along with the curve button on.

Being able to make new animatons would complete the toolset.

== Possible Alternatives ==

Instead of letting us make new animations, can you at least post some kind of tutorial so we can get new .ANI into the toolset? I have experience with 3d studio max, so maybe I can make new animations then export them for use in the toolset.

Feature request: Creating a creature with the player's head morph

2010-01-18T20:44:20Z

JackFuzz: /* Custom Creature Head Mapped to Player */

[[Category:Feature requests]]

== Custom Creature Head Mapped to Player ==
I want my custom creature that I design to have the head of the player. So under "head morph" in creature creation I want to simply type PLAYER to have it use the players head morph.

* This creature will be customized to wear items and equipment the player does not have.

* Such cutscenes are past and future cutscenes that show the player from another point in time in the game.

* I will use the correct body type. If the player is a human I would naturally use a human body in the creature creation. The point is that the creature will have the look I want (via armor & items).

== Unfortunate Work Around ==

* Disassociate cutscene from conversation line and instead have the conversation line fire a custom script.

* Custom script adds the items and gear I want the player to wear in the cutscene. Custom script also remembers what the user was wearing previously. The script does all this then fires the cutscene so the player is wearing the intended armor and items ONLY needed for the cutscene.

* When the cutscene is finished, have the cutscene fire another custom script which restores the players original armor and deletes the new armor and items added that were only intended for the cutscene.

Feature request: Creating a creature with the player's head morph

2010-01-18T20:44:05Z

JackFuzz: Created page with 'Category:Feature requests == Custom Creature Head Mapped to Player == I want my custom creature that I design to have the head of the player. So under "head morph" in crea...'

[[Category:Feature requests]]

== Custom Creature Head Mapped to Player ==

I want my custom creature that I design to have the head of the player. So under "head morph" in creature creation I want to simply type PLAYER to have it use the players head morph.

* This creature will be customized to wear items and equipment the player does not have.

* Such cutscenes are past and future cutscenes that show the player from another point in time in the game.

* I will use the correct body type. If the player is a human I would naturally use a human body in the creature creation. The point is that the creature will have the look I want (via armor & items).

== Unfortunate Work Around ==

* Disassociate cutscene from conversation line and instead have the conversation line fire a custom script.

* Custom script adds the items and gear I want the player to wear in the cutscene. Custom script also remembers what the user was wearing previously. The script does all this then fires the cutscene so the player is wearing the intended armor and items ONLY needed for the cutscene.

* When the cutscene is finished, have the cutscene fire another custom script which restores the players original armor and deletes the new armor and items added that were only intended for the cutscene.

Bug: cutscene editor in toolset lags when headtracking is set

2010-01-18T20:25:41Z

JackFuzz: Created page with '*'''Version found: 1.0.1008.0'''  *'''Status:''' Open == Description == The cutscene editor will begin to lag very badly when...'

*'''Version found: 1.0.1008.0''' 
*'''Status:''' Open

== Description ==
The cutscene editor will begin to lag very badly when I have headtracking set. The type of lag is 3-4 second delays when I do
anything! I'll click the timeline and it will hang for 4 seconds.
If I scrub a slider it will take 3-5 seconds for it to respond. But
as soon as I disable headtracking from all headtracking slots and
set them to blank the problem goes away.

== Workarounds ==
Don't turn on headtracking until your cutscene is completely done.
Do all your headtracking work last!

[[Category:Toolset bugs]]

Script

2010-01-17T11:16:52Z

JackFuzz: /* Inventory Count - basic syntax */

Scripts in Dragon Age are used to control all manner of game activity. Much of the functionality that would normally be handled by the game engine is actually managed by core scripts, allowing deep customizability.

== [[Scripting overview]] - basic syntax ==

The DA scripting language is very similar to C in terms of syntax. Files can be included into other files, with files containing libraries of functions designated by a "_h" suffix. (eg. wrappers_h)

== [[Event (dascript type)|Event]]s - driving practically everything ==

Dragon Age has an event-driven scripting model, with event objects being passed to scripts containing different parameters depending on the event's type. A large portion of script-writing for a standard adventure is going to involve dealing with events. Common examples include:

* An event is fired to a plot's script whenever one of its flags is set or cleared
* An event is fired to an area's script when a team of creatures dies in it or when a creature (such as the player) enters
* Events are fired to the module's script during character generation
* Events are fired to creatures when certain things happen to them (such as being hit)

[[Custom AI]] for creatures is handled by creating custom AI event handlers.

== [[Effect (dascript type)|Effect]]s and [[Ability|Abilities]] - how to make things affect other things ==

Effects are a bundle of modifiers that are applied to an object or creature. Every effect has a type set on it that determines how it affects the object it is applied to. They also have a number of parameters on them, which vary based on the type, that change the specific behaviour. When the effect is removed (usually because the duration on the effect expires) the modifier is removed. These modifiers can be rule or stat based or more complicated visual and game effects.

They can be assigned different duration types which affect how they're applied and removed:

# Temporary: Applied for a short duration (measured in seconds)
# Permanent: Applied until manually removed through scripting
# Instant: These are one-shot modifiers that are not stored on the object (the death effect is an instant modifier for example)
# Equipped: Associated with an equipped item. The effect is removed when the item is unequipped.

Effects are commonly applied by abilities, which are possessed by both creatures and player characters.

==[[2DA]] files - All-purpose game-wide data repositories ==

2-Dimensional Arrays contain much of the raw data used by the game. They are generated from Microsoft Excel files. If you want to add new basic creature types, new treasure types, and so forth, you'll need to create new [[2DA]] files.

2DA row ID numbers need to be unique across all currently active addins for any given 2DA, otherwise they'll override each other with potentially disruptive effects. See [[2DA ranges in use]] for a list of 2DA row IDs currently used by popular addins.

== [[Treasure system]] ==

The treasure possessed by most creatures and containers is randomly generated by the game's core scripts using a system that selects from appropriate treasure types (for example, wild animals should rarely possess steel armor in their inventories, and Darkspawn are unlikely to be carrying fine porcelain vases) and auto-scales it to be reasonably useful or valuable at the character's level. Manipulating the treasure system can involve both [[local variable]]s and [[event (type)|event]]s.

To put a specific treasure item in a specific creature's [[inventory]], you'll have to create a new creature template for that creature. Inventory cannot be directly defined for particular objects already placed in an [[area]].

== [[Local variable]]s - data repositories for individual objects ==

Local variables are persistent variables that are associated with in-game objects. They are not the same as the temporary variables you can create in a script; local variables retain their values even when no scripts are using them, and are shared across any scripts that choose to access them.

Local variables are set using the SetLocal* functions and read using the GetLocal* functions. There are a number of SetLocal* functions in the game engine.

Local variables must be pre-defined in a variable [[2DA]] before they can be read or set using these functions. Dragon Age doesn't support the dynamic in-game allocation of new local variables.

== [[Inventory Count]] - basic syntax ==

How do you know if the user has enough inventory space before adding items?

//Get max inventory size
int iMaxInventorySize = GetMaxInventorySize(GetHero());
object[] oInv = GetItemsInInventory(GetHero(), GET_ITEMS_OPTION_BACKPACK, 0, "", 1);

PrintToLog("Max Inventory size:" + IntToString(iMaxInventorySize));
PrintToLog("Current Inventory count:" + IntToString(GetArraySize(oInv)));

This returned 102 items in my inventory out of a total of 120.

[[Category:Scripts]]

Script

2010-01-17T11:15:55Z

JackFuzz: /* Local variables - data repositories for individual objects */

Script

2010-01-17T11:15:30Z

JackFuzz: /* Inventory Count - basic syntax */

Script

2010-01-17T11:15:05Z

JackFuzz: /* Inventory Counts - get max and current inventory count */

Scripts in Dragon Age are used to control all manner of game activity. Much of the functionality that would normally be handled by the game engine is actually managed by core scripts, allowing deep customizability.

== [[Scripting overview]] - basic syntax ==

The DA scripting language is very similar to C in terms of syntax. Files can be included into other files, with files containing libraries of functions designated by a "_h" suffix. (eg. wrappers_h)

== [[Inventory Count]] - basic syntax ==

How do you know if the user has enough inventory space before adding items?

//Get max inventory size
int iMaxInventorySize = GetMaxInventorySize(GetHero());
object[] oInv = GetItemsInInventory(GetHero(), GET_ITEMS_OPTION_BACKPACK, 0, "", 1);

PrintToLog("Max Inventory size:" + IntToString(iMaxInventorySize));
PrintToLog("Current Inventory count:" + IntToString(GetArraySize(oInv)));

This returned 102 items in my inventory out of a total of 120.

== [[Event (dascript type)|Event]]s - driving practically everything ==

Dragon Age has an event-driven scripting model, with event objects being passed to scripts containing different parameters depending on the event's type. A large portion of script-writing for a standard adventure is going to involve dealing with events. Common examples include:

* An event is fired to a plot's script whenever one of its flags is set or cleared
* An event is fired to an area's script when a team of creatures dies in it or when a creature (such as the player) enters
* Events are fired to the module's script during character generation
* Events are fired to creatures when certain things happen to them (such as being hit)

[[Custom AI]] for creatures is handled by creating custom AI event handlers.

== [[Effect (dascript type)|Effect]]s and [[Ability|Abilities]] - how to make things affect other things ==

Effects are a bundle of modifiers that are applied to an object or creature. Every effect has a type set on it that determines how it affects the object it is applied to. They also have a number of parameters on them, which vary based on the type, that change the specific behaviour. When the effect is removed (usually because the duration on the effect expires) the modifier is removed. These modifiers can be rule or stat based or more complicated visual and game effects.

They can be assigned different duration types which affect how they're applied and removed:

# Temporary: Applied for a short duration (measured in seconds)
# Permanent: Applied until manually removed through scripting
# Instant: These are one-shot modifiers that are not stored on the object (the death effect is an instant modifier for example)
# Equipped: Associated with an equipped item. The effect is removed when the item is unequipped.

Effects are commonly applied by abilities, which are possessed by both creatures and player characters.

==[[2DA]] files - All-purpose game-wide data repositories ==

2-Dimensional Arrays contain much of the raw data used by the game. They are generated from Microsoft Excel files. If you want to add new basic creature types, new treasure types, and so forth, you'll need to create new [[2DA]] files.

2DA row ID numbers need to be unique across all currently active addins for any given 2DA, otherwise they'll override each other with potentially disruptive effects. See [[2DA ranges in use]] for a list of 2DA row IDs currently used by popular addins.

== [[Treasure system]] ==

The treasure possessed by most creatures and containers is randomly generated by the game's core scripts using a system that selects from appropriate treasure types (for example, wild animals should rarely possess steel armor in their inventories, and Darkspawn are unlikely to be carrying fine porcelain vases) and auto-scales it to be reasonably useful or valuable at the character's level. Manipulating the treasure system can involve both [[local variable]]s and [[event (type)|event]]s.

To put a specific treasure item in a specific creature's [[inventory]], you'll have to create a new creature template for that creature. Inventory cannot be directly defined for particular objects already placed in an [[area]].

== [[Local variable]]s - data repositories for individual objects ==

Local variables are persistent variables that are associated with in-game objects. They are not the same as the temporary variables you can create in a script; local variables retain their values even when no scripts are using them, and are shared across any scripts that choose to access them.

Local variables are set using the SetLocal* functions and read using the GetLocal* functions. There are a number of SetLocal* functions in the game engine.

Local variables must be pre-defined in a variable [[2DA]] before they can be read or set using these functions. Dragon Age doesn't support the dynamic in-game allocation of new local variables.

[[Category:Scripts]]

Script

2010-01-17T11:14:11Z

JackFuzz: /* Scripting overview - basic syntax */

Scripts in Dragon Age are used to control all manner of game activity. Much of the functionality that would normally be handled by the game engine is actually managed by core scripts, allowing deep customizability.

== [[Scripting overview]] - basic syntax ==

The DA scripting language is very similar to C in terms of syntax. Files can be included into other files, with files containing libraries of functions designated by a "_h" suffix. (eg. wrappers_h)

== [[Inventory Counts]] - get max and current inventory count ==

How do you know if the user has enough inventory space before adding items?

//Get max inventory size
int iMaxInventorySize = GetMaxInventorySize(GetHero());
object[] oInv = GetItemsInInventory(GetHero(), GET_ITEMS_OPTION_BACKPACK, 0, "", 1);

PrintToLog("Max Inventory size:" + IntToString(iMaxInventorySize));
PrintToLog("Current Inventory count:" + IntToString(GetArraySize(oInv)));

This returned 102 items in my inventory out of a total of 120.

Enjoy

== [[Event (dascript type)|Event]]s - driving practically everything ==

Dragon Age has an event-driven scripting model, with event objects being passed to scripts containing different parameters depending on the event's type. A large portion of script-writing for a standard adventure is going to involve dealing with events. Common examples include:

* An event is fired to a plot's script whenever one of its flags is set or cleared
* An event is fired to an area's script when a team of creatures dies in it or when a creature (such as the player) enters
* Events are fired to the module's script during character generation
* Events are fired to creatures when certain things happen to them (such as being hit)

[[Custom AI]] for creatures is handled by creating custom AI event handlers.

== [[Effect (dascript type)|Effect]]s and [[Ability|Abilities]] - how to make things affect other things ==

Effects are a bundle of modifiers that are applied to an object or creature. Every effect has a type set on it that determines how it affects the object it is applied to. They also have a number of parameters on them, which vary based on the type, that change the specific behaviour. When the effect is removed (usually because the duration on the effect expires) the modifier is removed. These modifiers can be rule or stat based or more complicated visual and game effects.

They can be assigned different duration types which affect how they're applied and removed:

# Temporary: Applied for a short duration (measured in seconds)
# Permanent: Applied until manually removed through scripting
# Instant: These are one-shot modifiers that are not stored on the object (the death effect is an instant modifier for example)
# Equipped: Associated with an equipped item. The effect is removed when the item is unequipped.

Effects are commonly applied by abilities, which are possessed by both creatures and player characters.

==[[2DA]] files - All-purpose game-wide data repositories ==

2-Dimensional Arrays contain much of the raw data used by the game. They are generated from Microsoft Excel files. If you want to add new basic creature types, new treasure types, and so forth, you'll need to create new [[2DA]] files.

2DA row ID numbers need to be unique across all currently active addins for any given 2DA, otherwise they'll override each other with potentially disruptive effects. See [[2DA ranges in use]] for a list of 2DA row IDs currently used by popular addins.

== [[Treasure system]] ==

The treasure possessed by most creatures and containers is randomly generated by the game's core scripts using a system that selects from appropriate treasure types (for example, wild animals should rarely possess steel armor in their inventories, and Darkspawn are unlikely to be carrying fine porcelain vases) and auto-scales it to be reasonably useful or valuable at the character's level. Manipulating the treasure system can involve both [[local variable]]s and [[event (type)|event]]s.

To put a specific treasure item in a specific creature's [[inventory]], you'll have to create a new creature template for that creature. Inventory cannot be directly defined for particular objects already placed in an [[area]].

== [[Local variable]]s - data repositories for individual objects ==

Local variables are persistent variables that are associated with in-game objects. They are not the same as the temporary variables you can create in a script; local variables retain their values even when no scripts are using them, and are shared across any scripts that choose to access them.

Local variables are set using the SetLocal* functions and read using the GetLocal* functions. There are a number of SetLocal* functions in the game engine.

Local variables must be pre-defined in a variable [[2DA]] before they can be read or set using these functions. Dragon Age doesn't support the dynamic in-game allocation of new local variables.

[[Category:Scripts]]

Morph

2010-01-06T01:22:45Z

JackFuzz: /* How to override companion & NPC Morphs */

[[Image:New resource.png|thumb|The new resource menu contains a "Morph" option]]

Morphs are highly customizable heads that can be added to many of the common humanoid creatures in Dragon Age to create unique characters. They are not listed on the palette window; to create a new morph you'll have to go to the "File" menu, select "New", and then select "Morph" from the list of resource types.

A morph must first start with a basic head shape. Select one from the drop-down menu in the toolbar (it defaults to "choose base", indicating the need to select one) and the head will appear in the main display. The camera can be maneuvered around it using many of the same basic controls used elsewhere in the toolset. The head bases that are available include male and female versions of Human, Dwarf, Elf, and a gender-neutral child's head.

Once the base is selected, an enormous number of options will become available in the object inspector for modifying the exact shape and texture of the head. Hairstyles and beards can be added, tattoo textures can be overlaid on the skin, and so forth - there are hundreds of parameters.

To speed the creation of unique generic NPCs, the "randomize" button in the toolbar will set the various shape parameters to random values. This doesn't affect all facial features, however, since many of the adjustable features would look quite bizarre when set to extreme values. Generally the effects of the randomize button are limited to tabs 4 through 8, and it doesn't affect all of the features even on those. Manual customization may still be required to produce a truly diverse crop of NPCs.

Note that for some features (for example, lip color) the opacity defaults to 0%, so you may not see an immediate effect when changing them unless you set the opacity higher first.

[[Image:Morph editor.png|600px|thumb|center]]

== How to override companion & NPC Morphs ==

1. Open toolset

2. '''File''' --> '''Manage Modules''' --> Switch to single player campaign

3. Open the '''"Creatures" palette''' and put the name of the companion or npc in the filter. Example: "alistair"

4. A few tabs open up.... Expand the '''"_Global/Followers"''' folder and you will see alistair's model, (i also included npc example):

companion:
gen00fl_alistair (Alistair)

npc:
ntb100cr_gheyna (Gheyna)

5. For companions REMOVE THE NUMBERS. For NPCs REMOVE the letters between the number and the _ ... Compare these to the ones in step 4:

companion:
genfl_alistair

npc:
ntb100_gheyna.mor

6. Then add the appropriate prefix.

ef_ = elf female
hm_ = human male
hf_ = human female
em_ = elf male
dm_ = dwarf male
df_ = dwarf female

7. So you would rename your morph:

companion:
hm_genfl_alistair.mor

npc:
ef_ntb100_gheyna.mor

8. Then place it into the folder:

\\\\Documents\\\\BioWare\\\\Dragon Age\\\\modules\\\\Single Player\\\\override

Examples:

Alistair: hm_genfl_alistair.mor
Morrigan: hf_genfl_morrigan.mor
Gheyna: ef_ntb100_gheyna.mor

== Beards and facial features ==

There are two basic types of beards available for facial morphs; model beards and stubble beards. Stubble beards are simply a texture overlay, and have no particular special effects associated with them. Model beards are three-dimensional objects that are affixed to the face, and it is important to be aware of certain limitations that come with using them.

In order to make a physical beard model fit properly onto the face, some facial features must be set to their default values. This is so that, as an example, one doesn't wind up with the tip of the chin poking out through the end of the beard. When you add a physical beard model to a head morph these specific facial features are automatically snapped to their default values and are locked there for as long as the beard is in place. If the beard is removed they become editable again, but it is important to note that they do ''not'' return to whatever values they had before the beard was added. So make the decision on whether a character has a physical beard before you spend a lot of time adjusting his jawline and other such details.

== Debug features ==

There are a number of features with "debug" in their names that are intended only to allow a facial artist to get a better view of certain parts of a facial morph, and if they are set to anything other than zero the morph won't be usable by the rest of the toolset. The most obvious example is the "teeth debug" parameter, which pulls the lips back to expose the model's teeth so that they can be adjusted in plain view.

== How to use a morph in your module ==

Morph is an art tool, not a design tool, and so it uses a somewhat different mechanism for making its output available to the designer than the other tools that come with the toolset. You can save a morph as a file in your regular filesystem but when you go to select a head morph in the creature designer you won't be able to import directly from the filesystem to use it.

Instead, you need to export the morph via the "post to local" command under the "Tools"->"Export" menu (alternately, right-click on the morph's display window and select "post to local" from the menu). Once the morph has been exported, it will be available in the creature creator's morph list when the appropriate body appearance model is selected (eg, a human female head morph is usable with a human female body appearance).

If you want to make a slight variation on an existing morph (say for example to change the hair colour or add a scar), load the mrh file of the desired morph, and then 'save as' with a new file name. Make your changes and save, then once again export to local. To make the new variant available, use "View"->"Refresh".

== How to replace the morph of an in game NPC (Single Player Campaign) ==

1. Open Toolset

2. Click the "Creatures" Button on the top right Palette Window

3. In the filter type the name of the NPC, example Bella or Desire or Murdock.

4. You'll see some folders appear. Navigate through them and find the NPC object:

Example: ntb100cr_gheyna (Gheyna)

5. Now left click that creature to highlight it.

6. On the bottom right the object inspector window appears full of information.

7. Scroll down the list until you see head morph, under appearance. Note the name of that file.

8. Rename the new morph file you exported to the name in the object inspector.

9. Now place your new morph in the following directory:

documents/bioware/dragon age/packages/core/override

Make sure you restart dragon age.

== Morph files ==

There are actually two files for every morph.
*.mrh - This is the source file for the morph data and can be saved anywhere and loaded from anywhere.
*.mor - This is the generated/processed binarized gff file that the game uses. You can change these in the toolset but it's not recommended.

To get the *.mor file you need to use the "export" command.

To edit an existing .mrh, you can either drag and drop the .mrh into the toolset or open the *.mrh from the toolset.

The head morph tool concatenates the two letter prefix (HM for human male, HF for human female, etc.) to the filename for you. If you saved a resource called "myhead", for example, and it was a human male then it would export a hm_myhead.mor. If it was a female dwarf it would save it as df_myhead.mor

The drop down for the head morph will also auto generate the two letter prefix based on the gender and appearance of the creature you are making.

== Deleting a morph ==

Morphs are an art asset, and as such are not stored in the database in the same manner as other resources. You can find morph files (.mor extension) in the \Dragon Age\packages\core\override\toolsetexport directory, to remove one simply delete it.

== Parameters ==

{{sidebox|
* Keep in mind that when selecting colors, you can open up a dropdown list where you browse for colors, and choose "All Tint Files *.tnt" to get a much wider range of color choices. The Tattoo colors especially (t1_tat_*) are very vibrant, and can give you 'very blue eyes', for example.
}}

Choose Base model name:

*HM_UHM_BASE - Human Male
*HF_UHM_BASE - Human Female
*DM_UHM_BASE - Dwarven Male
*DF_UHM_BASE - Dwarven Female
*EM_UHM_BASE - Elven Male
*EF_UHM_BASE - Elven Female
*QM_UHM_BASE - Qunari Male
*QF_UHM_BASE - Qunari Female
*KN_UHM_BASE - Child

*(Opacity 0.00 least color - 1.00 full color)
*(Anything 0.00 to 1.00 or -1.00 to 1.00 is a slider)
*(Left and Right = Left and Right of Morph Face not Left and Right as you look at the face.)

01. MATERIAL:

01. Face:

*Skin Color: 8 choices
*Lip Makeup Color: 27 choices
*Lip Makeup Opacity: 0.00 - 1.00
*Blush Makeup Color: 30 choices
*Blush Makeup Opacity: 0.00 - 1.00
*Eye Makeup Color: 36 choices
*Eye Makeup Opacity: 0.00 - 1.00

02. Skin Texture:

*Base Skin Texture: 12 choices
*Blend Skin Texture: 12 choices
*Blend Right Eye: 0.00 - 1.00
*Blend Left Eye: 0.00 - 1.00
*Blend Right Cheek: 0.00 - 1.00
*Blend Left Cheek: 0.00 - 1.00
*Blend Left Forehead: 0.00 - 1.00
*Blend Right Forehead: 0.00 - 1.00
*Blend Nose: 0.00 - 1.00
*Blend Middle Forehead: 0.00 - 1.00
*Blend All Override: 0.00 - 1.00

03. Skin Type:

*Blend Right Eye: 0.00 - 1.00
*Blend Left Eye: 0.00 - 1.00
*Blend Right Cheek: 0.00 - 1.00
*Blend Left Cheek: 0.00 - 1.00
*Blend Left Forehead: 0.00 - 1.00
*Blend Right Forehead: 0.00 - 1.00
*Blend Nose: 0.00 - 1.00
*Blend Middle Forehead: 0.00 - 1.00
*Blend All Override: 0.00 - 1.00

02. PART SELECTION:

1. Model: (Base model Chosen when starting.)

2. Parts:

*Eye Color: 11 choices
*Eyes: 2 choices
*Eye Texture: 16 choices
*Hair and Beard Color: 10 choices
*Hair: 17 choices
*Beard: 7 choices
*Eye Lashes: 1 choice
*Lashes Texture: 4 choices

3. Tattoo:

*Tattoo Mask: 14 choices
*Tattoo Channel 1 Color: 15 choices
*Tattoo 1 : R Channel: 0.00 - 1.00
*Tattoo Channel 2 Color: 15 choices
*Tattoo 2 : G Channel: 0.00 - 1.00
*Tattoo Channel 3 Color: 15 choices
*Tattoo 3 : B Channel: 0.00 - 1.00
*Tattoo Channel 4 Color: 15 choices
*Tattoo 4 : A Channel: 0.00 - 1.00

4. Brow and Stubble:

*Brow and Stubble Colors: 10 choices
*Bushy Eyebrows: 0.00 - 1.00 (only available if regular eyebrows set to 0.00)
*Regular Eyebrows: 0.00 - 1.00
*Thick Eyebrows: 0.00 - 1.00 (only available if regular eyebrows set to 0.00)
*Thinned Eyebrows: 0.00 - 1.00 (only available if regular eyebrows set to 0.00)
*Goatee: 0.00 - 1.00
*Soul Patch: 0.00 - 1.00
*Mustache: 0.00 - 1.00
*Pork Chops: 0.00 - 1.00

5. Crew Cut Selection:

*Sheppard: 0.00 - 1.00
*Receeding Hairline: 0.00 - 1.00
*Balding Hairline: 0.00 - 1.00

03. FEATURE SELECTION:

01. Shape:

*Head Shape 01: 0.00 - 1.00
*Head Shape 02: 0.00 - 1.00
*Head Shape 03: 0.00 - 1.00
*Head Shape Fat: 0.00 - 1.00
*Head Shape Thick: 0.00 - 1.00
*Head Shape Thin: 0.00 - 1.00
*(You can only choose to adjust one of these shapes.)

02. Nose:

*Eastern Nose: 0.00 - 1.00
*Flat Nose: 0.00 - 1.00
*Long Nose: 0.00 - 1.00
*Pig Nose: 0.00 - 1.00
*Straight Nose: 0.00 - 1.00
*Thick Nose: 0.00 - 1.00
*(You can only choose to adjust one of these shapes.)

03. Eye Shape:

*Eye Shape 01: 0.00 - 1.00
*Eye Shape 02: 0.00 - 1.00
*Eye Shape 02: 0.00 - 1.00
*Eye Shape 04: 0.00 - 1.00
*(You can only choose to adjust one of these shapes.)

04. Universal Shapes:

*Shape Chubby: 0.00 - 1.00
*Shape Skinny: 0.00 - 1.00
*(You can adjust both of these.)

Reset
*(Left clicking in box to right resets all selections to 0.00)

04. NOSE:

01. Targets:

*Nose Bend Left/Right: -1.00 - 1.00
*Nose Bridge In/Out: -1.00 - 1.00
*Nose Bridge Thin/Wide: -1.00 - 1.00
*Nose Up/Down: -1.00 - 1.00
*Nose Out/In: -1.00 - 1.00
*Nose Smaller/Larger: -1.00 - 1.00
*Nose Tip Up/Down: -1.00 - 1.00
*Nose Tip Out/In: -1.00 - 1.00
*Nostrils Narrow/Wide: -1.00 - 1.00

02. Shape:

*Nose Shape 1: 0.00 - 1.00
*Nose Shape 2: 0.00 - 1.00
*Nose Shape 3: 0.00 - 1.00
*Nose Shape 4: 0.00 - 1.00
*Nose Shape 5: 0.00 - 1.00
*Nose Shape 6: 0.00 - 1.00
*(You can choose to adjust any or all of these.)

Reset
*(Left clicking in box to right resets all selections to 0.00)

05. MOUTH:

01. Targets:

*Mouth Back/Forward: -1.00 - 1.00
*Mouth Corner Up/Down: -1.00 - 1.00
*Mouth Up/Down: -1.00 - 1.00
*Mouth Lips Fat/Thin: -1.00 - 1.00
*Mouth Lower Lip Fat: 0.00 - 1.00
*Mouth Lower Lip Up: 0.00 - 1.00
*Mouth Narrow/Wide: -1.00 - 1.00
*Mouth Over/Underbite: -1.00 - 1.00
*Mouth Upper Lip Down: 0.00 - 1.00
*Mouth Upper Lip Fat: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

06. EYES:

01. Targets:

*Eye Bags: 0.00 - 1.00
*Eye Brow Back/Forward: -1.00 - 1.00
*Eye Brow Down/Up: -1.00 - 1.00
*Eye Narrow/Wide: -1.00 - 1.00
*Eye Position Down/Up: -1.00 - 1.00
*Eyelash Fan: 0.00 - 1.00
*Eyelash Length: 0.00 - 1.00
*Eyes Back/Forward: -1.00 - 1.00
*Eyes Larger: 0.00 - 1.00
*Eyes Small: 0.00 - 1.00
*Eyes Squint: 0.00 - 1.00

02. Debug

Debug Cornea Larger/Smaller: -1.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

07. CHEEKS:

01. Targets:

*Cheeks Back/Forward: -1.00 - 1.00
*Cheeks Bones In/Out: -1.00 - 1.00
*Cheeks Gaunt: 0.00 - 1.00
*Cheeks Lower: 0.00 - 1.00
*Cheeks Up: 0.00 - 1.00
*Cheeks Wide: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

08. JAW:

01. Targets:

*Jaw Chin Down/Up: -1.00 - 1.00
*Jaw Chin In/Out: -1.00 - 1.00
*Jaw Chin Thin/Wide: -1.00 - 1.00
*Jaw Lower: 0.00 - 1.00
*Jaw Narrow/Wide: -1.00 - 1.00
*Jaw Square Shape: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

10. TEETH:

01. Targets:

*TeethChippedtoothLeft: 0.00 - 1.00
*TeethChippedtoothRight: 0.00 - 1.00
*TeethMissingLeft: 0.00 - 1.00
*TeethNoFront: 0.00 - 1.00
*Teeth Back/Forward: -1.00 - 1.00
*Teeth Close/Separate: -1.00 - 1.00
*Teeth Down/Up: -1.00 - 1.00

02. Debug:

*Teeth Wide/Narrow: -1.00 - 1.00
*Teeth Debug: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

11. EARS:

01. Targets:

*Ears Down/Up: -1.00 - 1.00
*Ears In/Out: -1.00 - 1.00
*Ears Large/Small: -1.00 - 1.00
*Ears Rotate Outwards: 0.00 - 1.00
*Ears Wide/Narrow: -1.00 - 1.00

02. Debug:

Ears Debug for Hair Crashing: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

12. NECK:

01. Targets:

*NeckApple: 0.00 - 1.00
*NeckThin: 0.00 - 1.00
*Neck Back: 0.00 - 1.00
*Neck Wide: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

13. BROWS:

01. Targets:

*Brow Down/Up: -1.00 - 1.00
*Forehead Out/In: -1.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

13. VIEW SETTINGS:

1. Light:

*Light Model: 6 choices
*Light Probe: 4 choices

2. Camera:

*Distance: Numeric
*Orientation: 3 coordinates
*Position: 3 coordinates

3. Object:

*Orientation: 3 coordinates
*Position: 3 coordinates

4. Facial Animation:

*FA name: Blank
*FA set: 5 choices

14. EXPORT SETTINGS

General:

Export .mop file: True/False (False default)

14. UNIQUE SHAPES:

01. Targets:

*Fat Man: 0.00 - 1.00
*Shape Alistair: 0.00 - 1.00
*Shape Daveth: 0.00 - 1.00
*Shape Duncan: 0.00 - 1.00
*Shape Jory: 0.00 - 1.00
*Shape King Cailan: 0.00 - 1.00
*Shape Loghain: 0.00 - 1.00
*Shape Old Male: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

== Tints and hairstyles ==

Tints and hairstyles often have somewhat uninformative names. The following thumbnails provide a preview summary of what these tints and hairstyles represent:

=== Dwarf male beards ===

<gallery>
Image:dm_brd_b1a_0 front.jpg | dm_brd_b1a_0 front
Image:dm_brd_b1a_0 side.jpg | dm_brd_b1a_0 side
Image:dm_brd_b2a_0 front.jpg | dm_brd_b2a_0 front
Image:dm_brd_b2a_0 side.jpg | dm_brd_b2a_0 side
Image:dm_brd_b3a_0 front.jpg | dm_brd_b3a_0 front
Image:dm_brd_b3a_0 side.jpg | dm_brd_b3a_0 side
Image:dm_brd_b4a_0 front.jpg | dm_brd_b4a_0 front
Image:dm_brd_b4a_0 side.jpg | dm_brd_b4a_0 side
Image:dm_brd_b5a_0 front.jpg | dm_brd_b5a_0 front
Image:dm_brd_b5a_0 side.jpg | dm_brd_b5a_0 side
Image:dm_brd_b6a_0 front.jpg | dm_brd_b6a_0 front
Image:dm_brd_b6a_0 side.jpg | dm_brd_b6a_0 side
Image:dm_brd_b7a_0 front.jpg | dm_brd_b7a_0 front
Image:dm_brd_b7a_0 side.jpg | dm_brd_b7a_0 side
</gallery>

=== Human female hairstyles ===

<gallery>
Image:hf_har_blda_0 front.jpg |hf_har_blda_0 front
Image:hf_har_blda_0 side.jpg | hf_har_blda_0 side
Image:hf_har_ha1a_0 front.jpg |hf_har_ha1a_0 front
Image:hf_har_ha1a_0 side.jpg | hf_har_ha1a_0 side
Image:hf_har_ha2a_0 front.jpg |hf_har_ha2a_0 front
Image:hf_har_ha2a_0 side.jpg | hf_har_ha2a_0 side
Image:hf_har_ha3a_0 front.jpg |hf_har_ha3a_0 front
Image:hf_har_ha3a_0 side.jpg | hf_har_ha3a_0 side
Image:hf_har_ha4a_0 front.jpg |hf_har_ha4a_0 front
Image:hf_har_ha4a_0 side.jpg | hf_har_ha4a_0 side
Image:hf_har_hb1a_0 front.jpg |hf_har_hb1a_0 front
Image:hf_har_hb1a_0 side.jpg | hf_har_hb1a_0 side
Image:hf_har_hb2a_0 front.jpg |hf_har_hb2a_0 front
Image:hf_har_hb2a_0 side.jpg | hf_har_hb2a_0 side
Image:hf_har_hb3a_0 front.jpg |hf_har_hb3a_0 front
Image:hf_har_hb3a_0 side.jpg | hf_har_hb3a_0 side
Image:hf_har_hb4a_0 front.jpg |hf_har_hb4a_0 front
Image:hf_har_hb4a_0 side.jpg | hf_har_hb4a_0 side
Image:hf_har_hc1a_0 front.jpg |hf_har_hc1a_0 front
Image:hf_har_hc1a_0 side.jpg | hf_har_hc1a_0 side
Image:hf_har_hc2a_0 front.jpg |hf_har_hc2a_0 front
Image:hf_har_hc2a_0 side.jpg | hf_har_hc2a_0 side
Image:hf_har_hc3a_0 front.jpg |hf_har_hc3a_0 front
Image:hf_har_hc3a_0 side.jpg | hf_har_hc3a_0 side
Image:hf_har_hc4a_0 front.jpg |hf_har_hc4a_0 front
Image:hf_har_hc4a_0 side.jpg | hf_har_hc4a_0 side
Image:hf_har_hd1a_0 front.jpg |hf_har_hd1a_0 front
Image:hf_har_hd1a_0 side.jpg | hf_har_hd1a_0 side
Image:hf_har_hd2a_0 front.jpg |hf_har_hd2a_0 front
Image:hf_har_hd2a_0 side.jpg | hf_har_hd2a_0 side
Image:hf_har_hd3a_0 front.jpg |hf_har_hd3a_0 front
Image:hf_har_hd3a_0 side.jpg | hf_har_hd3a_0 side
Image:hf_har_hd4a_0 front.jpg |hf_har_hd4a_0 front
Image:hf_har_hd4a_0 side.jpg | hf_har_hd4a_0 side
</gallery>

=== Human male beards ===

<gallery>
Image:hm_brd_b1a_0 front.jpg | hm_brd_b1a_0 front
Image:hm_brd_b1a_0 side.jpg | hm_brd_b1a_0 side
Image:hm_brd_b2a_0 front.jpg | hm_brd_b2a_0 front
Image:hm_brd_b2a_0 side.jpg | hm_brd_b2a_0 side
Image:hm_brd_b3a_0 front.jpg | hm_brd_b3a_0 front
Image:hm_brd_b3a_0 side.jpg | hm_brd_b3a_0 side
Image:hm_brd_b4a_0 front.jpg | hm_brd_b4a_0 front
Image:hm_brd_b4a_0 side.jpg | hm_brd_b4a_0 side
Image:hm_brd_b5a_0 front.jpg | hm_brd_b5a_0 front
Image:hm_brd_b5a_0 side.jpg | hm_brd_b5a_0 side
Image:hm_brd_b6a_0 front.jpg | hm_brd_b6a_0 front
Image:hm_brd_b6a_0 side.jpg | hm_brd_b6a_0 side
</gallery>

=== Human male hairstyles ===

<gallery>
Image:hm_har_blda_0 front.jpg | hm_har_blda_0 front
Image:hm_har_blda_0 side.jpg | hm_har_blda_0 side
Image:hm_har_ha1a_0 front.jpg | hm_har_ha1a_0 front
Image:hm_har_ha1a_0 side.jpg | hm_har_ha1a_0 side
Image:hm_har_ha2a_0 front.jpg | hm_har_ha2a_0 front
Image:hm_har_ha2a_0 side.jpg | hm_har_ha2a_0 side
Image:hm_har_ha3a_0 front.jpg | hm_har_ha3a_0 front
Image:hm_har_ha3a_0 side.jpg | hm_har_ha3a_0 side
Image:hm_har_hb1a_0 front.jpg | hm_har_hb1a_0 front
Image:hm_har_hb1a_0 side.jpg | hm_har_hb1a_0 side
Image:hm_har_hb2a_0 front.jpg | hm_har_hb2a_0 front
Image:hm_har_hb2a_0 side.jpg | hm_har_hb2a_0 side
Image:hm_har_hb3a_0 front.jpg | hm_har_hb3a_0 front
Image:hm_har_hb3a_0 side.jpg | hm_har_hb3a_0 side
Image:hm_har_hb4a_0 front.jpg | hm_har_hb4a_0 front
Image:hm_har_hb4a_0 side.jpg | hm_har_hb4a_0 side
Image:hm_har_hc1a_0 front.jpg | hm_har_hc1a_0 front
Image:hm_har_hc1a_0 side.jpg | hm_har_hc1a_0 side
Image:hm_har_hc2a_0 front.jpg | hm_har_hc2a_0 front
Image:hm_har_hc2a_0 side.jpg | hm_har_hc2a_0 side
Image:hm_har_hc3a_0 front.jpg | hm_har_hc3a_0 front
Image:hm_har_hc3a_0 side.jpg | hm_har_hc3a_0 side
Image:hm_har_hc4a_0 front.jpg | hm_har_hc4a_0 front
Image:hm_har_hc4a_0 side.jpg | hm_har_hc4a_0 side
Image:hm_har_hd1a_0 front.jpg | hm_har_hd1a_0 front
Image:hm_har_hd1a_0 side.jpg | hm_har_hd1a_0 side
Image:hm_har_hd2a_0 front.jpg | hm_har_hd2a_0 front
Image:hm_har_hd2a_0 side.jpg | hm_har_hd2a_0 side
Image:hm_har_hd3a_0 front.jpg | hm_har_hd3a_0 front
Image:hm_har_hd3a_0 side.jpg | hm_har_hd3a_0 side
Image:hm_har_hd4a_0 front.jpg | hm_har_hd4a_0 front
Image:hm_har_hd4a_0 side.jpg | hm_har_hd4a_0 side
</gallery>

=== Eye shadow ===

<gallery>
Image:t1_mue_bk1.jpg | t1_mue_bk1
Image:t1_mue_bk2.jpg | t1_mue_bk2
Image:t1_mue_bk3.jpg | t1_mue_bk3
Image:t1_mue_bl1.jpg | t1_mue_bl1
Image:t1_mue_bl2.jpg | t1_mue_bl2
Image:t1_mue_bl3.jpg | t1_mue_bl3
Image:t1_mue_gn1.jpg | t1_mue_gn1
Image:t1_mue_gn2.jpg | t1_mue_gn2
Image:t1_mue_gn3.jpg | t1_mue_gn3
Image:t1_mue_gr1.jpg | t1_mue_gr1
Image:t1_mue_gr2.jpg | t1_mue_gr2
Image:t1_mue_gr3.jpg | t1_mue_gr3
Image:t1_mue_or1.jpg | t1_mue_or1
Image:t1_mue_or2.jpg | t1_mue_or2
Image:t1_mue_or3.jpg | t1_mue_or3
Image:t1_mue_pi1.jpg | t1_mue_pi1
Image:t1_mue_pi2.jpg | t1_mue_pi2
Image:t1_mue_pi3.jpg | t1_mue_pi3
Image:t1_mue_pu1.jpg | t1_mue_pu1
Image:t1_mue_pu2.jpg | t1_mue_pu2
Image:t1_mue_pu3.jpg | t1_mue_pu3
Image:t1_mue_re1.jpg | t1_mue_re1
Image:t1_mue_re2.jpg | t1_mue_re2
Image:t1_mue_re3.jpg | t1_mue_re3
Image:t1_mue_ro1.jpg | t1_mue_ro1
Image:t1_mue_ro2.jpg | t1_mue_ro2
Image:t1_mue_ro3.jpg | t1_mue_ro3
Image:t1_mue_te1.jpg | t1_mue_te1
Image:t1_mue_te2.jpg | t1_mue_te2
Image:t1_mue_te3.jpg | t1_mue_te3
Image:t1_mue_wh1.jpg | t1_mue_wh1
Image:t1_mue_wh2.jpg | t1_mue_wh2
Image:t1_mue_wh3.jpg | t1_mue_wh3
Image:t1_mue_ye1.jpg | t1_mue_ye1
Image:t1_mue_ye2.jpg | t1_mue_ye2
Image:t1_mue_ye3.jpg | t1_mue_ye3
</gallery>

=== Lip colour ===

<gallery>
Image:t1_mul_bk1.jpg | t1_mul_bk1
Image:t1_mul_bk2.jpg | t1_mul_bk2
Image:t1_mul_bk3.jpg | t1_mul_bk3
Image:t1_mul_pi1.jpg | t1_mul_pi1
Image:t1_mul_pi2.jpg | t1_mul_pi2
Image:t1_mul_pi3.jpg | t1_mul_pi3
Image:t1_mul_pu1.jpg | t1_mul_pu1
Image:t1_mul_pu2.jpg | t1_mul_pu2
Image:t1_mul_pu3.jpg | t1_mul_pu3
Image:t1_mul_re1.jpg | t1_mul_re1
Image:t1_mul_re2.jpg | t1_mul_re2
Image:t1_mul_re3.jpg | t1_mul_re3
Image:t1_mul_ro1.jpg | t1_mul_ro1
Image:t1_mul_ro2.jpg | t1_mul_ro2
Image:t1_mul_ro3.jpg | t1_mul_ro3
Image:t1_mul_ta1.jpg | t1_mul_ta1
Image:t1_mul_ta2.jpg | t1_mul_ta2
Image:t1_mul_ta3.jpg | t1_mul_ta3
Image:t1_mul_te1.jpg | t1_mul_te1
Image:t1_mul_te2.jpg | t1_mul_te2
Image:t1_mul_te3.jpg | t1_mul_te3
Image:t1_mul_wh1.jpg | t1_mul_wh1
Image:t1_mul_wh2.jpg | t1_mul_wh2
Image:t1_mul_wh3.jpg | t1_mul_wh3
</gallery>

=== Skin tone ===

<gallery>
Image:t1_skn_001.jpg | t1_skn_001
Image:t1_skn_002.jpg | t1_skn_002
Image:t1_skn_003.jpg | t1_skn_003
Image:t1_skn_004.jpg | t1_skn_004
Image:t1_skn_005.jpg | t1_skn_005
Image:t1_skn_006.jpg | t1_skn_006
Image:t1_skn_007.jpg | t1_skn_007
Image:t1_skn_blank.jpg| t1_skn_blank
</gallery>

=== Eye colour ===

<gallery>
Image:t3_eye_amb.jpg | t3_eye_amb
Image:t3_eye_blk.jpg | t3_eye_blk
Image:t3_eye_dbl.jpg | t3_eye_dbl
Image:t3_eye_dbr.jpg | t3_eye_dbr
Image:t3_eye_grn.jpg | t3_eye_grn
Image:t3_eye_gry.jpg | t3_eye_gry
Image:t3_eye_hzl.jpg | t3_eye_hzl
Image:t3_eye_ice.jpg | t3_eye_ice
Image:t3_eye_lbl.jpg | t3_eye_lbl
Image:t3_eye_lbr.jpg | t3_eye_lbr
Image:t3_eye_tea.jpg | t3_eye_tea
</gallery>

=== Hair colour ===

<gallery>
Image:t3_har_blk front.jpg|t3_har_blk front
Image:t3_har_blk side.jpg| t3_har_blk side
Image:t3_har_bln front.jpg|t3_har_bln front
Image:t3_har_bln side.jpg| t3_har_bln side
Image:t3_har_dbl front.jpg|t3_har_dbl front
Image:t3_har_dbl side.jpg| t3_har_dbl side
Image:t3_har_dbr front.jpg|t3_har_dbr front
Image:t3_har_dbr side.jpg| t3_har_dbr side
Image:t3_har_gry front.jpg|t3_har_gry front
Image:t3_har_gry side.jpg| t3_har_gry side
Image:t3_har_lbr front.jpg|t3_har_lbr front
Image:t3_har_lbr side.jpg| t3_har_lbr side
Image:t3_har_org front.jpg|t3_har_org front
Image:t3_har_org side.jpg| t3_har_org side
Image:t3_har_rbr front.jpg|t3_har_rbr front
Image:t3_har_rbr side.jpg| t3_har_rbr side
Image:t3_har_red front.jpg|t3_har_red front
Image:t3_har_red side.jpg| t3_har_red side
Image:t3_har_wht front.jpg|t3_har_wht front
Image:t3_har_wht side.jpg| t3_har_wht side
</gallery>

== Blush colour ==

<gallery perrow="3">
Image:T1_mub_bk1.jpg | t1_mub_bk1
Image:T1_mub_bk2.jpg | t1_mub_bk2
Image:T1_mub_bk3.jpg | t1_mub_bk3
Image:T1_mub_br1.jpg | t1_mub_br1
Image:T1_mub_br2.jpg | t1_mub_br2
Image:T1_mub_br3.jpg | t1_mub_br3
Image:T1_mub_or1.jpg | t1_mub_or1
Image:T1_mub_or2.jpg | t1_mub_or2
Image:T1_mub_or3.jpg | t1_mub_or3
Image:T1_mub_pi1.jpg | t1_mub_pi1
Image:T1_mub_pi2.jpg | t1_mub_pi2
Image:T1_mub_pi3.jpg | t1_mub_pi3
Image:T1_mub_pu1.jpg | t1_mub_pu1
Image:T1_mub_pu2.jpg | t1_mub_pu2
Image:T1_mub_pu3.jpg | t1_mub_pu3
Image:T1_mub_re1.jpg | t1_mub_re1
Image:T1_mub_re2.jpg | t1_mub_re2
Image:T1_mub_re3.jpg | t1_mub_re3
Image:T1_mub_ro1.jpg | t1_mub_ro1
Image:T1_mub_ro2.jpg | t1_mub_ro2
Image:T1_mub_ro3.jpg | t1_mub_ro3
Image:T1_mub_ta1.jpg | t1_mub_ta1
Image:T1_mub_ta2.jpg | t1_mub_ta2
Image:T1_mub_ta3.jpg | t1_mub_ta3
Image:T1_mub_te1.jpg | t1_mub_te1
Image:T1_mub_te2.jpg | t1_mub_te2
Image:T1_mub_te3.jpg | t1_mub_te3
Image:T1_mub_wh1.jpg | t1_mub_wh1
Image:T1_mub_wh2.jpg | t1_mub_wh2
Image:T1_mub_wh3.jpg | t1_mub_wh3
</gallery>

== Tattoos ==

{| border="1" cellspacing="0" cellpadding="2"
|-
! Tint file !! Colour
|-
| t1_tat_blk || Black
|-
| t1_tat_dgn || Dark Green
|-
| t1_tat_org || Orange
|-
| t1_tat_blu || Blue
|-
| t1_tat_dpu || Dark Purple
|-
| t1_tat_pnk || Pink
|-
| t1_tat_brn || Brown
|-
| t1_tat_drd || Dark Red
|-
| t1_tat_pur || Purple
|-
| t1_tat_dbl || Dark Blue
|-
| t1_tat_grn || Green
|-
| t1_tat_red || Red
|-
| t1_tat_dbr || Dark Brown
|-
| t1_tat_gry || Grey
|-
| t1_tat_yel || Yellow
|}

You can use a different colour for each Tattoo layer.

You can combine (layer) Tattoos 1 to 4 for each Tattoo mask if desired.

Sliders 0.00 to 1.00 determines darkness of the Tattoo.

All screen shots set at 1.00, black colour

<gallery>
Image:uh tat av1 0t tattoo 1.jpg | uh tat av1 0t tattoo 1
Image:uh tat av1 0t tattoo 2.jpg | uh tat av1 0t tattoo 2
Image:uh tat av1 0t tattoo 3.jpg | uh tat av1 0t tattoo 3
Image:uh tat av1 0t tattoo 4.jpg | uh tat av1 0t tattoo 4
Image:uh tat av2 0t tattoo 1.jpg | uh tat av2 0t tattoo 1
Image:uh tat av2 0t tattoo 2.jpg | uh tat av2 0t tattoo 2
Image:uh tat av2 0t tattoo 3.jpg | uh tat av2 0t tattoo 3
Image:uh tat av2 0t tattoo 4.jpg | uh tat av2 0t tattoo 4
Image:uh tat av3 0t tattoo 1.jpg | uh tat av3 0t tattoo 1
Image:uh tat av3 0t tattoo 2.jpg | uh tat av3 0t tattoo 2
Image:uh tat av3 0t tattoo 3.jpg | uh tat av3 0t tattoo 3
Image:uh tat av3 0t tattoo 4.jpg | uh tat av3 0t tattoo 4
Image:uh tat dw1 0t tattoo 1.jpg | uh tat dw1 0t tattoo 1
Image:uh tat dw1 0t tattoo 2.jpg | uh tat dw1 0t tattoo 2
Image:uh tat dw1 0t tattoo 3.jpg | uh tat dw1 0t tattoo 3
Image:uh tat dw1 0t tattoo 4.jpg | uh tat dw1 0t tattoo 4
Image:uh tat dw2 0t tattoo 1.jpg | uh tat dw2 0t tattoo 1
Image:uh tat dw2 0t tattoo 2.jpg | uh tat dw2 0t tattoo 2
Image:uh tat dw2 0t tattoo 3.jpg | uh tat dw2 0t tattoo 3
Image:uh tat dw2 0t tattoo 4.jpg | uh tat dw2 0t tattoo 4
Image:uh tat ed1 0t tattoo 1.jpg | uh tat ed1 0t tattoo 1
Image:uh tat ed1 0t tattoo 2.jpg | uh tat ed1 0t tattoo 2
Image:uh tat ed1 0t tattoo 3.jpg | uh tat ed1 0t tattoo 3
Image:uh tat ed1 0t tattoo 4.jpg | uh tat ed1 0t tattoo 4
Image:uh tat ed2 0t tattoo 1.jpg | uh tat ed2 0t tattoo 1
Image:uh tat ed2 0t tattoo 2.jpg | uh tat ed2 0t tattoo 2
Image:uh tat ed2 0t tattoo 3.jpg | uh tat ed2 0t tattoo 3
Image:uh tat ed2 0t tattoo 4.jpg | uh tat ed2 0t tattoo 4
Image:uh tat ed3 0t tattoo 1.jpg | uh tat ed3 0t tattoo 1
Image:uh tat ed3 0t tattoo 2.jpg | uh tat ed3 0t tattoo 2
Image:uh tat ed3 0t tattoo 3.jpg | uh tat ed3 0t tattoo 3
Image:uh tat ed3 0t tattoo 4.jpg | uh tat ed3 0t tattoo 4
Image:uh tat ed4 0t tattoo 1.jpg | uh tat ed4 0t tattoo 1
Image:uh tat ed4 0t tattoo 2.jpg | uh tat ed4 0t tattoo 2
Image:uh tat ed4 0t tattoo 3.jpg | uh tat ed4 0t tattoo 3
Image:uh tat ed4 0t tattoo 4.jpg | uh tat ed4 0t tattoo 4
</gallery>

[[Category:Morphs]]

Morph

2010-01-06T01:09:10Z

JackFuzz: /* Beards and facial features */

[[Image:New resource.png|thumb|The new resource menu contains a "Morph" option]]

Morphs are highly customizable heads that can be added to many of the common humanoid creatures in Dragon Age to create unique characters. They are not listed on the palette window; to create a new morph you'll have to go to the "File" menu, select "New", and then select "Morph" from the list of resource types.

A morph must first start with a basic head shape. Select one from the drop-down menu in the toolbar (it defaults to "choose base", indicating the need to select one) and the head will appear in the main display. The camera can be maneuvered around it using many of the same basic controls used elsewhere in the toolset. The head bases that are available include male and female versions of Human, Dwarf, Elf, and a gender-neutral child's head.

Once the base is selected, an enormous number of options will become available in the object inspector for modifying the exact shape and texture of the head. Hairstyles and beards can be added, tattoo textures can be overlaid on the skin, and so forth - there are hundreds of parameters.

To speed the creation of unique generic NPCs, the "randomize" button in the toolbar will set the various shape parameters to random values. This doesn't affect all facial features, however, since many of the adjustable features would look quite bizarre when set to extreme values. Generally the effects of the randomize button are limited to tabs 4 through 8, and it doesn't affect all of the features even on those. Manual customization may still be required to produce a truly diverse crop of NPCs.

Note that for some features (for example, lip color) the opacity defaults to 0%, so you may not see an immediate effect when changing them unless you set the opacity higher first.

[[Image:Morph editor.png|600px|thumb|center]]

== How to override companion & NPC Morphs ==

1. Open toolset

2. '''File''' --> '''Manage Modules''' --> Switch to single player campaign

3. Open the '''"Creatures" palette''' and put the name of the companion or npc in the filter. Example: "alistair"

4. A few tabs open up.... Expand the '''"_Global/Followers"''' folder and you will see alistair's model:

gen00fl_alistair (Alistair)

5. Remove the numbers

genfl_alistair

6. Then add the appropriate prefix.

ef_ = elf female
hm_ = human male
hf_ = human female
em_ = elf male
dm_ = dwarf male
df_ = dwarf female

7. So you would rename your morph:

hm_genfl_alistair.mor

8. Then place it into the folder:

\\\\Documents\\\\BioWare\\\\Dragon Age\\\\modules\\\\Single Player\\\\override

Examples:

Alistair: hm_genfl_alistair.mor
Morrigan: hf_genfl_morrigan.mor
Gheyna: ef_ntb100_gheyna.mor

== Beards and facial features ==

There are two basic types of beards available for facial morphs; model beards and stubble beards. Stubble beards are simply a texture overlay, and have no particular special effects associated with them. Model beards are three-dimensional objects that are affixed to the face, and it is important to be aware of certain limitations that come with using them.

In order to make a physical beard model fit properly onto the face, some facial features must be set to their default values. This is so that, as an example, one doesn't wind up with the tip of the chin poking out through the end of the beard. When you add a physical beard model to a head morph these specific facial features are automatically snapped to their default values and are locked there for as long as the beard is in place. If the beard is removed they become editable again, but it is important to note that they do ''not'' return to whatever values they had before the beard was added. So make the decision on whether a character has a physical beard before you spend a lot of time adjusting his jawline and other such details.

== Debug features ==

There are a number of features with "debug" in their names that are intended only to allow a facial artist to get a better view of certain parts of a facial morph, and if they are set to anything other than zero the morph won't be usable by the rest of the toolset. The most obvious example is the "teeth debug" parameter, which pulls the lips back to expose the model's teeth so that they can be adjusted in plain view.

== How to use a morph in your module ==

Morph is an art tool, not a design tool, and so it uses a somewhat different mechanism for making its output available to the designer than the other tools that come with the toolset. You can save a morph as a file in your regular filesystem but when you go to select a head morph in the creature designer you won't be able to import directly from the filesystem to use it.

Instead, you need to export the morph via the "post to local" command under the "Tools"->"Export" menu (alternately, right-click on the morph's display window and select "post to local" from the menu). Once the morph has been exported, it will be available in the creature creator's morph list when the appropriate body appearance model is selected (eg, a human female head morph is usable with a human female body appearance).

If you want to make a slight variation on an existing morph (say for example to change the hair colour or add a scar), load the mrh file of the desired morph, and then 'save as' with a new file name. Make your changes and save, then once again export to local. To make the new variant available, use "View"->"Refresh".

== How to replace the morph of an in game NPC (Single Player Campaign) ==

1. Open Toolset

2. Click the "Creatures" Button on the top right Palette Window

3. In the filter type the name of the NPC, example Bella or Desire or Murdock.

4. You'll see some folders appear. Navigate through them and find the NPC object:

Example: ntb100cr_gheyna (Gheyna)

5. Now left click that creature to highlight it.

6. On the bottom right the object inspector window appears full of information.

7. Scroll down the list until you see head morph, under appearance. Note the name of that file.

8. Rename the new morph file you exported to the name in the object inspector.

9. Now place your new morph in the following directory:

documents/bioware/dragon age/packages/core/override

Make sure you restart dragon age.

== Morph files ==

There are actually two files for every morph.
*.mrh - This is the source file for the morph data and can be saved anywhere and loaded from anywhere.
*.mor - This is the generated/processed binarized gff file that the game uses. You can change these in the toolset but it's not recommended.

To get the *.mor file you need to use the "export" command.

To edit an existing .mrh, you can either drag and drop the .mrh into the toolset or open the *.mrh from the toolset.

The head morph tool concatenates the two letter prefix (HM for human male, HF for human female, etc.) to the filename for you. If you saved a resource called "myhead", for example, and it was a human male then it would export a hm_myhead.mor. If it was a female dwarf it would save it as df_myhead.mor

The drop down for the head morph will also auto generate the two letter prefix based on the gender and appearance of the creature you are making.

== Deleting a morph ==

Morphs are an art asset, and as such are not stored in the database in the same manner as other resources. You can find morph files (.mor extension) in the \Dragon Age\packages\core\override\toolsetexport directory, to remove one simply delete it.

== Parameters ==

{{sidebox|
* Keep in mind that when selecting colors, you can open up a dropdown list where you browse for colors, and choose "All Tint Files *.tnt" to get a much wider range of color choices. The Tattoo colors especially (t1_tat_*) are very vibrant, and can give you 'very blue eyes', for example.
}}

Choose Base model name:

*HM_UHM_BASE - Human Male
*HF_UHM_BASE - Human Female
*DM_UHM_BASE - Dwarven Male
*DF_UHM_BASE - Dwarven Female
*EM_UHM_BASE - Elven Male
*EF_UHM_BASE - Elven Female
*QM_UHM_BASE - Qunari Male
*QF_UHM_BASE - Qunari Female
*KN_UHM_BASE - Child

*(Opacity 0.00 least color - 1.00 full color)
*(Anything 0.00 to 1.00 or -1.00 to 1.00 is a slider)
*(Left and Right = Left and Right of Morph Face not Left and Right as you look at the face.)

01. MATERIAL:

01. Face:

*Skin Color: 8 choices
*Lip Makeup Color: 27 choices
*Lip Makeup Opacity: 0.00 - 1.00
*Blush Makeup Color: 30 choices
*Blush Makeup Opacity: 0.00 - 1.00
*Eye Makeup Color: 36 choices
*Eye Makeup Opacity: 0.00 - 1.00

02. Skin Texture:

*Base Skin Texture: 12 choices
*Blend Skin Texture: 12 choices
*Blend Right Eye: 0.00 - 1.00
*Blend Left Eye: 0.00 - 1.00
*Blend Right Cheek: 0.00 - 1.00
*Blend Left Cheek: 0.00 - 1.00
*Blend Left Forehead: 0.00 - 1.00
*Blend Right Forehead: 0.00 - 1.00
*Blend Nose: 0.00 - 1.00
*Blend Middle Forehead: 0.00 - 1.00
*Blend All Override: 0.00 - 1.00

03. Skin Type:

*Blend Right Eye: 0.00 - 1.00
*Blend Left Eye: 0.00 - 1.00
*Blend Right Cheek: 0.00 - 1.00
*Blend Left Cheek: 0.00 - 1.00
*Blend Left Forehead: 0.00 - 1.00
*Blend Right Forehead: 0.00 - 1.00
*Blend Nose: 0.00 - 1.00
*Blend Middle Forehead: 0.00 - 1.00
*Blend All Override: 0.00 - 1.00

02. PART SELECTION:

1. Model: (Base model Chosen when starting.)

2. Parts:

*Eye Color: 11 choices
*Eyes: 2 choices
*Eye Texture: 16 choices
*Hair and Beard Color: 10 choices
*Hair: 17 choices
*Beard: 7 choices
*Eye Lashes: 1 choice
*Lashes Texture: 4 choices

3. Tattoo:

*Tattoo Mask: 14 choices
*Tattoo Channel 1 Color: 15 choices
*Tattoo 1 : R Channel: 0.00 - 1.00
*Tattoo Channel 2 Color: 15 choices
*Tattoo 2 : G Channel: 0.00 - 1.00
*Tattoo Channel 3 Color: 15 choices
*Tattoo 3 : B Channel: 0.00 - 1.00
*Tattoo Channel 4 Color: 15 choices
*Tattoo 4 : A Channel: 0.00 - 1.00

4. Brow and Stubble:

*Brow and Stubble Colors: 10 choices
*Bushy Eyebrows: 0.00 - 1.00 (only available if regular eyebrows set to 0.00)
*Regular Eyebrows: 0.00 - 1.00
*Thick Eyebrows: 0.00 - 1.00 (only available if regular eyebrows set to 0.00)
*Thinned Eyebrows: 0.00 - 1.00 (only available if regular eyebrows set to 0.00)
*Goatee: 0.00 - 1.00
*Soul Patch: 0.00 - 1.00
*Mustache: 0.00 - 1.00
*Pork Chops: 0.00 - 1.00

5. Crew Cut Selection:

*Sheppard: 0.00 - 1.00
*Receeding Hairline: 0.00 - 1.00
*Balding Hairline: 0.00 - 1.00

03. FEATURE SELECTION:

01. Shape:

*Head Shape 01: 0.00 - 1.00
*Head Shape 02: 0.00 - 1.00
*Head Shape 03: 0.00 - 1.00
*Head Shape Fat: 0.00 - 1.00
*Head Shape Thick: 0.00 - 1.00
*Head Shape Thin: 0.00 - 1.00
*(You can only choose to adjust one of these shapes.)

02. Nose:

*Eastern Nose: 0.00 - 1.00
*Flat Nose: 0.00 - 1.00
*Long Nose: 0.00 - 1.00
*Pig Nose: 0.00 - 1.00
*Straight Nose: 0.00 - 1.00
*Thick Nose: 0.00 - 1.00
*(You can only choose to adjust one of these shapes.)

03. Eye Shape:

*Eye Shape 01: 0.00 - 1.00
*Eye Shape 02: 0.00 - 1.00
*Eye Shape 02: 0.00 - 1.00
*Eye Shape 04: 0.00 - 1.00
*(You can only choose to adjust one of these shapes.)

04. Universal Shapes:

*Shape Chubby: 0.00 - 1.00
*Shape Skinny: 0.00 - 1.00
*(You can adjust both of these.)

Reset
*(Left clicking in box to right resets all selections to 0.00)

04. NOSE:

01. Targets:

*Nose Bend Left/Right: -1.00 - 1.00
*Nose Bridge In/Out: -1.00 - 1.00
*Nose Bridge Thin/Wide: -1.00 - 1.00
*Nose Up/Down: -1.00 - 1.00
*Nose Out/In: -1.00 - 1.00
*Nose Smaller/Larger: -1.00 - 1.00
*Nose Tip Up/Down: -1.00 - 1.00
*Nose Tip Out/In: -1.00 - 1.00
*Nostrils Narrow/Wide: -1.00 - 1.00

02. Shape:

*Nose Shape 1: 0.00 - 1.00
*Nose Shape 2: 0.00 - 1.00
*Nose Shape 3: 0.00 - 1.00
*Nose Shape 4: 0.00 - 1.00
*Nose Shape 5: 0.00 - 1.00
*Nose Shape 6: 0.00 - 1.00
*(You can choose to adjust any or all of these.)

Reset
*(Left clicking in box to right resets all selections to 0.00)

05. MOUTH:

01. Targets:

*Mouth Back/Forward: -1.00 - 1.00
*Mouth Corner Up/Down: -1.00 - 1.00
*Mouth Up/Down: -1.00 - 1.00
*Mouth Lips Fat/Thin: -1.00 - 1.00
*Mouth Lower Lip Fat: 0.00 - 1.00
*Mouth Lower Lip Up: 0.00 - 1.00
*Mouth Narrow/Wide: -1.00 - 1.00
*Mouth Over/Underbite: -1.00 - 1.00
*Mouth Upper Lip Down: 0.00 - 1.00
*Mouth Upper Lip Fat: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

06. EYES:

01. Targets:

*Eye Bags: 0.00 - 1.00
*Eye Brow Back/Forward: -1.00 - 1.00
*Eye Brow Down/Up: -1.00 - 1.00
*Eye Narrow/Wide: -1.00 - 1.00
*Eye Position Down/Up: -1.00 - 1.00
*Eyelash Fan: 0.00 - 1.00
*Eyelash Length: 0.00 - 1.00
*Eyes Back/Forward: -1.00 - 1.00
*Eyes Larger: 0.00 - 1.00
*Eyes Small: 0.00 - 1.00
*Eyes Squint: 0.00 - 1.00

02. Debug

Debug Cornea Larger/Smaller: -1.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

07. CHEEKS:

01. Targets:

*Cheeks Back/Forward: -1.00 - 1.00
*Cheeks Bones In/Out: -1.00 - 1.00
*Cheeks Gaunt: 0.00 - 1.00
*Cheeks Lower: 0.00 - 1.00
*Cheeks Up: 0.00 - 1.00
*Cheeks Wide: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

08. JAW:

01. Targets:

*Jaw Chin Down/Up: -1.00 - 1.00
*Jaw Chin In/Out: -1.00 - 1.00
*Jaw Chin Thin/Wide: -1.00 - 1.00
*Jaw Lower: 0.00 - 1.00
*Jaw Narrow/Wide: -1.00 - 1.00
*Jaw Square Shape: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

10. TEETH:

01. Targets:

*TeethChippedtoothLeft: 0.00 - 1.00
*TeethChippedtoothRight: 0.00 - 1.00
*TeethMissingLeft: 0.00 - 1.00
*TeethNoFront: 0.00 - 1.00
*Teeth Back/Forward: -1.00 - 1.00
*Teeth Close/Separate: -1.00 - 1.00
*Teeth Down/Up: -1.00 - 1.00

02. Debug:

*Teeth Wide/Narrow: -1.00 - 1.00
*Teeth Debug: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

11. EARS:

01. Targets:

*Ears Down/Up: -1.00 - 1.00
*Ears In/Out: -1.00 - 1.00
*Ears Large/Small: -1.00 - 1.00
*Ears Rotate Outwards: 0.00 - 1.00
*Ears Wide/Narrow: -1.00 - 1.00

02. Debug:

Ears Debug for Hair Crashing: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

12. NECK:

01. Targets:

*NeckApple: 0.00 - 1.00
*NeckThin: 0.00 - 1.00
*Neck Back: 0.00 - 1.00
*Neck Wide: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

13. BROWS:

01. Targets:

*Brow Down/Up: -1.00 - 1.00
*Forehead Out/In: -1.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

13. VIEW SETTINGS:

1. Light:

*Light Model: 6 choices
*Light Probe: 4 choices

2. Camera:

*Distance: Numeric
*Orientation: 3 coordinates
*Position: 3 coordinates

3. Object:

*Orientation: 3 coordinates
*Position: 3 coordinates

4. Facial Animation:

*FA name: Blank
*FA set: 5 choices

14. EXPORT SETTINGS

General:

Export .mop file: True/False (False default)

14. UNIQUE SHAPES:

01. Targets:

*Fat Man: 0.00 - 1.00
*Shape Alistair: 0.00 - 1.00
*Shape Daveth: 0.00 - 1.00
*Shape Duncan: 0.00 - 1.00
*Shape Jory: 0.00 - 1.00
*Shape King Cailan: 0.00 - 1.00
*Shape Loghain: 0.00 - 1.00
*Shape Old Male: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

== Tints and hairstyles ==

Tints and hairstyles often have somewhat uninformative names. The following thumbnails provide a preview summary of what these tints and hairstyles represent:

=== Dwarf male beards ===

<gallery>
Image:dm_brd_b1a_0 front.jpg | dm_brd_b1a_0 front
Image:dm_brd_b1a_0 side.jpg | dm_brd_b1a_0 side
Image:dm_brd_b2a_0 front.jpg | dm_brd_b2a_0 front
Image:dm_brd_b2a_0 side.jpg | dm_brd_b2a_0 side
Image:dm_brd_b3a_0 front.jpg | dm_brd_b3a_0 front
Image:dm_brd_b3a_0 side.jpg | dm_brd_b3a_0 side
Image:dm_brd_b4a_0 front.jpg | dm_brd_b4a_0 front
Image:dm_brd_b4a_0 side.jpg | dm_brd_b4a_0 side
Image:dm_brd_b5a_0 front.jpg | dm_brd_b5a_0 front
Image:dm_brd_b5a_0 side.jpg | dm_brd_b5a_0 side
Image:dm_brd_b6a_0 front.jpg | dm_brd_b6a_0 front
Image:dm_brd_b6a_0 side.jpg | dm_brd_b6a_0 side
Image:dm_brd_b7a_0 front.jpg | dm_brd_b7a_0 front
Image:dm_brd_b7a_0 side.jpg | dm_brd_b7a_0 side
</gallery>

=== Human female hairstyles ===

<gallery>
Image:hf_har_blda_0 front.jpg |hf_har_blda_0 front
Image:hf_har_blda_0 side.jpg | hf_har_blda_0 side
Image:hf_har_ha1a_0 front.jpg |hf_har_ha1a_0 front
Image:hf_har_ha1a_0 side.jpg | hf_har_ha1a_0 side
Image:hf_har_ha2a_0 front.jpg |hf_har_ha2a_0 front
Image:hf_har_ha2a_0 side.jpg | hf_har_ha2a_0 side
Image:hf_har_ha3a_0 front.jpg |hf_har_ha3a_0 front
Image:hf_har_ha3a_0 side.jpg | hf_har_ha3a_0 side
Image:hf_har_ha4a_0 front.jpg |hf_har_ha4a_0 front
Image:hf_har_ha4a_0 side.jpg | hf_har_ha4a_0 side
Image:hf_har_hb1a_0 front.jpg |hf_har_hb1a_0 front
Image:hf_har_hb1a_0 side.jpg | hf_har_hb1a_0 side
Image:hf_har_hb2a_0 front.jpg |hf_har_hb2a_0 front
Image:hf_har_hb2a_0 side.jpg | hf_har_hb2a_0 side
Image:hf_har_hb3a_0 front.jpg |hf_har_hb3a_0 front
Image:hf_har_hb3a_0 side.jpg | hf_har_hb3a_0 side
Image:hf_har_hb4a_0 front.jpg |hf_har_hb4a_0 front
Image:hf_har_hb4a_0 side.jpg | hf_har_hb4a_0 side
Image:hf_har_hc1a_0 front.jpg |hf_har_hc1a_0 front
Image:hf_har_hc1a_0 side.jpg | hf_har_hc1a_0 side
Image:hf_har_hc2a_0 front.jpg |hf_har_hc2a_0 front
Image:hf_har_hc2a_0 side.jpg | hf_har_hc2a_0 side
Image:hf_har_hc3a_0 front.jpg |hf_har_hc3a_0 front
Image:hf_har_hc3a_0 side.jpg | hf_har_hc3a_0 side
Image:hf_har_hc4a_0 front.jpg |hf_har_hc4a_0 front
Image:hf_har_hc4a_0 side.jpg | hf_har_hc4a_0 side
Image:hf_har_hd1a_0 front.jpg |hf_har_hd1a_0 front
Image:hf_har_hd1a_0 side.jpg | hf_har_hd1a_0 side
Image:hf_har_hd2a_0 front.jpg |hf_har_hd2a_0 front
Image:hf_har_hd2a_0 side.jpg | hf_har_hd2a_0 side
Image:hf_har_hd3a_0 front.jpg |hf_har_hd3a_0 front
Image:hf_har_hd3a_0 side.jpg | hf_har_hd3a_0 side
Image:hf_har_hd4a_0 front.jpg |hf_har_hd4a_0 front
Image:hf_har_hd4a_0 side.jpg | hf_har_hd4a_0 side
</gallery>

=== Human male beards ===

<gallery>
Image:hm_brd_b1a_0 front.jpg | hm_brd_b1a_0 front
Image:hm_brd_b1a_0 side.jpg | hm_brd_b1a_0 side
Image:hm_brd_b2a_0 front.jpg | hm_brd_b2a_0 front
Image:hm_brd_b2a_0 side.jpg | hm_brd_b2a_0 side
Image:hm_brd_b3a_0 front.jpg | hm_brd_b3a_0 front
Image:hm_brd_b3a_0 side.jpg | hm_brd_b3a_0 side
Image:hm_brd_b4a_0 front.jpg | hm_brd_b4a_0 front
Image:hm_brd_b4a_0 side.jpg | hm_brd_b4a_0 side
Image:hm_brd_b5a_0 front.jpg | hm_brd_b5a_0 front
Image:hm_brd_b5a_0 side.jpg | hm_brd_b5a_0 side
Image:hm_brd_b6a_0 front.jpg | hm_brd_b6a_0 front
Image:hm_brd_b6a_0 side.jpg | hm_brd_b6a_0 side
</gallery>

=== Human male hairstyles ===

<gallery>
Image:hm_har_blda_0 front.jpg | hm_har_blda_0 front
Image:hm_har_blda_0 side.jpg | hm_har_blda_0 side
Image:hm_har_ha1a_0 front.jpg | hm_har_ha1a_0 front
Image:hm_har_ha1a_0 side.jpg | hm_har_ha1a_0 side
Image:hm_har_ha2a_0 front.jpg | hm_har_ha2a_0 front
Image:hm_har_ha2a_0 side.jpg | hm_har_ha2a_0 side
Image:hm_har_ha3a_0 front.jpg | hm_har_ha3a_0 front
Image:hm_har_ha3a_0 side.jpg | hm_har_ha3a_0 side
Image:hm_har_hb1a_0 front.jpg | hm_har_hb1a_0 front
Image:hm_har_hb1a_0 side.jpg | hm_har_hb1a_0 side
Image:hm_har_hb2a_0 front.jpg | hm_har_hb2a_0 front
Image:hm_har_hb2a_0 side.jpg | hm_har_hb2a_0 side
Image:hm_har_hb3a_0 front.jpg | hm_har_hb3a_0 front
Image:hm_har_hb3a_0 side.jpg | hm_har_hb3a_0 side
Image:hm_har_hb4a_0 front.jpg | hm_har_hb4a_0 front
Image:hm_har_hb4a_0 side.jpg | hm_har_hb4a_0 side
Image:hm_har_hc1a_0 front.jpg | hm_har_hc1a_0 front
Image:hm_har_hc1a_0 side.jpg | hm_har_hc1a_0 side
Image:hm_har_hc2a_0 front.jpg | hm_har_hc2a_0 front
Image:hm_har_hc2a_0 side.jpg | hm_har_hc2a_0 side
Image:hm_har_hc3a_0 front.jpg | hm_har_hc3a_0 front
Image:hm_har_hc3a_0 side.jpg | hm_har_hc3a_0 side
Image:hm_har_hc4a_0 front.jpg | hm_har_hc4a_0 front
Image:hm_har_hc4a_0 side.jpg | hm_har_hc4a_0 side
Image:hm_har_hd1a_0 front.jpg | hm_har_hd1a_0 front
Image:hm_har_hd1a_0 side.jpg | hm_har_hd1a_0 side
Image:hm_har_hd2a_0 front.jpg | hm_har_hd2a_0 front
Image:hm_har_hd2a_0 side.jpg | hm_har_hd2a_0 side
Image:hm_har_hd3a_0 front.jpg | hm_har_hd3a_0 front
Image:hm_har_hd3a_0 side.jpg | hm_har_hd3a_0 side
Image:hm_har_hd4a_0 front.jpg | hm_har_hd4a_0 front
Image:hm_har_hd4a_0 side.jpg | hm_har_hd4a_0 side
</gallery>

=== Eye shadow ===

<gallery>
Image:t1_mue_bk1.jpg | t1_mue_bk1
Image:t1_mue_bk2.jpg | t1_mue_bk2
Image:t1_mue_bk3.jpg | t1_mue_bk3
Image:t1_mue_bl1.jpg | t1_mue_bl1
Image:t1_mue_bl2.jpg | t1_mue_bl2
Image:t1_mue_bl3.jpg | t1_mue_bl3
Image:t1_mue_gn1.jpg | t1_mue_gn1
Image:t1_mue_gn2.jpg | t1_mue_gn2
Image:t1_mue_gn3.jpg | t1_mue_gn3
Image:t1_mue_gr1.jpg | t1_mue_gr1
Image:t1_mue_gr2.jpg | t1_mue_gr2
Image:t1_mue_gr3.jpg | t1_mue_gr3
Image:t1_mue_or1.jpg | t1_mue_or1
Image:t1_mue_or2.jpg | t1_mue_or2
Image:t1_mue_or3.jpg | t1_mue_or3
Image:t1_mue_pi1.jpg | t1_mue_pi1
Image:t1_mue_pi2.jpg | t1_mue_pi2
Image:t1_mue_pi3.jpg | t1_mue_pi3
Image:t1_mue_pu1.jpg | t1_mue_pu1
Image:t1_mue_pu2.jpg | t1_mue_pu2
Image:t1_mue_pu3.jpg | t1_mue_pu3
Image:t1_mue_re1.jpg | t1_mue_re1
Image:t1_mue_re2.jpg | t1_mue_re2
Image:t1_mue_re3.jpg | t1_mue_re3
Image:t1_mue_ro1.jpg | t1_mue_ro1
Image:t1_mue_ro2.jpg | t1_mue_ro2
Image:t1_mue_ro3.jpg | t1_mue_ro3
Image:t1_mue_te1.jpg | t1_mue_te1
Image:t1_mue_te2.jpg | t1_mue_te2
Image:t1_mue_te3.jpg | t1_mue_te3
Image:t1_mue_wh1.jpg | t1_mue_wh1
Image:t1_mue_wh2.jpg | t1_mue_wh2
Image:t1_mue_wh3.jpg | t1_mue_wh3
Image:t1_mue_ye1.jpg | t1_mue_ye1
Image:t1_mue_ye2.jpg | t1_mue_ye2
Image:t1_mue_ye3.jpg | t1_mue_ye3
</gallery>

=== Lip colour ===

<gallery>
Image:t1_mul_bk1.jpg | t1_mul_bk1
Image:t1_mul_bk2.jpg | t1_mul_bk2
Image:t1_mul_bk3.jpg | t1_mul_bk3
Image:t1_mul_pi1.jpg | t1_mul_pi1
Image:t1_mul_pi2.jpg | t1_mul_pi2
Image:t1_mul_pi3.jpg | t1_mul_pi3
Image:t1_mul_pu1.jpg | t1_mul_pu1
Image:t1_mul_pu2.jpg | t1_mul_pu2
Image:t1_mul_pu3.jpg | t1_mul_pu3
Image:t1_mul_re1.jpg | t1_mul_re1
Image:t1_mul_re2.jpg | t1_mul_re2
Image:t1_mul_re3.jpg | t1_mul_re3
Image:t1_mul_ro1.jpg | t1_mul_ro1
Image:t1_mul_ro2.jpg | t1_mul_ro2
Image:t1_mul_ro3.jpg | t1_mul_ro3
Image:t1_mul_ta1.jpg | t1_mul_ta1
Image:t1_mul_ta2.jpg | t1_mul_ta2
Image:t1_mul_ta3.jpg | t1_mul_ta3
Image:t1_mul_te1.jpg | t1_mul_te1
Image:t1_mul_te2.jpg | t1_mul_te2
Image:t1_mul_te3.jpg | t1_mul_te3
Image:t1_mul_wh1.jpg | t1_mul_wh1
Image:t1_mul_wh2.jpg | t1_mul_wh2
Image:t1_mul_wh3.jpg | t1_mul_wh3
</gallery>

=== Skin tone ===

<gallery>
Image:t1_skn_001.jpg | t1_skn_001
Image:t1_skn_002.jpg | t1_skn_002
Image:t1_skn_003.jpg | t1_skn_003
Image:t1_skn_004.jpg | t1_skn_004
Image:t1_skn_005.jpg | t1_skn_005
Image:t1_skn_006.jpg | t1_skn_006
Image:t1_skn_007.jpg | t1_skn_007
Image:t1_skn_blank.jpg| t1_skn_blank
</gallery>

=== Eye colour ===

<gallery>
Image:t3_eye_amb.jpg | t3_eye_amb
Image:t3_eye_blk.jpg | t3_eye_blk
Image:t3_eye_dbl.jpg | t3_eye_dbl
Image:t3_eye_dbr.jpg | t3_eye_dbr
Image:t3_eye_grn.jpg | t3_eye_grn
Image:t3_eye_gry.jpg | t3_eye_gry
Image:t3_eye_hzl.jpg | t3_eye_hzl
Image:t3_eye_ice.jpg | t3_eye_ice
Image:t3_eye_lbl.jpg | t3_eye_lbl
Image:t3_eye_lbr.jpg | t3_eye_lbr
Image:t3_eye_tea.jpg | t3_eye_tea
</gallery>

=== Hair colour ===

<gallery>
Image:t3_har_blk front.jpg|t3_har_blk front
Image:t3_har_blk side.jpg| t3_har_blk side
Image:t3_har_bln front.jpg|t3_har_bln front
Image:t3_har_bln side.jpg| t3_har_bln side
Image:t3_har_dbl front.jpg|t3_har_dbl front
Image:t3_har_dbl side.jpg| t3_har_dbl side
Image:t3_har_dbr front.jpg|t3_har_dbr front
Image:t3_har_dbr side.jpg| t3_har_dbr side
Image:t3_har_gry front.jpg|t3_har_gry front
Image:t3_har_gry side.jpg| t3_har_gry side
Image:t3_har_lbr front.jpg|t3_har_lbr front
Image:t3_har_lbr side.jpg| t3_har_lbr side
Image:t3_har_org front.jpg|t3_har_org front
Image:t3_har_org side.jpg| t3_har_org side
Image:t3_har_rbr front.jpg|t3_har_rbr front
Image:t3_har_rbr side.jpg| t3_har_rbr side
Image:t3_har_red front.jpg|t3_har_red front
Image:t3_har_red side.jpg| t3_har_red side
Image:t3_har_wht front.jpg|t3_har_wht front
Image:t3_har_wht side.jpg| t3_har_wht side
</gallery>

== Blush colour ==

<gallery perrow="3">
Image:T1_mub_bk1.jpg | t1_mub_bk1
Image:T1_mub_bk2.jpg | t1_mub_bk2
Image:T1_mub_bk3.jpg | t1_mub_bk3
Image:T1_mub_br1.jpg | t1_mub_br1
Image:T1_mub_br2.jpg | t1_mub_br2
Image:T1_mub_br3.jpg | t1_mub_br3
Image:T1_mub_or1.jpg | t1_mub_or1
Image:T1_mub_or2.jpg | t1_mub_or2
Image:T1_mub_or3.jpg | t1_mub_or3
Image:T1_mub_pi1.jpg | t1_mub_pi1
Image:T1_mub_pi2.jpg | t1_mub_pi2
Image:T1_mub_pi3.jpg | t1_mub_pi3
Image:T1_mub_pu1.jpg | t1_mub_pu1
Image:T1_mub_pu2.jpg | t1_mub_pu2
Image:T1_mub_pu3.jpg | t1_mub_pu3
Image:T1_mub_re1.jpg | t1_mub_re1
Image:T1_mub_re2.jpg | t1_mub_re2
Image:T1_mub_re3.jpg | t1_mub_re3
Image:T1_mub_ro1.jpg | t1_mub_ro1
Image:T1_mub_ro2.jpg | t1_mub_ro2
Image:T1_mub_ro3.jpg | t1_mub_ro3
Image:T1_mub_ta1.jpg | t1_mub_ta1
Image:T1_mub_ta2.jpg | t1_mub_ta2
Image:T1_mub_ta3.jpg | t1_mub_ta3
Image:T1_mub_te1.jpg | t1_mub_te1
Image:T1_mub_te2.jpg | t1_mub_te2
Image:T1_mub_te3.jpg | t1_mub_te3
Image:T1_mub_wh1.jpg | t1_mub_wh1
Image:T1_mub_wh2.jpg | t1_mub_wh2
Image:T1_mub_wh3.jpg | t1_mub_wh3
</gallery>

== Tattoos ==

{| border="1" cellspacing="0" cellpadding="2"
|-
! Tint file !! Colour
|-
| t1_tat_blk || Black
|-
| t1_tat_dgn || Dark Green
|-
| t1_tat_org || Orange
|-
| t1_tat_blu || Blue
|-
| t1_tat_dpu || Dark Purple
|-
| t1_tat_pnk || Pink
|-
| t1_tat_brn || Brown
|-
| t1_tat_drd || Dark Red
|-
| t1_tat_pur || Purple
|-
| t1_tat_dbl || Dark Blue
|-
| t1_tat_grn || Green
|-
| t1_tat_red || Red
|-
| t1_tat_dbr || Dark Brown
|-
| t1_tat_gry || Grey
|-
| t1_tat_yel || Yellow
|}

You can use a different colour for each Tattoo layer.

You can combine (layer) Tattoos 1 to 4 for each Tattoo mask if desired.

Sliders 0.00 to 1.00 determines darkness of the Tattoo.

All screen shots set at 1.00, black colour

<gallery>
Image:uh tat av1 0t tattoo 1.jpg | uh tat av1 0t tattoo 1
Image:uh tat av1 0t tattoo 2.jpg | uh tat av1 0t tattoo 2
Image:uh tat av1 0t tattoo 3.jpg | uh tat av1 0t tattoo 3
Image:uh tat av1 0t tattoo 4.jpg | uh tat av1 0t tattoo 4
Image:uh tat av2 0t tattoo 1.jpg | uh tat av2 0t tattoo 1
Image:uh tat av2 0t tattoo 2.jpg | uh tat av2 0t tattoo 2
Image:uh tat av2 0t tattoo 3.jpg | uh tat av2 0t tattoo 3
Image:uh tat av2 0t tattoo 4.jpg | uh tat av2 0t tattoo 4
Image:uh tat av3 0t tattoo 1.jpg | uh tat av3 0t tattoo 1
Image:uh tat av3 0t tattoo 2.jpg | uh tat av3 0t tattoo 2
Image:uh tat av3 0t tattoo 3.jpg | uh tat av3 0t tattoo 3
Image:uh tat av3 0t tattoo 4.jpg | uh tat av3 0t tattoo 4
Image:uh tat dw1 0t tattoo 1.jpg | uh tat dw1 0t tattoo 1
Image:uh tat dw1 0t tattoo 2.jpg | uh tat dw1 0t tattoo 2
Image:uh tat dw1 0t tattoo 3.jpg | uh tat dw1 0t tattoo 3
Image:uh tat dw1 0t tattoo 4.jpg | uh tat dw1 0t tattoo 4
Image:uh tat dw2 0t tattoo 1.jpg | uh tat dw2 0t tattoo 1
Image:uh tat dw2 0t tattoo 2.jpg | uh tat dw2 0t tattoo 2
Image:uh tat dw2 0t tattoo 3.jpg | uh tat dw2 0t tattoo 3
Image:uh tat dw2 0t tattoo 4.jpg | uh tat dw2 0t tattoo 4
Image:uh tat ed1 0t tattoo 1.jpg | uh tat ed1 0t tattoo 1
Image:uh tat ed1 0t tattoo 2.jpg | uh tat ed1 0t tattoo 2
Image:uh tat ed1 0t tattoo 3.jpg | uh tat ed1 0t tattoo 3
Image:uh tat ed1 0t tattoo 4.jpg | uh tat ed1 0t tattoo 4
Image:uh tat ed2 0t tattoo 1.jpg | uh tat ed2 0t tattoo 1
Image:uh tat ed2 0t tattoo 2.jpg | uh tat ed2 0t tattoo 2
Image:uh tat ed2 0t tattoo 3.jpg | uh tat ed2 0t tattoo 3
Image:uh tat ed2 0t tattoo 4.jpg | uh tat ed2 0t tattoo 4
Image:uh tat ed3 0t tattoo 1.jpg | uh tat ed3 0t tattoo 1
Image:uh tat ed3 0t tattoo 2.jpg | uh tat ed3 0t tattoo 2
Image:uh tat ed3 0t tattoo 3.jpg | uh tat ed3 0t tattoo 3
Image:uh tat ed3 0t tattoo 4.jpg | uh tat ed3 0t tattoo 4
Image:uh tat ed4 0t tattoo 1.jpg | uh tat ed4 0t tattoo 1
Image:uh tat ed4 0t tattoo 2.jpg | uh tat ed4 0t tattoo 2
Image:uh tat ed4 0t tattoo 3.jpg | uh tat ed4 0t tattoo 3
Image:uh tat ed4 0t tattoo 4.jpg | uh tat ed4 0t tattoo 4
</gallery>

[[Category:Morphs]]

User talk:JackFuzz

2009-12-30T08:11:08Z

JackFuzz: /* Morph Edit */

==Morph Edit==
Hello, I just have a question pertaining to your edit on the [[Morph]] page with the subhead "How to replace the morph of an in game NPC (Single Player Campaign)". When I access the creatures and try to find an NPC, there are none. All I can find are monsters and a few "test" NPC's, but none that are actually in the game. Is there an extra resource source that includes NPC's and the companions? I cannot find them anywhere in the Toolset.

Thanks for any help. --[[User:Tricause|Tricause]] 01:44, 30 December 2009 (UTC)

1. Make sure you have version 1.0.1008.0 installed

2. File --> Manage Modules --> Switch to "Single Player" then click "open"

3. Now try my tutorial.

Morph

2009-12-28T03:23:23Z

JackFuzz: /* How to use a morph in your module */

[[Image:New resource.png|thumb|The new resource menu contains a "Morph" option]]

Morphs are highly customizable heads that can be added to many of the common humanoid creatures in Dragon Age to create unique characters. They are not listed on the palette window; to create a new morph you'll have to go to the "File" menu, select "New", and then select "Morph" from the list of resource types.

A morph must first start with a basic head shape. Select one from the drop-down menu in the toolbar (it defaults to "choose base", indicating the need to select one) and the head will appear in the main display. The camera can be maneuvered around it using many of the same basic controls used elsewhere in the toolset. The head bases that are available include male and female versions of Human, Dwarf, Elf, and a gender-neutral child's head.

Once the base is selected, an enormous number of options will become available in the object inspector for modifying the exact shape and texture of the head. Hairstyles and beards can be added, tattoo textures can be overlaid on the skin, and so forth - there are hundreds of parameters.

To speed the creation of unique generic NPCs, the "randomize" button in the toolbar will set the various shape parameters to random values. This doesn't affect all facial features, however, since many of the adjustable features would look quite bizarre when set to extreme values. Generally the effects of the randomize button are limited to tabs 4 through 8, and it doesn't affect all of the features even on those. Manual customization may still be required to produce a truly diverse crop of NPCs.

Note that for some features (for example, lip color) the opacity defaults to 0%, so you may not see an immediate effect when changing them unless you set the opacity higher first.

[[Image:Morph editor.png|600px|thumb|center]]

== Beards and facial features ==

There are two basic types of beards available for facial morphs; model beards and stubble beards. Stubble beards are simply a texture overlay, and have no particular special effects associated with them. Model beards are three-dimensional objects that are affixed to the face, and it is important to be aware of certain limitations that come with using them.

In order to make a physical beard model fit properly onto the face, some facial features must be set to their default values. This is so that, as an example, one doesn't wind up with the tip of the chin poking out through the end of the beard. When you add a physical beard model to a head morph these specific facial features are automatically snapped to their default values and are locked there for as long as the beard is in place. If the beard is removed they become editable again, but it is important to note that they do ''not'' return to whatever values they had before the beard was added. So make the decision on whether a character has a physical beard before you spend a lot of time adjusting his jawline and other such details.

== Debug features ==

There are a number of features with "debug" in their names that are intended only to allow a facial artist to get a better view of certain parts of a facial morph, and if they are set to anything other than zero the morph won't be usable by the rest of the toolset. The most obvious example is the "teeth debug" parameter, which pulls the lips back to expose the model's teeth so that they can be adjusted in plain view.

== How to use a morph in your module ==

Morph is an art tool, not a design tool, and so it uses a somewhat different mechanism for making its output available to the designer than the other tools that come with the toolset. You can save a morph as a file in your regular filesystem but when you go to select a head morph in the creature designer you won't be able to import directly from the filesystem to use it.

Instead, you need to export the morph via the "post to local" command under the "Tools"->"Export" menu (alternately, right-click on the morph's display window and select "post to local" from the menu). Once the morph has been exported, it will be available in the creature creator's morph list when the appropriate body appearance model is selected (eg, a human female head morph is usable with a human female body appearance).

If you want to make a slight variation on an existing morph (say for example to change the hair colour or add a scar), load the mrh file of the desired morph, and then 'save as' with a new file name. Make your changes and save, then once again export to local. To make the new variant available, use "View"->"Refresh".

== How to replace the morph of an in game NPC (Single Player Campaign) ==

1. Open Toolset

2. Click the "Creatures" Button on the top right Palette Window

3. In the filter type the name of the NPC, example Bella or Desire or Murdock.

4. You'll see some folders appear. Navigate through them and find the NPC object:

Example: ntb100cr_gheyna (Gheyna)

5. Now left click that creature to highlight it.

6. On the bottom right the object inspector window appears full of information.

7. Scroll down the list until you see head morph, under appearance. Note the name of that file.

8. Rename the new morph file you exported to the name in the object inspector.

9. Now place your new morph in the following directory:

documents/bioware/dragon age/packages/core/override

Make sure you restart dragon age.

== Morph files ==

There are actually two files for every morph.
*.mrh - This is the source file for the morph data and can be saved anywhere and loaded from anywhere.
*.mor - This is the generated/processed binarized gff file that the game uses. You can change these in the toolset but it's not recommended.

To get the *.mor file you need to use the "export" command.

To edit an existing .mrh, you can either drag and drop the .mrh into the toolset or open the *.mrh from the toolset.

The head morph tool concatenates the two letter prefix (HM for human male, HF for human female, etc.) to the filename for you. If you saved a resource called "myhead", for example, and it was a human male then it would export a hm_myhead.mor. If it was a female dwarf it would save it as df_myhead.mor

The drop down for the head morph will also auto generate the two letter prefix based on the gender and appearance of the creature you are making.

== Deleting a morph ==

Morphs are an art asset, and as such are not stored in the database in the same manner as other resources. You can find morph files (.mor extension) in the \Dragon Age\packages\core\override\toolsetexport directory, to remove one simply delete it.

== Parameters ==

{{sidebox|
* Keep in mind that when selecting colors, you can open up a dropdown list where you browse for colors, and choose "All Tint Files *.tnt" to get a much wider range of color choices. The Tattoo colors especially (t1_tat_*) are very vibrant, and can give you 'very blue eyes', for example.
}}

Choose Base model name:

*HM_UHM_BASE - Human Male
*HF_UHM_BASE - Human Female
*DM_UHM_BASE - Dwarven Male
*DF_UHM_BASE - Dwarven Female
*EM_UHM_BASE - Elven Male
*EF_UHM_BASE - Elven Female
*QM_UHM_BASE - Qunari Male
*QF_UHM_BASE - Qunari Female
*KN_UHM_BASE - Child

*(Opacity 0.00 least color - 1.00 full color)
*(Anything 0.00 to 1.00 or -1.00 to 1.00 is a slider)
*(Left and Right = Left and Right of Morph Face not Left and Right as you look at the face.)

01. MATERIAL:

01. Face:

*Skin Color: 8 choices
*Lip Makeup Color: 27 choices
*Lip Makeup Opacity: 0.00 - 1.00
*Blush Makeup Color: 30 choices
*Blush Makeup Opacity: 0.00 - 1.00
*Eye Makeup Color: 36 choices
*Eye Makeup Opacity: 0.00 - 1.00

02. Skin Texture:

*Base Skin Texture: 12 choices
*Blend Skin Texture: 12 choices
*Blend Right Eye: 0.00 - 1.00
*Blend Left Eye: 0.00 - 1.00
*Blend Right Cheek: 0.00 - 1.00
*Blend Left Cheek: 0.00 - 1.00
*Blend Left Forehead: 0.00 - 1.00
*Blend Right Forehead: 0.00 - 1.00
*Blend Nose: 0.00 - 1.00
*Blend Middle Forehead: 0.00 - 1.00
*Blend All Override: 0.00 - 1.00

03. Skin Type:

*Blend Right Eye: 0.00 - 1.00
*Blend Left Eye: 0.00 - 1.00
*Blend Right Cheek: 0.00 - 1.00
*Blend Left Cheek: 0.00 - 1.00
*Blend Left Forehead: 0.00 - 1.00
*Blend Right Forehead: 0.00 - 1.00
*Blend Nose: 0.00 - 1.00
*Blend Middle Forehead: 0.00 - 1.00
*Blend All Override: 0.00 - 1.00

02. PART SELECTION:

1. Model: (Base model Chosen when starting.)

2. Parts:

*Eye Color: 11 choices
*Eyes: 2 choices
*Eye Texture: 16 choices
*Hair and Beard Color: 10 choices
*Hair: 17 choices
*Beard: 7 choices
*Eye Lashes: 1 choice
*Lashes Texture: 4 choices

3. Tattoo:

*Tattoo Mask: 14 choices
*Tattoo Channel 1 Color: 15 choices
*Tattoo 1 : R Channel: 0.00 - 1.00
*Tattoo Channel 2 Color: 15 choices
*Tattoo 2 : G Channel: 0.00 - 1.00
*Tattoo Channel 3 Color: 15 choices
*Tattoo 3 : B Channel: 0.00 - 1.00
*Tattoo Channel 4 Color: 15 choices
*Tattoo 4 : A Channel: 0.00 - 1.00

4. Brow and Stubble:

*Brow and Stubble Colors: 10 choices
*Bushy Eyebrows: 0.00 - 1.00 (only available if regular eyebrows set to 0.00)
*Regular Eyebrows: 0.00 - 1.00
*Thick Eyebrows: 0.00 - 1.00 (only available if regular eyebrows set to 0.00)
*Thinned Eyebrows: 0.00 - 1.00 (only available if regular eyebrows set to 0.00)
*Goatee: 0.00 - 1.00
*Soul Patch: 0.00 - 1.00
*Mustache: 0.00 - 1.00
*Pork Chops: 0.00 - 1.00

5. Crew Cut Selection:

*Sheppard: 0.00 - 1.00
*Receeding Hairline: 0.00 - 1.00
*Balding Hairline: 0.00 - 1.00

03. FEATURE SELECTION:

01. Shape:

*Head Shape 01: 0.00 - 1.00
*Head Shape 02: 0.00 - 1.00
*Head Shape 03: 0.00 - 1.00
*Head Shape Fat: 0.00 - 1.00
*Head Shape Thick: 0.00 - 1.00
*Head Shape Thin: 0.00 - 1.00
*(You can only choose to adjust one of these shapes.)

02. Nose:

*Eastern Nose: 0.00 - 1.00
*Flat Nose: 0.00 - 1.00
*Long Nose: 0.00 - 1.00
*Pig Nose: 0.00 - 1.00
*Straight Nose: 0.00 - 1.00
*Thick Nose: 0.00 - 1.00
*(You can only choose to adjust one of these shapes.)

03. Eye Shape:

*Eye Shape 01: 0.00 - 1.00
*Eye Shape 02: 0.00 - 1.00
*Eye Shape 02: 0.00 - 1.00
*Eye Shape 04: 0.00 - 1.00
*(You can only choose to adjust one of these shapes.)

04. Universal Shapes:

*Shape Chubby: 0.00 - 1.00
*Shape Skinny: 0.00 - 1.00
*(You can adjust both of these.)

Reset
*(Left clicking in box to right resets all selections to 0.00)

04. NOSE:

01. Targets:

*Nose Bend Left/Right: -1.00 - 1.00
*Nose Bridge In/Out: -1.00 - 1.00
*Nose Bridge Thin/Wide: -1.00 - 1.00
*Nose Up/Down: -1.00 - 1.00
*Nose Out/In: -1.00 - 1.00
*Nose Smaller/Larger: -1.00 - 1.00
*Nose Tip Up/Down: -1.00 - 1.00
*Nose Tip Out/In: -1.00 - 1.00
*Nostrils Narrow/Wide: -1.00 - 1.00

02. Shape:

*Nose Shape 1: 0.00 - 1.00
*Nose Shape 2: 0.00 - 1.00
*Nose Shape 3: 0.00 - 1.00
*Nose Shape 4: 0.00 - 1.00
*Nose Shape 5: 0.00 - 1.00
*Nose Shape 6: 0.00 - 1.00
*(You can choose to adjust any or all of these.)

Reset
*(Left clicking in box to right resets all selections to 0.00)

05. MOUTH:

01. Targets:

*Mouth Back/Forward: -1.00 - 1.00
*Mouth Corner Up/Down: -1.00 - 1.00
*Mouth Up/Down: -1.00 - 1.00
*Mouth Lips Fat/Thin: -1.00 - 1.00
*Mouth Lower Lip Fat: 0.00 - 1.00
*Mouth Lower Lip Up: 0.00 - 1.00
*Mouth Narrow/Wide: -1.00 - 1.00
*Mouth Over/Underbite: -1.00 - 1.00
*Mouth Upper Lip Down: 0.00 - 1.00
*Mouth Upper Lip Fat: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

06. EYES:

01. Targets:

*Eye Bags: 0.00 - 1.00
*Eye Brow Back/Forward: -1.00 - 1.00
*Eye Brow Down/Up: -1.00 - 1.00
*Eye Narrow/Wide: -1.00 - 1.00
*Eye Position Down/Up: -1.00 - 1.00
*Eyelash Fan: 0.00 - 1.00
*Eyelash Length: 0.00 - 1.00
*Eyes Back/Forward: -1.00 - 1.00
*Eyes Larger: 0.00 - 1.00
*Eyes Small: 0.00 - 1.00
*Eyes Squint: 0.00 - 1.00

02. Debug

Debug Cornea Larger/Smaller: -1.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

07. CHEEKS:

01. Targets:

*Cheeks Back/Forward: -1.00 - 1.00
*Cheeks Bones In/Out: -1.00 - 1.00
*Cheeks Gaunt: 0.00 - 1.00
*Cheeks Lower: 0.00 - 1.00
*Cheeks Up: 0.00 - 1.00
*Cheeks Wide: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

08. JAW:

01. Targets:

*Jaw Chin Down/Up: -1.00 - 1.00
*Jaw Chin In/Out: -1.00 - 1.00
*Jaw Chin Thin/Wide: -1.00 - 1.00
*Jaw Lower: 0.00 - 1.00
*Jaw Narrow/Wide: -1.00 - 1.00
*Jaw Square Shape: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

10. TEETH:

01. Targets:

*TeethChippedtoothLeft: 0.00 - 1.00
*TeethChippedtoothRight: 0.00 - 1.00
*TeethMissingLeft: 0.00 - 1.00
*TeethNoFront: 0.00 - 1.00
*Teeth Back/Forward: -1.00 - 1.00
*Teeth Close/Separate: -1.00 - 1.00
*Teeth Down/Up: -1.00 - 1.00

02. Debug:

*Teeth Wide/Narrow: -1.00 - 1.00
*Teeth Debug: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

11. EARS:

01. Targets:

*Ears Down/Up: -1.00 - 1.00
*Ears In/Out: -1.00 - 1.00
*Ears Large/Small: -1.00 - 1.00
*Ears Rotate Outwards: 0.00 - 1.00
*Ears Wide/Narrow: -1.00 - 1.00

02. Debug:

Ears Debug for Hair Crashing: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

12. NECK:

01. Targets:

*NeckApple: 0.00 - 1.00
*NeckThin: 0.00 - 1.00
*Neck Back: 0.00 - 1.00
*Neck Wide: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

13. BROWS:

01. Targets:

*Brow Down/Up: -1.00 - 1.00
*Forehead Out/In: -1.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

13. VIEW SETTINGS:

1. Light:

*Light Model: 6 choices
*Light Probe: 4 choices

2. Camera:

*Distance: Numeric
*Orientation: 3 coordinates
*Position: 3 coordinates

3. Object:

*Orientation: 3 coordinates
*Position: 3 coordinates

4. Facial Animation:

*FA name: Blank
*FA set: 5 choices

14. EXPORT SETTINGS

General:

Export .mop file: True/False (False default)

14. UNIQUE SHAPES:

01. Targets:

*Fat Man: 0.00 - 1.00
*Shape Alistair: 0.00 - 1.00
*Shape Daveth: 0.00 - 1.00
*Shape Duncan: 0.00 - 1.00
*Shape Jory: 0.00 - 1.00
*Shape King Cailan: 0.00 - 1.00
*Shape Loghain: 0.00 - 1.00
*Shape Old Male: 0.00 - 1.00

Reset
*(Left clicking in box to right resets all selections to 0.00)

== Tints and hairstyles ==

Tints and hairstyles often have somewhat uninformative names. The following thumbnails provide a preview summary of what these tints and hairstyles represent:

=== Dwarf male beards ===

<gallery>
Image:dm_brd_b1a_0 front.jpg | dm_brd_b1a_0 front
Image:dm_brd_b1a_0 side.jpg | dm_brd_b1a_0 side
Image:dm_brd_b2a_0 front.jpg | dm_brd_b2a_0 front
Image:dm_brd_b2a_0 side.jpg | dm_brd_b2a_0 side
Image:dm_brd_b3a_0 front.jpg | dm_brd_b3a_0 front
Image:dm_brd_b3a_0 side.jpg | dm_brd_b3a_0 side
Image:dm_brd_b4a_0 front.jpg | dm_brd_b4a_0 front
Image:dm_brd_b4a_0 side.jpg | dm_brd_b4a_0 side
Image:dm_brd_b5a_0 front.jpg | dm_brd_b5a_0 front
Image:dm_brd_b5a_0 side.jpg | dm_brd_b5a_0 side
Image:dm_brd_b6a_0 front.jpg | dm_brd_b6a_0 front
Image:dm_brd_b6a_0 side.jpg | dm_brd_b6a_0 side
Image:dm_brd_b7a_0 front.jpg | dm_brd_b7a_0 front
Image:dm_brd_b7a_0 side.jpg | dm_brd_b7a_0 side
</gallery>

=== Human female hairstyles ===

<gallery>
Image:hf_har_blda_0 front.jpg |hf_har_blda_0 front
Image:hf_har_blda_0 side.jpg | hf_har_blda_0 side
Image:hf_har_ha1a_0 front.jpg |hf_har_ha1a_0 front
Image:hf_har_ha1a_0 side.jpg | hf_har_ha1a_0 side
Image:hf_har_ha2a_0 front.jpg |hf_har_ha2a_0 front
Image:hf_har_ha2a_0 side.jpg | hf_har_ha2a_0 side
Image:hf_har_ha3a_0 front.jpg |hf_har_ha3a_0 front
Image:hf_har_ha3a_0 side.jpg | hf_har_ha3a_0 side
Image:hf_har_ha4a_0 front.jpg |hf_har_ha4a_0 front
Image:hf_har_ha4a_0 side.jpg | hf_har_ha4a_0 side
Image:hf_har_hb1a_0 front.jpg |hf_har_hb1a_0 front
Image:hf_har_hb1a_0 side.jpg | hf_har_hb1a_0 side
Image:hf_har_hb2a_0 front.jpg |hf_har_hb2a_0 front
Image:hf_har_hb2a_0 side.jpg | hf_har_hb2a_0 side
Image:hf_har_hb3a_0 front.jpg |hf_har_hb3a_0 front
Image:hf_har_hb3a_0 side.jpg | hf_har_hb3a_0 side
Image:hf_har_hb4a_0 front.jpg |hf_har_hb4a_0 front
Image:hf_har_hb4a_0 side.jpg | hf_har_hb4a_0 side
Image:hf_har_hc1a_0 front.jpg |hf_har_hc1a_0 front
Image:hf_har_hc1a_0 side.jpg | hf_har_hc1a_0 side
Image:hf_har_hc2a_0 front.jpg |hf_har_hc2a_0 front
Image:hf_har_hc2a_0 side.jpg | hf_har_hc2a_0 side
Image:hf_har_hc3a_0 front.jpg |hf_har_hc3a_0 front
Image:hf_har_hc3a_0 side.jpg | hf_har_hc3a_0 side
Image:hf_har_hc4a_0 front.jpg |hf_har_hc4a_0 front
Image:hf_har_hc4a_0 side.jpg | hf_har_hc4a_0 side
Image:hf_har_hd1a_0 front.jpg |hf_har_hd1a_0 front
Image:hf_har_hd1a_0 side.jpg | hf_har_hd1a_0 side
Image:hf_har_hd2a_0 front.jpg |hf_har_hd2a_0 front
Image:hf_har_hd2a_0 side.jpg | hf_har_hd2a_0 side
Image:hf_har_hd3a_0 front.jpg |hf_har_hd3a_0 front
Image:hf_har_hd3a_0 side.jpg | hf_har_hd3a_0 side
Image:hf_har_hd4a_0 front.jpg |hf_har_hd4a_0 front
Image:hf_har_hd4a_0 side.jpg | hf_har_hd4a_0 side
</gallery>

=== Human male beards ===

<gallery>
Image:hm_brd_b1a_0 front.jpg | hm_brd_b1a_0 front
Image:hm_brd_b1a_0 side.jpg | hm_brd_b1a_0 side
Image:hm_brd_b2a_0 front.jpg | hm_brd_b2a_0 front
Image:hm_brd_b2a_0 side.jpg | hm_brd_b2a_0 side
Image:hm_brd_b3a_0 front.jpg | hm_brd_b3a_0 front
Image:hm_brd_b3a_0 side.jpg | hm_brd_b3a_0 side
Image:hm_brd_b4a_0 front.jpg | hm_brd_b4a_0 front
Image:hm_brd_b4a_0 side.jpg | hm_brd_b4a_0 side
Image:hm_brd_b5a_0 front.jpg | hm_brd_b5a_0 front
Image:hm_brd_b5a_0 side.jpg | hm_brd_b5a_0 side
Image:hm_brd_b6a_0 front.jpg | hm_brd_b6a_0 front
Image:hm_brd_b6a_0 side.jpg | hm_brd_b6a_0 side
</gallery>

=== Human male hairstyles ===

<gallery>
Image:hm_har_blda_0 front.jpg | hm_har_blda_0 front
Image:hm_har_blda_0 side.jpg | hm_har_blda_0 side
Image:hm_har_ha1a_0 front.jpg | hm_har_ha1a_0 front
Image:hm_har_ha1a_0 side.jpg | hm_har_ha1a_0 side
Image:hm_har_ha2a_0 front.jpg | hm_har_ha2a_0 front
Image:hm_har_ha2a_0 side.jpg | hm_har_ha2a_0 side
Image:hm_har_ha3a_0 front.jpg | hm_har_ha3a_0 front
Image:hm_har_ha3a_0 side.jpg | hm_har_ha3a_0 side
Image:hm_har_hb1a_0 front.jpg | hm_har_hb1a_0 front
Image:hm_har_hb1a_0 side.jpg | hm_har_hb1a_0 side
Image:hm_har_hb2a_0 front.jpg | hm_har_hb2a_0 front
Image:hm_har_hb2a_0 side.jpg | hm_har_hb2a_0 side
Image:hm_har_hb3a_0 front.jpg | hm_har_hb3a_0 front
Image:hm_har_hb3a_0 side.jpg | hm_har_hb3a_0 side
Image:hm_har_hb4a_0 front.jpg | hm_har_hb4a_0 front
Image:hm_har_hb4a_0 side.jpg | hm_har_hb4a_0 side
Image:hm_har_hc1a_0 front.jpg | hm_har_hc1a_0 front
Image:hm_har_hc1a_0 side.jpg | hm_har_hc1a_0 side
Image:hm_har_hc2a_0 front.jpg | hm_har_hc2a_0 front
Image:hm_har_hc2a_0 side.jpg | hm_har_hc2a_0 side
Image:hm_har_hc3a_0 front.jpg | hm_har_hc3a_0 front
Image:hm_har_hc3a_0 side.jpg | hm_har_hc3a_0 side
Image:hm_har_hc4a_0 front.jpg | hm_har_hc4a_0 front
Image:hm_har_hc4a_0 side.jpg | hm_har_hc4a_0 side
Image:hm_har_hd1a_0 front.jpg | hm_har_hd1a_0 front
Image:hm_har_hd1a_0 side.jpg | hm_har_hd1a_0 side
Image:hm_har_hd2a_0 front.jpg | hm_har_hd2a_0 front
Image:hm_har_hd2a_0 side.jpg | hm_har_hd2a_0 side
Image:hm_har_hd3a_0 front.jpg | hm_har_hd3a_0 front
Image:hm_har_hd3a_0 side.jpg | hm_har_hd3a_0 side
Image:hm_har_hd4a_0 front.jpg | hm_har_hd4a_0 front
Image:hm_har_hd4a_0 side.jpg | hm_har_hd4a_0 side
</gallery>

=== Eye shadow ===

<gallery>
Image:t1_mue_bk1.jpg | t1_mue_bk1
Image:t1_mue_bk2.jpg | t1_mue_bk2
Image:t1_mue_bk3.jpg | t1_mue_bk3
Image:t1_mue_bl1.jpg | t1_mue_bl1
Image:t1_mue_bl2.jpg | t1_mue_bl2
Image:t1_mue_bl3.jpg | t1_mue_bl3
Image:t1_mue_gn1.jpg | t1_mue_gn1
Image:t1_mue_gn2.jpg | t1_mue_gn2
Image:t1_mue_gn3.jpg | t1_mue_gn3
Image:t1_mue_gr1.jpg | t1_mue_gr1
Image:t1_mue_gr2.jpg | t1_mue_gr2
Image:t1_mue_gr3.jpg | t1_mue_gr3
Image:t1_mue_or1.jpg | t1_mue_or1
Image:t1_mue_or2.jpg | t1_mue_or2
Image:t1_mue_or3.jpg | t1_mue_or3
Image:t1_mue_pi1.jpg | t1_mue_pi1
Image:t1_mue_pi2.jpg | t1_mue_pi2
Image:t1_mue_pi3.jpg | t1_mue_pi3
Image:t1_mue_pu1.jpg | t1_mue_pu1
Image:t1_mue_pu2.jpg | t1_mue_pu2
Image:t1_mue_pu3.jpg | t1_mue_pu3
Image:t1_mue_re1.jpg | t1_mue_re1
Image:t1_mue_re2.jpg | t1_mue_re2
Image:t1_mue_re3.jpg | t1_mue_re3
Image:t1_mue_ro1.jpg | t1_mue_ro1
Image:t1_mue_ro2.jpg | t1_mue_ro2
Image:t1_mue_ro3.jpg | t1_mue_ro3
Image:t1_mue_te1.jpg | t1_mue_te1
Image:t1_mue_te2.jpg | t1_mue_te2
Image:t1_mue_te3.jpg | t1_mue_te3
Image:t1_mue_wh1.jpg | t1_mue_wh1
Image:t1_mue_wh2.jpg | t1_mue_wh2
Image:t1_mue_wh3.jpg | t1_mue_wh3
Image:t1_mue_ye1.jpg | t1_mue_ye1
Image:t1_mue_ye2.jpg | t1_mue_ye2
Image:t1_mue_ye3.jpg | t1_mue_ye3
</gallery>

=== Lip colour ===

<gallery>
Image:t1_mul_bk1.jpg | t1_mul_bk1
Image:t1_mul_bk2.jpg | t1_mul_bk2
Image:t1_mul_bk3.jpg | t1_mul_bk3
Image:t1_mul_pi1.jpg | t1_mul_pi1
Image:t1_mul_pi2.jpg | t1_mul_pi2
Image:t1_mul_pi3.jpg | t1_mul_pi3
Image:t1_mul_pu1.jpg | t1_mul_pu1
Image:t1_mul_pu2.jpg | t1_mul_pu2
Image:t1_mul_pu3.jpg | t1_mul_pu3
Image:t1_mul_re1.jpg | t1_mul_re1
Image:t1_mul_re2.jpg | t1_mul_re2
Image:t1_mul_re3.jpg | t1_mul_re3
Image:t1_mul_ro1.jpg | t1_mul_ro1
Image:t1_mul_ro2.jpg | t1_mul_ro2
Image:t1_mul_ro3.jpg | t1_mul_ro3
Image:t1_mul_ta1.jpg | t1_mul_ta1
Image:t1_mul_ta2.jpg | t1_mul_ta2
Image:t1_mul_ta3.jpg | t1_mul_ta3
Image:t1_mul_te1.jpg | t1_mul_te1
Image:t1_mul_te2.jpg | t1_mul_te2
Image:t1_mul_te3.jpg | t1_mul_te3
Image:t1_mul_wh1.jpg | t1_mul_wh1
Image:t1_mul_wh2.jpg | t1_mul_wh2
Image:t1_mul_wh3.jpg | t1_mul_wh3
</gallery>

=== Skin tone ===

<gallery>
Image:t1_skn_001.jpg | t1_skn_001
Image:t1_skn_002.jpg | t1_skn_002
Image:t1_skn_003.jpg | t1_skn_003
Image:t1_skn_004.jpg | t1_skn_004
Image:t1_skn_005.jpg | t1_skn_005
Image:t1_skn_006.jpg | t1_skn_006
Image:t1_skn_007.jpg | t1_skn_007
Image:t1_skn_blank.jpg| t1_skn_blank
</gallery>

=== Eye colour ===

<gallery>
Image:t3_eye_amb.jpg | t3_eye_amb
Image:t3_eye_blk.jpg | t3_eye_blk
Image:t3_eye_dbl.jpg | t3_eye_dbl
Image:t3_eye_dbr.jpg | t3_eye_dbr
Image:t3_eye_grn.jpg | t3_eye_grn
Image:t3_eye_gry.jpg | t3_eye_gry
Image:t3_eye_hzl.jpg | t3_eye_hzl
Image:t3_eye_ice.jpg | t3_eye_ice
Image:t3_eye_lbl.jpg | t3_eye_lbl
Image:t3_eye_lbr.jpg | t3_eye_lbr
Image:t3_eye_tea.jpg | t3_eye_tea
</gallery>

=== Hair colour ===

<gallery>
Image:t3_har_blk front.jpg|t3_har_blk front
Image:t3_har_blk side.jpg| t3_har_blk side
Image:t3_har_bln front.jpg|t3_har_bln front
Image:t3_har_bln side.jpg| t3_har_bln side
Image:t3_har_dbl front.jpg|t3_har_dbl front
Image:t3_har_dbl side.jpg| t3_har_dbl side
Image:t3_har_dbr front.jpg|t3_har_dbr front
Image:t3_har_dbr side.jpg| t3_har_dbr side
Image:t3_har_gry front.jpg|t3_har_gry front
Image:t3_har_gry side.jpg| t3_har_gry side
Image:t3_har_lbr front.jpg|t3_har_lbr front
Image:t3_har_lbr side.jpg| t3_har_lbr side
Image:t3_har_org front.jpg|t3_har_org front
Image:t3_har_org side.jpg| t3_har_org side
Image:t3_har_rbr front.jpg|t3_har_rbr front
Image:t3_har_rbr side.jpg| t3_har_rbr side
Image:t3_har_red front.jpg|t3_har_red front
Image:t3_har_red side.jpg| t3_har_red side
Image:t3_har_wht front.jpg|t3_har_wht front
Image:t3_har_wht side.jpg| t3_har_wht side
</gallery>

== Blush colour ==

<gallery perrow="3">
Image:T1_mub_bk1.jpg | t1_mub_bk1
Image:T1_mub_bk2.jpg | t1_mub_bk2
Image:T1_mub_bk3.jpg | t1_mub_bk3
Image:T1_mub_br1.jpg | t1_mub_br1
Image:T1_mub_br2.jpg | t1_mub_br2
Image:T1_mub_br3.jpg | t1_mub_br3
Image:T1_mub_or1.jpg | t1_mub_or1
Image:T1_mub_or2.jpg | t1_mub_or2
Image:T1_mub_or3.jpg | t1_mub_or3
Image:T1_mub_pi1.jpg | t1_mub_pi1
Image:T1_mub_pi2.jpg | t1_mub_pi2
Image:T1_mub_pi3.jpg | t1_mub_pi3
Image:T1_mub_pu1.jpg | t1_mub_pu1
Image:T1_mub_pu2.jpg | t1_mub_pu2
Image:T1_mub_pu3.jpg | t1_mub_pu3
Image:T1_mub_re1.jpg | t1_mub_re1
Image:T1_mub_re2.jpg | t1_mub_re2
Image:T1_mub_re3.jpg | t1_mub_re3
Image:T1_mub_ro1.jpg | t1_mub_ro1
Image:T1_mub_ro2.jpg | t1_mub_ro2
Image:T1_mub_ro3.jpg | t1_mub_ro3
Image:T1_mub_ta1.jpg | t1_mub_ta1
Image:T1_mub_ta2.jpg | t1_mub_ta2
Image:T1_mub_ta3.jpg | t1_mub_ta3
Image:T1_mub_te1.jpg | t1_mub_te1
Image:T1_mub_te2.jpg | t1_mub_te2
Image:T1_mub_te3.jpg | t1_mub_te3
Image:T1_mub_wh1.jpg | t1_mub_wh1
Image:T1_mub_wh2.jpg | t1_mub_wh2
Image:T1_mub_wh3.jpg | t1_mub_wh3
</gallery>

== Tattoos ==

{| border="1" cellspacing="0" cellpadding="2"
|-
! Tint file !! Colour
|-
| t1_tat_blk || Black
|-
| t1_tat_dgn || Dark Green
|-
| t1_tat_org || Orange
|-
| t1_tat_blu || Blue
|-
| t1_tat_dpu || Dark Purple
|-
| t1_tat_pnk || Pink
|-
| t1_tat_brn || Brown
|-
| t1_tat_drd || Dark Red
|-
| t1_tat_pur || Purple
|-
| t1_tat_dbl || Dark Blue
|-
| t1_tat_grn || Green
|-
| t1_tat_red || Red
|-
| t1_tat_dbr || Dark Brown
|-
| t1_tat_gry || Grey
|-
| t1_tat_yel || Yellow
|}

You can use a different colour for each Tattoo layer.

You can combine (layer) Tattoos 1 to 4 for each Tattoo mask if desired.

Sliders 0.00 to 1.00 determines darkness of the Tattoo.

All screen shots set at 1.00, black colour

<gallery>
Image:uh tat av1 0t tattoo 1.jpg | uh tat av1 0t tattoo 1
Image:uh tat av1 0t tattoo 2.jpg | uh tat av1 0t tattoo 2
Image:uh tat av1 0t tattoo 3.jpg | uh tat av1 0t tattoo 3
Image:uh tat av1 0t tattoo 4.jpg | uh tat av1 0t tattoo 4
Image:uh tat av2 0t tattoo 1.jpg | uh tat av2 0t tattoo 1
Image:uh tat av2 0t tattoo 2.jpg | uh tat av2 0t tattoo 2
Image:uh tat av2 0t tattoo 3.jpg | uh tat av2 0t tattoo 3
Image:uh tat av2 0t tattoo 4.jpg | uh tat av2 0t tattoo 4
Image:uh tat av3 0t tattoo 1.jpg | uh tat av3 0t tattoo 1
Image:uh tat av3 0t tattoo 2.jpg | uh tat av3 0t tattoo 2
Image:uh tat av3 0t tattoo 3.jpg | uh tat av3 0t tattoo 3
Image:uh tat av3 0t tattoo 4.jpg | uh tat av3 0t tattoo 4
Image:uh tat dw1 0t tattoo 1.jpg | uh tat dw1 0t tattoo 1
Image:uh tat dw1 0t tattoo 2.jpg | uh tat dw1 0t tattoo 2
Image:uh tat dw1 0t tattoo 3.jpg | uh tat dw1 0t tattoo 3
Image:uh tat dw1 0t tattoo 4.jpg | uh tat dw1 0t tattoo 4
Image:uh tat dw2 0t tattoo 1.jpg | uh tat dw2 0t tattoo 1
Image:uh tat dw2 0t tattoo 2.jpg | uh tat dw2 0t tattoo 2
Image:uh tat dw2 0t tattoo 3.jpg | uh tat dw2 0t tattoo 3
Image:uh tat dw2 0t tattoo 4.jpg | uh tat dw2 0t tattoo 4
Image:uh tat ed1 0t tattoo 1.jpg | uh tat ed1 0t tattoo 1
Image:uh tat ed1 0t tattoo 2.jpg | uh tat ed1 0t tattoo 2
Image:uh tat ed1 0t tattoo 3.jpg | uh tat ed1 0t tattoo 3
Image:uh tat ed1 0t tattoo 4.jpg | uh tat ed1 0t tattoo 4
Image:uh tat ed2 0t tattoo 1.jpg | uh tat ed2 0t tattoo 1
Image:uh tat ed2 0t tattoo 2.jpg | uh tat ed2 0t tattoo 2
Image:uh tat ed2 0t tattoo 3.jpg | uh tat ed2 0t tattoo 3
Image:uh tat ed2 0t tattoo 4.jpg | uh tat ed2 0t tattoo 4
Image:uh tat ed3 0t tattoo 1.jpg | uh tat ed3 0t tattoo 1
Image:uh tat ed3 0t tattoo 2.jpg | uh tat ed3 0t tattoo 2
Image:uh tat ed3 0t tattoo 3.jpg | uh tat ed3 0t tattoo 3
Image:uh tat ed3 0t tattoo 4.jpg | uh tat ed3 0t tattoo 4
Image:uh tat ed4 0t tattoo 1.jpg | uh tat ed4 0t tattoo 1
Image:uh tat ed4 0t tattoo 2.jpg | uh tat ed4 0t tattoo 2
Image:uh tat ed4 0t tattoo 3.jpg | uh tat ed4 0t tattoo 3
Image:uh tat ed4 0t tattoo 4.jpg | uh tat ed4 0t tattoo 4
</gallery>

[[Category:Morphs]]

How-tos

2009-12-27T06:08:46Z

JackFuzz: /* Adding music to cutscenes */

This page lists how to accomplish tasks that are relatively simple and commonly needed, but that touch on multiple areas of the toolset or are difficult to figure out intuitively how to do.

Just collecting ideas at the moment, add headers if you think a how-to is needed on a particular subject.

*[[3D control]]

== Run a cutscene from a trigger ==

!!compile fails in test database due to bad core libraries, so this hasn't been tested!!

Create a script:

<dascript>
#include "events_h"
#include "global_objects_h"
#include "utility_h"

void main ()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
int nEventHandled = FALSE;
switch (nEventType)
{
case EVENT_TYPE_ENTER:
{
object oCreature = GetEventCreator(ev);
if(IsHero(oCreature)) {
resource rCutscene = R"my_cutscene.cut";
CS_LoadCutscene(rCutscene);
DestroyObject(OBJECT_SELF, 0);
}
break;
}
if (!nEventHandled) //If this event wasn't handled by this script, let the core script try
{
HandleEvent(ev, RESOURCE_SCRIPT_TRIGGER_CORE);
}
}
</dascript>

And set it as the event script for the trigger that you want to have run the cutscene.

== Add a follower to the player's party ==

<dascript>
if(IsPlayer(oCreature)) {
object oFollower = GetObjectByTag("myfollower");
UT_HireFollower(oCreature, oFollower);
}
</dascript>

Note that with Toolset v1.0.982.0, calling UT_HireFollower() will result in a follower who's unable to gain xp. This happens due to the call of
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, '''TRUE''');
to the function
void WR_SetFollowerState(object oCreature, int nState, int nSendEvent = TRUE, int nMinLevel = 0, '''int bPreventLevelup''' = FALSE)
To enable the xp gain, the flag CREATURE_REWARD_FLAGS needs to be cleared from the follower after the hired event was processed (there the flag is set). Alternatively, the relevant contents of UT_HireFollower() are to be called directly using bPreventLevelup = FALSE.

== Have an enemy play possum and then get up to fight ==

Set the creature's CREATURE_SPAWN_DEAD variable to 2.

When it's time for the creature to rise and attack, execute the following script commands:

<dascript>
#include "wrappers_h"
...
WR_SetObjectActive(oCreature, TRUE);
SetCommandable(oCreature, TRUE);
// Make sure to set this flag back to 0 to avoid problems with savegames.
SetLocalInt(oCreature, CREATURE_SPAWN_DEAD, 0);
UT_CombatStart(oCreature, oPC);
</dascript>

== Insert content into an existing area ==

If you want to add new content on to an existing area (for example, putting a new character or area transition door into an area that exists in the single-player campaign) there are two different ways to do it. One is to override the existing area with a new area of your own design that duplicates the original with the exception of your additions. This is straightforward to do but can interact poorly with other add-ons - you can only have one version of an area active at a time.

A more elegant and extensible approach is to use a [[PRCSCR]]_-prefixed M2DA. The PRCSCR M2DA has a very simple structure and a simple but profound effect:

*ID - a unique integer identifier for each row
*AreaListName - a string that identifies a specific area list, or the special keyword "any".
*Script - the name of a script file.

Whenever a player enters an area in an area list in this M2DA the associated script will be run. A modder can therefore include a script with his mod that will be run when the player enters an existing area that he didn't create. This script can freely add or remove placeables and creatures and perform whatever other modifications to the area that a script is capable of doing.

Note that the script will be run every time the player enters the area, so you'll want to have an associated plot flag to ensure that the changes are only made once.

The following example is a script that adds a new character from an add-on module to an existing area in the main game:

<dascript>
void main()
{
//Check whether we've added Joblo already.
if (WR_GetPlotFlag("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
)

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

Since you can't add [[waypoint]]s to an existing area you'll need to enter the position and orientation values for the target location manually. You can find them by creating a local copy of the area in question and temporarily adding a waypoint to copy down the coordinates and orientation you'll need.

== Add new music ==

Open up [[FMOD]]

It creates a project - set the build directory to your DA override directory - with project highlighted, it is over on the top right about half way down the project settings. You can set a default resource directory but that will just set where the file browser defaults to so it is optional. I'd also define a name in those parameters while you are there.

From there, you need a new event !!(not sure whether a blank default is generated or whether you have to right click and make a default blank event)!!. After you have an event, highlight it and change to the event tab (2nd tab). Here you need to import your file to link to that event.

On that tab I think it creates a empty row for your new event - right click and add wavetable or something like that - I think I use the top option. (Again, might be wrong but the basic goal is getting a audio file in that screen that plays when you hit the play button at the top)

Browse to your wav file or whatever you have.

From there you should be able to play the sound both in the pop-up box and (once that is closed) back in the event tab. You'll see the name of the wave in that once empty row (IIRC).

If you want, you can add layers of sounds to this event using the same process over and over, but keeping it simple; we'll just move along.

Now you have a project and an event. You can set various parameters on the first tab that alter pitch etc on the first tab. (When you import the sound, you set whether it is a one shot or looping).

Once you have that done, go to the top drop down and find build. Build the files and you should see extra files in your override directory.

From there, just open up the toolset (or hit refresh from within the toolset) and your project and event sounds should show up in the listing of sounds.

You can then drag and drop them into the game or cutscene and they will play.

== Adding music to cutscenes ==

The way we have been doing the music changes is via placed sound objects. These sound objects are generally created in [[FMOD]], and in FMOD you can say if the music will persist after the cutscene or end when the cutscene ends.

We are just using other sounds to switch music tracks. Designers can add music switch parameter to any sound in Fmod Designer, usually this is just VO line to change music track, for example:

[[Image:FMOD music switch.jpg]]

If there are no other sounds, designers can create empty sound event and add #music parameter there and place this sound on cutscene timeline.
Music track has to be defined in the same group as music in current area in “music.fdp” to work.

[[Image:FMOD music switch 2.jpg]]

<pre>
#music:name,1 – non looping, for stingers
#music:name – for looping music
</pre>

--------------
Another way
--------------

1. Open up '''FMOD''' (fmod comes with dragon age, do a search for fmod in dragon age directory)

2. '''File''' ---> '''New Project''' --> and call the project whatever you want and place it in whatever folder you want.

3. '''Double click''' the '''folder''' under '''Hierarchy''' (purple icon folder) and an event will appear beneath it. Name this event whatever you want. (If there is no event for some reason right click and add one).

4. Now click '''"Event Editor"''' Tab. (Make sure your event was selected before you do this).

5. '''Right click''' one of the open sound fields (find it) and click '''"Add Sound"'''. (just right click all over until you see the option).

6. In this window you will see '''"LOOPING"''' and '''"ONE SHOT"''' on the right hand side. Looping will be selected by default. If you want your music to loop over & over again even after a cutscene is over leave it there. If you want your music to play ONE TIME then select "One Shot".

7. Now it's time to '''pick your music file''' by clicking '''"new wavetable"'''. '''Browse''' to your music file (wav), select it and '''press ok'''.

8. '''VERY VERY IMPORTANT'''.. '''YOU MUST DO THIS STEP'''....... Right click slightly above the timeline and click '''"ADD PARAMETER"'''.

9. Now '''right click''' your new blank parameter, look at the bottom and click '''"PARAMETER PROPERTIES"'''. Another new window will pop up.

10. '''VERY IMPORTANT'''..... Name this parameter:

#duck:music,1000,0,5000,-30

Now click ok.

11. Your new parameter should read: '''#duck:music,1000,0,5000,-30 (Primary)'''

12. Now click '''"Build"''' and do '''"build project"'''.

13. Note the new files in the directory where you saved the project.

14. Copy the '''FEV & FSB''' files from your FMOD project folder '''INTO YOUR OVERRIDE folder'''. I made a folder called music to be organized.

FMODProjectFolder/whatever.fev
FMODProjectFolder/whatever.fsb

COPY TO

Dragon Age\modules\Single Player\override\toolsetexport\music

15. Now open up '''toolset''' and navigate to '''sound palette''' and you should see your new sound file. Type the name of your sound file in the filter to find it faster. (Do not type the folder name in the filter. The filter works by filenames and not folders).

16. Open a '''cutscene''', then left click your new sound file in the right hand sound palette window to select and highlight it. (just a simple left click on it).

17. Now '''left click anywhere in your cutscene''' and a sound icon will be added which is your sound file.

'''Congrats''', 17 steps and now you've added a simple music file to your project and ready for your cutscene. *Sweats*

== Delete resources ==

Resource deletion can sometimes be a bit complicated. Check the following:

*Resources must be checked in when deleted. This is so that the toolset can be sure that all dependencies have been properly resolved.
*If other resources reference the resource it can't be deleted. This means that sometimes you'll need to delete resources in a specific order. For example, you can't delete a creature that's being used in an area, but you could delete the area and then delete the creature. Occasionally there may be circular references that you'll need to break by editing the resources before deleting them. For example:
**A stage can reference an area, which can then reference the stage.
**A plot file can have an associated event script, which will almost certainly include the plot file.
**A stage can reference a creature, which references a dialogue, which references the original stage.

== Removing Modules ==

Deleting a Module from the Toolset
Setup:
I created a module called Meep with a unique id of rcfMeep, added in one area with a waypoint, configured the starting area/waypoint info, and exported it with dependencies. And now I want to strip it out.

Step 1: Removing it from the game

* Navigate to My Documents\Bioware\AddIns
* Delete the folder called rcfMeep
* Done

Removing from the game is fairly easy. The toolset? Not so much. The reason for this is that the information is stored in the SQL Database. Now if you just want to remove the module from the Manage Modules list, that is easy.

* Open Sql Server Management Studio Express. I'm not sure if the default installation installs this or not. If not, it can be downloaded from Microsoft.
* Connect to the BWDATOOLSET server, assuming that you kept the default options.
* Expand Databases
* Expand bw_dragonage_content
* Expand Tables
* Right click and select open on the dbo.Modules table
* This will bring up an excell-like window. Find your module, right-click on the row, and select delete. Say ok to the confirmation.
* Module is now PERMANENTLY removed. Absolutely no way of recovering it.

Now depending on the size of the Module, you just orphaned a bunch of resources. Areas, placables, conversations, they all get placed into the database. And once you remove the module ID, you just lost your ability to remove these resources. Now do keep in mind that 95% of this junk is just text, so it hardly takes up any room. It's not really a major issue. However if you [[How-tos#Delete resources|delete out the resources]] within the toolset before you remove the module reference you should avoid this.

== Override Events (e.g. those in player_core) ==
Look here: [[Event override]]

== Create a lootable placeable that vanishes when looted ==

For a player-usable placeable, use the following event script to make it give its contents to the player and then vanish when clicked on.

<dascript>
#include "wrappers_h"
void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
switch (nEventType)
{
case EVENT_TYPE_USE:
{
//MoveAllItems(OBJECT_SELF, GetHero());
AddCreatureMoney (1000000, GetHero(), TRUE);
Safe_Destroy_Object(OBJECT_SELF);
}
}
}
</dascript>

If you wanted to use standard resources you could achieve the same thing (though not destroying the placeable) simply by adding "_autoloot" to the end of the placeable's tag.

== Move the player to a new area after a cutscene plays ==

Stand-alone cutscenes have an "end script" parameter that sets a script to run once the cutscene ends. Use a script such as the following:

<dascript>
void main()
{
DoAreaTransition("destination_area_tag", "destination_waypoint_tag");
}
</dascript>
[[category:tutorials]]

How-tos

2009-12-26T21:29:35Z

JackFuzz: /* Adding music to cutscenes */

This page lists how to accomplish tasks that are relatively simple and commonly needed, but that touch on multiple areas of the toolset or are difficult to figure out intuitively how to do.

Just collecting ideas at the moment, add headers if you think a how-to is needed on a particular subject.

*[[3D control]]

== Run a cutscene from a trigger ==

!!compile fails in test database due to bad core libraries, so this hasn't been tested!!

Create a script:

<dascript>
#include "events_h"
#include "global_objects_h"
#include "utility_h"

void main ()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
int nEventHandled = FALSE;
switch (nEventType)
{
case EVENT_TYPE_ENTER:
{
object oCreature = GetEventCreator(ev);
if(IsHero(oCreature)) {
resource rCutscene = R"my_cutscene.cut";
CS_LoadCutscene(rCutscene);
DestroyObject(OBJECT_SELF, 0);
}
break;
}
if (!nEventHandled) //If this event wasn't handled by this script, let the core script try
{
HandleEvent(ev, RESOURCE_SCRIPT_TRIGGER_CORE);
}
}
</dascript>

And set it as the event script for the trigger that you want to have run the cutscene.

== Add a follower to the player's party ==

<dascript>
if(IsPlayer(oCreature)) {
object oFollower = GetObjectByTag("myfollower");
UT_HireFollower(oCreature, oFollower);
}
</dascript>

Note that with Toolset v1.0.982.0, calling UT_HireFollower() will result in a follower who's unable to gain xp. This happens due to the call of
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, '''TRUE''');
to the function
void WR_SetFollowerState(object oCreature, int nState, int nSendEvent = TRUE, int nMinLevel = 0, '''int bPreventLevelup''' = FALSE)
To enable the xp gain, the flag CREATURE_REWARD_FLAGS needs to be cleared from the follower after the hired event was processed (there the flag is set). Alternatively, the relevant contents of UT_HireFollower() are to be called directly using bPreventLevelup = FALSE.

== Have an enemy play possum and then get up to fight ==

Set the creature's CREATURE_SPAWN_DEAD variable to 2.

When it's time for the creature to rise and attack, execute the following script commands:

<dascript>
#include "wrappers_h"
...
WR_SetObjectActive(oCreature, TRUE);
SetCommandable(oCreature, TRUE);
// Make sure to set this flag back to 0 to avoid problems with savegames.
SetLocalInt(oCreature, CREATURE_SPAWN_DEAD, 0);
UT_CombatStart(oCreature, oPC);
</dascript>

== Insert content into an existing area ==

If you want to add new content on to an existing area (for example, putting a new character or area transition door into an area that exists in the single-player campaign) there are two different ways to do it. One is to override the existing area with a new area of your own design that duplicates the original with the exception of your additions. This is straightforward to do but can interact poorly with other add-ons - you can only have one version of an area active at a time.

A more elegant and extensible approach is to use a [[PRCSCR]]_-prefixed M2DA. The PRCSCR M2DA has a very simple structure and a simple but profound effect:

*ID - a unique integer identifier for each row
*AreaListName - a string that identifies a specific area list, or the special keyword "any".
*Script - the name of a script file.

Whenever a player enters an area in an area list in this M2DA the associated script will be run. A modder can therefore include a script with his mod that will be run when the player enters an existing area that he didn't create. This script can freely add or remove placeables and creatures and perform whatever other modifications to the area that a script is capable of doing.

Note that the script will be run every time the player enters the area, so you'll want to have an associated plot flag to ensure that the changes are only made once.

The following example is a script that adds a new character from an add-on module to an existing area in the main game:

<dascript>
void main()
{
//Check whether we've added Joblo already.
if (WR_GetPlotFlag("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
)

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

Since you can't add [[waypoint]]s to an existing area you'll need to enter the position and orientation values for the target location manually. You can find them by creating a local copy of the area in question and temporarily adding a waypoint to copy down the coordinates and orientation you'll need.

== Add new music ==

Open up [[FMOD]]

It creates a project - set the build directory to your DA override directory - with project highlighted, it is over on the top right about half way down the project settings. You can set a default resource directory but that will just set where the file browser defaults to so it is optional. I'd also define a name in those parameters while you are there.

From there, you need a new event !!(not sure whether a blank default is generated or whether you have to right click and make a default blank event)!!. After you have an event, highlight it and change to the event tab (2nd tab). Here you need to import your file to link to that event.

On that tab I think it creates a empty row for your new event - right click and add wavetable or something like that - I think I use the top option. (Again, might be wrong but the basic goal is getting a audio file in that screen that plays when you hit the play button at the top)

Browse to your wav file or whatever you have.

From there you should be able to play the sound both in the pop-up box and (once that is closed) back in the event tab. You'll see the name of the wave in that once empty row (IIRC).

If you want, you can add layers of sounds to this event using the same process over and over, but keeping it simple; we'll just move along.

Now you have a project and an event. You can set various parameters on the first tab that alter pitch etc on the first tab. (When you import the sound, you set whether it is a one shot or looping).

Once you have that done, go to the top drop down and find build. Build the files and you should see extra files in your override directory.

From there, just open up the toolset (or hit refresh from within the toolset) and your project and event sounds should show up in the listing of sounds.

You can then drag and drop them into the game or cutscene and they will play.

== Adding music to cutscenes ==

The way we have been doing the music changes is via placed sound objects. These sound objects are generally created in [[FMOD]], and in FMOD you can say if the music will persist after the cutscene or end when the cutscene ends.

We are just using other sounds to switch music tracks. Designers can add music switch parameter to any sound in Fmod Designer, usually this is just VO line to change music track, for example:

[[Image:FMOD music switch.jpg]]

If there are no other sounds, designers can create empty sound event and add #music parameter there and place this sound on cutscene timeline.
Music track has to be defined in the same group as music in current area in “music.fdp” to work.

[[Image:FMOD music switch 2.jpg]]

<pre>
#music:name,1 – non looping, for stingers
#music:name – for looping music
</pre>

--------------
Another way
--------------

1. Open up '''FMOD''' (fmod comes with dragon age, do a search for fmod in dragon age directory)

2. '''File''' ---> '''New Project''' --> and call the project whatever you want and place it in whatever folder you want.

3. '''Double click''' the '''folder''' under '''Hierarchy''' (purple icon folder) and an event will appear beneath it. Name this event whatever you want. (If there is no event for some reason right click and add one).

4. Now click '''"Event Editor"''' Tab.

5. '''Right click''' one of the open sound fields (find it) and click '''"Add Sound"'''. (just right click all over until you see the option).

6. In this window you will see '''"LOOPING"''' and '''"ONE SHOT"''' on the right hand side. Looping will be selected by default. If you want your music to loop over & over again even after a cutscene is over leave it there. If you want your music to play ONE TIME then select "One Shot".

7. Now it's time to '''pick your music file''' by clicking '''"new wavetable"'''. '''Browse''' to your music file (wav), select it and '''press ok'''.

8. '''VERY VERY IMPORTANT'''.. '''YOU MUST DO THIS STEP'''....... Right click slightly above the timeline and click '''"ADD PARAMETER"'''.

9. Now '''right click''' your new blank parameter, look at the bottom and click '''"PARAMETER PROPERTIES"'''. Another new window will pop up.

10. '''VERY IMPORTANT'''..... Name this parameter:

#duck:music,1000,0,5000,-30

Now click ok.

11. Your new parameter should read: '''#duck:music,1000,0,5000,-30 (Primary)'''

12. Now click '''"Build"''' and do '''"build project"'''.

13. Note the new files in the directory where you saved the project.

14. Copy the '''FEV & FSB''' files from your FMOD project folder '''INTO YOUR OVERRIDE folder'''. I made a folder called music to be organized.

FMODProjectFolder/whatever.fev
FMODProjectFolder/whatever.fsb

COPY TO

Dragon Age\modules\Single Player\override\toolsetexport\music

15. Now open up '''toolset''' and navigate to '''sound palette''' and you should see your new sound file. Type the name of your sound file in the filter to find it faster. (Do not type the folder name in the filter. The filter works by filenames and not folders).

16. Open a '''cutscene''', then left click your new sound file in the right hand sound palette window to select and highlight it. (just a simple left click on it).

17. Now '''left click anywhere in your cutscene''' and a sound icon will be added which is your sound file.

'''Congrats''', 17 steps and now you've added a simple music file to your project and ready for your cutscene. *Sweats*

== Delete resources ==

Resource deletion can sometimes be a bit complicated. Check the following:

*Resources must be checked in when deleted. This is so that the toolset can be sure that all dependencies have been properly resolved.
*If other resources reference the resource it can't be deleted. This means that sometimes you'll need to delete resources in a specific order. For example, you can't delete a creature that's being used in an area, but you could delete the area and then delete the creature. Occasionally there may be circular references that you'll need to break by editing the resources before deleting them. For example:
**A stage can reference an area, which can then reference the stage.
**A plot file can have an associated event script, which will almost certainly include the plot file.
**A stage can reference a creature, which references a dialogue, which references the original stage.

== Removing Modules ==

Deleting a Module from the Toolset
Setup:
I created a module called Meep with a unique id of rcfMeep, added in one area with a waypoint, configured the starting area/waypoint info, and exported it with dependencies. And now I want to strip it out.

Step 1: Removing it from the game

* Navigate to My Documents\Bioware\AddIns
* Delete the folder called rcfMeep
* Done

Removing from the game is fairly easy. The toolset? Not so much. The reason for this is that the information is stored in the SQL Database. Now if you just want to remove the module from the Manage Modules list, that is easy.

* Open Sql Server Management Studio Express. I'm not sure if the default installation installs this or not. If not, it can be downloaded from Microsoft.
* Connect to the BWDATOOLSET server, assuming that you kept the default options.
* Expand Databases
* Expand bw_dragonage_content
* Expand Tables
* Right click and select open on the dbo.Modules table
* This will bring up an excell-like window. Find your module, right-click on the row, and select delete. Say ok to the confirmation.
* Module is now PERMANENTLY removed. Absolutely no way of recovering it.

Now depending on the size of the Module, you just orphaned a bunch of resources. Areas, placables, conversations, they all get placed into the database. And once you remove the module ID, you just lost your ability to remove these resources. Now do keep in mind that 95% of this junk is just text, so it hardly takes up any room. It's not really a major issue. However if you [[How-tos#Delete resources|delete out the resources]] within the toolset before you remove the module reference you should avoid this.

== Override Events (e.g. those in player_core) ==
Look here: [[Event override]]

== Create a lootable placeable that vanishes when looted ==

For a player-usable placeable, use the following event script to make it give its contents to the player and then vanish when clicked on.

<dascript>
#include "wrappers_h"
void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
switch (nEventType)
{
case EVENT_TYPE_USE:
{
//MoveAllItems(OBJECT_SELF, GetHero());
AddCreatureMoney (1000000, GetHero(), TRUE);
Safe_Destroy_Object(OBJECT_SELF);
}
}
}
</dascript>

If you wanted to use standard resources you could achieve the same thing (though not destroying the placeable) simply by adding "_autoloot" to the end of the placeable's tag.

== Move the player to a new area after a cutscene plays ==

Stand-alone cutscenes have an "end script" parameter that sets a script to run once the cutscene ends. Use a script such as the following:

<dascript>
void main()
{
DoAreaTransition("destination_area_tag", "destination_waypoint_tag");
}
</dascript>
[[category:tutorials]]

How-tos

2009-12-26T20:55:55Z

JackFuzz: /* Add new music */

This page lists how to accomplish tasks that are relatively simple and commonly needed, but that touch on multiple areas of the toolset or are difficult to figure out intuitively how to do.

Just collecting ideas at the moment, add headers if you think a how-to is needed on a particular subject.

*[[3D control]]

== Run a cutscene from a trigger ==

!!compile fails in test database due to bad core libraries, so this hasn't been tested!!

Create a script:

<dascript>
#include "events_h"
#include "global_objects_h"
#include "utility_h"

void main ()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
int nEventHandled = FALSE;
switch (nEventType)
{
case EVENT_TYPE_ENTER:
{
object oCreature = GetEventCreator(ev);
if(IsHero(oCreature)) {
resource rCutscene = R"my_cutscene.cut";
CS_LoadCutscene(rCutscene);
DestroyObject(OBJECT_SELF, 0);
}
break;
}
if (!nEventHandled) //If this event wasn't handled by this script, let the core script try
{
HandleEvent(ev, RESOURCE_SCRIPT_TRIGGER_CORE);
}
}
</dascript>

And set it as the event script for the trigger that you want to have run the cutscene.

== Add a follower to the player's party ==

<dascript>
if(IsPlayer(oCreature)) {
object oFollower = GetObjectByTag("myfollower");
UT_HireFollower(oCreature, oFollower);
}
</dascript>

Note that with Toolset v1.0.982.0, calling UT_HireFollower() will result in a follower who's unable to gain xp. This happens due to the call of
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, '''TRUE''');
to the function
void WR_SetFollowerState(object oCreature, int nState, int nSendEvent = TRUE, int nMinLevel = 0, '''int bPreventLevelup''' = FALSE)
To enable the xp gain, the flag CREATURE_REWARD_FLAGS needs to be cleared from the follower after the hired event was processed (there the flag is set). Alternatively, the relevant contents of UT_HireFollower() are to be called directly using bPreventLevelup = FALSE.

== Have an enemy play possum and then get up to fight ==

Set the creature's CREATURE_SPAWN_DEAD variable to 2.

When it's time for the creature to rise and attack, execute the following script commands:

<dascript>
#include "wrappers_h"
...
WR_SetObjectActive(oCreature, TRUE);
SetCommandable(oCreature, TRUE);
// Make sure to set this flag back to 0 to avoid problems with savegames.
SetLocalInt(oCreature, CREATURE_SPAWN_DEAD, 0);
UT_CombatStart(oCreature, oPC);
</dascript>

== Insert content into an existing area ==

If you want to add new content on to an existing area (for example, putting a new character or area transition door into an area that exists in the single-player campaign) there are two different ways to do it. One is to override the existing area with a new area of your own design that duplicates the original with the exception of your additions. This is straightforward to do but can interact poorly with other add-ons - you can only have one version of an area active at a time.

A more elegant and extensible approach is to use a [[PRCSCR]]_-prefixed M2DA. The PRCSCR M2DA has a very simple structure and a simple but profound effect:

*ID - a unique integer identifier for each row
*AreaListName - a string that identifies a specific area list, or the special keyword "any".
*Script - the name of a script file.

Whenever a player enters an area in an area list in this M2DA the associated script will be run. A modder can therefore include a script with his mod that will be run when the player enters an existing area that he didn't create. This script can freely add or remove placeables and creatures and perform whatever other modifications to the area that a script is capable of doing.

Note that the script will be run every time the player enters the area, so you'll want to have an associated plot flag to ensure that the changes are only made once.

The following example is a script that adds a new character from an add-on module to an existing area in the main game:

<dascript>
void main()
{
//Check whether we've added Joblo already.
if (WR_GetPlotFlag("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
)

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

Since you can't add [[waypoint]]s to an existing area you'll need to enter the position and orientation values for the target location manually. You can find them by creating a local copy of the area in question and temporarily adding a waypoint to copy down the coordinates and orientation you'll need.

== Add new music ==

Open up [[FMOD]]

It creates a project - set the build directory to your DA override directory - with project highlighted, it is over on the top right about half way down the project settings. You can set a default resource directory but that will just set where the file browser defaults to so it is optional. I'd also define a name in those parameters while you are there.

From there, you need a new event !!(not sure whether a blank default is generated or whether you have to right click and make a default blank event)!!. After you have an event, highlight it and change to the event tab (2nd tab). Here you need to import your file to link to that event.

On that tab I think it creates a empty row for your new event - right click and add wavetable or something like that - I think I use the top option. (Again, might be wrong but the basic goal is getting a audio file in that screen that plays when you hit the play button at the top)

Browse to your wav file or whatever you have.

From there you should be able to play the sound both in the pop-up box and (once that is closed) back in the event tab. You'll see the name of the wave in that once empty row (IIRC).

If you want, you can add layers of sounds to this event using the same process over and over, but keeping it simple; we'll just move along.

Now you have a project and an event. You can set various parameters on the first tab that alter pitch etc on the first tab. (When you import the sound, you set whether it is a one shot or looping).

Once you have that done, go to the top drop down and find build. Build the files and you should see extra files in your override directory.

From there, just open up the toolset (or hit refresh from within the toolset) and your project and event sounds should show up in the listing of sounds.

You can then drag and drop them into the game or cutscene and they will play.

== Adding music to cutscenes ==

The way we have been doing the music changes is via placed sound objects. These sound objects are generally created in [[FMOD]], and in FMOD you can say if the music will persist after the cutscene or end when the cutscene ends.

We are just using other sounds to switch music tracks. Designers can add music switch parameter to any sound in Fmod Designer, usually this is just VO line to change music track, for example:

[[Image:FMOD music switch.jpg]]

If there are no other sounds, designers can create empty sound event and add #music parameter there and place this sound on cutscene timeline.
Music track has to be defined in the same group as music in current area in “music.fdp” to work.

[[Image:FMOD music switch 2.jpg]]

<pre>
#music:name,1 – non looping, for stingers
#music:name – for looping music
</pre>

''Dec 26,2009 - Can someone please expand on what is said here? This part of the tutorial is extremely confusing. I've been trying to add music to a cutscene but I can't stop other music from playing alongside mine. This part of the tutorial for adding music is extremely confusing and needs more indepth instruction. For example, WHERE IS MUSIC.FDP? It's no where in my dragon age folder.

Can someone show an example of how to use:

#music:name,1 – non looping, for stingers
#music:name – for looping music ''
----------------

== Delete resources ==

Resource deletion can sometimes be a bit complicated. Check the following:

*Resources must be checked in when deleted. This is so that the toolset can be sure that all dependencies have been properly resolved.
*If other resources reference the resource it can't be deleted. This means that sometimes you'll need to delete resources in a specific order. For example, you can't delete a creature that's being used in an area, but you could delete the area and then delete the creature. Occasionally there may be circular references that you'll need to break by editing the resources before deleting them. For example:
**A stage can reference an area, which can then reference the stage.
**A plot file can have an associated event script, which will almost certainly include the plot file.
**A stage can reference a creature, which references a dialogue, which references the original stage.

== Removing Modules ==

Deleting a Module from the Toolset
Setup:
I created a module called Meep with a unique id of rcfMeep, added in one area with a waypoint, configured the starting area/waypoint info, and exported it with dependencies. And now I want to strip it out.

Step 1: Removing it from the game

* Navigate to My Documents\Bioware\AddIns
* Delete the folder called rcfMeep
* Done

Removing from the game is fairly easy. The toolset? Not so much. The reason for this is that the information is stored in the SQL Database. Now if you just want to remove the module from the Manage Modules list, that is easy.

* Open Sql Server Management Studio Express. I'm not sure if the default installation installs this or not. If not, it can be downloaded from Microsoft.
* Connect to the BWDATOOLSET server, assuming that you kept the default options.
* Expand Databases
* Expand bw_dragonage_content
* Expand Tables
* Right click and select open on the dbo.Modules table
* This will bring up an excell-like window. Find your module, right-click on the row, and select delete. Say ok to the confirmation.
* Module is now PERMANENTLY removed. Absolutely no way of recovering it.

Now depending on the size of the Module, you just orphaned a bunch of resources. Areas, placables, conversations, they all get placed into the database. And once you remove the module ID, you just lost your ability to remove these resources. Now do keep in mind that 95% of this junk is just text, so it hardly takes up any room. It's not really a major issue. However if you [[How-tos#Delete resources|delete out the resources]] within the toolset before you remove the module reference you should avoid this.

== Override Events (e.g. those in player_core) ==
Look here: [[Event override]]

== Create a lootable placeable that vanishes when looted ==

For a player-usable placeable, use the following event script to make it give its contents to the player and then vanish when clicked on.

<dascript>
#include "wrappers_h"
void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
switch (nEventType)
{
case EVENT_TYPE_USE:
{
//MoveAllItems(OBJECT_SELF, GetHero());
AddCreatureMoney (1000000, GetHero(), TRUE);
Safe_Destroy_Object(OBJECT_SELF);
}
}
}
</dascript>

If you wanted to use standard resources you could achieve the same thing (though not destroying the placeable) simply by adding "_autoloot" to the end of the placeable's tag.

== Move the player to a new area after a cutscene plays ==

Stand-alone cutscenes have an "end script" parameter that sets a script to run once the cutscene ends. Use a script such as the following:

<dascript>
void main()
{
DoAreaTransition("destination_area_tag", "destination_waypoint_tag");
}
</dascript>
[[category:tutorials]]

How-tos

2009-12-26T20:54:14Z

JackFuzz: /* Adding music to cutscenes */

This page lists how to accomplish tasks that are relatively simple and commonly needed, but that touch on multiple areas of the toolset or are difficult to figure out intuitively how to do.

Just collecting ideas at the moment, add headers if you think a how-to is needed on a particular subject.

*[[3D control]]

== Run a cutscene from a trigger ==

!!compile fails in test database due to bad core libraries, so this hasn't been tested!!

Create a script:

<dascript>
#include "events_h"
#include "global_objects_h"
#include "utility_h"

void main ()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
int nEventHandled = FALSE;
switch (nEventType)
{
case EVENT_TYPE_ENTER:
{
object oCreature = GetEventCreator(ev);
if(IsHero(oCreature)) {
resource rCutscene = R"my_cutscene.cut";
CS_LoadCutscene(rCutscene);
DestroyObject(OBJECT_SELF, 0);
}
break;
}
if (!nEventHandled) //If this event wasn't handled by this script, let the core script try
{
HandleEvent(ev, RESOURCE_SCRIPT_TRIGGER_CORE);
}
}
</dascript>

And set it as the event script for the trigger that you want to have run the cutscene.

== Add a follower to the player's party ==

<dascript>
if(IsPlayer(oCreature)) {
object oFollower = GetObjectByTag("myfollower");
UT_HireFollower(oCreature, oFollower);
}
</dascript>

Note that with Toolset v1.0.982.0, calling UT_HireFollower() will result in a follower who's unable to gain xp. This happens due to the call of
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, '''TRUE''');
to the function
void WR_SetFollowerState(object oCreature, int nState, int nSendEvent = TRUE, int nMinLevel = 0, '''int bPreventLevelup''' = FALSE)
To enable the xp gain, the flag CREATURE_REWARD_FLAGS needs to be cleared from the follower after the hired event was processed (there the flag is set). Alternatively, the relevant contents of UT_HireFollower() are to be called directly using bPreventLevelup = FALSE.

== Have an enemy play possum and then get up to fight ==

Set the creature's CREATURE_SPAWN_DEAD variable to 2.

When it's time for the creature to rise and attack, execute the following script commands:

<dascript>
#include "wrappers_h"
...
WR_SetObjectActive(oCreature, TRUE);
SetCommandable(oCreature, TRUE);
// Make sure to set this flag back to 0 to avoid problems with savegames.
SetLocalInt(oCreature, CREATURE_SPAWN_DEAD, 0);
UT_CombatStart(oCreature, oPC);
</dascript>

== Insert content into an existing area ==

If you want to add new content on to an existing area (for example, putting a new character or area transition door into an area that exists in the single-player campaign) there are two different ways to do it. One is to override the existing area with a new area of your own design that duplicates the original with the exception of your additions. This is straightforward to do but can interact poorly with other add-ons - you can only have one version of an area active at a time.

A more elegant and extensible approach is to use a [[PRCSCR]]_-prefixed M2DA. The PRCSCR M2DA has a very simple structure and a simple but profound effect:

*ID - a unique integer identifier for each row
*AreaListName - a string that identifies a specific area list, or the special keyword "any".
*Script - the name of a script file.

Whenever a player enters an area in an area list in this M2DA the associated script will be run. A modder can therefore include a script with his mod that will be run when the player enters an existing area that he didn't create. This script can freely add or remove placeables and creatures and perform whatever other modifications to the area that a script is capable of doing.

Note that the script will be run every time the player enters the area, so you'll want to have an associated plot flag to ensure that the changes are only made once.

The following example is a script that adds a new character from an add-on module to an existing area in the main game:

<dascript>
void main()
{
//Check whether we've added Joblo already.
if (WR_GetPlotFlag("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
)

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

Since you can't add [[waypoint]]s to an existing area you'll need to enter the position and orientation values for the target location manually. You can find them by creating a local copy of the area in question and temporarily adding a waypoint to copy down the coordinates and orientation you'll need.

== Add new music ==

Open up [[FMOD]]

It creates a project - set the build directory to your DA override directory - with project highlighted, it is over on the top right about half way down the project settings. You can set a default resource directory but that will just set where the file browser defaults to so it is optional. I'd also define a name in those parameters while you are there.

From there, you need a new event !!(not sure whether a blank default is generated or whether you have to right click and make a default blank event)!!. After you have an event, highlight it and change to the event tab (2nd tab). Here you need to import your file to link to that event.

On that tab I think it creates a empty row for your new event - right click and add wavetable or something like that - I think I use the top option. (Again, might be wrong but the basic goal is getting a audio file in that screen that plays when you hit the play button at the top)

Browse to your wav file or whatever you have.

From there you should be able to play the sound both in the pop-up box and (once that is closed) back in the event tab. You'll see the name of the wave in that once empty row (IIRC).

If you want, you can add layers of sounds to this event using the same process over and over, but keeping it simple; we'll just move along.

Now you have a project and an event. You can set various parameters on the first tab that alter pitch etc on the first tab. (When you import the sound, you set whether it is a one shot or looping).

Once you have that done, go to the top drop down and find build. Build the files and you should see extra files in your override directory.

From there, just open up the toolset (or hit refresh from within the toolset) and your project and event sounds should show up in the listing of sounds.

You can then drag and drop them into the game or cutscene and they will play.

----------------
Can someone please expand on what is said here? This part of the tutorial is extremely confusing. I've been trying to add music to a cutscene but I can't stop other music from playing alongside mine.
----------------

== Adding music to cutscenes ==

The way we have been doing the music changes is via placed sound objects. These sound objects are generally created in [[FMOD]], and in FMOD you can say if the music will persist after the cutscene or end when the cutscene ends.

We are just using other sounds to switch music tracks. Designers can add music switch parameter to any sound in Fmod Designer, usually this is just VO line to change music track, for example:

[[Image:FMOD music switch.jpg]]

If there are no other sounds, designers can create empty sound event and add #music parameter there and place this sound on cutscene timeline.
Music track has to be defined in the same group as music in current area in “music.fdp” to work.

[[Image:FMOD music switch 2.jpg]]

<pre>
#music:name,1 – non looping, for stingers
#music:name – for looping music
</pre>

''Dec 26,2009 - Can someone please expand on what is said here? This part of the tutorial is extremely confusing. I've been trying to add music to a cutscene but I can't stop other music from playing alongside mine. This part of the tutorial for adding music is extremely confusing and needs more indepth instruction. For example, WHERE IS MUSIC.FDP? It's no where in my dragon age folder.

Can someone show an example of how to use:

#music:name,1 – non looping, for stingers
#music:name – for looping music ''
----------------

== Delete resources ==

Resource deletion can sometimes be a bit complicated. Check the following:

*Resources must be checked in when deleted. This is so that the toolset can be sure that all dependencies have been properly resolved.
*If other resources reference the resource it can't be deleted. This means that sometimes you'll need to delete resources in a specific order. For example, you can't delete a creature that's being used in an area, but you could delete the area and then delete the creature. Occasionally there may be circular references that you'll need to break by editing the resources before deleting them. For example:
**A stage can reference an area, which can then reference the stage.
**A plot file can have an associated event script, which will almost certainly include the plot file.
**A stage can reference a creature, which references a dialogue, which references the original stage.

== Removing Modules ==

Deleting a Module from the Toolset
Setup:
I created a module called Meep with a unique id of rcfMeep, added in one area with a waypoint, configured the starting area/waypoint info, and exported it with dependencies. And now I want to strip it out.

Step 1: Removing it from the game

* Navigate to My Documents\Bioware\AddIns
* Delete the folder called rcfMeep
* Done

Removing from the game is fairly easy. The toolset? Not so much. The reason for this is that the information is stored in the SQL Database. Now if you just want to remove the module from the Manage Modules list, that is easy.

* Open Sql Server Management Studio Express. I'm not sure if the default installation installs this or not. If not, it can be downloaded from Microsoft.
* Connect to the BWDATOOLSET server, assuming that you kept the default options.
* Expand Databases
* Expand bw_dragonage_content
* Expand Tables
* Right click and select open on the dbo.Modules table
* This will bring up an excell-like window. Find your module, right-click on the row, and select delete. Say ok to the confirmation.
* Module is now PERMANENTLY removed. Absolutely no way of recovering it.

Now depending on the size of the Module, you just orphaned a bunch of resources. Areas, placables, conversations, they all get placed into the database. And once you remove the module ID, you just lost your ability to remove these resources. Now do keep in mind that 95% of this junk is just text, so it hardly takes up any room. It's not really a major issue. However if you [[How-tos#Delete resources|delete out the resources]] within the toolset before you remove the module reference you should avoid this.

== Override Events (e.g. those in player_core) ==
Look here: [[Event override]]

== Create a lootable placeable that vanishes when looted ==

For a player-usable placeable, use the following event script to make it give its contents to the player and then vanish when clicked on.

<dascript>
#include "wrappers_h"
void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
switch (nEventType)
{
case EVENT_TYPE_USE:
{
//MoveAllItems(OBJECT_SELF, GetHero());
AddCreatureMoney (1000000, GetHero(), TRUE);
Safe_Destroy_Object(OBJECT_SELF);
}
}
}
</dascript>

If you wanted to use standard resources you could achieve the same thing (though not destroying the placeable) simply by adding "_autoloot" to the end of the placeable's tag.

== Move the player to a new area after a cutscene plays ==

Stand-alone cutscenes have an "end script" parameter that sets a script to run once the cutscene ends. Use a script such as the following:

<dascript>
void main()
{
DoAreaTransition("destination_area_tag", "destination_waypoint_tag");
}
</dascript>
[[category:tutorials]]

How-tos

2009-12-26T19:34:32Z

JackFuzz: /* Adding music to cutscenes */

This page lists how to accomplish tasks that are relatively simple and commonly needed, but that touch on multiple areas of the toolset or are difficult to figure out intuitively how to do.

Just collecting ideas at the moment, add headers if you think a how-to is needed on a particular subject.

*[[3D control]]

== Run a cutscene from a trigger ==

!!compile fails in test database due to bad core libraries, so this hasn't been tested!!

Create a script:

<dascript>
#include "events_h"
#include "global_objects_h"
#include "utility_h"

void main ()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
int nEventHandled = FALSE;
switch (nEventType)
{
case EVENT_TYPE_ENTER:
{
object oCreature = GetEventCreator(ev);
if(IsHero(oCreature)) {
resource rCutscene = R"my_cutscene.cut";
CS_LoadCutscene(rCutscene);
DestroyObject(OBJECT_SELF, 0);
}
break;
}
if (!nEventHandled) //If this event wasn't handled by this script, let the core script try
{
HandleEvent(ev, RESOURCE_SCRIPT_TRIGGER_CORE);
}
}
</dascript>

And set it as the event script for the trigger that you want to have run the cutscene.

== Add a follower to the player's party ==

<dascript>
if(IsPlayer(oCreature)) {
object oFollower = GetObjectByTag("myfollower");
UT_HireFollower(oCreature, oFollower);
}
</dascript>

Note that with Toolset v1.0.982.0, calling UT_HireFollower() will result in a follower who's unable to gain xp. This happens due to the call of
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, '''TRUE''');
to the function
void WR_SetFollowerState(object oCreature, int nState, int nSendEvent = TRUE, int nMinLevel = 0, '''int bPreventLevelup''' = FALSE)
To enable the xp gain, the flag CREATURE_REWARD_FLAGS needs to be cleared from the follower after the hired event was processed (there the flag is set). Alternatively, the relevant contents of UT_HireFollower() are to be called directly using bPreventLevelup = FALSE.

== Have an enemy play possum and then get up to fight ==

Set the creature's CREATURE_SPAWN_DEAD variable to 2.

When it's time for the creature to rise and attack, execute the following script commands:

<dascript>
#include "wrappers_h"
...
WR_SetObjectActive(oCreature, TRUE);
SetCommandable(oCreature, TRUE);
// Make sure to set this flag back to 0 to avoid problems with savegames.
SetLocalInt(oCreature, CREATURE_SPAWN_DEAD, 0);
UT_CombatStart(oCreature, oPC);
</dascript>

== Insert content into an existing area ==

If you want to add new content on to an existing area (for example, putting a new character or area transition door into an area that exists in the single-player campaign) there are two different ways to do it. One is to override the existing area with a new area of your own design that duplicates the original with the exception of your additions. This is straightforward to do but can interact poorly with other add-ons - you can only have one version of an area active at a time.

A more elegant and extensible approach is to use a [[PRCSCR]]_-prefixed M2DA. The PRCSCR M2DA has a very simple structure and a simple but profound effect:

*ID - a unique integer identifier for each row
*AreaListName - a string that identifies a specific area list, or the special keyword "any".
*Script - the name of a script file.

Whenever a player enters an area in an area list in this M2DA the associated script will be run. A modder can therefore include a script with his mod that will be run when the player enters an existing area that he didn't create. This script can freely add or remove placeables and creatures and perform whatever other modifications to the area that a script is capable of doing.

Note that the script will be run every time the player enters the area, so you'll want to have an associated plot flag to ensure that the changes are only made once.

The following example is a script that adds a new character from an add-on module to an existing area in the main game:

<dascript>
void main()
{
//Check whether we've added Joblo already.
if (WR_GetPlotFlag("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
)

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

Since you can't add [[waypoint]]s to an existing area you'll need to enter the position and orientation values for the target location manually. You can find them by creating a local copy of the area in question and temporarily adding a waypoint to copy down the coordinates and orientation you'll need.

== Add new music ==

Open up [[FMOD]]

It creates a project - set the build directory to your DA override directory - with project highlighted, it is over on the top right about half way down the project settings. You can set a default resource directory but that will just set where the file browser defaults to so it is optional. I'd also define a name in those parameters while you are there.

From there, you need a new event !!(not sure whether a blank default is generated or whether you have to right click and make a default blank event)!!. After you have an event, highlight it and change to the event tab (2nd tab). Here you need to import your file to link to that event.

On that tab I think it creates a empty row for your new event - right click and add wavetable or something like that - I think I use the top option. (Again, might be wrong but the basic goal is getting a audio file in that screen that plays when you hit the play button at the top)

Browse to your wav file or whatever you have.

From there you should be able to play the sound both in the pop-up box and (once that is closed) back in the event tab. You'll see the name of the wave in that once empty row (IIRC).

If you want, you can add layers of sounds to this event using the same process over and over, but keeping it simple; we'll just move along.

Now you have a project and an event. You can set various parameters on the first tab that alter pitch etc on the first tab. (When you import the sound, you set whether it is a one shot or looping).

Once you have that done, go to the top drop down and find build. Build the files and you should see extra files in your override directory.

From there, just open up the toolset (or hit refresh from within the toolset) and your project and event sounds should show up in the listing of sounds.

You can then drag and drop them into the game or cutscene and they will play.

----------------
Can someone please expand on what is said here? This part of the tutorial is extremely confusing. I've been trying to add music to a cutscene but I can't stop other music from playing alongside mine.
----------------

== Adding music to cutscenes ==

The way we have been doing the music changes is via placed sound objects. These sound objects are generally created in [[FMOD]], and in FMOD you can say if the music will persist after the cutscene or end when the cutscene ends.

We are just using other sounds to switch music tracks. Designers can add music switch parameter to any sound in Fmod Designer, usually this is just VO line to change music track, for example:

[[Image:FMOD music switch.jpg]]

If there are no other sounds, designers can create empty sound event and add #music parameter there and place this sound on cutscene timeline.
Music track has to be defined in the same group as music in current area in “music.fdp” to work.

[[Image:FMOD music switch 2.jpg]]

<pre>
#music:name,1 – non looping, for stingers
#music:name – for looping music
</pre>

''Can someone please expand on what is said here? This part of the tutorial is extremely confusing. I've been trying to add music to a cutscene but I can't stop other music from playing alongside mine. This part of the tutorial for adding music is extremely confusing and needs more indepth instruction. For example, WHERE IS MUSIC.FDP? It's no where in my dragon age folder.

Can someone show an example of how to use:

#music:name,1 – non looping, for stingers ??
#music:name – for looping music ??

''
----------------

== Delete resources ==

Resource deletion can sometimes be a bit complicated. Check the following:

*Resources must be checked in when deleted. This is so that the toolset can be sure that all dependencies have been properly resolved.
*If other resources reference the resource it can't be deleted. This means that sometimes you'll need to delete resources in a specific order. For example, you can't delete a creature that's being used in an area, but you could delete the area and then delete the creature. Occasionally there may be circular references that you'll need to break by editing the resources before deleting them. For example:
**A stage can reference an area, which can then reference the stage.
**A plot file can have an associated event script, which will almost certainly include the plot file.
**A stage can reference a creature, which references a dialogue, which references the original stage.

== Removing Modules ==

Deleting a Module from the Toolset
Setup:
I created a module called Meep with a unique id of rcfMeep, added in one area with a waypoint, configured the starting area/waypoint info, and exported it with dependencies. And now I want to strip it out.

Step 1: Removing it from the game

* Navigate to My Documents\Bioware\AddIns
* Delete the folder called rcfMeep
* Done

Removing from the game is fairly easy. The toolset? Not so much. The reason for this is that the information is stored in the SQL Database. Now if you just want to remove the module from the Manage Modules list, that is easy.

* Open Sql Server Management Studio Express. I'm not sure if the default installation installs this or not. If not, it can be downloaded from Microsoft.
* Connect to the BWDATOOLSET server, assuming that you kept the default options.
* Expand Databases
* Expand bw_dragonage_content
* Expand Tables
* Right click and select open on the dbo.Modules table
* This will bring up an excell-like window. Find your module, right-click on the row, and select delete. Say ok to the confirmation.
* Module is now PERMANENTLY removed. Absolutely no way of recovering it.

Now depending on the size of the Module, you just orphaned a bunch of resources. Areas, placables, conversations, they all get placed into the database. And once you remove the module ID, you just lost your ability to remove these resources. Now do keep in mind that 95% of this junk is just text, so it hardly takes up any room. It's not really a major issue. However if you [[How-tos#Delete resources|delete out the resources]] within the toolset before you remove the module reference you should avoid this.

== Override Events (e.g. those in player_core) ==
Look here: [[Event override]]

== Create a lootable placeable that vanishes when looted ==

For a player-usable placeable, use the following event script to make it give its contents to the player and then vanish when clicked on.

<dascript>
#include "wrappers_h"
void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
switch (nEventType)
{
case EVENT_TYPE_USE:
{
//MoveAllItems(OBJECT_SELF, GetHero());
AddCreatureMoney (1000000, GetHero(), TRUE);
Safe_Destroy_Object(OBJECT_SELF);
}
}
}
</dascript>

If you wanted to use standard resources you could achieve the same thing (though not destroying the placeable) simply by adding "_autoloot" to the end of the placeable's tag.

== Move the player to a new area after a cutscene plays ==

Stand-alone cutscenes have an "end script" parameter that sets a script to run once the cutscene ends. Use a script such as the following:

<dascript>
void main()
{
DoAreaTransition("destination_area_tag", "destination_waypoint_tag");
}
</dascript>
[[category:tutorials]]

How-tos

2009-12-26T19:25:55Z

JackFuzz: /* Adding music to cutscenes */

This page lists how to accomplish tasks that are relatively simple and commonly needed, but that touch on multiple areas of the toolset or are difficult to figure out intuitively how to do.

Just collecting ideas at the moment, add headers if you think a how-to is needed on a particular subject.

*[[3D control]]

== Run a cutscene from a trigger ==

!!compile fails in test database due to bad core libraries, so this hasn't been tested!!

Create a script:

<dascript>
#include "events_h"
#include "global_objects_h"
#include "utility_h"

void main ()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
int nEventHandled = FALSE;
switch (nEventType)
{
case EVENT_TYPE_ENTER:
{
object oCreature = GetEventCreator(ev);
if(IsHero(oCreature)) {
resource rCutscene = R"my_cutscene.cut";
CS_LoadCutscene(rCutscene);
DestroyObject(OBJECT_SELF, 0);
}
break;
}
if (!nEventHandled) //If this event wasn't handled by this script, let the core script try
{
HandleEvent(ev, RESOURCE_SCRIPT_TRIGGER_CORE);
}
}
</dascript>

And set it as the event script for the trigger that you want to have run the cutscene.

== Add a follower to the player's party ==

<dascript>
if(IsPlayer(oCreature)) {
object oFollower = GetObjectByTag("myfollower");
UT_HireFollower(oCreature, oFollower);
}
</dascript>

Note that with Toolset v1.0.982.0, calling UT_HireFollower() will result in a follower who's unable to gain xp. This happens due to the call of
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, '''TRUE''');
to the function
void WR_SetFollowerState(object oCreature, int nState, int nSendEvent = TRUE, int nMinLevel = 0, '''int bPreventLevelup''' = FALSE)
To enable the xp gain, the flag CREATURE_REWARD_FLAGS needs to be cleared from the follower after the hired event was processed (there the flag is set). Alternatively, the relevant contents of UT_HireFollower() are to be called directly using bPreventLevelup = FALSE.

== Have an enemy play possum and then get up to fight ==

Set the creature's CREATURE_SPAWN_DEAD variable to 2.

When it's time for the creature to rise and attack, execute the following script commands:

<dascript>
#include "wrappers_h"
...
WR_SetObjectActive(oCreature, TRUE);
SetCommandable(oCreature, TRUE);
// Make sure to set this flag back to 0 to avoid problems with savegames.
SetLocalInt(oCreature, CREATURE_SPAWN_DEAD, 0);
UT_CombatStart(oCreature, oPC);
</dascript>

== Insert content into an existing area ==

If you want to add new content on to an existing area (for example, putting a new character or area transition door into an area that exists in the single-player campaign) there are two different ways to do it. One is to override the existing area with a new area of your own design that duplicates the original with the exception of your additions. This is straightforward to do but can interact poorly with other add-ons - you can only have one version of an area active at a time.

A more elegant and extensible approach is to use a [[PRCSCR]]_-prefixed M2DA. The PRCSCR M2DA has a very simple structure and a simple but profound effect:

*ID - a unique integer identifier for each row
*AreaListName - a string that identifies a specific area list, or the special keyword "any".
*Script - the name of a script file.

Whenever a player enters an area in an area list in this M2DA the associated script will be run. A modder can therefore include a script with his mod that will be run when the player enters an existing area that he didn't create. This script can freely add or remove placeables and creatures and perform whatever other modifications to the area that a script is capable of doing.

Note that the script will be run every time the player enters the area, so you'll want to have an associated plot flag to ensure that the changes are only made once.

The following example is a script that adds a new character from an add-on module to an existing area in the main game:

<dascript>
void main()
{
//Check whether we've added Joblo already.
if (WR_GetPlotFlag("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
)

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

Since you can't add [[waypoint]]s to an existing area you'll need to enter the position and orientation values for the target location manually. You can find them by creating a local copy of the area in question and temporarily adding a waypoint to copy down the coordinates and orientation you'll need.

== Add new music ==

Open up [[FMOD]]

It creates a project - set the build directory to your DA override directory - with project highlighted, it is over on the top right about half way down the project settings. You can set a default resource directory but that will just set where the file browser defaults to so it is optional. I'd also define a name in those parameters while you are there.

From there, you need a new event !!(not sure whether a blank default is generated or whether you have to right click and make a default blank event)!!. After you have an event, highlight it and change to the event tab (2nd tab). Here you need to import your file to link to that event.

On that tab I think it creates a empty row for your new event - right click and add wavetable or something like that - I think I use the top option. (Again, might be wrong but the basic goal is getting a audio file in that screen that plays when you hit the play button at the top)

Browse to your wav file or whatever you have.

From there you should be able to play the sound both in the pop-up box and (once that is closed) back in the event tab. You'll see the name of the wave in that once empty row (IIRC).

If you want, you can add layers of sounds to this event using the same process over and over, but keeping it simple; we'll just move along.

Now you have a project and an event. You can set various parameters on the first tab that alter pitch etc on the first tab. (When you import the sound, you set whether it is a one shot or looping).

Once you have that done, go to the top drop down and find build. Build the files and you should see extra files in your override directory.

From there, just open up the toolset (or hit refresh from within the toolset) and your project and event sounds should show up in the listing of sounds.

You can then drag and drop them into the game or cutscene and they will play.

----------------
Can someone please expand on what is said here? This part of the tutorial is extremely confusing. I've been trying to add music to a cutscene but I can't stop other music from playing alongside mine.
----------------

== Adding music to cutscenes ==

The way we have been doing the music changes is via placed sound objects. These sound objects are generally created in [[FMOD]], and in FMOD you can say if the music will persist after the cutscene or end when the cutscene ends.

We are just using other sounds to switch music tracks. Designers can add music switch parameter to any sound in Fmod Designer, usually this is just VO line to change music track, for example:

[[Image:FMOD music switch.jpg]]

If there are no other sounds, designers can create empty sound event and add #music parameter there and place this sound on cutscene timeline.
Music track has to be defined in the same group as music in current area in “music.fdp” to work.

[[Image:FMOD music switch 2.jpg]]

<pre>
#music:name,1 – non looping, for stingers
#music:name – for looping music
</pre>

''Can someone please expand on what is said here? This part of the tutorial is extremely confusing. I've been trying to add music to a cutscene but I can't stop other music from playing alongside mine. This part of the tutorial for adding music is extremely confusing and needs more indepth instruction. For example, WHERE IS MUSIC.FDP? It's no where in my dragon age folder.''
----------------

== Delete resources ==

Resource deletion can sometimes be a bit complicated. Check the following:

*Resources must be checked in when deleted. This is so that the toolset can be sure that all dependencies have been properly resolved.
*If other resources reference the resource it can't be deleted. This means that sometimes you'll need to delete resources in a specific order. For example, you can't delete a creature that's being used in an area, but you could delete the area and then delete the creature. Occasionally there may be circular references that you'll need to break by editing the resources before deleting them. For example:
**A stage can reference an area, which can then reference the stage.
**A plot file can have an associated event script, which will almost certainly include the plot file.
**A stage can reference a creature, which references a dialogue, which references the original stage.

== Removing Modules ==

Deleting a Module from the Toolset
Setup:
I created a module called Meep with a unique id of rcfMeep, added in one area with a waypoint, configured the starting area/waypoint info, and exported it with dependencies. And now I want to strip it out.

Step 1: Removing it from the game

* Navigate to My Documents\Bioware\AddIns
* Delete the folder called rcfMeep
* Done

Removing from the game is fairly easy. The toolset? Not so much. The reason for this is that the information is stored in the SQL Database. Now if you just want to remove the module from the Manage Modules list, that is easy.

* Open Sql Server Management Studio Express. I'm not sure if the default installation installs this or not. If not, it can be downloaded from Microsoft.
* Connect to the BWDATOOLSET server, assuming that you kept the default options.
* Expand Databases
* Expand bw_dragonage_content
* Expand Tables
* Right click and select open on the dbo.Modules table
* This will bring up an excell-like window. Find your module, right-click on the row, and select delete. Say ok to the confirmation.
* Module is now PERMANENTLY removed. Absolutely no way of recovering it.

Now depending on the size of the Module, you just orphaned a bunch of resources. Areas, placables, conversations, they all get placed into the database. And once you remove the module ID, you just lost your ability to remove these resources. Now do keep in mind that 95% of this junk is just text, so it hardly takes up any room. It's not really a major issue. However if you [[How-tos#Delete resources|delete out the resources]] within the toolset before you remove the module reference you should avoid this.

== Override Events (e.g. those in player_core) ==
Look here: [[Event override]]

== Create a lootable placeable that vanishes when looted ==

For a player-usable placeable, use the following event script to make it give its contents to the player and then vanish when clicked on.

<dascript>
#include "wrappers_h"
void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
switch (nEventType)
{
case EVENT_TYPE_USE:
{
//MoveAllItems(OBJECT_SELF, GetHero());
AddCreatureMoney (1000000, GetHero(), TRUE);
Safe_Destroy_Object(OBJECT_SELF);
}
}
}
</dascript>

If you wanted to use standard resources you could achieve the same thing (though not destroying the placeable) simply by adding "_autoloot" to the end of the placeable's tag.

== Move the player to a new area after a cutscene plays ==

Stand-alone cutscenes have an "end script" parameter that sets a script to run once the cutscene ends. Use a script such as the following:

<dascript>
void main()
{
DoAreaTransition("destination_area_tag", "destination_waypoint_tag");
}
</dascript>
[[category:tutorials]]

How-tos

2009-12-26T19:25:01Z

JackFuzz: /* Adding music to cutscenes */

This page lists how to accomplish tasks that are relatively simple and commonly needed, but that touch on multiple areas of the toolset or are difficult to figure out intuitively how to do.

Just collecting ideas at the moment, add headers if you think a how-to is needed on a particular subject.

*[[3D control]]

== Run a cutscene from a trigger ==

!!compile fails in test database due to bad core libraries, so this hasn't been tested!!

Create a script:

<dascript>
#include "events_h"
#include "global_objects_h"
#include "utility_h"

void main ()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
int nEventHandled = FALSE;
switch (nEventType)
{
case EVENT_TYPE_ENTER:
{
object oCreature = GetEventCreator(ev);
if(IsHero(oCreature)) {
resource rCutscene = R"my_cutscene.cut";
CS_LoadCutscene(rCutscene);
DestroyObject(OBJECT_SELF, 0);
}
break;
}
if (!nEventHandled) //If this event wasn't handled by this script, let the core script try
{
HandleEvent(ev, RESOURCE_SCRIPT_TRIGGER_CORE);
}
}
</dascript>

And set it as the event script for the trigger that you want to have run the cutscene.

== Add a follower to the player's party ==

<dascript>
if(IsPlayer(oCreature)) {
object oFollower = GetObjectByTag("myfollower");
UT_HireFollower(oCreature, oFollower);
}
</dascript>

Note that with Toolset v1.0.982.0, calling UT_HireFollower() will result in a follower who's unable to gain xp. This happens due to the call of
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, '''TRUE''');
to the function
void WR_SetFollowerState(object oCreature, int nState, int nSendEvent = TRUE, int nMinLevel = 0, '''int bPreventLevelup''' = FALSE)
To enable the xp gain, the flag CREATURE_REWARD_FLAGS needs to be cleared from the follower after the hired event was processed (there the flag is set). Alternatively, the relevant contents of UT_HireFollower() are to be called directly using bPreventLevelup = FALSE.

== Have an enemy play possum and then get up to fight ==

Set the creature's CREATURE_SPAWN_DEAD variable to 2.

When it's time for the creature to rise and attack, execute the following script commands:

<dascript>
#include "wrappers_h"
...
WR_SetObjectActive(oCreature, TRUE);
SetCommandable(oCreature, TRUE);
// Make sure to set this flag back to 0 to avoid problems with savegames.
SetLocalInt(oCreature, CREATURE_SPAWN_DEAD, 0);
UT_CombatStart(oCreature, oPC);
</dascript>

== Insert content into an existing area ==

If you want to add new content on to an existing area (for example, putting a new character or area transition door into an area that exists in the single-player campaign) there are two different ways to do it. One is to override the existing area with a new area of your own design that duplicates the original with the exception of your additions. This is straightforward to do but can interact poorly with other add-ons - you can only have one version of an area active at a time.

A more elegant and extensible approach is to use a [[PRCSCR]]_-prefixed M2DA. The PRCSCR M2DA has a very simple structure and a simple but profound effect:

*ID - a unique integer identifier for each row
*AreaListName - a string that identifies a specific area list, or the special keyword "any".
*Script - the name of a script file.

Whenever a player enters an area in an area list in this M2DA the associated script will be run. A modder can therefore include a script with his mod that will be run when the player enters an existing area that he didn't create. This script can freely add or remove placeables and creatures and perform whatever other modifications to the area that a script is capable of doing.

Note that the script will be run every time the player enters the area, so you'll want to have an associated plot flag to ensure that the changes are only made once.

The following example is a script that adds a new character from an add-on module to an existing area in the main game:

<dascript>
void main()
{
//Check whether we've added Joblo already.
if (WR_GetPlotFlag("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
)

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

Since you can't add [[waypoint]]s to an existing area you'll need to enter the position and orientation values for the target location manually. You can find them by creating a local copy of the area in question and temporarily adding a waypoint to copy down the coordinates and orientation you'll need.

== Add new music ==

Open up [[FMOD]]

It creates a project - set the build directory to your DA override directory - with project highlighted, it is over on the top right about half way down the project settings. You can set a default resource directory but that will just set where the file browser defaults to so it is optional. I'd also define a name in those parameters while you are there.

From there, you need a new event !!(not sure whether a blank default is generated or whether you have to right click and make a default blank event)!!. After you have an event, highlight it and change to the event tab (2nd tab). Here you need to import your file to link to that event.

On that tab I think it creates a empty row for your new event - right click and add wavetable or something like that - I think I use the top option. (Again, might be wrong but the basic goal is getting a audio file in that screen that plays when you hit the play button at the top)

Browse to your wav file or whatever you have.

From there you should be able to play the sound both in the pop-up box and (once that is closed) back in the event tab. You'll see the name of the wave in that once empty row (IIRC).

If you want, you can add layers of sounds to this event using the same process over and over, but keeping it simple; we'll just move along.

Now you have a project and an event. You can set various parameters on the first tab that alter pitch etc on the first tab. (When you import the sound, you set whether it is a one shot or looping).

Once you have that done, go to the top drop down and find build. Build the files and you should see extra files in your override directory.

From there, just open up the toolset (or hit refresh from within the toolset) and your project and event sounds should show up in the listing of sounds.

You can then drag and drop them into the game or cutscene and they will play.

----------------
Can someone please expand on what is said here? This part of the tutorial is extremely confusing. I've been trying to add music to a cutscene but I can't stop other music from playing alongside mine.
----------------

== Adding music to cutscenes ==

The way we have been doing the music changes is via placed sound objects. These sound objects are generally created in [[FMOD]], and in FMOD you can say if the music will persist after the cutscene or end when the cutscene ends.

We are just using other sounds to switch music tracks. Designers can add music switch parameter to any sound in Fmod Designer, usually this is just VO line to change music track, for example:

[[Image:FMOD music switch.jpg]]

If there are no other sounds, designers can create empty sound event and add #music parameter there and place this sound on cutscene timeline.
Music track has to be defined in the same group as music in current area in “music.fdp” to work.

[[Image:FMOD music switch 2.jpg]]

<pre>
#music:name,1 – non looping, for stingers
#music:name – for looping music
</pre>

''Can someone please expand on what is said here? This part of the tutorial is extremely confusing. I've been trying to add music to a cutscene but I can't stop other music from playing alongside mine. This part of the tutorial for adding music is extremely confusing and needs more indepth instruction.''
----------------

== Delete resources ==

Resource deletion can sometimes be a bit complicated. Check the following:

*Resources must be checked in when deleted. This is so that the toolset can be sure that all dependencies have been properly resolved.
*If other resources reference the resource it can't be deleted. This means that sometimes you'll need to delete resources in a specific order. For example, you can't delete a creature that's being used in an area, but you could delete the area and then delete the creature. Occasionally there may be circular references that you'll need to break by editing the resources before deleting them. For example:
**A stage can reference an area, which can then reference the stage.
**A plot file can have an associated event script, which will almost certainly include the plot file.
**A stage can reference a creature, which references a dialogue, which references the original stage.

== Removing Modules ==

Deleting a Module from the Toolset
Setup:
I created a module called Meep with a unique id of rcfMeep, added in one area with a waypoint, configured the starting area/waypoint info, and exported it with dependencies. And now I want to strip it out.

Step 1: Removing it from the game

* Navigate to My Documents\Bioware\AddIns
* Delete the folder called rcfMeep
* Done

Removing from the game is fairly easy. The toolset? Not so much. The reason for this is that the information is stored in the SQL Database. Now if you just want to remove the module from the Manage Modules list, that is easy.

* Open Sql Server Management Studio Express. I'm not sure if the default installation installs this or not. If not, it can be downloaded from Microsoft.
* Connect to the BWDATOOLSET server, assuming that you kept the default options.
* Expand Databases
* Expand bw_dragonage_content
* Expand Tables
* Right click and select open on the dbo.Modules table
* This will bring up an excell-like window. Find your module, right-click on the row, and select delete. Say ok to the confirmation.
* Module is now PERMANENTLY removed. Absolutely no way of recovering it.

Now depending on the size of the Module, you just orphaned a bunch of resources. Areas, placables, conversations, they all get placed into the database. And once you remove the module ID, you just lost your ability to remove these resources. Now do keep in mind that 95% of this junk is just text, so it hardly takes up any room. It's not really a major issue. However if you [[How-tos#Delete resources|delete out the resources]] within the toolset before you remove the module reference you should avoid this.

== Override Events (e.g. those in player_core) ==
Look here: [[Event override]]

== Create a lootable placeable that vanishes when looted ==

For a player-usable placeable, use the following event script to make it give its contents to the player and then vanish when clicked on.

<dascript>
#include "wrappers_h"
void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
switch (nEventType)
{
case EVENT_TYPE_USE:
{
//MoveAllItems(OBJECT_SELF, GetHero());
AddCreatureMoney (1000000, GetHero(), TRUE);
Safe_Destroy_Object(OBJECT_SELF);
}
}
}
</dascript>

If you wanted to use standard resources you could achieve the same thing (though not destroying the placeable) simply by adding "_autoloot" to the end of the placeable's tag.

== Move the player to a new area after a cutscene plays ==

Stand-alone cutscenes have an "end script" parameter that sets a script to run once the cutscene ends. Use a script such as the following:

<dascript>
void main()
{
DoAreaTransition("destination_area_tag", "destination_waypoint_tag");
}
</dascript>
[[category:tutorials]]

How-tos

2009-12-26T19:24:29Z

JackFuzz: /* Adding music to cutscenes */

This page lists how to accomplish tasks that are relatively simple and commonly needed, but that touch on multiple areas of the toolset or are difficult to figure out intuitively how to do.

Just collecting ideas at the moment, add headers if you think a how-to is needed on a particular subject.

*[[3D control]]

== Run a cutscene from a trigger ==

!!compile fails in test database due to bad core libraries, so this hasn't been tested!!

Create a script:

<dascript>
#include "events_h"
#include "global_objects_h"
#include "utility_h"

void main ()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
int nEventHandled = FALSE;
switch (nEventType)
{
case EVENT_TYPE_ENTER:
{
object oCreature = GetEventCreator(ev);
if(IsHero(oCreature)) {
resource rCutscene = R"my_cutscene.cut";
CS_LoadCutscene(rCutscene);
DestroyObject(OBJECT_SELF, 0);
}
break;
}
if (!nEventHandled) //If this event wasn't handled by this script, let the core script try
{
HandleEvent(ev, RESOURCE_SCRIPT_TRIGGER_CORE);
}
}
</dascript>

And set it as the event script for the trigger that you want to have run the cutscene.

== Add a follower to the player's party ==

<dascript>
if(IsPlayer(oCreature)) {
object oFollower = GetObjectByTag("myfollower");
UT_HireFollower(oCreature, oFollower);
}
</dascript>

Note that with Toolset v1.0.982.0, calling UT_HireFollower() will result in a follower who's unable to gain xp. This happens due to the call of
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, '''TRUE''');
to the function
void WR_SetFollowerState(object oCreature, int nState, int nSendEvent = TRUE, int nMinLevel = 0, '''int bPreventLevelup''' = FALSE)
To enable the xp gain, the flag CREATURE_REWARD_FLAGS needs to be cleared from the follower after the hired event was processed (there the flag is set). Alternatively, the relevant contents of UT_HireFollower() are to be called directly using bPreventLevelup = FALSE.

== Have an enemy play possum and then get up to fight ==

Set the creature's CREATURE_SPAWN_DEAD variable to 2.

When it's time for the creature to rise and attack, execute the following script commands:

<dascript>
#include "wrappers_h"
...
WR_SetObjectActive(oCreature, TRUE);
SetCommandable(oCreature, TRUE);
// Make sure to set this flag back to 0 to avoid problems with savegames.
SetLocalInt(oCreature, CREATURE_SPAWN_DEAD, 0);
UT_CombatStart(oCreature, oPC);
</dascript>

== Insert content into an existing area ==

If you want to add new content on to an existing area (for example, putting a new character or area transition door into an area that exists in the single-player campaign) there are two different ways to do it. One is to override the existing area with a new area of your own design that duplicates the original with the exception of your additions. This is straightforward to do but can interact poorly with other add-ons - you can only have one version of an area active at a time.

A more elegant and extensible approach is to use a [[PRCSCR]]_-prefixed M2DA. The PRCSCR M2DA has a very simple structure and a simple but profound effect:

*ID - a unique integer identifier for each row
*AreaListName - a string that identifies a specific area list, or the special keyword "any".
*Script - the name of a script file.

Whenever a player enters an area in an area list in this M2DA the associated script will be run. A modder can therefore include a script with his mod that will be run when the player enters an existing area that he didn't create. This script can freely add or remove placeables and creatures and perform whatever other modifications to the area that a script is capable of doing.

Note that the script will be run every time the player enters the area, so you'll want to have an associated plot flag to ensure that the changes are only made once.

The following example is a script that adds a new character from an add-on module to an existing area in the main game:

<dascript>
void main()
{
//Check whether we've added Joblo already.
if (WR_GetPlotFlag("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
)

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

Since you can't add [[waypoint]]s to an existing area you'll need to enter the position and orientation values for the target location manually. You can find them by creating a local copy of the area in question and temporarily adding a waypoint to copy down the coordinates and orientation you'll need.

== Add new music ==

Open up [[FMOD]]

It creates a project - set the build directory to your DA override directory - with project highlighted, it is over on the top right about half way down the project settings. You can set a default resource directory but that will just set where the file browser defaults to so it is optional. I'd also define a name in those parameters while you are there.

From there, you need a new event !!(not sure whether a blank default is generated or whether you have to right click and make a default blank event)!!. After you have an event, highlight it and change to the event tab (2nd tab). Here you need to import your file to link to that event.

On that tab I think it creates a empty row for your new event - right click and add wavetable or something like that - I think I use the top option. (Again, might be wrong but the basic goal is getting a audio file in that screen that plays when you hit the play button at the top)

Browse to your wav file or whatever you have.

From there you should be able to play the sound both in the pop-up box and (once that is closed) back in the event tab. You'll see the name of the wave in that once empty row (IIRC).

If you want, you can add layers of sounds to this event using the same process over and over, but keeping it simple; we'll just move along.

Now you have a project and an event. You can set various parameters on the first tab that alter pitch etc on the first tab. (When you import the sound, you set whether it is a one shot or looping).

Once you have that done, go to the top drop down and find build. Build the files and you should see extra files in your override directory.

From there, just open up the toolset (or hit refresh from within the toolset) and your project and event sounds should show up in the listing of sounds.

You can then drag and drop them into the game or cutscene and they will play.

----------------
Can someone please expand on what is said here? This part of the tutorial is extremely confusing. I've been trying to add music to a cutscene but I can't stop other music from playing alongside mine.
----------------

== Adding music to cutscenes ==

The way we have been doing the music changes is via placed sound objects. These sound objects are generally created in [[FMOD]], and in FMOD you can say if the music will persist after the cutscene or end when the cutscene ends.

We are just using other sounds to switch music tracks. Designers can add music switch parameter to any sound in Fmod Designer, usually this is just VO line to change music track, for example:

[[Image:FMOD music switch.jpg]]

If there are no other sounds, designers can create empty sound event and add #music parameter there and place this sound on cutscene timeline.
Music track has to be defined in the same group as music in current area in “music.fdp” to work.

[[Image:FMOD music switch 2.jpg]]

<pre>
#music:name,1 – non looping, for stingers
#music:name – for looping music
</pre>

''Can someone please expand on what is said here? This part of the tutorial is extremely confusing. I've been trying to add music to a cutscene but I can't stop other music from playing alongside mine.''
----------------

== Delete resources ==

Resource deletion can sometimes be a bit complicated. Check the following:

*Resources must be checked in when deleted. This is so that the toolset can be sure that all dependencies have been properly resolved.
*If other resources reference the resource it can't be deleted. This means that sometimes you'll need to delete resources in a specific order. For example, you can't delete a creature that's being used in an area, but you could delete the area and then delete the creature. Occasionally there may be circular references that you'll need to break by editing the resources before deleting them. For example:
**A stage can reference an area, which can then reference the stage.
**A plot file can have an associated event script, which will almost certainly include the plot file.
**A stage can reference a creature, which references a dialogue, which references the original stage.

== Removing Modules ==

Deleting a Module from the Toolset
Setup:
I created a module called Meep with a unique id of rcfMeep, added in one area with a waypoint, configured the starting area/waypoint info, and exported it with dependencies. And now I want to strip it out.

Step 1: Removing it from the game

* Navigate to My Documents\Bioware\AddIns
* Delete the folder called rcfMeep
* Done

Removing from the game is fairly easy. The toolset? Not so much. The reason for this is that the information is stored in the SQL Database. Now if you just want to remove the module from the Manage Modules list, that is easy.

* Open Sql Server Management Studio Express. I'm not sure if the default installation installs this or not. If not, it can be downloaded from Microsoft.
* Connect to the BWDATOOLSET server, assuming that you kept the default options.
* Expand Databases
* Expand bw_dragonage_content
* Expand Tables
* Right click and select open on the dbo.Modules table
* This will bring up an excell-like window. Find your module, right-click on the row, and select delete. Say ok to the confirmation.
* Module is now PERMANENTLY removed. Absolutely no way of recovering it.

Now depending on the size of the Module, you just orphaned a bunch of resources. Areas, placables, conversations, they all get placed into the database. And once you remove the module ID, you just lost your ability to remove these resources. Now do keep in mind that 95% of this junk is just text, so it hardly takes up any room. It's not really a major issue. However if you [[How-tos#Delete resources|delete out the resources]] within the toolset before you remove the module reference you should avoid this.

== Override Events (e.g. those in player_core) ==
Look here: [[Event override]]

== Create a lootable placeable that vanishes when looted ==

For a player-usable placeable, use the following event script to make it give its contents to the player and then vanish when clicked on.

<dascript>
#include "wrappers_h"
void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
switch (nEventType)
{
case EVENT_TYPE_USE:
{
//MoveAllItems(OBJECT_SELF, GetHero());
AddCreatureMoney (1000000, GetHero(), TRUE);
Safe_Destroy_Object(OBJECT_SELF);
}
}
}
</dascript>

If you wanted to use standard resources you could achieve the same thing (though not destroying the placeable) simply by adding "_autoloot" to the end of the placeable's tag.

== Move the player to a new area after a cutscene plays ==

Stand-alone cutscenes have an "end script" parameter that sets a script to run once the cutscene ends. Use a script such as the following:

<dascript>
void main()
{
DoAreaTransition("destination_area_tag", "destination_waypoint_tag");
}
</dascript>
[[category:tutorials]]

How-tos

2009-12-26T19:23:46Z

JackFuzz: /* Adding music to cutscenes */

This page lists how to accomplish tasks that are relatively simple and commonly needed, but that touch on multiple areas of the toolset or are difficult to figure out intuitively how to do.

Just collecting ideas at the moment, add headers if you think a how-to is needed on a particular subject.

*[[3D control]]

== Run a cutscene from a trigger ==

!!compile fails in test database due to bad core libraries, so this hasn't been tested!!

Create a script:

<dascript>
#include "events_h"
#include "global_objects_h"
#include "utility_h"

void main ()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
int nEventHandled = FALSE;
switch (nEventType)
{
case EVENT_TYPE_ENTER:
{
object oCreature = GetEventCreator(ev);
if(IsHero(oCreature)) {
resource rCutscene = R"my_cutscene.cut";
CS_LoadCutscene(rCutscene);
DestroyObject(OBJECT_SELF, 0);
}
break;
}
if (!nEventHandled) //If this event wasn't handled by this script, let the core script try
{
HandleEvent(ev, RESOURCE_SCRIPT_TRIGGER_CORE);
}
}
</dascript>

And set it as the event script for the trigger that you want to have run the cutscene.

== Add a follower to the player's party ==

<dascript>
if(IsPlayer(oCreature)) {
object oFollower = GetObjectByTag("myfollower");
UT_HireFollower(oCreature, oFollower);
}
</dascript>

Note that with Toolset v1.0.982.0, calling UT_HireFollower() will result in a follower who's unable to gain xp. This happens due to the call of
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, '''TRUE''');
to the function
void WR_SetFollowerState(object oCreature, int nState, int nSendEvent = TRUE, int nMinLevel = 0, '''int bPreventLevelup''' = FALSE)
To enable the xp gain, the flag CREATURE_REWARD_FLAGS needs to be cleared from the follower after the hired event was processed (there the flag is set). Alternatively, the relevant contents of UT_HireFollower() are to be called directly using bPreventLevelup = FALSE.

== Have an enemy play possum and then get up to fight ==

Set the creature's CREATURE_SPAWN_DEAD variable to 2.

When it's time for the creature to rise and attack, execute the following script commands:

<dascript>
#include "wrappers_h"
...
WR_SetObjectActive(oCreature, TRUE);
SetCommandable(oCreature, TRUE);
// Make sure to set this flag back to 0 to avoid problems with savegames.
SetLocalInt(oCreature, CREATURE_SPAWN_DEAD, 0);
UT_CombatStart(oCreature, oPC);
</dascript>

== Insert content into an existing area ==

If you want to add new content on to an existing area (for example, putting a new character or area transition door into an area that exists in the single-player campaign) there are two different ways to do it. One is to override the existing area with a new area of your own design that duplicates the original with the exception of your additions. This is straightforward to do but can interact poorly with other add-ons - you can only have one version of an area active at a time.

A more elegant and extensible approach is to use a [[PRCSCR]]_-prefixed M2DA. The PRCSCR M2DA has a very simple structure and a simple but profound effect:

*ID - a unique integer identifier for each row
*AreaListName - a string that identifies a specific area list, or the special keyword "any".
*Script - the name of a script file.

Whenever a player enters an area in an area list in this M2DA the associated script will be run. A modder can therefore include a script with his mod that will be run when the player enters an existing area that he didn't create. This script can freely add or remove placeables and creatures and perform whatever other modifications to the area that a script is capable of doing.

Note that the script will be run every time the player enters the area, so you'll want to have an associated plot flag to ensure that the changes are only made once.

The following example is a script that adds a new character from an add-on module to an existing area in the main game:

<dascript>
void main()
{
//Check whether we've added Joblo already.
if (WR_GetPlotFlag("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
)

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

Since you can't add [[waypoint]]s to an existing area you'll need to enter the position and orientation values for the target location manually. You can find them by creating a local copy of the area in question and temporarily adding a waypoint to copy down the coordinates and orientation you'll need.

== Add new music ==

Open up [[FMOD]]

It creates a project - set the build directory to your DA override directory - with project highlighted, it is over on the top right about half way down the project settings. You can set a default resource directory but that will just set where the file browser defaults to so it is optional. I'd also define a name in those parameters while you are there.

From there, you need a new event !!(not sure whether a blank default is generated or whether you have to right click and make a default blank event)!!. After you have an event, highlight it and change to the event tab (2nd tab). Here you need to import your file to link to that event.

On that tab I think it creates a empty row for your new event - right click and add wavetable or something like that - I think I use the top option. (Again, might be wrong but the basic goal is getting a audio file in that screen that plays when you hit the play button at the top)

Browse to your wav file or whatever you have.

From there you should be able to play the sound both in the pop-up box and (once that is closed) back in the event tab. You'll see the name of the wave in that once empty row (IIRC).

If you want, you can add layers of sounds to this event using the same process over and over, but keeping it simple; we'll just move along.

Now you have a project and an event. You can set various parameters on the first tab that alter pitch etc on the first tab. (When you import the sound, you set whether it is a one shot or looping).

Once you have that done, go to the top drop down and find build. Build the files and you should see extra files in your override directory.

From there, just open up the toolset (or hit refresh from within the toolset) and your project and event sounds should show up in the listing of sounds.

You can then drag and drop them into the game or cutscene and they will play.

----------------
Can someone please expand on what is said here? This part of the tutorial is extremely confusing. I've been trying to add music to a cutscene but I can't stop other music from playing alongside mine.
----------------

== Adding music to cutscenes ==

The way we have been doing the music changes is via placed sound objects. These sound objects are generally created in [[FMOD]], and in FMOD you can say if the music will persist after the cutscene or end when the cutscene ends.

We are just using other sounds to switch music tracks. Designers can add music switch parameter to any sound in Fmod Designer, usually this is just VO line to change music track, for example:

[[Image:FMOD music switch.jpg]]

If there are no other sounds, designers can create empty sound event and add #music parameter there and place this sound on cutscene timeline.
Music track has to be defined in the same group as music in current area in “music.fdp” to work.

[[Image:FMOD music switch 2.jpg]]

<pre>
#music:name,1 – non looping, for stingers
#music:name – for looping music
</pre>

== Delete resources ==

Resource deletion can sometimes be a bit complicated. Check the following:

*Resources must be checked in when deleted. This is so that the toolset can be sure that all dependencies have been properly resolved.
*If other resources reference the resource it can't be deleted. This means that sometimes you'll need to delete resources in a specific order. For example, you can't delete a creature that's being used in an area, but you could delete the area and then delete the creature. Occasionally there may be circular references that you'll need to break by editing the resources before deleting them. For example:
**A stage can reference an area, which can then reference the stage.
**A plot file can have an associated event script, which will almost certainly include the plot file.
**A stage can reference a creature, which references a dialogue, which references the original stage.

== Removing Modules ==

Deleting a Module from the Toolset
Setup:
I created a module called Meep with a unique id of rcfMeep, added in one area with a waypoint, configured the starting area/waypoint info, and exported it with dependencies. And now I want to strip it out.

Step 1: Removing it from the game

* Navigate to My Documents\Bioware\AddIns
* Delete the folder called rcfMeep
* Done

Removing from the game is fairly easy. The toolset? Not so much. The reason for this is that the information is stored in the SQL Database. Now if you just want to remove the module from the Manage Modules list, that is easy.

* Open Sql Server Management Studio Express. I'm not sure if the default installation installs this or not. If not, it can be downloaded from Microsoft.
* Connect to the BWDATOOLSET server, assuming that you kept the default options.
* Expand Databases
* Expand bw_dragonage_content
* Expand Tables
* Right click and select open on the dbo.Modules table
* This will bring up an excell-like window. Find your module, right-click on the row, and select delete. Say ok to the confirmation.
* Module is now PERMANENTLY removed. Absolutely no way of recovering it.

Now depending on the size of the Module, you just orphaned a bunch of resources. Areas, placables, conversations, they all get placed into the database. And once you remove the module ID, you just lost your ability to remove these resources. Now do keep in mind that 95% of this junk is just text, so it hardly takes up any room. It's not really a major issue. However if you [[How-tos#Delete resources|delete out the resources]] within the toolset before you remove the module reference you should avoid this.

== Override Events (e.g. those in player_core) ==
Look here: [[Event override]]

== Create a lootable placeable that vanishes when looted ==

For a player-usable placeable, use the following event script to make it give its contents to the player and then vanish when clicked on.

<dascript>
#include "wrappers_h"
void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
switch (nEventType)
{
case EVENT_TYPE_USE:
{
//MoveAllItems(OBJECT_SELF, GetHero());
AddCreatureMoney (1000000, GetHero(), TRUE);
Safe_Destroy_Object(OBJECT_SELF);
}
}
}
</dascript>

If you wanted to use standard resources you could achieve the same thing (though not destroying the placeable) simply by adding "_autoloot" to the end of the placeable's tag.

== Move the player to a new area after a cutscene plays ==

Stand-alone cutscenes have an "end script" parameter that sets a script to run once the cutscene ends. Use a script such as the following:

<dascript>
void main()
{
DoAreaTransition("destination_area_tag", "destination_waypoint_tag");
}
</dascript>
[[category:tutorials]]

How-tos

2009-12-26T18:48:15Z

JackFuzz: /* Adding music to cutscenes */

This page lists how to accomplish tasks that are relatively simple and commonly needed, but that touch on multiple areas of the toolset or are difficult to figure out intuitively how to do.

Just collecting ideas at the moment, add headers if you think a how-to is needed on a particular subject.

*[[3D control]]

== Run a cutscene from a trigger ==

!!compile fails in test database due to bad core libraries, so this hasn't been tested!!

Create a script:

<dascript>
#include "events_h"
#include "global_objects_h"
#include "utility_h"

void main ()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
int nEventHandled = FALSE;
switch (nEventType)
{
case EVENT_TYPE_ENTER:
{
object oCreature = GetEventCreator(ev);
if(IsHero(oCreature)) {
resource rCutscene = R"my_cutscene.cut";
CS_LoadCutscene(rCutscene);
DestroyObject(OBJECT_SELF, 0);
}
break;
}
if (!nEventHandled) //If this event wasn't handled by this script, let the core script try
{
HandleEvent(ev, RESOURCE_SCRIPT_TRIGGER_CORE);
}
}
</dascript>

And set it as the event script for the trigger that you want to have run the cutscene.

== Add a follower to the player's party ==

<dascript>
if(IsPlayer(oCreature)) {
object oFollower = GetObjectByTag("myfollower");
UT_HireFollower(oCreature, oFollower);
}
</dascript>

Note that with Toolset v1.0.982.0, calling UT_HireFollower() will result in a follower who's unable to gain xp. This happens due to the call of
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, '''TRUE''');
to the function
void WR_SetFollowerState(object oCreature, int nState, int nSendEvent = TRUE, int nMinLevel = 0, '''int bPreventLevelup''' = FALSE)
To enable the xp gain, the flag CREATURE_REWARD_FLAGS needs to be cleared from the follower after the hired event was processed (there the flag is set). Alternatively, the relevant contents of UT_HireFollower() are to be called directly using bPreventLevelup = FALSE.

== Have an enemy play possum and then get up to fight ==

Set the creature's CREATURE_SPAWN_DEAD variable to 2.

When it's time for the creature to rise and attack, execute the following script commands:

<dascript>
#include "wrappers_h"
...
WR_SetObjectActive(oCreature, TRUE);
SetCommandable(oCreature, TRUE);
// Make sure to set this flag back to 0 to avoid problems with savegames.
SetLocalInt(oCreature, CREATURE_SPAWN_DEAD, 0);
UT_CombatStart(oCreature, oPC);
</dascript>

== Insert content into an existing area ==

If you want to add new content on to an existing area (for example, putting a new character or area transition door into an area that exists in the single-player campaign) there are two different ways to do it. One is to override the existing area with a new area of your own design that duplicates the original with the exception of your additions. This is straightforward to do but can interact poorly with other add-ons - you can only have one version of an area active at a time.

A more elegant and extensible approach is to use a [[PRCSCR]]_-prefixed M2DA. The PRCSCR M2DA has a very simple structure and a simple but profound effect:

*ID - a unique integer identifier for each row
*AreaListName - a string that identifies a specific area list, or the special keyword "any".
*Script - the name of a script file.

Whenever a player enters an area in an area list in this M2DA the associated script will be run. A modder can therefore include a script with his mod that will be run when the player enters an existing area that he didn't create. This script can freely add or remove placeables and creatures and perform whatever other modifications to the area that a script is capable of doing.

Note that the script will be run every time the player enters the area, so you'll want to have an associated plot flag to ensure that the changes are only made once.

The following example is a script that adds a new character from an add-on module to an existing area in the main game:

<dascript>
void main()
{
//Check whether we've added Joblo already.
if (WR_GetPlotFlag("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
)

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

Since you can't add [[waypoint]]s to an existing area you'll need to enter the position and orientation values for the target location manually. You can find them by creating a local copy of the area in question and temporarily adding a waypoint to copy down the coordinates and orientation you'll need.

== Add new music ==

Open up [[FMOD]]

It creates a project - set the build directory to your DA override directory - with project highlighted, it is over on the top right about half way down the project settings. You can set a default resource directory but that will just set where the file browser defaults to so it is optional. I'd also define a name in those parameters while you are there.

From there, you need a new event !!(not sure whether a blank default is generated or whether you have to right click and make a default blank event)!!. After you have an event, highlight it and change to the event tab (2nd tab). Here you need to import your file to link to that event.

On that tab I think it creates a empty row for your new event - right click and add wavetable or something like that - I think I use the top option. (Again, might be wrong but the basic goal is getting a audio file in that screen that plays when you hit the play button at the top)

Browse to your wav file or whatever you have.

From there you should be able to play the sound both in the pop-up box and (once that is closed) back in the event tab. You'll see the name of the wave in that once empty row (IIRC).

If you want, you can add layers of sounds to this event using the same process over and over, but keeping it simple; we'll just move along.

Now you have a project and an event. You can set various parameters on the first tab that alter pitch etc on the first tab. (When you import the sound, you set whether it is a one shot or looping).

Once you have that done, go to the top drop down and find build. Build the files and you should see extra files in your override directory.

From there, just open up the toolset (or hit refresh from within the toolset) and your project and event sounds should show up in the listing of sounds.

You can then drag and drop them into the game or cutscene and they will play.

== Adding music to cutscenes ==

The way we have been doing the music changes is via placed sound objects. These sound objects are generally created in [[FMOD]], and in FMOD you can say if the music will persist after the cutscene or end when the cutscene ends.

We are just using other sounds to switch music tracks. Designers can add music switch parameter to any sound in Fmod Designer, usually this is just VO line to change music track, for example:

[[Image:FMOD music switch.jpg]]

If there are no other sounds, designers can create empty sound event and add #music parameter there and place this sound on cutscene timeline.
Music track has to be defined in the same group as music in current area in “music.fdp” to work.

[[Image:FMOD music switch 2.jpg]]

<pre>
#music:name,1 – non looping, for stingers
#music:name – for looping music
</pre>

== Delete resources ==

Resource deletion can sometimes be a bit complicated. Check the following:

*Resources must be checked in when deleted. This is so that the toolset can be sure that all dependencies have been properly resolved.
*If other resources reference the resource it can't be deleted. This means that sometimes you'll need to delete resources in a specific order. For example, you can't delete a creature that's being used in an area, but you could delete the area and then delete the creature. Occasionally there may be circular references that you'll need to break by editing the resources before deleting them. For example:
**A stage can reference an area, which can then reference the stage.
**A plot file can have an associated event script, which will almost certainly include the plot file.
**A stage can reference a creature, which references a dialogue, which references the original stage.

== Removing Modules ==

Deleting a Module from the Toolset
Setup:
I created a module called Meep with a unique id of rcfMeep, added in one area with a waypoint, configured the starting area/waypoint info, and exported it with dependencies. And now I want to strip it out.

Step 1: Removing it from the game

* Navigate to My Documents\Bioware\AddIns
* Delete the folder called rcfMeep
* Done

Removing from the game is fairly easy. The toolset? Not so much. The reason for this is that the information is stored in the SQL Database. Now if you just want to remove the module from the Manage Modules list, that is easy.

* Open Sql Server Management Studio Express. I'm not sure if the default installation installs this or not. If not, it can be downloaded from Microsoft.
* Connect to the BWDATOOLSET server, assuming that you kept the default options.
* Expand Databases
* Expand bw_dragonage_content
* Expand Tables
* Right click and select open on the dbo.Modules table
* This will bring up an excell-like window. Find your module, right-click on the row, and select delete. Say ok to the confirmation.
* Module is now PERMANENTLY removed. Absolutely no way of recovering it.

Now depending on the size of the Module, you just orphaned a bunch of resources. Areas, placables, conversations, they all get placed into the database. And once you remove the module ID, you just lost your ability to remove these resources. Now do keep in mind that 95% of this junk is just text, so it hardly takes up any room. It's not really a major issue. However if you [[How-tos#Delete resources|delete out the resources]] within the toolset before you remove the module reference you should avoid this.

== Override Events (e.g. those in player_core) ==
Look here: [[Event override]]

== Create a lootable placeable that vanishes when looted ==

For a player-usable placeable, use the following event script to make it give its contents to the player and then vanish when clicked on.

<dascript>
#include "wrappers_h"
void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
switch (nEventType)
{
case EVENT_TYPE_USE:
{
//MoveAllItems(OBJECT_SELF, GetHero());
AddCreatureMoney (1000000, GetHero(), TRUE);
Safe_Destroy_Object(OBJECT_SELF);
}
}
}
</dascript>

If you wanted to use standard resources you could achieve the same thing (though not destroying the placeable) simply by adding "_autoloot" to the end of the placeable's tag.

== Move the player to a new area after a cutscene plays ==

Stand-alone cutscenes have an "end script" parameter that sets a script to run once the cutscene ends. Use a script such as the following:

<dascript>
void main()
{
DoAreaTransition("destination_area_tag", "destination_waypoint_tag");
}
</dascript>
[[category:tutorials]]

How-tos

2009-12-26T07:52:38Z

JackFuzz: /* Adding music to cutscenes */

This page lists how to accomplish tasks that are relatively simple and commonly needed, but that touch on multiple areas of the toolset or are difficult to figure out intuitively how to do.

Just collecting ideas at the moment, add headers if you think a how-to is needed on a particular subject.

*[[3D control]]

== Run a cutscene from a trigger ==

!!compile fails in test database due to bad core libraries, so this hasn't been tested!!

Create a script:

<dascript>
#include "events_h"
#include "global_objects_h"
#include "utility_h"

void main ()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
int nEventHandled = FALSE;
switch (nEventType)
{
case EVENT_TYPE_ENTER:
{
object oCreature = GetEventCreator(ev);
if(IsHero(oCreature)) {
resource rCutscene = R"my_cutscene.cut";
CS_LoadCutscene(rCutscene);
DestroyObject(OBJECT_SELF, 0);
}
break;
}
if (!nEventHandled) //If this event wasn't handled by this script, let the core script try
{
HandleEvent(ev, RESOURCE_SCRIPT_TRIGGER_CORE);
}
}
</dascript>

And set it as the event script for the trigger that you want to have run the cutscene.

== Add a follower to the player's party ==

<dascript>
if(IsPlayer(oCreature)) {
object oFollower = GetObjectByTag("myfollower");
UT_HireFollower(oCreature, oFollower);
}
</dascript>

Note that with Toolset v1.0.982.0, calling UT_HireFollower() will result in a follower who's unable to gain xp. This happens due to the call of
WR_SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE, TRUE, 0, '''TRUE''');
to the function
void WR_SetFollowerState(object oCreature, int nState, int nSendEvent = TRUE, int nMinLevel = 0, '''int bPreventLevelup''' = FALSE)
To enable the xp gain, the flag CREATURE_REWARD_FLAGS needs to be cleared from the follower after the hired event was processed (there the flag is set). Alternatively, the relevant contents of UT_HireFollower() are to be called directly using bPreventLevelup = FALSE.

== Have an enemy play possum and then get up to fight ==

Set the creature's CREATURE_SPAWN_DEAD variable to 2.

When it's time for the creature to rise and attack, execute the following script commands:

<dascript>
#include "wrappers_h"
...
WR_SetObjectActive(oCreature, TRUE);
SetCommandable(oCreature, TRUE);
// Make sure to set this flag back to 0 to avoid problems with savegames.
SetLocalInt(oCreature, CREATURE_SPAWN_DEAD, 0);
UT_CombatStart(oCreature, oPC);
</dascript>

== Insert content into an existing area ==

If you want to add new content on to an existing area (for example, putting a new character or area transition door into an area that exists in the single-player campaign) there are two different ways to do it. One is to override the existing area with a new area of your own design that duplicates the original with the exception of your additions. This is straightforward to do but can interact poorly with other add-ons - you can only have one version of an area active at a time.

A more elegant and extensible approach is to use a [[PRCSCR]]_-prefixed M2DA. The PRCSCR M2DA has a very simple structure and a simple but profound effect:

*ID - a unique integer identifier for each row
*AreaListName - a string that identifies a specific area list, or the special keyword "any".
*Script - the name of a script file.

Whenever a player enters an area in an area list in this M2DA the associated script will be run. A modder can therefore include a script with his mod that will be run when the player enters an existing area that he didn't create. This script can freely add or remove placeables and creatures and perform whatever other modifications to the area that a script is capable of doing.

Note that the script will be run every time the player enters the area, so you'll want to have an associated plot flag to ensure that the changes are only made once.

The following example is a script that adds a new character from an add-on module to an existing area in the main game:

<dascript>
void main()
{
//Check whether we've added Joblo already.
if (WR_GetPlotFlag("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
)

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

Since you can't add [[waypoint]]s to an existing area you'll need to enter the position and orientation values for the target location manually. You can find them by creating a local copy of the area in question and temporarily adding a waypoint to copy down the coordinates and orientation you'll need.

== Add new music ==

Open up [[FMOD]]

It creates a project - set the build directory to your DA override directory - with project highlighted, it is over on the top right about half way down the project settings. You can set a default resource directory but that will just set where the file browser defaults to so it is optional. I'd also define a name in those parameters while you are there.

From there, you need a new event !!(not sure whether a blank default is generated or whether you have to right click and make a default blank event)!!. After you have an event, highlight it and change to the event tab (2nd tab). Here you need to import your file to link to that event.

On that tab I think it creates a empty row for your new event - right click and add wavetable or something like that - I think I use the top option. (Again, might be wrong but the basic goal is getting a audio file in that screen that plays when you hit the play button at the top)

Browse to your wav file or whatever you have.

From there you should be able to play the sound both in the pop-up box and (once that is closed) back in the event tab. You'll see the name of the wave in that once empty row (IIRC).

If you want, you can add layers of sounds to this event using the same process over and over, but keeping it simple; we'll just move along.

Now you have a project and an event. You can set various parameters on the first tab that alter pitch etc on the first tab. (When you import the sound, you set whether it is a one shot or looping).

Once you have that done, go to the top drop down and find build. Build the files and you should see extra files in your override directory.

From there, just open up the toolset (or hit refresh from within the toolset) and your project and event sounds should show up in the listing of sounds.

You can then drag and drop them into the game or cutscene and they will play.

== Adding music to cutscenes ==

The way we have been doing the music changes is via placed sound objects. These sound objects are generally created in [[FMOD]], and in FMOD you can say if the music will persist after the cutscene or end when the cutscene ends.

We are just using other sounds to switch music tracks. Designers can add music switch parameter to any sound in Fmod Designer, usually this is just VO line to change music track, for example:

[[Image:FMOD music switch.jpg]]

If there are no other sounds, designers can create empty sound event and add #music parameter there and place this sound on cutscene timeline.
Music track has to be defined in the same group as music in current area in “music.fdp” to work.

[[Image:FMOD music switch 2.jpg]]

<pre>
#music:name,1 – non looping, for stingers
#music:name – for looping music
</pre>

--------------
Another way
--------------

1. Open up FMOD (fmod comes with dragon age, do a search for fmod in dragon age directory)

2. File ---> New Project --> and call it whatever you want and place it in whatever folder you want.

3. Double click the folder under Hierarchy (purple icon folder) and an event will appear beneath it. Name this event whatever you want.

4. Click "Event Editor" Tab.

5. Right click one of the open fields and click "Add Sound". (just right click all over until you see the option.

6. In this window you will see "LOOPING" and "ONE SHOT" on the right hand side. Looping will be selected by default. If you want this FSB to loop over & over again leave it there. If you want this FSB to only play your WAV file one time then click "One Shot".

7. Now pick your wav by clicking "new wavetable". Then press ok.

8. Now click "Build" and do "build project".

9. Note the new files in the directory where you saved the project.

10. Copy all the files from the folder where you build to into a new folder in your override folder (except the actual original wav file).

copy files here (i made a folder called music to be organized)

Dragon Age\modules\Single Player\override\toolsetexport\music

11. Now open up toolset and navigate to sound palette and you should see your new sound file.

12. Open a cutscene, then left click your sound file in the right hand sound palette window.

13. Now left click anywhere in your cutscene and a sound icon will be added which is your sound file.

Congrats.

== Delete resources ==

Resource deletion can sometimes be a bit complicated. Check the following:

*Resources must be checked in when deleted. This is so that the toolset can be sure that all dependencies have been properly resolved.
*If other resources reference the resource it can't be deleted. This means that sometimes you'll need to delete resources in a specific order. For example, you can't delete a creature that's being used in an area, but you could delete the area and then delete the creature. Occasionally there may be circular references that you'll need to break by editing the resources before deleting them. For example:
**A stage can reference an area, which can then reference the stage.
**A plot file can have an associated event script, which will almost certainly include the plot file.
**A stage can reference a creature, which references a dialogue, which references the original stage.

== Removing Modules ==

Deleting a Module from the Toolset
Setup:
I created a module called Meep with a unique id of rcfMeep, added in one area with a waypoint, configured the starting area/waypoint info, and exported it with dependencies. And now I want to strip it out.

Step 1: Removing it from the game

* Navigate to My Documents\Bioware\AddIns
* Delete the folder called rcfMeep
* Done

Removing from the game is fairly easy. The toolset? Not so much. The reason for this is that the information is stored in the SQL Database. Now if you just want to remove the module from the Manage Modules list, that is easy.

* Open Sql Server Management Studio Express. I'm not sure if the default installation installs this or not. If not, it can be downloaded from Microsoft.
* Connect to the BWDATOOLSET server, assuming that you kept the default options.
* Expand Databases
* Expand bw_dragonage_content
* Expand Tables
* Right click and select open on the dbo.Modules table
* This will bring up an excell-like window. Find your module, right-click on the row, and select delete. Say ok to the confirmation.
* Module is now PERMANENTLY removed. Absolutely no way of recovering it.

Now depending on the size of the Module, you just orphaned a bunch of resources. Areas, placables, conversations, they all get placed into the database. And once you remove the module ID, you just lost your ability to remove these resources. Now do keep in mind that 95% of this junk is just text, so it hardly takes up any room. It's not really a major issue. However if you [[How-tos#Delete resources|delete out the resources]] within the toolset before you remove the module reference you should avoid this.

== Override Events (e.g. those in player_core) ==
Look here: [[Event override]]

== Create a lootable placeable that vanishes when looted ==

For a player-usable placeable, use the following event script to make it give its contents to the player and then vanish when clicked on.

<dascript>
#include "wrappers_h"
void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
switch (nEventType)
{
case EVENT_TYPE_USE:
{
//MoveAllItems(OBJECT_SELF, GetHero());
AddCreatureMoney (1000000, GetHero(), TRUE);
Safe_Destroy_Object(OBJECT_SELF);
}
}
}
</dascript>

If you wanted to use standard resources you could achieve the same thing (though not destroying the placeable) simply by adding "_autoloot" to the end of the placeable's tag.

== Move the player to a new area after a cutscene plays ==

Stand-alone cutscenes have an "end script" parameter that sets a script to run once the cutscene ends. Use a script such as the following:

<dascript>
void main()
{
DoAreaTransition("destination_area_tag", "destination_waypoint_tag");
}
</dascript>
[[category:tutorials]]