Dragon Age Toolset Wiki - User contributions [en]

StartCharGen

2023-03-13T22:43:48Z

Ashhawk: Pasted the description for nImportEnabled from the toolset, sadly it's cut off exactly like that.

{{Generated with errors}}
{{dafunction
|name=StartCharGen
|brief=Starts the character generation or level up process
|param1type=object
|param1name=oCreature
|param1desc=The creature to generate
|param1default=
|param2type=int
|param2name=nMode
|param2desc=0 = char gen, 1 = level up
|param2default=0
|param3type=int
|param3name=nImportEnabled
|param3desc=applicable to chargen only, allows importing a hero from an existing save file (in addition to
|param3default=FALSE
|returntype=void
|returndesc=
|sourcefile=script.ldf
|sourcemodule=
}}

== Description ==

Do not use, use the functions in ui_h instead!!
Starts the character generation or level up process.










[[Category: Inventory & equip slot functions]]
[[Category:Character generation]]

Bug:Leliana's head morph has her eyes in her mouth

2022-12-12T20:34:00Z

Ashhawk: Removing BSN link notice

*'''Version found:''' N/A 
*'''Status:''' Closed

== Description ==


The head morph for Leliana, available at [http://social.bioware.com/project/1331/], has her eyes tucked down inside her mouth. This is caused by the "unique shape" slider for Leliana.

The uem_chf_05a_0.mmh file had duplicated node data for the mshh entry. While all of the other MMH files for the unique shapes have only six nodes, the Leliana one has seven. The sixth and seventh nodes are duplicates. For whatever reason, all of the other unique shapes had their mesh labeled EyesM1, but only the Leliana one had EyesM2.

== Workarounds ==


This bug was with the game data rather than the toolset itself, and has been patched in patch003.erf located in <code>packages\core\patch</code>.

[[Category:Closed bugs]]
[[Category:Morphs]]

Bug:Leliana's head morph has her eyes in her mouth

2022-12-12T20:32:51Z

Ashhawk: This bug was patched in patch003.erf, so should be fixed for most people these days, but I'm not sure which game patch number that corresponds to.

{{BSN link}}

*'''Version found:''' N/A 
*'''Status:''' Closed

== Description ==


The head morph for Leliana, available at [http://social.bioware.com/project/1331/], has her eyes tucked down inside her mouth. This is caused by the "unique shape" slider for Leliana.

The uem_chf_05a_0.mmh file had duplicated node data for the mshh entry. While all of the other MMH files for the unique shapes have only six nodes, the Leliana one has seven. The sixth and seventh nodes are duplicates. For whatever reason, all of the other unique shapes had their mesh labeled EyesM1, but only the Leliana one had EyesM2.

== Workarounds ==


This bug was with the game data rather than the toolset itself, and has been patched in patch003.erf located in <code>packages\core\patch</code>.

[[Category:Closed bugs]]
[[Category:Morphs]]

Naming conventions

2022-09-10T10:18:22Z

Ashhawk: Added some definitions from the VFX list page

BioWare's resources follow a naming convention which allows for easy management and easy location of resources needed. When creating new resources it is a good idea to follow the existing naming convention (or your own scheme if you have a preferred one), to differentiate your work from that of others and to help you keep your resources organized.

For the most part the names you give your resources will matter only to you, there are very few situations where the toolset pays attention to the specific form that a resource name takes. So provided you're working on your own any naming convention that suits your particular style will suffice.

Although only one campaign is loaded at a time in game, unintended conflict can arise between the campaign and any core resource mods the player may have installed. If two design resources have the same name, only one will load. This is determined by the [[Source directory priorities]]. So, it's good to choose names that are likely to be unique.

Usually resources are separated by underscores into categories and have prefixes sorting them based on a certain main class, or suffixes giving them certain variations.

__TOC__

== Resource Naming Convention ==

Design resource names are free-form. As a matter of convenience and courtesy to players, you might prefer to follow a convention that reduces the risk of conflict between add-ins and improves compatibility with future Bioware releases. Bear in mind that only one resource with a given name will load in game.

For simple mods, it might be sufficient to use a unique resource name prefix which is unlikely to be used by anyone else. See [[Prefixes in use]].

Larger mods and campaigns may prefer a more professional approach which makes scripting more legible by identifying the resource type etc.

In either case, it would be wise to avoid a prefix that Bioware has already used, such as "gen".

The convention used in the main Single Player campaign of Dragon Age is as follows:

<pre>cir200cr_bloodmage</pre>

*Three-letter prefix indicating which large-scale area of the game the resource begins to (particular origin story, prelude, etc) or "gen" for global resources.
*three-digit number unique to a particular area, generally starting with 100 and incrementing in hundreds for major areas. Accessory areas are given numbers within the block of one hundred that their 'parent' area belongs to. "global" resources are often given the number 000.
*two-letter code indicating what general type of resource it is ("ar" for area, "al" for area list, "ip" for placeable, "cr" for creature, "im" for item, "tr" for trigger, "pt" for plot, "st" for stage, "cs" for cutscene, "wp" for waypoint). A major exception here is event scripts, which have exactly the same name as the resource they're the script for. Dialogue files are also generally named exactly the same as their owner resource. Merchants usually have the owner name, with the prefix "store_".
*An underscore.
*The remainder of the name is free-form and human-readable, a descriptive term to remind you at a glance what the resource is.

== Model File Naming Convention ==

=== Items ===

<pre>[MainClass]_[MODELTYPE]_[MODELSUBTYPE][MODELVARIATION]_[LOD].MMH / PHY

[ef]_[rob]_[enc][a]_[0].mmh (ef_rob_enca_0.mmh)</pre>

*Where [MainClass] is of General type of a Model. The Toolset will build the MainClass based on Race/Gender/Itemtype etc, so this must be correct. (see below)
*[MODELTYPE] as defined with [[2DA|2DAs]]. Typically a short name describing the Model ie. Wolf. See: [[ItemVariations.xls]]
*[MODELSUBTYPE] is optional as defined with [[2DA|2DAs]]. Typically a short name describing different Variations of a Model. See: [[ItemVariations.xls]]
*[MODELVARIATION] is optional as defined with [[2DA|2DAs]]. Typically one letter a, b, c describing further Variations. See: [[ItemVariations.xls]]
*[LOD] is optional for LOD Versions of Models, where its 0, 2 or 3 from highest to lowest LOD. Options are dependant on resourcetype, however 0 is always required if LOD is applicable.

=== Creatures ===

<pre>[MainClass]+[ModelName]_[LOD].MMH / PHY

[c]_[deepstkra]_[0].mmh (c_deepstkra_0.mmh)</pre>

*[MainClass] is the general type of the model. When no override is set in [[APR base.xls]], the toolset will generate it based on race and gender. (see below)
*[ModelName] is the Modelname (including mainclass) described in [[APR base.xls]]. When no Modelname is given, and Modeltype is P, the toolset will generate it based on [[NakedVariations.xls]] (unsure)
*[LOD] is optional for LOD Versions of Models, where its 0, 2 or 3 from highest to lowest LOD. Options are dependant on resourcetype, however 0 is always required if LOD is applicable.

This accounts for the game being able to locate a [[MMH]] via 2DA definitions. [[MSH]] / [[MAO]] / [[DDS]] Files are referenced by the MMH and each other but follow similar schemes.

=== Model Main Class Naming Convention ===

*base
*blk - black boxes of various sizes and proportions, used to obscure the portions of models that lie "outside" an interior level where the player shouldn't be able to see.
*c - Creature (full body)
*cai - Cave Int.
*cav - Caves
*cdr - Cave Deep Road
*che - Chantry Exterior
*chi - Chantry Interior
*cn - Creatures split into body/head/eyes
*cs - Cutscene
*df - dwarf female accessories and components
*dm - dwarf male accessories and components
*dne - dwarf noble exterior level pieces
*dni - dwarf noble interior level pieces
*dse - Dwarf Slum Exterior
*dsi - Dwarf Slum Interior
*dwe - Dwarven Exterior (Orzammar City)
*dwi - Dwarven Interior
*ef - elf female accessories and components
*el - Lights
*el_lr - Light Rig
*el_lp - Light Probe
*em - elf male accessories and components
*fca - Fereldan Castle
*fce - Fereldan Castle/City Exterior
*fci - Fereldan Castle Interior
*fde - Fade
*fdi - Fereldan Dungeon Interior
*fhe - Fereldan Human Exterior
*fhec - ? (used in Redcliffe Village)
*fhi - Ferelden Human Interior
*fne - Ferelden noble exterior level pieces
*frt - Fort (Drakon)
*fti - Fereldan Town Interior
*ftr - Fort (Drakon) Roof
*fve - Fereldan Village Exterior
*fx - Effects
*fxa - Ability Effects
*fxc - Creature Effects
*fxe - Environmental Effects
*fxg - Glyph (or Ground?) Effects (eg AOE placement/aim indicators)
*fxm - Animator cutscene effects
*fxp - Prop Effects
*hf - human female accessories and components
*hm - human male accessories and components
*hro - Hero Sets
*kn - Kid (child) related
*lightrig
*material
*nm - ? (just Duncan's body)
*pf - Female (race-neutral) related
*plc - placeables
*pm - Male (race-neutral) related
*pn - Related to any gender or race
*prp - props
*prv - Provings
*qm - Qunari male related
*sb - Skybox
*sca
*sr - Selection Ring (creature allegiance indicator rings)
*tce - Tevinter Castle Exterior
*tci - Tevinter Castle Interior
*tfi - Tevinter Fade Interior
*tools - models used by the toolset
*trn - ? (possibly terrain creation utilities)
*tti - Tevinter Tower Interior
*tve - Tevinter Exterior
*tvi - Tevinter Interior
*tvm - ? (Tevinter something)
*ue - Eye morph targets
*uem - Eyes and eye morph targets
*uh - Head morph targets
*uhm - Heads and head morph targets
*ul - Eyelash morph targets
*ulm - Eyelashes and eyelash morph targets
*v
*vfx - Visual Effects
*vis - Vista Objects
*vst - Vista Objects
*w - weapon models
*water - waterfall pieces
*zz - models used in debugging

== Voice Over File Naming Convention ==

<pre>[LineID]_m.WAV</pre>

*with [LineID] replaced by the ID number for the conversation line's string table entry.

This accounts for being able to locate thousands of VO lines, when assigning them to their conversation line.

See [[voice over]] for more information on how to manage voice over recording.

== Animation File Naming Convention ==

<pre>mh.dg_5p_tn_l_45.ANI</pre>

The various parts of the animation name gives you information about the type of animation. This for example means "male human dialogue 5 paces turn left 45 degrees."

All humanoid animations prefix with mh. (male human). There is also a small list of fh (female human), These work across all races pretty much.

After the prefix you have the following:
*2p - a 2 person animation... usually lined up (i.e. give and receive, punch and punched, kiss and kissed)
*am - ambient... full animations that so specific actions (i.e. blacksmith, cheering, clean floor)
*cb - combat animations
*cu - custom animation, usually for a specific cutscene or purpose
*dg - dialog... animation fpr the purpose of use within dialogs (although we use all these animations)
*po - pose based animations - these are specific poses and gestures for talking dialogs
*wi - world interaction - similar to ambient but more about interacting with world objects (desks, leaning, sitting)

After the above second prefix the rest is usually descriptive (or some what). Key thing to note:
*en - enter animation... this is the animation that gets the actor doing the animation... usually from a standing neutral position
*lp - looping animation - this is the animation that loops to keep the actor in a pose or position
*ex - exit animation - this is the animation that gets the actor out of the lp animation... usually to a standing neutral position
*tw - twitch, an animation that plays from the lp animation

So, for example:
*mh.wi_sit_en - animation goes from standing neutral to sitting
*mh.wi_sit_lp - animation loops in the sitting pose
*mh.wi_sit_ex - animation goes from sitting to standing neutral
*mh.wi_sit_tw1 - an animation that plays from sit_lp, such as someone scratching their head

== Vegetation (Speedtree) File Naming Convention ==

<pre>tre c oakfixl.SPT</pre>

Vegetation is sorted in main categories via Prefix:

*bsh - Bushes
*gra - Grass
*tre - Trees

The last part is a short description of the vegetation type, ie Oak, which is a Oaktree.

== See Also ==

*[[Art Resources]]
*[[Designer Resources]]
*[[Compatibility]]

[[Category:Art resources]]

Naming conventions

2022-09-09T20:36:14Z

Ashhawk: CN correction

BioWare's resources follow a naming convention which allows for easy management and easy location of resources needed. When creating new resources it is a good idea to follow the existing naming convention (or your own scheme if you have a preferred one), to differentiate your work from that of others and to help you keep your resources organized.

For the most part the names you give your resources will matter only to you, there are very few situations where the toolset pays attention to the specific form that a resource name takes. So provided you're working on your own any naming convention that suits your particular style will suffice.

Although only one campaign is loaded at a time in game, unintended conflict can arise between the campaign and any core resource mods the player may have installed. If two design resources have the same name, only one will load. This is determined by the [[Source directory priorities]]. So, it's good to choose names that are likely to be unique.

Usually resources are separated by underscores into categories and have prefixes sorting them based on a certain main class, or suffixes giving them certain variations.

__TOC__

== Resource Naming Convention ==

Design resource names are free-form. As a matter of convenience and courtesy to players, you might prefer to follow a convention that reduces the risk of conflict between add-ins and improves compatibility with future Bioware releases. Bear in mind that only one resource with a given name will load in game.

For simple mods, it might be sufficient to use a unique resource name prefix which is unlikely to be used by anyone else. See [[Prefixes in use]].

Larger mods and campaigns may prefer a more professional approach which makes scripting more legible by identifying the resource type etc.

In either case, it would be wise to avoid a prefix that Bioware has already used, such as "gen".

The convention used in the main Single Player campaign of Dragon Age is as follows:

<pre>cir200cr_bloodmage</pre>

*Three-letter prefix indicating which large-scale area of the game the resource begins to (particular origin story, prelude, etc) or "gen" for global resources.
*three-digit number unique to a particular area, generally starting with 100 and incrementing in hundreds for major areas. Accessory areas are given numbers within the block of one hundred that their 'parent' area belongs to. "global" resources are often given the number 000.
*two-letter code indicating what general type of resource it is ("ar" for area, "al" for area list, "ip" for placeable, "cr" for creature, "im" for item, "tr" for trigger, "pt" for plot, "st" for stage, "cs" for cutscene, "wp" for waypoint). A major exception here is event scripts, which have exactly the same name as the resource they're the script for. Dialogue files are also generally named exactly the same as their owner resource. Merchants usually have the owner name, with the prefix "store_".
*An underscore.
*The remainder of the name is free-form and human-readable, a descriptive term to remind you at a glance what the resource is.

== Model File Naming Convention ==

=== Items ===

<pre>[MainClass]_[MODELTYPE]_[MODELSUBTYPE][MODELVARIATION]_[LOD].MMH / PHY

[ef]_[rob]_[enc][a]_[0].mmh (ef_rob_enca_0.mmh)</pre>

*Where [MainClass] is of General type of a Model. The Toolset will build the MainClass based on Race/Gender/Itemtype etc, so this must be correct. (see below)
*[MODELTYPE] as defined with [[2DA|2DAs]]. Typically a short name describing the Model ie. Wolf. See: [[ItemVariations.xls]]
*[MODELSUBTYPE] is optional as defined with [[2DA|2DAs]]. Typically a short name describing different Variations of a Model. See: [[ItemVariations.xls]]
*[MODELVARIATION] is optional as defined with [[2DA|2DAs]]. Typically one letter a, b, c describing further Variations. See: [[ItemVariations.xls]]
*[LOD] is optional for LOD Versions of Models, where its 0, 2 or 3 from highest to lowest LOD. Options are dependant on resourcetype, however 0 is always required if LOD is applicable.

=== Creatures ===

<pre>[MainClass]+[ModelName]_[LOD].MMH / PHY

[c]_[deepstkra]_[0].mmh (c_deepstkra_0.mmh)</pre>

*[MainClass] is the general type of the model. When no override is set in [[APR base.xls]], the toolset will generate it based on race and gender. (see below)
*[ModelName] is the Modelname (including mainclass) described in [[APR base.xls]]. When no Modelname is given, and Modeltype is P, the toolset will generate it based on [[NakedVariations.xls]] (unsure)
*[LOD] is optional for LOD Versions of Models, where its 0, 2 or 3 from highest to lowest LOD. Options are dependant on resourcetype, however 0 is always required if LOD is applicable.

This accounts for the game being able to locate a [[MMH]] via 2DA definitions. [[MSH]] / [[MAO]] / [[DDS]] Files are referenced by the MMH and each other but follow similar schemes.

=== Model Main Class Naming Convention ===

*base
*blk - black boxes of various sizes and proportions, used to obscure the portions of models that lie "outside" an interior level where the player shouldn't be able to see.
*c - Creature (full body)
*cai - Cave Int.
*cav - Caves
*cdr - Cave Deep Road
*che - Chantry Exterior
*chi - Chantry Interior
*cn - Creatures split into body/head/eyes
*cs - Cutscene
*df - dwarf female accessories and components
*dm - dwarf male accessories and components
*dne - dwarf noble exterior level pieces
*dni - dwarf noble interior level pieces
*dse - Dwarf Slum Exterior
*dsi - Dwarf Slum Interior
*dwe - Dwarven Exterior (Orzammar City)
*dwi - Dwarven Interior
*ef - elf female accessories and components
*el - Lights
*el_lr - Light Rig
*el_lp - Light Probe
*em - elf male accessories and components
*fca - Fereldan Castle
*fce - Fereldan Castle/City Exterior
*fci - Fereldan Castle Interior
*fde - Fade
*fdi - Fereldan Dungeon Interior
*fhe - Fereldan Human Exterior
*fhec - ? (used in Redcliffe Village)
*fhi - Ferelden Human Interior
*fne - Ferelden noble exterior level pieces
*frt - Fort (Drakon)
*fti - Fereldan Town Interior
*ftr - Fort (Drakon) Roof
*fve - Fereldan Village Exterior
*fx - Effects
*fxa - Ability Effects
*fxc - Creature Effects
*fxe
*fxg - Glyph (or Ground?) Effects (eg AOE placement/aim indicators)
*fxm
*fxp - Prop Effects
*hf - human female accessories and components
*hm - human male accessories and components
*hro - Hero Sets
*kn - Kid (child) related
*lightrig
*material
*nm - ? (just Duncan's body)
*pf - Female (race-neutral) related
*plc - placeables
*pm - Male (race-neutral) related
*pn - Related to any gender or race
*prp - props
*prv - Provings
*qm - Qunari male related
*sb - Skybox
*sca
*sr - ? Ring (creature allegiance indicator rings)
*tce - Tevinter Castle Exterior
*tci - Tevinter Castle Interior
*tfi - Tevinter Fade Interior
*tools - models used by the toolset
*trn - ? (possibly terrain creation utilities)
*tti - Tevinter Tower Interior
*tve - Tevinter Exterior
*tvi - Tevinter Interior
*tvm - ? (Tevinter something)
*ue - Eye morph targets
*uem - Eyes and eye morph targets
*uh - Head morph targets
*uhm - Heads and head morph targets
*ul - Eyelash morph targets
*ulm - Eyelashes and eyelash morph targets
*v
*vfx - Visual Effects
*vis - Vista Objects
*vst - Vista Objects
*w - weapon models
*water - waterfall pieces
*zz - models used in debugging

== Voice Over File Naming Convention ==

<pre>[LineID]_m.WAV</pre>

*with [LineID] replaced by the ID number for the conversation line's string table entry.

This accounts for being able to locate thousands of VO lines, when assigning them to their conversation line.

See [[voice over]] for more information on how to manage voice over recording.

== Animation File Naming Convention ==

<pre>mh.dg_5p_tn_l_45.ANI</pre>

The various parts of the animation name gives you information about the type of animation. This for example means "male human dialogue 5 paces turn left 45 degrees."

All humanoid animations prefix with mh. (male human). There is also a small list of fh (female human), These work across all races pretty much.

After the prefix you have the following:
*2p - a 2 person animation... usually lined up (i.e. give and receive, punch and punched, kiss and kissed)
*am - ambient... full animations that so specific actions (i.e. blacksmith, cheering, clean floor)
*cb - combat animations
*cu - custom animation, usually for a specific cutscene or purpose
*dg - dialog... animation fpr the purpose of use within dialogs (although we use all these animations)
*po - pose based animations - these are specific poses and gestures for talking dialogs
*wi - world interaction - similar to ambient but more about interacting with world objects (desks, leaning, sitting)

After the above second prefix the rest is usually descriptive (or some what). Key thing to note:
*en - enter animation... this is the animation that gets the actor doing the animation... usually from a standing neutral position
*lp - looping animation - this is the animation that loops to keep the actor in a pose or position
*ex - exit animation - this is the animation that gets the actor out of the lp animation... usually to a standing neutral position
*tw - twitch, an animation that plays from the lp animation

So, for example:
*mh.wi_sit_en - animation goes from standing neutral to sitting
*mh.wi_sit_lp - animation loops in the sitting pose
*mh.wi_sit_ex - animation goes from sitting to standing neutral
*mh.wi_sit_tw1 - an animation that plays from sit_lp, such as someone scratching their head

== Vegetation (Speedtree) File Naming Convention ==

<pre>tre c oakfixl.SPT</pre>

Vegetation is sorted in main categories via Prefix:

*bsh - Bushes
*gra - Grass
*tre - Trees

The last part is a short description of the vegetation type, ie Oak, which is a Oaktree.

== See Also ==

*[[Art Resources]]
*[[Designer Resources]]
*[[Compatibility]]

[[Category:Art resources]]

Level tutorial

2022-09-09T20:29:54Z

Ashhawk: Fixed some list markup

==Lighting ==

# Basic lighting (or advanced lighting)
# Render Lighting
# Save the Lightmap
# Test the Level

=== Basic Lighting ===

To light an area with basic lighting, do the following:

In the first room:

* Static Light (Change Light Radius to 600)
* Ambient Light
* Light Probe

In all other rooms:

* Static Light (Light Radius = 600)
* Light Probe

[[File:Light-basicsetup.jpg]]

Thats it! Now continue on to the "Render Lighting" step.

=== Render Lighting ===

Just click the Render lightmaps button, and then wait for the light maps to render. When they are done rendering RE-OPEN the level you were working on, and click the visualization button on.
Save the Lightmap (back to top)

With visualization on. Click the

* Render lightprobes button - Wait for them to process
* Generate pathfinding
* From File Menu choose "Save As" and click save.

All you are doing is saving over top of the original map. This is needed to create or update the ERF lighting map that is created with your level.

=== Lightmaps / Lightprobes ===

A light map is pre-rendered lighting information which:

* Is only affected by baked and static lights.
* Makes things pretty.

== Making a Basic Room ==

===Create a new level===

[[File:New resource.png|200px]]

Select "Room Level" and click next and finish.

===Setting the Grid===

[[Image:Level editor snap options.png]]

Set the grid by clicking on the magnet button.

* Set the grid size to 4
* Ensure the "Snap to surface" box is checked.

NOTE: You should always try to use the highest grid setting possible.

=== New Room ===

[[File:Level editor newroommenu.jpg]]

Create a new room by right clicking on "New area" under "Room World". Then left click on the new room to select it.

Each room contains a list of models or objects including some lights, but it also has properties.

=== Spawning Objects ===

Right click on the "New Room" and select "Insert" then "Spawn Model"

You should see a window like this:

[[File:Level editor spawnmodelmenu.jpg]]

Click on any item in the window to select it then click on the small squareish icon in the top right hand corner of the window. It should look something like this:

[[File:Level editor spawnitemwinprev.jpg]]

Go to the files labeled "dwi_" and select "dwi_livgroom_strt01". Press "Ok" and you should have this:

[[File:Level editor firstitem.jpg]]

Now press the 3D axis button. It should look like this: [[File:Icon3AxisMovement.png]]. Your piece will have a 3D manipulator on it and look like this:

NOTE ABOUT TILESETS: All tilesets will fit together differently. Be sure to use the same tileset for a single map.

==Interiors==

Exteriors and Interiors (Room Levels) are different beasts. We'll start with Interiors. A lot of the things you'll do in interiors are equally applicable to Exteriors, too.

First thing you need to do is enter a "Layout Name" in the Object Inspector. This is the name of the file you’ll be referencing in the designer toolset.

To do anything you need to create a room:

* Right-click on “New Area” then Insert -> New Room.

Rooms are solely in the art tool for visibility reasons. If something isn’t visible, the models inside it don’t have to be in memory. Sometimes a room will be comprised of several art “rooms.” The goal should always be to break up visibility so only necessary art resources are in memory at any given time.

Room names are only important internally. They are never used in the design toolset.

Now that you have a room, right-click on it then select "Insert". Check out all the things you can add to a room. The following sections cover some of the options.

===Models===

When inserting a Spawn Model, currently you just see a file list with no preview. Hopefully a model preview system makes its way into the toolset soon. So select a few different files and see what they are.

* For work flow, it’s best to grab areas similar to the ones you are and copy and paste rooms or groups.
* Another work flow tip, it can be good to put any piece you could possibly need all together in a group in some sort of palette room. Then copy those and paste them where you need.

If you copy and paste an object, the new object is placed immediately on top of the other one. So visually you can’t tell if the operation was successful.

You can also place things with the "Model Placement" button. In the Object Inspector click on Name and you can then add a model name. Then when you left-click that object will appear in the world.
If create something with a right-click insert that model will appear at position 0,0,0 right now. Hopefully that’ll change.

===Groups===

"Model" Groups can be copied, pasted, imported, exported, and dragged between rooms/areas.

To create a Model Group:

* Right click on the desired room/area and select Insert -> New Group.
* Now you can insert new models into the group or drag existing models into the group.
* You can also create a group from existing models by selecting the desired models and then right clicking on them and selecting Grouping -> Create Group from Selection.

Groups can exist inside other groups.

===Connecting Rooms===

To "connect" rooms, click on a room and add connected and visible rooms.

* Connected rooms share pathfinding information (you can walk to them.)
* Visible rooms are rendered from the current room (any rooms you can actually see from inside this room.)

===Populating Rooms===

If you have a room selected, now you can place a variety of things. Right-click on your newly created room and look at what you can “Insert”.

===Best Practices===

These practices are in place to ensure a successful export every time of a level that is playable and functional (also every time). Please add to this if you find more practice that avoid issues.

* Try to make sure each art “room” is visible to as few other rooms as possible. Having multiple rooms loaded in memory will be a BIG performance hit. Jags in halls are your friend.
* Put a dynamic, ambient light in each and every room until a more global ambient light solution is in place. Which rooms are visible to which will change, so walls of blackness may greet the player.
* Run through every room in your level in Preview Mode before posting it to the network.
* When beginning a level, it is best to start at 0,0,0 so that all your floor and wall tiles are multiples of 8 and it is easy to quickly glance at their position to see they are correct.
* When placing wall and floor tiles, set your snap size to at least 2. 4 and 8 are also recommended for quick area creation.
* Always have your interior map have 0x, 0y on a playable room. Either the beginning of the level or the center.
* Village tiles are much smaller than other tiles. Half the size. So are the Ferelden Castle Interior pieces.

===Tips and Tricks===

The following list helps make level building go much quicker:

* For building interiors “Change Snap Options” is invaluable. The default values are .5 and 45 degrees.
* Selection Lock allows you to make an object (or group of objects) non-selectable when you click on them in the world view.
** This is most often used to make the interior tiles non-selectable as you are placing and moving around props.

=== Troubleshooting ===

# I load an interior area in the engine and everything is black. Or, alternatively, I'm running through an area and suddenly I enter a black patch and am now stuck.
#* Rooms have to have a light, or be attached to a room that has a light, for anything to be visible. Artists and tech designers can fix this by attaching a Dynamic Ambient light to that room.
#* An alternate problem that could cause this other than lighting is improper physics for floor pieces. This can cause the player to "fall through" the floor and have it seem like everything went black. Typically, if this happens, you can notice it by the fact that if you walk backwards the room does not show up again. If it were lighting that was causing this, you could walk back and see the room again the way it was before. The solution to this is to find the model which is causing you to fall in the art toolset and fix it.
# My placeables in an interior area are not showing up in the engine. I see them in the toolset, but not in the game.
#* A tile needs to have physics attached to it, otherwise any placeable put on top of it will not appear in the engine. The model for the tile will need to be fixed.

== Exteriors==

Exterior levels can turn themselves into rather large projects and it will be rare that they will be tackled for light content. Regardless, they are important to know and understand.

===Creating Terrain Worlds===

The first thing you will notice after creating a new exterior level is that there is an "Advanced" button when you are picking the size of the area. These greatly effects how your textures look in the area. We have been advised to use the following settings for ALL exterior levels until further notice:

* Cells Per Sector: 16
* Base Cell Resolution: 8
* Blend Texel Size: 320
* Cell Length: 128
* Cell Width: 128
* Tesselation Level: 4

===Modifying Terrain Worlds===

There are many unique interface features available to exterior areas, some of which may need some explaining:

* Smooth - Smooths all terrain within the brush radius. This will turn your monstrous mountains into puny hills.
* Tesselate - Splits up the polygons of the area into smaller ones, allowing for more delicate modifications. There is a limit of how many times this can be applied, but the smallest size should be enough for any endeavor. Right clicking undoes the Teselation.
* Texture Smooth - Smooths two or more materials together. You will use this if you want them to look nice.
* Relax Map - If the terrain texture has been stretched by distortion of the terrain mesh, this tool restores it to its original scale.
* Terrain Chunk Management - Used for naming and setting Blend Mask Size for Terrain Chunks.
* Show/Hide Terrain Chunk Boundries - Shows Terrain Chunk boundries that make up the Terrain World.

Aside from morphing terrain, like interiors, you can add spawn models and lighting anywhere you wish. At the moment, lighting does not effect terrain in the toolset, but it does effect all the spawn models you have placed. Right clicking on "Terrain World" will allow you to insert any object.

=== Materials===

In order to add a new material, right click on the Palette Object and select Insert -> New Material. Following that, give the material a name and set its Scale and Textures.

Scale:

* Relief: How many times the texture is mapped onto the material (???)
* UVTile: Scale of the texture. Higher numbers shrink the texture down (for instance smaller cobblestones). Default value is 1.

Textures:

* Diffuse: Defines the color and intensity of light reflected back by the material.
* Heightmap: Defines the height of individual pixels on the material.
* Normal: Defines the direction the material appears to be facing.
* Specular: Defines “shiny-ness”. The lighter it is, the shinier the material will be.

===Skyboxes===

Clicking on the "Exportable Area Property Box"

Find "Skydome Model" Under the Atmosphere Settings. Select sb_newlayout from the list. This is a dynamic shell, you can change it's characteristics. Don't use any of the other shells.

===Creating an Exportable Area===

In order to export an exterior, you must first designate what part of your Terrain world it takes up:

* Create an [[exportable area]] ([[File:IconAddExportableArea.png]] button in the toolbar)
** When you are ready to export a part of your Terrain World, press this button. It will bring up a window allowing you to set many options that will effect the export. For now, you are only concerned with Defining the Area. (TODO: Other options are not covered.)
** After defining an area, close the window and select the Exportable Area you just created from the list. With this selected, you may now access the standard export and preview buttons on the menu.

== Texturing==

=== Loading up the Palette ===

When you first create an exterior level you will have to add textures to the palette.

[[File:Level editor PaletteTab.jpg]]

Go to the object window and click on the diffuse section. Click on the little dots to open the window.

[[File:Level editor SelectMaterial.jpg]]

All textures for terrain you will need start with the "ter_" prefix. Or you can find your own textures by name. So if you wanted to add a rock texture from DAO look for '''ter_rock_d'''

'''Note that all textures, will have 4 suffixes. d, n, h, and s. These stand for diffuse, normal, height, and specular respectively.''' So when you finish selecting the diffuse you like, go back and choose the corresponding textures for normal, height and specular to complete the texture.

[[File:Level editor ObjectIns-NewMat1.jpg]]

[[File:Level editor OpenTexture.jpg]]

Limit of 8 Textures

===Texture Settings===

'''UV Setting - UVTile is 1 by default but you need to change it to 8 if you use your own textures - this way texture will loooks like in the file itself.'''

Relief Settings

Sound material Type

Typical Textures to use

Texture Tools

Texture Paint

Brush Settings

Grid Opacity

===Important Things you should know===

====Layering Textures====

When you paint a slightly transparent texture on top of another you will see the textures blend together. You can only blend 3 textures on top of each other in this way. If you add a 4th the first texture will disappear on the area you painted the newest texture. And it will look odd.

Instead of making a big mix of textures, set base textures for an area and use those to paint. You should only worry about blending at the seems of the textures for the most part.
Chunk Boundaries

====Why don't my textures blend well?====

If you are starting a new map your textures will likely blend together in a very pixelated fashion. If this is the case, you have to play with "Chunk Size".

[[File:Level editor ChunkCheckers.jpg|600px]]

Look for the checkerboard "View/Hide Terrain Chunk Boundaries" button. Turn it on and your terrain will look like an orange checkerboard. Each of these squares is a "chunk". Now look for the other checkerboard button. (Chunk Management Tool)

[[File:Level editor ChunkSelected.jpg]]

With this open;

* Click on the "Select Chunk" button
* Click on the square you want to modify
* Change the "Blend Mask Size" to either 128(low quality), 256(fair quality) or 512(High quality)

Limitation of 3 Textures on top of each other

[[Category:Tutorials]]
[[Category:Level layouts]]

Naming conventions

2022-09-09T19:38:42Z

Ashhawk: Added some definitions and some possibilities

BioWare's resources follow a naming convention which allows for easy management and easy location of resources needed. When creating new resources it is a good idea to follow the existing naming convention (or your own scheme if you have a preferred one), to differentiate your work from that of others and to help you keep your resources organized.

For the most part the names you give your resources will matter only to you, there are very few situations where the toolset pays attention to the specific form that a resource name takes. So provided you're working on your own any naming convention that suits your particular style will suffice.

Although only one campaign is loaded at a time in game, unintended conflict can arise between the campaign and any core resource mods the player may have installed. If two design resources have the same name, only one will load. This is determined by the [[Source directory priorities]]. So, it's good to choose names that are likely to be unique.

Usually resources are separated by underscores into categories and have prefixes sorting them based on a certain main class, or suffixes giving them certain variations.

__TOC__

== Resource Naming Convention ==

Design resource names are free-form. As a matter of convenience and courtesy to players, you might prefer to follow a convention that reduces the risk of conflict between add-ins and improves compatibility with future Bioware releases. Bear in mind that only one resource with a given name will load in game.

For simple mods, it might be sufficient to use a unique resource name prefix which is unlikely to be used by anyone else. See [[Prefixes in use]].

Larger mods and campaigns may prefer a more professional approach which makes scripting more legible by identifying the resource type etc.

In either case, it would be wise to avoid a prefix that Bioware has already used, such as "gen".

The convention used in the main Single Player campaign of Dragon Age is as follows:

<pre>cir200cr_bloodmage</pre>

*Three-letter prefix indicating which large-scale area of the game the resource begins to (particular origin story, prelude, etc) or "gen" for global resources.
*three-digit number unique to a particular area, generally starting with 100 and incrementing in hundreds for major areas. Accessory areas are given numbers within the block of one hundred that their 'parent' area belongs to. "global" resources are often given the number 000.
*two-letter code indicating what general type of resource it is ("ar" for area, "al" for area list, "ip" for placeable, "cr" for creature, "im" for item, "tr" for trigger, "pt" for plot, "st" for stage, "cs" for cutscene, "wp" for waypoint). A major exception here is event scripts, which have exactly the same name as the resource they're the script for. Dialogue files are also generally named exactly the same as their owner resource. Merchants usually have the owner name, with the prefix "store_".
*An underscore.
*The remainder of the name is free-form and human-readable, a descriptive term to remind you at a glance what the resource is.

== Model File Naming Convention ==

=== Items ===

<pre>[MainClass]_[MODELTYPE]_[MODELSUBTYPE][MODELVARIATION]_[LOD].MMH / PHY

[ef]_[rob]_[enc][a]_[0].mmh (ef_rob_enca_0.mmh)</pre>

*Where [MainClass] is of General type of a Model. The Toolset will build the MainClass based on Race/Gender/Itemtype etc, so this must be correct. (see below)
*[MODELTYPE] as defined with [[2DA|2DAs]]. Typically a short name describing the Model ie. Wolf. See: [[ItemVariations.xls]]
*[MODELSUBTYPE] is optional as defined with [[2DA|2DAs]]. Typically a short name describing different Variations of a Model. See: [[ItemVariations.xls]]
*[MODELVARIATION] is optional as defined with [[2DA|2DAs]]. Typically one letter a, b, c describing further Variations. See: [[ItemVariations.xls]]
*[LOD] is optional for LOD Versions of Models, where its 0, 2 or 3 from highest to lowest LOD. Options are dependant on resourcetype, however 0 is always required if LOD is applicable.

=== Creatures ===

<pre>[MainClass]+[ModelName]_[LOD].MMH / PHY

[c]_[deepstkra]_[0].mmh (c_deepstkra_0.mmh)</pre>

*[MainClass] is the general type of the model. When no override is set in [[APR base.xls]], the toolset will generate it based on race and gender. (see below)
*[ModelName] is the Modelname (including mainclass) described in [[APR base.xls]]. When no Modelname is given, and Modeltype is P, the toolset will generate it based on [[NakedVariations.xls]] (unsure)
*[LOD] is optional for LOD Versions of Models, where its 0, 2 or 3 from highest to lowest LOD. Options are dependant on resourcetype, however 0 is always required if LOD is applicable.

This accounts for the game being able to locate a [[MMH]] via 2DA definitions. [[MSH]] / [[MAO]] / [[DDS]] Files are referenced by the MMH and each other but follow similar schemes.

=== Model Main Class Naming Convention ===

*base
*blk - black boxes of various sizes and proportions, used to obscure the portions of models that lie "outside" an interior level where the player shouldn't be able to see.
*c - creature
*cai - Cave Int.
*cav - Caves
*cdr - Cave Deep Road
*che - Chantry Exterior
*chi - Chantry Interior
*cn - Commmon Body Meshes
*cs - Cutscene
*df - dwarf female accessories and components
*dm - dwarf male accessories and components
*dne - dwarf noble exterior level pieces
*dni - dwarf noble interior level pieces
*dse - Dwarf Slum Exterior
*dsi - Dwarf Slum Interior
*dwe - Dwarven Exterior (Orzammar City)
*dwi - Dwarven Interior
*ef - elf female accessories and components
*el - Lights
*el_lr - Light Rig
*el_lp - Light Probe
*em - elf male accessories and components
*fca - Fereldan Castle
*fce - Fereldan Castle/City Exterior
*fci - Fereldan Castle Interior
*fde - Fade
*fdi - Fereldan Dungeon Interior
*fhe - Fereldan Human Exterior
*fhec - ? (used in Redcliffe Village)
*fhi - Ferelden Human Interior
*fne - Ferelden noble exterior level pieces
*frt - Fort (Drakon)
*fti - Fereldan Town Interior
*ftr - Fort (Drakon) Roof
*fve - Fereldan Village Exterior
*fx - Effects
*fxa - Ability Effects
*fxc - Creature Effects
*fxe
*fxg - Glyph (or Ground?) Effects (eg AOE placement/aim indicators)
*fxm
*fxp - Prop Effects
*hf - human female accessories and components
*hm - human male accessories and components
*hro - Hero Sets
*kn - Kid (child) related
*lightrig
*material
*nm - ? (just Duncan's body)
*pf - Female (race-neutral) related
*plc - placeables
*pm - Male (race-neutral) related
*pn - Related to any gender or race
*prp - props
*prv - Provings
*qm - Qunari male related
*sb - Skybox
*sca
*sr - ? Ring (creature allegiance indicator rings)
*tce - Tevinter Castle Exterior
*tci - Tevinter Castle Interior
*tfi - Tevinter Fade Interior
*tools - models used by the toolset
*trn - ? (possibly terrain creation utilities)
*tti - Tevinter Tower Interior
*tve - Tevinter Exterior
*tvi - Tevinter Interior
*tvm - ? (Tevinter something)
*ue - Eye morph targets
*uem - Eyes and eye morph targets
*uh - Head morph targets
*uhm - Heads and head morph targets
*ul - Eyelash morph targets
*ulm - Eyelashes and eyelash morph targets
*v
*vfx - Visual Effects
*vis - Vista Objects
*vst - Vista Objects
*w - weapon models
*water - waterfall pieces
*zz - models used in debugging

== Voice Over File Naming Convention ==

<pre>[LineID]_m.WAV</pre>

*with [LineID] replaced by the ID number for the conversation line's string table entry.

This accounts for being able to locate thousands of VO lines, when assigning them to their conversation line.

See [[voice over]] for more information on how to manage voice over recording.

== Animation File Naming Convention ==

<pre>mh.dg_5p_tn_l_45.ANI</pre>

The various parts of the animation name gives you information about the type of animation. This for example means "male human dialogue 5 paces turn left 45 degrees."

All humanoid animations prefix with mh. (male human). There is also a small list of fh (female human), These work across all races pretty much.

After the prefix you have the following:
*2p - a 2 person animation... usually lined up (i.e. give and receive, punch and punched, kiss and kissed)
*am - ambient... full animations that so specific actions (i.e. blacksmith, cheering, clean floor)
*cb - combat animations
*cu - custom animation, usually for a specific cutscene or purpose
*dg - dialog... animation fpr the purpose of use within dialogs (although we use all these animations)
*po - pose based animations - these are specific poses and gestures for talking dialogs
*wi - world interaction - similar to ambient but more about interacting with world objects (desks, leaning, sitting)

After the above second prefix the rest is usually descriptive (or some what). Key thing to note:
*en - enter animation... this is the animation that gets the actor doing the animation... usually from a standing neutral position
*lp - looping animation - this is the animation that loops to keep the actor in a pose or position
*ex - exit animation - this is the animation that gets the actor out of the lp animation... usually to a standing neutral position
*tw - twitch, an animation that plays from the lp animation

So, for example:
*mh.wi_sit_en - animation goes from standing neutral to sitting
*mh.wi_sit_lp - animation loops in the sitting pose
*mh.wi_sit_ex - animation goes from sitting to standing neutral
*mh.wi_sit_tw1 - an animation that plays from sit_lp, such as someone scratching their head

== Vegetation (Speedtree) File Naming Convention ==

<pre>tre c oakfixl.SPT</pre>

Vegetation is sorted in main categories via Prefix:

*bsh - Bushes
*gra - Grass
*tre - Trees

The last part is a short description of the vegetation type, ie Oak, which is a Oaktree.

== See Also ==

*[[Art Resources]]
*[[Designer Resources]]
*[[Compatibility]]

[[Category:Art resources]]

Texture Formats

2022-08-17T09:52:30Z

Ashhawk: Added link to list of textures page

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

== Texture Types ==

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

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

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

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

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

Additional texture types are used on some models. The most common type is a height map used on static objects like floors and walls, designated with the ''h'' suffix. Other types are emission (glow) maps designated with the ''e'' suffix, and fresnel maps utilized by some metallic materials, designated with the ''f'' suffix. There's also icon textures, prefixed with ''ico_''

=== Diffuse Map ===

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

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

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

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

DDS Compression: [[DDS Export Settings]]

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

=== Normal Map ===

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

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

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

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

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

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

DDS Compression: [[DDS Export Settings]]

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

=== Specular Map ===

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

Specular maps function in a manner not dissimilar to alpha masks, in that the closer to white an area it is, the brighter the highlight. This information is stored in alpha channel of the specular map. The RGB part of the map defines tint applied to the highlight, as not all materials reflect the light equally -- some can reflect the color of the light source, while for others this will be the color of the reflecting object. The tint helps to simulate the latter behavior.

DDS Compression: [[DDS Export Settings]]

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

=== Tint Map ===

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

Commonly only the RGB Channels are used, where one given channel always masks a specific Surface (ie Metal). So that a tint like "Red Steel" can be reapplyable to the full range of armor models, which applies a red tint to only that mask.

Equally, the alpha channel is often only used for skin tints, where applicable.

DDS Compression: [[DDS Export Settings]]

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

== Material Object ==

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

== Level of Detail ==

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

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

== Related Links ==

[[Reskinning an item tutorial]]

[[Material editor|Material Editor]]

[[Material Tint System]]

[[List of textures]]

=== External Links ===

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

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

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

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

[[Category:Textures]]

List of textures

2022-08-17T09:51:42Z

Ashhawk: Created page with "This is a '''list of all the textures''' in vanilla Dragon Age: Origins and its DLC, including user interface textures. Duplicates have been removed from the standard-quality..."

This is a '''list of all the textures''' in vanilla Dragon Age: Origins and its DLC, including user interface textures. Duplicates have been removed from the standard-quality lists in favour of the high-quality versions; DLC have otherwise been merged. Texture atlases and speedtree textures found in the area layout .gpu.rim files have been omitted. Toolset textures have been omitted.

== Base game (standard quality) ==

* arial12.dds
* arrow_gradient_e.dds
* ashe_d.dds
* ashe_n.dds
* ashe_s.dds
* bad_cubemap.dds
* baddog01_d.dds
* baddog01_n.dds
* baddog01_s.dds
* bark02_d.dds
* bark02_n.dds
* bark02_spec.dds
* berserkers_tent_flag_d.dds
* berserkers_tent_small_02d.dds
* berserkers_tent_small_02s.dds
* bk_c_boxwood.dds
* bk_c_longpine.dds
* bk_c_longpine_n.dds
* bk_c_oak.dds
* bk_c_oak_n.dds
* bk_f_fir.dds
* bk_f_longpine.dds
* bk_f_longpine_n.dds
* bk_f_oak.dds
* bk_f_oak_n.dds
* bk_f_pine.dds
* bk_f_pine_n.dds
* bk_m_fir.dds
* bk_m_pine.dds
* bk_m_pine_n.dds
* bk_s_alpine.dds
* bk_s_alpine_n.dds
* bk_s_pine.dds
* bk_x_hair.dds
* bk_x_hair_n.dds
* bk_x_hydra.dds
* bk_x_hydra_n.dds
* bk_x_roots.dds
* bk_x_roots_n.dds
* bk_x_sporelg.dds
* bk_x_sporelg_n.dds
* bk_x_sporesm.dds
* bk_x_sporesm2.dds
* bonfirewood01_d.dds
* bonfirewood01_e.dds
* bonfirewood01_n.dds
* cai_dtrims1_d.dds
* cai_dtrims1_h.dds
* cai_dtrims1_n.dds
* cai_dtrims1_s.dds
* cai_dwall01_d.dds
* cai_dwall01_h.dds
* cai_dwall01_n.dds
* cai_dwall01_s.dds
* cai_dwall02_d.dds
* cai_dwall03_d.dds
* cai_dwall03_n.dds
* cai_dwall03_s.dds
* cai_dwall04_d.dds
* cai_dwall04_n.dds
* cai_dwall04_s.dds
* cai_exit01_d.dds
* cai_floor03_d.dds
* cai_floor03_n.dds
* cai_floor03_s.dds
* cai_stal1_d.dds
* cai_stal1_n.dds
* cai_stal3_d.dds
* cai_stal3_n.dds
* cai_stal3_sg.dds
* cai_trims_d.dds
* cai_trims_n.dds
* cai_trims_s.dds
* cai_wall05_d.dds
* cai_wall05_n.dds
* cai_wall05_s.dds
* cai_wall2_d.dds
* cai_wall2_n.dds
* cai_wall3_d.dds
* cai_wall3_n.dds
* candlemetal_d.dds
* candlemetal_n.dds
* candlemetal_s.dds
* carvebark02_d.dds
* carvebark02_h.dds
* carvebark02_n.dds
* carvebark02_s.dds
* castle.dds
* cav_master_d.dds
* cav_master_n.dds
* cav_master_s.dds
* cc_arl100.dds
* cc_arl101.dds
* cc_arl110.dds
* cc_arl120.dds
* cc_arl130.dds
* cc_arl140.dds
* cc_arl141.dds
* cc_arl150.dds
* cc_arl160.dds
* cc_arl170.dds
* cc_arl180.dds
* cc_arl190.dds
* cc_arl200.dds
* cc_arl210.dds
* cc_arl220.dds
* cc_arl230.dds
* cc_arl300.dds
* cc_bdc100.dds
* cc_bdc110.dds
* cc_bdc120.dds
* cc_bdc130.dds
* cc_bdc140.dds
* cc_bdc200.dds
* cc_bdc210.dds
* cc_bdn100.dds
* cc_bdn110.dds
* cc_bdn120.dds
* cc_bdn200.dds
* cc_bdn210.dds
* cc_bdn300.dds
* cc_bdn400.dds
* cc_bec100.dds
* cc_bec110.dds
* cc_bec120.dds
* cc_bec200.dds
* cc_bec210.dds
* cc_bed100.dds
* cc_bed110.dds
* cc_bed200.dds
* cc_bhm100.dds
* cc_bhm200.dds
* cc_bhm250.dds
* cc_bhm500.dds
* cc_bhm600.dds
* cc_bhm700.dds
* cc_bhn100.dds
* cc_bhn200.dds
* cc_cam100.dds
* cc_chargen.dds
* cc_cir100.dds
* cc_cir110.dds
* cc_cir200.dds
* cc_cir210.dds
* cc_cir220.dds
* cc_cir230.dds
* cc_cir240.dds
* cc_cir300.dds
* cc_cir310.dds
* cc_cir320.dds
* cc_cir330.dds
* cc_cir340.dds
* cc_cir350.dds
* cc_cir360.dds
* cc_cir361.dds
* cc_cir362.dds
* cc_cir363.dds
* cc_cir364.dds
* cc_cir365.dds
* cc_cir366.dds
* cc_cir368.dds
* cc_cir369.dds
* cc_cir370.dds
* cc_cli100.dds
* cc_cli150.dds
* cc_cli200.dds
* cc_cli210.dds
* cc_cli220.dds
* cc_cli300.dds
* cc_cli310.dds
* cc_cli400.dds
* cc_cli410.dds
* cc_cli420.dds
* cc_cli600.dds
* cc_cli700.dds
* cc_cli800.dds
* cc_cli900.dds
* cc_default.dds
* cc_den100.dds
* cc_den200.dds
* cc_den211.dds
* cc_den220.dds
* cc_den230.dds
* cc_den240.dds
* cc_den250.dds
* cc_den260.dds
* cc_den270.dds
* cc_den280.dds
* cc_den300.dds
* cc_den310.dds
* cc_den320.dds
* cc_den330.dds
* cc_den340.dds
* cc_den350.dds
* cc_den360.dds
* cc_den400.dds
* cc_den410.dds
* cc_den500.dds
* cc_den510.dds
* cc_den511.dds
* cc_den600.dds
* cc_den911.dds
* cc_den912.dds
* cc_den920.dds
* cc_den921.dds
* cc_den922.dds
* cc_den950.dds
* cc_den951.dds
* cc_den952.dds
* cc_den960.dds
* cc_den961.dds
* cc_den962.dds
* cc_den963.dds
* cc_den964.dds
* cc_den965.dds
* cc_den970.dds
* cc_den971.dds
* cc_epi100.dds
* cc_epi200.dds
* cc_epi300.dds
* cc_lot100.dds
* cc_lot110.dds
* cc_lot120.dds
* cc_ntb100.dds
* cc_ntb200.dds
* cc_ntb210.dds
* cc_ntb310.dds
* cc_ntb330.dds
* cc_ntb340.dds
* cc_orz100.dds
* cc_orz110.dds
* cc_orz200.dds
* cc_orz210.dds
* cc_orz220.dds
* cc_orz230.dds
* cc_orz240.dds
* cc_orz250.dds
* cc_orz260.dds
* cc_orz300.dds
* cc_orz310.dds
* cc_orz320.dds
* cc_orz330.dds
* cc_orz340.dds
* cc_orz400.dds
* cc_orz410.dds
* cc_orz420.dds
* cc_orz510.dds
* cc_orz520.dds
* cc_orz530.dds
* cc_orz540.dds
* cc_orz550.dds
* cc_pre100d.dds
* cc_pre100n.dds
* cc_pre200.dds
* cc_pre210.dds
* cc_pre211.dds
* cc_pre410.dds
* cc_pre420.dds
* cc_pre430.dds
* cc_pre440.dds
* cc_ran100.dds
* cc_ran105.dds
* cc_ran110.dds
* cc_ran130.dds
* cc_ran152.dds
* cc_ran154.dds
* cc_ran190.dds
* cc_ran200.dds
* cc_ran210.dds
* cc_ran220.dds
* cc_ran230.dds
* cc_ran240.dds
* cc_ran250.dds
* cc_ran260.dds
* cc_ran270.dds
* cc_ran280.dds
* cc_ran290.dds
* cc_ran300.dds
* cc_ran310.dds
* cc_ran320.dds
* cc_ran401.dds
* cc_ran405.dds
* cc_ran409.dds
* cc_ran500.dds
* cc_ran510.dds
* cc_ran520.dds
* cc_ran530.dds
* cc_ran600.dds
* cc_ran700.dds
* cc_ran800.dds
* cc_ran900.dds
* cc_ran920.dds
* cc_ran950.dds
* cc_urn100.dds
* cc_urn110.dds
* cc_urn120.dds
* cc_urn130.dds
* cc_urn200.dds
* cc_urn210.dds
* cc_urn220.dds
* cc_urn230.dds
* cdr_master_d.dds
* cdr_master_n.dds
* cdr_master_s.dds
* chantry_tent_flag_d.dds
* chantry_tent_small_02d.dds
* chantry_tent_small_02s.dds
* chantrysymbol_d.dds
* chantrysymbol_n.dds
* chantrysymbol_s.dds
* che_plasterroof_d.dds
* che_plasterroof_n.dds
* che_plasterroof_s.dds
* che_stonewall_d.dds
* che_stonewall_n.dds
* che_stonewall_s.dds
* chi_master_d.dds
* chi_master_n.dds
* chi_master_s.dds
* corpse_charred_01d.dds
* corpse_dog_01d.dds
* corpse_dog_01n.dds
* corpse_dog_01s.dds
* corpse_dwarf_01d.dds
* corpse_dwarf_01n.dds
* corpse_dwarf_01s.dds
* corpse_human_01d.dds
* corpse_human_01n.dds
* corpse_human_01s.dds
* corpse_hurlock_01d.dds
* corpse_hurlock_01n.dds
* corpse_hurlock_01s.dds
* corpse_knight_01d.dds
* corpse_knight_01n.dds
* corpse_knight_01s.dds
* corpse_pile_01d.dds
* corpse_pile_01n.dds
* corpse_pile_01s.dds
* corpse_pile_02d.dds
* corpse_pile_03d.dds
* corpse_pile_03n.dds
* corpse_pile_03s.dds
* corpse_templar_01d.dds
* corpse_templar_01n.dds
* corpse_templar_01s.dds
* d_waterspec.dds
* da_defaultcc.dds
* da_vignette.dds
* deadbodycom_d.dds
* deadbodycom_n.dds
* deadbodycom_s.dds
* default_black.dds
* default_blackcubemap.dds
* default_flatnm.dds
* default_gray50.dds
* default_missing.dds
* default_white.dds
* defaultmoon.dds
* defaultsun.dds
* distor_b.dds
* distor_b_alph.dds
* distort_clou.dds
* distort_clou_alp.dds
* dne_bldng_master.dds
* dne_bldng_master_n.dds
* dne_bldng_master_s.dds
* dne_cavemaster_d.dds
* dne_cavemaster_n.dds
* dne_pal_master.dds
* dne_pal_master_n.dds
* dne_pal_master_s.dds
* dni_master_d.dds
* dni_master_n.dds
* dni_master_s.dds
* doorass_diff.dds
* doorass_norm.dds
* doorass_spec.dds
* dse_master.dds
* dse_master_n.dds
* dse_master_s.dds
* dsi_cavemaster_d.dds
* dsi_cavemaster_n.dds
* dsi_cavemaster_s.dds
* dsi_master_d.dds
* dsi_master_n.dds
* dsi_master_s.dds
* duncan_tent_small_02d.dds
* duncan_tent_small_02s.dds
* dwe_lavark01d.dds
* dwe_lavark01n.dds
* dwfrug_d.dds
* dwfrug_n.dds
* dwfrug_s.dds
* dwi_beam01d.dds
* dwi_beam01n.dds
* dwi_beam01s.dds
* dwi_black_d.dds
* dwi_doorwy03d.dds
* dwi_doorwy03n.dds
* dwi_floor01d.dds
* dwi_floor01n.dds
* dwi_floor02d.dds
* dwi_floor02n.dds
* dwi_floor02s.dds
* dwi_genspec01.dds
* dwi_grate01d.dds
* dwi_grate01n.dds
* dwi_pillar01d.dds
* dwi_pillar01n.dds
* dwi_rkwall03s.dds
* dwi_rock01d.dds
* dwi_rock01n.dds
* dwi_rock02d.dds
* dwi_rock02n.dds
* dwi_rstnug1_d.dds
* dwi_rstnug1_n.dds
* dwi_rstnug1_s.dds
* dwi_throne01d.dds
* dwi_throne01n.dds
* dwi_throne01s.dds
* dwi_wall02d.dds
* dwi_wall02n.dds
* dwi_wall02s.dds
* dwi_wall03d.dds
* dwi_wall03h.dds
* dwi_wall03n.dds
* dwi_wall03s.dds
* dwi_wall04d.dds
* dwi_wall04n.dds
* dwi_wall04s.dds
* dwi_wall05d.dds
* dwi_wall05n.dds
* dwpain_d.dds
* dwpain_n.dds
* dwpain_s.dds
* eci_wall_d.dds
* eci_wall_h.dds
* eci_wall_n.dds
* eci_wall_s.dds
* fade01_d.dds
* fade01_e.dds
* fade01_n.dds
* fade01_s.dds
* fadeeffectmask.dds
* fadesaturatemask.dds
* fca_master_d.dds
* fca_master_n.dds
* fca_master_s.dds
* fce_door_01d.dds
* fce_door_01n.dds
* fce_estwall05_0_lod.dds
* fce_slumfnt01_01_lod.dds
* fci_black_d.dds
* fci_canvas_do.dds
* fci_canvas_n.dds
* fci_canvas2_d.dds
* fci_canvas2_h.dds
* fci_canvas2_n.dds
* fci_crwindow2_d.dds
* fci_crwindow2_h.dds
* fci_crwindow2_n.dds
* fci_crwindow2_s.dds
* fci_dunroof_d.dds
* fci_dunroof_n.dds
* fci_dunroof_s.dds
* fci_egrnd4_d.dds
* fci_egrnd4_h.dds
* fci_egrnd4_n.dds
* fci_egrnd4_s.dds
* fci_endwoodbm_d.dds
* fci_endwoodbm_n.dds
* fci_ewall1_d.dds
* fci_ewall1_h.dds
* fci_ewall1_n.dds
* fci_ewall1_s.dds
* fci_ewall2_d.dds
* fci_ewall2_h.dds
* fci_ewall2_n.dds
* fci_ewall2_s.dds
* fci_ewall3_d.dds
* fci_ewall3_h.dds
* fci_ewall3_n.dds
* fci_ewall3_s.dds
* fci_ewall4_d.dds
* fci_ewall4_h.dds
* fci_ewall4_n.dds
* fci_ewall4_s.dds
* fci_ewood1_d.dds
* fci_igrnd1_d.dds
* fci_igrnd1_h.dds
* fci_igrnd1_n.dds
* fci_igrnd1_s.dds
* fci_iroof_d.dds
* fci_iroof_h.dds
* fci_iroof_n.dds
* fci_iroof_s.dds
* fci_iwall2_d.dds
* fci_iwall2_h.dds
* fci_iwall2_n.dds
* fci_iwall2_s.dds
* fci_iwall3_d.dds
* fci_iwall3_h.dds
* fci_iwall3_n.dds
* fci_iwall3_s.dds
* fci_iwall4_d.dds
* fci_iwall4_h.dds
* fci_iwall4_n.dds
* fci_iwall4_s.dds
* fci_iwood1_d.dds
* fci_iwood1_h.dds
* fci_iwood1_n.dds
* fci_iwood1_s.dds
* fci_iwood1s_n.dds
* fci_iwoodp_d.dds
* fci_iwoodp_h.dds
* fci_iwoodp_n.dds
* fci_iwoodp_s.dds
* fci_metal1_d.dds
* fci_metal1_n.dds
* fci_metal1_s.dds
* fci_rocks_d.dds
* fci_rocks_n.dds
* fci_rocks_s.dds
* fci_stpillar_d.dds
* fci_stpillar_n.dds
* fci_stpillar_s.dds
* fci_trims_d.dds
* fci_trims_n.dds
* fci_trims_s.dds
* fci_trims2_d.dds
* fci_trims2_n.dds
* fci_trims2_s.dds
* fci_woodd_d.dds
* fci_woodd_n.dds
* fci_woodd_s.dds
* fci_woodo_n.dds
* fdi_master_d.dds
* fdi_master_n.dds
* fdi_master_s.dds
* fei_terfade_01_d.dds
* fei_terfade_01_n.dds
* fei_terfade_01_s.dds
* fei_terfade_02_d.dds
* fei_terfade_02_n.dds
* fei_terfade_02_s.dds
* fei_terfade_03_d.dds
* fei_terfade_03_n.dds
* fei_terfade_03_s.dds
* fei_terfade_04_d.dds
* fei_terfade_04_n.dds
* fei_terfade_04_s.dds
* fei_terfade_05_d.dds
* fei_terfade_05_n.dds
* fei_terfade_05_s.dds
* fei_terfade_06_d.dds
* fei_terfade_06_n.dds
* fei_terfade_06_s.dds
* ferchra_01_d.dds
* ferchra_01_n.dds
* fhe_canvas2_d.dds
* fhe_master_d.dds
* fhe_master_n.dds
* fhe_master_s.dds
* fhi_master_d.dds
* fhi_master_n.dds
* fhi_master_s.dds
* floatingbridge_d.dds
* floatingbridge_n.dds
* floatingbridge_s.dds
* fne_master_d.dds
* fne_master_n.dds
* fne_master_s.dds
* fne_master2_d.dds
* fne_master2_n.dds
* fne_master2_s.dds
* fne_plcbridge_d.dds
* fne_plcbridge_e.dds
* fti_master_d.dds
* fti_master_n.dds
* fti_master_s.dds
* ftr_master_d.dds
* ftr_master_n.dds
* ftr_master_s.dds
* fx_2000_diff.dds
* fx_2001_diff.dds
* fx_aoe.dds
* fx_aoe_no.dds
* fx_aura_circle.dds
* fx_cone.dds
* fx_symbol.dds
* gnawsignd.dds
* gnawsignn.dds
* goldmetal_d.dds
* goldmetal_s.dds
* gpumemoryover.dds
* grey_dif.dds
* h_andorala_0.dds
* h_aoamarana_0.dds
* h_aohowea_0.dds
* h_aoredclifa_0.dds
* h_aosouthra_0.dds
* h_aowestera_0.dds
* h_ashwarria_0.dds
* h_calcrowsa_0.dds
* h_coenchana_0.dds
* h_compncrfa_0.dds
* h_creationa_0.dds
* h_dalisht1a_0.dds
* h_dalisht2a_0.dds
* h_deshparaa_0.dds
* h_dumata_0.dds
* h_entropyoa_0.dds
* h_ephemeraa_0.dds
* h_gddofhhma_0.dds
* h_gdofcrfta_0.dds
* h_gdofdhfna_0.dds
* h_gdofgnava_0.dds
* h_gdofhunta_0.dds
* h_gdofsekna_0.dds
* h_gdofvenga_0.dds
* h_greywrada_0.dds
* h_haakonwba_0.dds
* h_hseofauda_0.dds
* h_impchanta_0.dds
* h_kingferea_0.dds
* h_korthomfa_0.dds
* h_ladyoskya_0.dds
* h_legofdeda_0.dds
* h_luscana_0.dds
* h_primalora_0.dds
* h_razikalea_0.dds
* h_smithcrfa_0.dds
* h_templarsa_0.dds
* h_teyofhira_0.dds
* h_teyoflota_0.dds
* h_teyrncoua_0.dds
* h_thotha_0.dds
* h_thsilsisa_0.dds
* h_togwarena_0.dds
* h_ursusbara_0.dds
* h_urthemiea_0.dds
* hn_p_father_dif.dds
* hn_p_father_nrm.dds
* hn_p_mother_dif.dds
* hn_p_mother_nrm.dds
* hro_anvil_floor01d.dds
* hro_anvil_floor01n.dds
* hro_anvil_floor01s.dds
* hro_anvil_lyr01d.dds
* hro_anvil_lyr01e.dds
* hro_anvil_lyr01n.dds
* hro_anvil_lyr01s.dds
* hro_anvil_lyr02d.dds
* hro_anvil_lyr02e.dds
* hro_anvil_lyr02n.dds
* hro_anvil_lyr02s.dds
* hro_anvil_wall01d.dds
* hro_anvil_wall01n.dds
* hro_den_bgcastle_d.dds
* hro_den_fdrakdoor_d.dds
* hro_den_fdrakdoor_n.dds
* hro_den_fdrakdoor_s.dds
* hro_den_fdrakeag_d.dds
* hro_den_fdrakeag_n.dds
* hro_den_fdrakeag_s.dds
* hro_den_fdrakent_d.dds
* hro_den_fdrakent_n.dds
* hro_den_fdrakent_s.dds
* hro_den_fdrakon_mt_d.dds
* hro_den_fdrakonctmap.dds
* hro_den_fdrakonmt.dds
* hro_den_fortdrakon_d.dds
* hro_den_gate_n.dds
* hro_den_gate_s.dds
* hro_den_roocircle_d.dds
* hro_den_roocircle_n.dds
* hro_den_roocircle_s.dds
* hro_den_rooftrim_d.dds
* hro_den_rooftrim_n.dds
* hro_den_rooftrim_s.dds
* hro_dni_assembly_d.dds
* hro_dni_assembly_n.dds
* hro_dni_assembly_s.dds
* hro_dni_warroom_d.dds
* hro_dni_warroom_n.dds
* hro_dni_warroom_s.dds
* hro_dsi_caverock_d.dds
* hro_dsi_caverock_n.dds
* hro_dsi_caverock_s.dds
* hro_fci_throne_d.dds
* hro_fci_throne_n.dds
* hro_fci_throne_s.dds
* hro_fie_bda_d.dds
* hro_fie_bdb_d.dds
* hro_fie_citymap_d.dds
* hro_froof_maintve_d.dds
* hro_froof_maintve_n.dds
* hro_froof_maintve_s.dds
* hro_orz_ent_door_d.dds
* hro_orz_ent_door_n.dds
* hro_orz_ent_door_s.dds
* hro_orz_ent_stone_d.dds
* hro_orz_ent_stone_n.dds
* hro_orz_ent_stone_s.dds
* hro_party_pkr_d.dds
* hro_party_pkr_n.dds
* hro_party_pkr_s.dds
* hro_tvi_domepit_d.dds
* hro_tvi_domepit_n.dds
* hro_tvi_domepit_s.dds
* hro_tvitreewall_d.dds
* hro_tvitreewall_n.dds
* hro_tvitreewall_s.dds
* hro_webroof_d.dds
* hro_webroof_n.dds
* hro_webroof_s.dds
* hvo_brd_slime_01a.dds
* hvo_brd_slime_01d.dds
* hvo_brd_slime_01n.dds
* hvo_brd_slime_01s.dds
* ice_mesh.dds
* ice_spec_mesh.dds
* iconrgby.dds
* iconrgbya.dds
* king_large_tent_d.dds
* king_large_tent_n.dds
* king_large_tent_s.dds
* king_tent_flag_d.dds
* king_tent_small_02d.dds
* king_tent_small_02s.dds
* kingflag01_d.dds
* kingflag01_s.dds
* lgtomb01_d.dds
* lgtomb01_n.dds
* lgtomb01_s.dds
* lgtomb02_d.dds
* lgtomb02_n.dds
* lgtomb02_s.dds
* lightbulb01.dds
* lmd_orange32.dds
* lmd_white32.dds
* lmd_white8.dds
* loghain_tent_small_02d.dds
* loghain_tent_small_02s.dds
* lyrium01_d.dds
* lyrium01_e.dds
* lyrium01_n.dds
* lyrium01_s.dds
* mages_tent_small_02d.dds
* mages_tent_small_02s.dds
* mapfogbrush.dds
* mapvisbrush.dds
* markettent_d.dds
* markettent_n.dds
* markettent_s.dds
* matdef_dce_diffuse.dds
* matdef_de_diffuse.dds
* matdef_de_normal.dds
* matdef_de_relief.dds
* matdef_de_specular.dds
* matdef_dm_diffuse.dds
* matdef_dm_normal.dds
* matdef_dn_diffuse.dds
* matdef_dn_specular.dds
* matdef_dp_diffuse.dds
* matdef_dp_normal.dds
* matdef_dp_specular.dds
* mossground2_d.dds
* mossground2_h.dds
* mossground2_n.dds
* mossground2_s.dds
* mousnow01_d.dds
* mousnow01_n.dds
* mousnow01_s.dds
* mousnow02_d.dds
* mousnow02_h.dds
* mousnow02_n.dds
* mousnow02_s.dds
* newbark.dds
* newbark_n.dds
* newbarkl.dds
* newbarkl_n.dds
* newbarks.dds
* newflags_diff.dds
* night_probe_3654.dds
* normal_grass.dds
* p__dog_01_d.dds
* p__dog_01_n.dds
* p__dog_01_s.dds
* p_alchemy_bowl_01d.dds
* p_alchemy_bowl_01n.dds
* p_alchemy_bowl_01s.dds
* p_alchemy_frog_01d.dds
* p_alchemy_frog_01n.dds
* p_alchemy_frog_01s.dds
* p_alchemy_recipe_01d.dds
* p_alchemy_recipe_01n.dds
* p_alchemy_recipe_01s.dds
* p_alchemy_scale_01d.dds
* p_alchemy_scale_01n.dds
* p_alchemy_scale_01s.dds
* p_alchemy_shelf_01d.dds
* p_alchemy_shelf_01n.dds
* p_alchemy_vials_01d.dds
* p_alchemy_vials_01n.dds
* p_alchemy_vials_01s.dds
* p_anvil_01d.dds
* p_anvil_01n.dds
* p_anvil_01s.dds
* p_aravela_01d.dds
* p_aravela_01n.dds
* p_aravela_01s.dds
* p_aravelb_01d.dds
* p_aravelb_01n.dds
* p_aravelb_01s.dds
* p_armoire_01d.dds
* p_armoire_01n.dds
* p_armoire_01s.dds
* p_armor_stand_01d.dds
* p_armor_stand_01n.dds
* p_armor_stand_01s.dds
* p_armorsuit_01d.dds
* p_armorsuit_01n.dds
* p_armorsuit_01s.dds
* p_ballista_01d.dds
* p_ballista_01n.dds
* p_ballista_01s.dds
* p_ballista_bolt_01d.dds
* p_ballista_bolt_01n.dds
* p_ballista_bolt_01s.dds
* p_ballista_bottom_01d.dds
* p_ballista_bottom_01n.dds
* p_ballista_bottom_01s.dds
* p_ballista_top_01d.dds
* p_ballista_top_01n.dds
* p_bandages_01d.dds
* p_bandages_01n.dds
* p_bandages_01s.dds
* p_barrel_oild.dds
* p_barrel_oiln.dds
* p_barrel_oils.dds
* p_barrel01_0d.dds
* p_barrel01_0n.dds
* p_barrel01_0s.dds
* p_basket_empty_01d.dds
* p_basket_empty_01n.dds
* p_basket_empty_01s.dds
* p_bath_stone_01d.dds
* p_bath_stone_01n.dds
* p_bed_canopyd.dds
* p_bed_canopyn.dds
* p_bed_canopys.dds
* p_bed_larged.dds
* p_bed_largen.dds
* p_bed_larges.dds
* p_bed_roll_01d.dds
* p_bed_roll_01n.dds
* p_bed_roll_01s.dds
* p_bedding_clothd.dds
* p_bedding_clothn.dds
* p_bedding_cloths.dds
* p_bedding_commond.dds
* p_bedding_commonn.dds
* p_bedding_commons.dds
* p_bedding_ornated.dds
* p_bedding_ornaten.dds
* p_bedding_ornates.dds
* p_bench_log_01d.dds
* p_bench_log_01n.dds
* p_bench_log_01s.dds
* p_bench_marble_01d.dds
* p_bench_marble_01n.dds
* p_bench_marble_01s.dds
* p_bird_cage_01d.dds
* p_bird_cage_01n.dds
* p_bird_cage_01s.dds
* p_bird_feeder_01d.dds
* p_bird_feeder_01n.dds
* p_bird_feeder_01s.dds
* p_bird_stand_01d.dds
* p_bird_stand_01n.dds
* p_bird_stand_01s.dds
* p_bit_bridal_01d.dds
* p_bit_bridal_01n.dds
* p_bit_bridal_01s.dds
* p_blackboard_01d.dds
* p_blackboard_01n.dds
* p_blackboard_01s.dds
* p_blacksmith_toolsd.dds
* p_blacksmith_toolsn.dds
* p_blacksmith_toolss.dds
* p_blood_altar_01d.dds
* p_blood_altar_01n.dds
* p_blood_altar_01s.dds
* p_boat_making_01d.dds
* p_boat_making_01n.dds
* p_boat_making_01s.dds
* p_bottle_wine_01d.dds
* p_bottle_wine_01n.dds
* p_bottle_wine_01s.dds
* p_bowl_fruit_01d.dds
* p_bowl_fruit_01n.dds
* p_bowl_fruit_01s.dds
* p_bowl_large_01d.dds
* p_bowl_large_01n.dds
* p_bowl_large_01s.dds
* p_bowl_mixing_01d.dds
* p_bowl_mixing_01n.dds
* p_bowl_mixing_01s.dds
* p_bowl_pewter_01d.dds
* p_bowl_pewter_01n.dds
* p_bowl_pewter_01s.dds
* p_bowl_wood_01d.dds
* p_bowl_wood_01n.dds
* p_bowl_wood_01s.dds
* p_brasstorch_01d.dds
* p_brasstorch_01n.dds
* p_brasstorch_01s.dds
* p_btevbench1_01d.dds
* p_btevbench1_01n.dds
* p_btevbench1_01s.dds
* p_btevbookshelf1_01d.dds
* p_btevbookshelf1_01n.dds
* p_btevbookshelf1_01s.dds
* p_btevpot1_01d.dds
* p_btevpot1_01n.dds
* p_btevpot1_01s.dds
* p_btevpot2_01d.dds
* p_btevpot2_01n.dds
* p_btevpot2_01s.dds
* p_btevpot3_01d.dds
* p_btevpot3_01n.dds
* p_btevpot3_01s.dds
* p_btevtable2_01d.dds
* p_btevtable2_01n.dds
* p_btevtable2_01s.dds
* p_btevwartable1_01d.dds
* p_btevwartable1_01n.dds
* p_btevwartable1_01s.dds
* p_bucket_01d.dds
* p_bucket_01n.dds
* p_bucket_01s.dds
* p_bunkbed_01_d.dds
* p_bunkbed_01_n.dds
* p_bunkbed_01_s.dds
* p_butcher_boardd.dds
* p_butcher_boardn.dds
* p_butcher_boards.dds
* p_cabbage_01d.dds
* p_cabbage_01n.dds
* p_cabbage_01s.dds
* p_cabinet_ornate_01d.dds
* p_cabinet_ornate_01n.dds
* p_cabinet_ornate_01s.dds
* p_cabinet_steel_01d.dds
* p_cabinet_steel_01n.dds
* p_cabinet_steel_01s.dds
* p_cage_animal_01d.dds
* p_cage_animal_01n.dds
* p_cage_animal_01s.dds
* p_cage_animal02d.dds
* p_cage_animal02n.dds
* p_cage_animal02s.dds
* p_cage_animal03d.dds
* p_cage_animal03n.dds
* p_cage_animal03s.dds
* p_cage_human_01d.dds
* p_cage_human_01dlo.dds
* p_cage_human_01n.dds
* p_cage_human_01nlo.dds
* p_cage_human_01slo.dds
* p_cage_human_01t.dds
* p_camping_tentd.dds
* p_camping_tentn.dds
* p_camping_tents.dds
* p_candle_holder_01d.dds
* p_candle_holder_01n.dds
* p_candle_holder_01s.dds
* p_candle_holder_02d.dds
* p_candle_holder_02n.dds
* p_candle_holder_02s.dds
* p_cargoboatd.dds
* p_cargoboatn.dds
* p_cargoboats.dds
* p_carriage_01d.dds
* p_carriage_01n.dds
* p_carriage_01s.dds
* p_cart_01d.dds
* p_cart_01n.dds
* p_cart_01s.dds
* p_cart_02d.dds
* p_cart_02s.dds
* p_chain_shackles_01d.dds
* p_chain_shackles_01n.dds
* p_chain_shackles_01s.dds
* p_chamber_pot_01d.dds
* p_chamber_pot_01n.dds
* p_chamber_pot_01s.dds
* p_chantry_altar_01d.dds
* p_chantry_altar_01n.dds
* p_chantry_altar_01s.dds
* p_chantry_altar_b_01d.dds
* p_chantry_altar_b_01n.dds
* p_chantry_altar_b_01s.dds
* p_chest_iron_01d.dds
* p_chest_iron_01n.dds
* p_chest_iron_01s.dds
* p_chest_ornate_01d.dds
* p_chest_ornate_01n.dds
* p_chest_ornate_01s.dds
* p_chest_ornate_02d.dds
* p_chest_ornate_02s.dds
* p_chicken_coop_d.dds
* p_chicken_coop_n.dds
* p_chicken_coop_s.dds
* p_china_vase_01d.dds
* p_china_vase_01n.dds
* p_china_vase_01s.dds
* p_chopping_blockd.dds
* p_chopping_blockn.dds
* p_chopping_blocks.dds
* p_classroom_table_01d.dds
* p_classroom_table_01n.dds
* p_classroom_table_01s.dds
* p_coal_pan_01d.dds
* p_coal_pan_01n.dds
* p_coal_pan_01s.dds
* p_cocoon_01d.dds
* p_cocoon_01n.dds
* p_cocoon_01s.dds
* p_coil_whip_01d.dds
* p_coil_whip_01n.dds
* p_coil_whip_01s.dds
* p_commoner_bkslf_01d.dds
* p_commoner_bkslf_01n.dds
* p_commoner_bkslf_01s.dds
* p_cooking_spitd.dds
* p_cooking_spitn.dds
* p_cooking_spits.dds
* p_cork_float_01d.dds
* p_cork_float_01n.dds
* p_cork_float_01s.dds
* p_couch_01d.dds
* p_couch_01n.dds
* p_couch_01s.dds
* p_crate_large_01d.dds
* p_crate_large_01n.dds
* p_crate_large_01s.dds
* p_crate_wood_01d.dds
* p_crate_wood_01n.dds
* p_crate_wood_01s.dds
* p_creature_bones_01d.dds
* p_creature_bones_01n.dds
* p_creature_bones_01s.dds
* p_cup_wood_01d.dds
* p_cup_wood_01n.dds
* p_cup_wood_01s.dds
* p_curios_03d.dds
* p_curios_03n.dds
* p_curios_03s.dds
* p_curious_02d.dds
* p_curious_02n.dds
* p_curious_02s.dds
* p_darkspawn_barricade_01d.dds
* p_darkspawn_barricade_01n.dds
* p_darkspawn_barricade_01s.dds
* p_decanter_01d.dds
* p_decanter_01n.dds
* p_decanter_01s.dds
* p_deeproast_d.dds
* p_deeproast_n.dds
* p_deeproast_s.dds
* p_demon_sconce_01d.dds
* p_demon_sconce_01n.dds
* p_demon_sconce_01s.dds
* p_demon_torch_01d.dds
* p_demon_torch_01n.dds
* p_demon_torch_01s.dds
* p_desk_large_01d.dds
* p_desk_large_01n.dds
* p_desk_large_01s.dds
* p_desk_ornate_01d.dds
* p_desk_ornate_01n.dds
* p_desk_ornate_01s.dds
* p_desk_small_01d.dds
* p_desk_small_01n.dds
* p_desk_small_01s.dds
* p_dragonegg_01d.dds
* p_dragonegg_01n.dds
* p_dragonegg_01s.dds
* p_dryingrack_01d.dds
* p_dryingrack_01n.dds
* p_dryingrack_01s.dds
* p_dryingrack_01t.dds
* p_ds_flesh_banner_01d.dds
* p_ds_totem_01d.dds
* p_ds_totem_01n.dds
* p_ds_totem_01s.dds
* p_ds_totem_02d.dds
* p_ds_totem_base_01d.dds
* p_ds_totem_base_01n.dds
* p_ds_totem_base_01s.dds
* p_ds_totem_base_02d.dds
* p_ds_totem_cloth_01d.dds
* p_ds_totem_rock_01d.dds
* p_ds_totem_rock_01n.dds
* p_ds_totem_rock_01s.dds
* p_dsforge_01d.dds
* p_dsforge_01n.dds
* p_dsforge_01s.dds
* p_dstools_01d.dds
* p_dstools_01n.dds
* p_dstools_01s.dds
* p_eaten_creature_d.dds
* p_eaten_creature_n.dds
* p_eaten_creature_s.dds
* p_face_rockl1_01d.dds
* p_face_rockl1_01n.dds
* p_face_rockl1_01s.dds
* p_fade_pedestal_01d.dds
* p_fade_pedestal_01n.dds
* p_fade_pedestal_01s.dds
* p_fade_rock1_01d.dds
* p_fade_rock1_01n.dds
* p_fade_rock1_01s.dds
* p_fade_rock2_01d.dds
* p_fade_rock2_01n.dds
* p_fade_rock2_01s.dds
* p_fade_rock3_01d.dds
* p_fade_rock3_01n.dds
* p_fade_rock3_01s.dds
* p_fade_rock4_01d.dds
* p_fade_rock4_01n.dds
* p_fade_rock4_01s.dds
* p_fade_rock5_01d.dds
* p_fade_rock5_01n.dds
* p_fade_rock5_01s.dds
* p_fade_rock6_01d.dds
* p_fade_rock6_01n.dds
* p_fade_rock6_01s.dds
* p_fade_rock7_01d.dds
* p_fade_rock7_01n.dds
* p_fade_rock7_01s.dds
* p_fade_rock8_01d.dds
* p_fade_rock8_01n.dds
* p_fade_rock8_01s.dds
* p_fade_rock9_01d.dds
* p_fade_rock9_01n.dds
* p_fade_rock9_01s.dds
* p_fade_rockl2_01d.dds
* p_fade_rockl2_01n.dds
* p_fade_rockl2_01s.dds
* p_fade_rockl3_01d.dds
* p_fade_rockl3_01n.dds
* p_fade_rockl3_01s.dds
* p_fademirror_01d.dds
* p_fademirror_01n.dds
* p_fademirror_01s.dds
* p_fademirror_mirror_01d.dds
* p_fademirror_mirror_01n.dds
* p_fademirror_mirror_01s.dds
* p_fence_01d.dds
* p_fence_01n.dds
* p_fence_01s.dds
* p_ferelden_altar_01d.dds
* p_ferelden_altar_01n.dds
* p_ferelden_altar_01s.dds
* p_ferelden_altar_b_01d.dds
* p_ferelden_altar_b_01n.dds
* p_ferelden_altar_b_01s.dds
* p_ferelden_statue2d.dds
* p_ferelden_statue2n.dds
* p_ferelden_statue2s.dds
* p_ferelden_statued.dds
* p_ferelden_statuen.dds
* p_ferelden_statues.dds
* p_ferelden_torch_01d.dds
* p_ferelden_torch_01n.dds
* p_ferelden_torch_01s.dds
* p_filth_pile_01d.dds
* p_filth_pile_01n.dds
* p_filth_pile_01s.dds
* p_fire_pitd.dds
* p_fire_pitn.dds
* p_fire_pits.dds
* p_fish_carving_01d.dds
* p_fish_carving_01n.dds
* p_fish_carving_01s.dds
* p_fish_net_01d.dds
* p_fish_net_01n.dds
* p_fish_net_01s.dds
* p_fishingboatd.dds
* p_fishingboatn.dds
* p_fishingboats.dds
* p_fleshpod_01d.dds
* p_fleshpod_01n.dds
* p_fleshpod_01s.dds
* p_fleshpod_02d.dds
* p_fleshpod_02n.dds
* p_fleshpod_02s.dds
* p_fleshpod_03d.dds
* p_fleshpod_03n.dds
* p_fleshpod_03s.dds
* p_flower_bunch_d.dds
* p_flower_bunch_n.dds
* p_flower_bunch_s.dds
* p_flower_potd.dds
* p_flower_potn.dds
* p_flower_pots.dds
* p_flower_wild_01d.dds
* p_flower_wild_01n.dds
* p_flower_wild_01s.dds
* p_food_bread_01d.dds
* p_food_bread_01n.dds
* p_food_bread_01s.dds
* p_food_cheese_01d.dds
* p_food_cheese_01n.dds
* p_food_cheese_01s.dds
* p_food_fish_01d.dds
* p_food_fish_01n.dds
* p_food_fish_01s.dds
* p_food_fruit_01d.dds
* p_food_fruit_01n.dds
* p_food_fruit_01s.dds
* p_food_meat_01d.dds
* p_food_meat_01n.dds
* p_food_meat_01s.dds
* p_food_pie_01d.dds
* p_food_pie_01n.dds
* p_food_pie_01s.dds
* p_food_vegetables_01d.dds
* p_food_vegetables_01n.dds
* p_food_vegetables_01s.dds
* p_forge_small_02d.dds
* p_forge_smalld.dds
* p_forge_smalln.dds
* p_forge_smalls.dds
* p_fruit_stand_01d.dds
* p_fruit_stand_01n.dds
* p_fruit_stand_01s.dds
* p_fur_01_d.dds
* p_fur_01_n.dds
* p_fur_piled.dds
* p_fur_pilen.dds
* p_fur_piles.dds
* p_gem1_01d.dds
* p_gem1_01n.dds
* p_gem1_01s.dds
* p_gem2_01d.dds
* p_gem2_01n.dds
* p_gem2_01s.dds
* p_german_altar_01d.dds
* p_goblet_01d.dds
* p_goblet_01n.dds
* p_goblet_01s.dds
* p_gong_01d.dds
* p_gong_01n.dds
* p_gong_01s.dds
* p_gravestone_01d.dds
* p_gravestone_01n.dds
* p_gravestone_01s.dds
* p_gravestone_02d.dds
* p_gravestone_02n.dds
* p_gravestone_02s.dds
* p_gravestone_03_d.dds
* p_gravestone_03_n.dds
* p_gravestone_03_s.dds
* p_gravestone_statue_01d.dds
* p_gravestone_statue_01n.dds
* p_gravestone_statue_01s.dds
* p_grindstone_01d.dds
* p_grindstone_01n.dds
* p_grindstone_01s.dds
* p_hanging_fish_01d.dds
* p_hanging_fish_01n.dds
* p_hanging_fish_01s.dds
* p_hanging_flowersd.dds
* p_hanging_flowersn.dds
* p_hanging_flowerss.dds
* p_hanging_garlicd.dds
* p_hanging_garlicn.dds
* p_hanging_garlics.dds
* p_hanging_meatd.dds
* p_hanging_meatn.dds
* p_hanging_meats.dds
* p_hanging_nug_01d.dds
* p_hanging_nug_01n.dds
* p_hanging_nug_01s.dds
* p_hanging_peppersd.dds
* p_hanging_peppersn.dds
* p_hanging_pepperss.dds
* p_hay_bale_01d.dds
* p_head_base01d.dds
* p_head_base01n.dds
* p_head_base01s.dds
* p_head_base02d.dds
* p_head_base02n.dds
* p_head_base02s.dds
* p_head_base03_0d.dds
* p_head_base03_0n.dds
* p_head_base03_0s.dds
* p_herb_basket_01d.dds
* p_herb_basket_01n.dds
* p_herb_basket_01s.dds
* p_herbalism1d.dds
* p_herbalism1n.dds
* p_herbalism1s.dds
* p_herbalism2d.dds
* p_herbalism2n.dds
* p_herbalism2s.dds
* p_herbalism3d.dds
* p_herbalism3n.dds
* p_herbalism3s.dds
* p_herbalism4d.dds
* p_herbalism4n.dds
* p_herbalism4s.dds
* p_herbalism5d.dds
* p_herbalism5s.dds
* p_hitching_post_01d.dds
* p_hitching_post_01n.dds
* p_hitching_post_01s.dds
* p_hugekeg_01d.dds
* p_hugekeg_01n.dds
* p_hugekeg_01s.dds
* p_hurlock_head_01d.dds
* p_hurlock_head_01n.dds
* p_idol_02d.dds
* p_idol_02n.dds
* p_idol_02s.dds
* p_incense_burner_01d.dds
* p_incense_burner_01n.dds
* p_incense_burner_01s.dds
* p_invention_01d.dds
* p_invention_01n.dds
* p_invention_01s.dds
* p_invention_02d.dds
* p_invention_02n.dds
* p_invention_02s.dds
* p_jug_water_01d.dds
* p_jug_water_01n.dds
* p_jug_water_01s.dds
* p_ladder_01d.dds
* p_ladder_01n.dds
* p_ladder_01s.dds
* p_large_anvil_01d.dds
* p_large_anvil_01e.dds
* p_large_anvil_01n.dds
* p_large_anvil_01s.dds
* p_large_anvil_base_01d.dds
* p_large_anvil_base_01n.dds
* p_large_anvil_base_01s.dds
* p_leather_stretcher_01d.dds
* p_leather_stretcher_01n.dds
* p_leather_stretcher_01s.dds
* p_legionnaire_altar_01d.dds
* p_legionnaire_altar_01n.dds
* p_legionnaire_altar_01s.dds
* p_lever_01d.dds
* p_lever_01n.dds
* p_lever_02_01d.dds
* p_lever_02_01n.dds
* p_lever_02_01s.dds
* p_library_shelves_01d.dds
* p_library_shelves_01n.dds
* p_library_shelves_01s.dds
* p_log_pile_d.dds
* p_log_pile_n.dds
* p_log_pile_s.dds
* p_logtrap_02d.dds
* p_logtrap_02n.dds
* p_loomd.dds
* p_loomn.dds
* p_looms.dds
* p_lyrium_dish_01d.dds
* p_lyrium_dish_01n.dds
* p_lyrium_dish_01s.dds
* p_lyrium_light_01d.dds
* p_lyrium_light_01e.dds
* p_lyrium_light_01n.dds
* p_lyrium_light_01s.dds
* p_lyrium_pot01_d.dds
* p_lyrium_pot01_n.dds
* p_lyrium_pot01_s.dds
* p_mage_sconce_01d.dds
* p_mage_sconce_01n.dds
* p_mage_sconce_01s.dds
* p_magical_apparatus_01d.dds
* p_map_01d.dds
* p_map_01n.dds
* p_market_armory_v1_01d.dds
* p_market_armory_v1_01n.dds
* p_market_armory_v1_01s.dds
* p_market_magic_v1_01d.dds
* p_market_magic_v1_01n.dds
* p_market_magic_v1_01s.dds
* p_market_stall1_01d.dds
* p_market_stall1_01n.dds
* p_market_stall1_01s.dds
* p_market_tavern_v1_01d.dds
* p_market_tavern_v1_01n.dds
* p_market_tavern_v1_01s.dds
* p_matress_02d.dds
* p_matress_02n.dds
* p_matress_02s.dds
* p_medarm01_0d.dds
* p_medarm01_0n.dds
* p_medarm01_0s.dds
* p_medboo01_0d.dds
* p_medboo01_0n.dds
* p_medboo01_0s.dds
* p_mirror_01_0d.dds
* p_mirror_01_0n.dds
* p_mirror_01_0s.dds
* p_monsterstatue1_0d.dds
* p_monsterstatue1_0n.dds
* p_monsterstatue1_0s.dds
* p_monsterstatue2_01d.dds
* p_monsterstatue2_01n.dds
* p_monsterstatue2_01s.dds
* p_monsterstatue4_01d.dds
* p_monsterstatue4_01n.dds
* p_monsterstatue4_01s.dds
* p_monsterstatue5_01d.dds
* p_monsterstatue5_01n.dds
* p_monsterstatue5_01s.dds
* p_monsterstatue6_01d.dds
* p_monsterstatue6_01n.dds
* p_monsterstatue6_01s.dds
* p_monsterstatue6_02d.dds
* p_monsterstatue6_02n.dds
* p_monsterstatue6_02s.dds
* p_monsterstatue6_03d.dds
* p_monsterstatue6_03n.dds
* p_monsterstatue6_03s.dds
* p_monsterstatue6_04d.dds
* p_monsterstatue6_04n.dds
* p_monsterstatue6_04s.dds
* p_monsterstatue6_05d.dds
* p_monsterstatue6_05n.dds
* p_monsterstatue6_05s.dds
* p_mug_pewterd.dds
* p_mug_pewtern.dds
* p_mug_pewters.dds
* p_musical_instrument_01d.dds
* p_musical_instrument_01n.dds
* p_musical_instrument_01s.dds
* p_musical_instrument_03d.dds
* p_musical_instrument_03n.dds
* p_musical_instrument_03s.dds
* p_paragon_female_01d.dds
* p_paragon_female_01n.dds
* p_paragon_female_01s.dds
* p_paragon_male_01d.dds
* p_paragon_male_01n.dds
* p_paragon_male_01s.dds
* p_pew_01_d.dds
* p_pew_01_n.dds
* p_pew_01_s.dds
* p_pile_rags_01d.dds
* p_pile_rags_01n.dds
* p_pile_rags_01s.dds
* p_pillareagle_d.dds
* p_pillareagle_n.dds
* p_pillow_01d.dds
* p_pillow_01n.dds
* p_pillow_01s.dds
* p_pillows_01ad.dds
* p_pillows_01as.dds
* p_pillows_01bd.dds
* p_pillows_01bs.dds
* p_pillows_01cd.dds
* p_pillows_01cs.dds
* p_pillows_01dd.dds
* p_pillows_01ds.dds
* p_pillows_01ed.dds
* p_pillows_01es.dds
* p_pillows_01fd.dds
* p_pillows_01fs.dds
* p_pillows_01n.dds
* p_plant_03d.dds
* p_plant_03n.dds
* p_plant_03s.dds
* p_plant_1_d.dds
* p_plant_1_n.dds
* p_plant_1_s.dds
* p_plant_2_d.dds
* p_plant_2_n.dds
* p_plant_2_s.dds
* p_plate_wood_01d.dds
* p_plate_wood_01n.dds
* p_plate_wood_01s.dds
* p_plough_0d.dds
* p_plough_0n.dds
* p_plough_0s.dds
* p_pool_water_01d.dds
* p_pool_water_01n.dds
* p_pool_water_01s.dds
* p_portcullis_01d.dds
* p_portcullis_01n.dds
* p_portcullis_01s.dds
* p_pot_1_01d.dds
* p_pot_1_01n.dds
* p_pot_1_01s.dds
* p_pot_2_01d.dds
* p_pot_2_01n.dds
* p_pot_2_01s.dds
* p_pot_3_01d.dds
* p_pot_3_01n.dds
* p_pot_3_01s.dds
* p_pot_cooking_01d.dds
* p_pot_cooking_01n.dds
* p_pot_cooking_01s.dds
* p_pot_weathered_01d.dds
* p_pot_weathered_01n.dds
* p_pot_weathered_01s.dds
* p_prop_01_d.dds
* p_prop_01_n.dds
* p_prop_01_s.dds
* p_pulpit_01d.dds
* p_pulpit_01n.dds
* p_pulpit_01s.dds
* p_pumpkin_0d.dds
* p_pumpkin_0n.dds
* p_pumpkin_0s.dds
* p_reliquary_01d.dds
* p_reliquary_01n.dds
* p_reliquary_01s.dds
* p_rock_topiary1_01d.dds
* p_rock_topiary1_01n.dds
* p_rock_topiary1_01s.dds
* p_rock_topiary2_01d.dds
* p_rock_topiary2_01n.dds
* p_rock_topiary2_01s.dds
* p_rock_topiary3_01d.dds
* p_rock_topiary3_01n.dds
* p_rock_topiary3_01s.dds
* p_rock_topiary4_01d.dds
* p_rock_topiary4_01n.dds
* p_rock_topiary4_01s.dds
* p_rope_01d.dds
* p_rope_01n.dds
* p_rope_01s.dds
* p_round_tabled.dds
* p_round_tablen.dds
* p_round_tables.dds
* p_rowboatd.dds
* p_rowboatn.dds
* p_rowboats.dds
* p_runepillar_01d.dds
* p_runepillar_01n.dds
* p_sack_01_0d.dds
* p_sack_01_0n.dds
* p_sack_01_0s.dds
* p_sack_02_0d.dds
* p_sack_02_0n.dds
* p_sack_02_0s.dds
* p_sack_03_0d.dds
* p_sack_03_0n.dds
* p_sack_03_0s.dds
* p_sack_04_0d.dds
* p_sack_04_0n.dds
* p_sack_04_0s.dds
* p_saw_horses_01d.dds
* p_saw_horses_01n.dds
* p_saw_horses_01s.dds
* p_scarecrow_01d.dds
* p_scarecrow_01n.dds
* p_scarecrow_01s.dds
* p_science_drawing_01d.dds
* p_science_drawing_01n.dds
* p_science_drawing_01s.dds
* p_science_drawing_02d.dds
* p_science_drawing_02n.dds
* p_science_drawing_02s.dds
* p_scroll_rack_01d.dds
* p_scroll_rack_01n.dds
* p_scroll_rack_01s.dds
* p_sexantd.dds
* p_sexantn.dds
* p_sexants.dds
* p_shelf3_d.dds
* p_shelf3_n.dds
* p_shelf3_s.dds
* p_shop_cart01_d.dds
* p_shop_cart01_n.dds
* p_shop_cart01_s.dds
* p_spirit_apparatus_01d.dds
* p_spirit_apparatus_01n.dds
* p_spirit_apparatus_01s.dds
* p_spit_meat_01d.dds
* p_spit_meat_01n.dds
* p_spit_meat_01s.dds
* p_statue_andraste_01d.dds
* p_statue_andraste_01n.dds
* p_statue_andraste_01s.dds
* p_stone_ruby1_01d.dds
* p_stone_ruby1_01n.dds
* p_stone_ruby1_01s.dds
* p_stone_ruby2_01d.dds
* p_stone_ruby2_01n.dds
* p_stone_ruby2_01s.dds
* p_stone_well_d.dds
* p_stone_well_n.dds
* p_stone_well_s.dds
* p_stool_01d.dds
* p_stool_01n.dds
* p_stool_01s.dds
* p_straw_mat_01d.dds
* p_straw_mat_01n.dds
* p_straw_mat_01s.dds
* p_sundiald.dds
* p_sundialn.dds
* p_sundials.dds
* p_table_feast_01_d.dds
* p_table_feast_01_n.dds
* p_table_feast_01_s.dds
* p_table_stone_01d.dds
* p_table_stone_01n.dds
* p_table_stone_01s.dds
* p_table_tall_01_d.dds
* p_table_tall_01_n.dds
* p_table_tall_01_s.dds
* p_tent_dahlish04d.dds
* p_tent_dahlish04n.dds
* p_tent_dahlish04s.dds
* p_tent_dahlish05d.dds
* p_tent_dahlish05n.dds
* p_tent_dahlish05s.dds
* p_tent_large_01d.dds
* p_tent_large_01n.dds
* p_tent_large_01s.dds
* p_tent_large_02d.dds
* p_tent_large_02n.dds
* p_tent_large_02s.dds
* p_tent_noble_01d.dds
* p_tent_noble_01n.dds
* p_tent_noble_01s.dds
* p_tent_small_02d.dds
* p_tent_small_02n.dds
* p_tent_small_02s.dds
* p_tevbench1_01d.dds
* p_tevbench1_01n.dds
* p_tevbench1_01s.dds
* p_tevbookshelf1_01d.dds
* p_tevbookshelf1_01n.dds
* p_tevbookshelf1_01s.dds
* p_tevbookshelf2_01d.dds
* p_tevbookshelf2_01n.dds
* p_tevbookshelf2_01s.dds
* p_tevchair2_01d.dds
* p_tevchair2_01n.dds
* p_tevchair2_01s.dds
* p_tevdesk2_01d.dds
* p_tevdesk2_01n.dds
* p_tevdesk2_01s.dds
* p_tevinter_altar_01d.dds
* p_tevinter_altar_01n.dds
* p_tevinter_altar_01s.dds
* p_tevinter_altar_b_01d.dds
* p_tevinter_altar_b_01n.dds
* p_tevinter_altar_b_01s.dds
* p_tevpot1_01d.dds
* p_tevpot1_01n.dds
* p_tevpot1_01s.dds
* p_tevpot2_01d.dds
* p_tevpot2_01n.dds
* p_tevpot2_01s.dds
* p_tevpot3_01d.dds
* p_tevpot3_01n.dds
* p_tevpot3_01s.dds
* p_tevstatue001_01d.dds
* p_tevstatue001_01n.dds
* p_tevstatue001_01s.dds
* p_tevstatue002_01d.dds
* p_tevstatue002_01n.dds
* p_tevstatue002_01s.dds
* p_tevstatue003_01d.dds
* p_tevstatue003_01n.dds
* p_tevstatue003_01s.dds
* p_tevtable1_01d.dds
* p_tevtable1_01n.dds
* p_tevtable1_01s.dds
* p_tevtable2_01d.dds
* p_tevtable2_01n.dds
* p_tevtable2_01s.dds
* p_tevwartable1_01d.dds
* p_tevwartable1_01n.dds
* p_tevwartable1_01s.dds
* p_throne_02d.dds
* p_throne_02n.dds
* p_throne_02s.dds
* p_tomato_plant_d.dds
* p_tomato_plant_n.dds
* p_tomato_plant_s.dds
* p_tools_fishing_0d.dds
* p_tools_fishing_0n.dds
* p_tools_fishing_0s.dds
* p_tools_skinningd.dds
* p_tools_skinningn.dds
* p_tools_skinnings.dds
* p_torture_rack_01d.dds
* p_torture_rack_01n.dds
* p_torture_rack_01s.dds
* p_torture_toolsd.dds
* p_torture_toolsn.dds
* p_torture_toolss.dds
* p_toy_01d.dds
* p_toy_01n.dds
* p_toy_01s.dds
* p_toy_02d.dds
* p_toy_02n.dds
* p_toy_02s.dds
* p_training_dummy_01d.dds
* p_training_dummy_01n.dds
* p_training_dummy_01s.dds
* p_tree_saw_01d.dds
* p_tree_saw_01n.dds
* p_tree_saw_01s.dds
* p_troughd.dds
* p_troughn.dds
* p_troughs.dds
* p_tub_d.dds
* p_tub_n.dds
* p_tub_s.dds
* p_turkish_lamp_01d.dds
* p_turkish_lamp_01n.dds
* p_turkish_lamp_01s.dds
* p_urn_ashes_01_d.dds
* p_urn_ashes_01_n.dds
* p_urn_ashes_01_s.dds
* p_vanity_02_0d.dds
* p_vanity_02_0n.dds
* p_vanity_02_0s.dds
* p_vase01_01d.dds
* p_vase01_01n.dds
* p_vase01_01s.dds
* p_wagon_chain_d.dds
* p_wagon_chain_n.dds
* p_wagon_chain_s.dds
* p_wagon_covered_01d.dds
* p_wagon_covered_01n.dds
* p_wagon_covered_01s.dds
* p_wagon_covered_01t.dds
* p_wall_carving2d.dds
* p_wall_carving2n.dds
* p_wall_carving2s.dds
* p_wall_carving3d.dds
* p_wall_carving3n.dds
* p_wall_carving3s.dds
* p_wall_carvingd.dds
* p_wall_carvingn.dds
* p_wall_carvings.dds
* p_wash_basin_01d.dds
* p_wash_basin_01n.dds
* p_wash_basin_01s.dds
* p_washbasin_01d.dds
* p_washbasin_01n.dds
* p_washbasin_01s.dds
* p_washboard_d.dds
* p_washboard_n.dds
* p_washboard_s.dds
* p_well_interiord.dds
* p_well_interiorn.dds
* p_well_interiors.dds
* p_wheel_barrow_01d.dds
* p_wheel_barrow_01n.dds
* p_wheel_barrow_01s.dds
* p_wine_rack_01d.dds
* p_wine_rack_01n.dds
* p_wine_rack_01s.dds
* p_wooden_buoy_01d.dds
* p_wooden_buoy_01n.dds
* p_wooden_buoy_01s.dds
* p_woodendragon_d.dds
* p_woodendragon_n.dds
* p_woodendragon_s.dds
* p_woodrope_02d.dds
* p_woodrope_02n.dds
* p_woodrope_02s.dds
* p_wpnaxe_0d.dds
* p_wpnaxe_0n.dds
* p_wpnaxe_0s.dds
* p_wpnbow_01_0d.dds
* p_wpnbow_01_0n.dds
* p_wpnbow_01_0s.dds
* p_wpnbow_02_0d.dds
* p_wpnbow_02_0n.dds
* p_wpnbow_02_0s.dds
* p_wpndsword_0d.dds
* p_wpndsword_0n.dds
* p_wpnpage_01d.dds
* p_wpnpage_01n.dds
* p_wpnpage_01s.dds
* p_wpnquiver01_0d.dds
* p_wpnquiver01_0n.dds
* p_wpnquiver01_0s.dds
* p_wpnsword_0n.dds
* p_wpnsword_0s.dds
* p_wpnswordblood_0d.dds
* p_wreckedboatd.dds
* p_wreckedboatn.dds
* p_wreckedboats.dds
* paintingwall_d.dds
* paintingwall_n.dds
* paintingwall_s.dds
* paintingwall02_d.dds
* paintingwall02_n.dds
* paintingwall02_s.dds
* pf_ulm_bas_0d.dds
* plasterwall04d.dds
* plasterwall04h.dds
* plasterwall04n.dds
* plasterwall05d.dds
* plasterwall05h.dds
* plasterwall05n.dds
* plasterwall06d.dds
* plasterwall06h.dds
* plasterwall06n.dds
* plc_bdoor01d.dds
* plc_bdoor01n.dds
* plc_bdoor01s.dds
* plc_bladetrap_diff.dds
* plc_chand01_0d.dds
* plc_cog01n.dds
* plc_cog01s.dds
* plc_cogc01d.dds
* plc_cogc07d.dds
* plc_cogo03d.dds
* plc_cogo05d.dds
* plc_coinpile01_d.dds
* plc_coinpile01_s.dds
* plc_doorcitydwf.dds
* plc_doorcitydwf_n.dds
* plc_doorcitydwf_s.dds
* plc_doordbl_01_diff.dds
* plc_doordbl_01_norm.dds
* plc_doordbl_01_spec.dds
* plc_doordbldwf_01_diff.dds
* plc_doordbldwf_01_norm.dds
* plc_doordbldwf_01_spec.dds
* plc_doordbldwf_02_diff.dds
* plc_doordbldwf_02_norm.dds
* plc_doordbldwf_02_spec.dds
* plc_doordbldwf_03_diff.dds
* plc_doordbldwf_03_norm.dds
* plc_doordbldwf_03_spec.dds
* plc_doordbldwf_04_diff.dds
* plc_doordbldwf_04_norm.dds
* plc_doordbldwf_04_spec.dds
* plc_doorlg_01_diff.dds
* plc_doorlg_01_norm.dds
* plc_doorlg_01_spec.dds
* plc_doorlg_02_diff.dds
* plc_doorlg_02_norm.dds
* plc_doorlg_02_spec.dds
* plc_doorlgdwf_01_diff.dds
* plc_doorlgdwf_01_norm.dds
* plc_doorlgdwf_01_spec.dds
* plc_doorlgdwf_02_diff.dds
* plc_doorlgdwf_02_norm.dds
* plc_doorlgdwf_02_spec.dds
* plc_doorlgdwf_03_diff.dds
* plc_doorlgdwf_03_norm.dds
* plc_doorlgdwf_03_spec.dds
* plc_doorlgdwf_04_diff.dds
* plc_doorlgdwf_04_norm.dds
* plc_doorlgdwf_04_spec.dds
* plc_doorlgdwf_05_diff.dds
* plc_doorlgdwf_05_norm.dds
* plc_doorlgdwf_05_spec.dds
* plc_doorsm_01_diff.dds
* plc_doorsm_01_norm.dds
* plc_doorsm_01_spec.dds
* plc_dwarfcoin_d.dds
* plc_dwarfcoin_n.dds
* plc_dwarfcoin_s.dds
* plc_halla_d.dds
* plc_halla_n.dds
* plc_halla_s.dds
* plc_halla_t.dds
* plc_hangingfemale_01_d.dds
* plc_hangingmale_01_d.dds
* plc_hangingmale_02_d.dds
* plc_ironbark1_d.dds
* plc_ironbark1_n.dds
* plc_lake_map01d.dds
* plc_mosstile_d.dds
* plc_mosstile_n.dds
* plc_mousehole_d.dds
* plc_mousehole_n.dds
* plc_mousehole_s.dds
* plc_platform_01d.dds
* plc_platform_01n.dds
* plc_poster_d.dds
* plc_poster_s.dds
* plc_pressure01_d.dds
* plc_pressure01_n.dds
* plc_pressure01_s.dds
* plc_pressure02_d.dds
* plc_pressure02_n.dds
* plc_pressure02_s.dds
* plc_registry02_d.dds
* plc_registry02_n.dds
* plc_registry02_s.dds
* plc_rescuefloor_01d.dds
* plc_rescuefloor_01n.dds
* plc_rescuefloor_01s.dds
* plc_rkwall03d.dds
* plc_rkwall03n.dds
* plc_rkwall03s.dds
* plc_rock04_d.dds
* plc_rock04_n.dds
* plc_shrub1_n.dds
* plc_shrub2_d.dds
* plc_shrubbark1_d.dds
* plc_shrubbark1_n.dds
* plc_shrubfrond_d.dds
* plc_shrubfrond_n.dds
* plc_smtrapdoor01_d.dds
* plc_smtrapdoor01_n.dds
* plc_smtrapdoor01_s.dds
* plc_tentsmall_02_lod.dds
* plc_thronechair_01_diff.dds
* plc_thronechair_01_norm.dds
* plc_thronechair_01_spec.dds
* plc_trpbladetci_d.dds
* plc_trpbladetci_n.dds
* plc_trpbladetci_s.dds
* plc_tvetower.dds
* plc_walldiv_d.dds
* plc_walldiv_n.dds
* plc_walldiv_s.dds
* plc_wood1_d.dds
* plc_wood1_s.dds
* plc_woodgt_sml_01_0_lod.dds
* pm_ulm_bas_0d.dds
* pn_crown_01d.dds
* pn_crown_01n.dds
* pn_crown_01s.dds
* pn_crown_01t.dds
* pn_eye_crpa_0d.dds
* pn_eye_nrma_0m.dds
* pn_ulm_bas_0d.dds
* prp_arm_dwpb_0d.dds
* prp_arm_dwpb_0n.dds
* prp_arm_dwpb_0s.dds
* prp_armorstand_02_0_d.dds
* prp_armorstand_03_0_d.dds
* prp_armorstand_04_0_d.dds
* prp_armorstand_05_0_d.dds
* prp_ashwraith_d.dds
* prp_ashwraith_n.dds
* prp_ashwraith_s.dds
* prp_bark_d.dds
* prp_bark_n.dds
* prp_basestatue01d.dds
* prp_basestatue01n.dds
* prp_bed01_0_d.dds
* prp_black01_d.dds
* prp_black01_s.dds
* prp_blankbanners_01d.dds
* prp_blankbanners_01n.dds
* prp_blankbanners_01s.dds
* prp_blncscale_d.dds
* prp_blood01_d.dds
* prp_blood01_n.dds
* prp_blood01_s.dds
* prp_bluecarp_d.dds
* prp_bluecarp_s.dds
* prp_bonfire_d.dds
* prp_bonfire_n.dds
* prp_bonfire01_0_lod.dds
* prp_bonfireash_d.dds
* prp_bowrack_d.dds
* prp_breadoven_05_0_d.dds
* prp_breadoven_05_0_s.dds
* prp_broadleaffrond_d.dds
* prp_broadleaffrond_n.dds
* prp_broadleafleaves_d.dds
* prp_broadleafleaves_n.dds
* prp_carpet_n.dds
* prp_carriage_01_lod.dds
* prp_cartempty_01_0_lod.dds
* prp_carvebark01_d.dds
* prp_carvebark01_n.dds
* prp_carvebark01_s.dds
* prp_carvebark02_d.dds
* prp_carvebark02_n.dds
* prp_carvebark02_s.dds
* prp_caskwine_01_diff.dds
* prp_caskwine_01_norm.dds
* prp_caskwine_01_spec.dds
* prp_caverock01_d.dds
* prp_caverock01_n.dds
* prp_chand01_0d.dds
* prp_chand01_0n.dds
* prp_chand01_0s.dds
* prp_chi_window1_d.dds
* prp_chi_window1_e.dds
* prp_chi_window1_n.dds
* prp_chi_window1_s.dds
* prp_chstwd_01_d.dds
* prp_chstwd_01_n.dds
* prp_cline0_0d.dds
* prp_cline0_0n.dds
* prp_cline0_0s.dds
* prp_cloth01_d.dds
* prp_cloth01_n.dds
* prp_cloth02_d.dds
* prp_cloth02_n.dds
* prp_cloth03_d.dds
* prp_clothtorn01_d.dds
* prp_clothtorn01_n.dds
* prp_clothtorn02_d.dds
* prp_clothtorn02_n.dds
* prp_clothtorn05_d.dds
* prp_coff01_0d.dds
* prp_coff01_0n.dds
* prp_coff01_0s.dds
* prp_coff02_0d.dds
* prp_coff02_0n.dds
* prp_coff02_0s.dds
* prp_corps01_d.dds
* prp_corps01_n.dds
* prp_corps01_s.dds
* prp_couldron_01_d.dds
* prp_couldron_01_n.dds
* prp_couldron_01_s.dds
* prp_creature_d.dds
* prp_creature_n.dds
* prp_creature_s.dds
* prp_crssd_swrd2_0_d.dds
* prp_curt05d.dds
* prp_curt05n.dds
* prp_curt05s.dds
* prp_curt08d.dds
* prp_curt08n.dds
* prp_curt08s.dds
* prp_deadox_01d.dds
* prp_deadox_01n.dds
* prp_deadox_01s.dds
* prp_deera_0d.dds
* prp_deera_0n.dds
* prp_deera_0s.dds
* prp_dirtpile01_d.dds
* prp_dirtpile01_n.dds
* prp_dni_archd01_d.dds
* prp_dni_archd01_n.dds
* prp_dni_lavapan01_d.dds
* prp_dni_lavapan01_n.dds
* prp_dni_pillar01_d.dds
* prp_dni_pillar01_n.dds
* prp_dni_plug02_d.dds
* prp_dni_plug02_n.dds
* prp_dni_plug02_s.dds
* prp_dni_plug03_d.dds
* prp_dni_plug03_n.dds
* prp_dni_rock01_d.dds
* prp_dni_rock01_n.dds
* prp_dni_rock02_d.dds
* prp_dni_rock02_n.dds
* prp_dni_support01_d.dds
* prp_dni_support01_n.dds
* prp_dni_torch01_d.dds
* prp_dni_torch01_n.dds
* prp_dni_torch02_d.dds
* prp_dni_torch02_n.dds
* prp_dni_wall01_d.dds
* prp_dni_wall01_n.dds
* prp_dni_walldivide01_d.dds
* prp_dni_walldivide01_n.dds
* prp_drkspstuf_11_0_lod.dds
* prp_drwven_registry_d.dds
* prp_drwven_registry_n.dds
* prp_drwven_registry_s.dds
* prp_dstotem_01_0_lod.dds
* prp_dw_bench01d.dds
* prp_dw_bench01n.dds
* prp_dw_box01d.dds
* prp_dw_box01n.dds
* prp_dw_carving3d.dds
* prp_dw_carving3n.dds
* prp_dw_carving4d.dds
* prp_dw_carving4n.dds
* prp_dw_chair1d.dds
* prp_dw_chair1n.dds
* prp_dw_floorart01d.dds
* prp_dw_floorart01n.dds
* prp_dw_rock01_d.dds
* prp_dw_rock01_n.dds
* prp_dw_rock02_d.dds
* prp_dw_slab01d.dds
* prp_dw_slab01n.dds
* prp_dw_slab02d.dds
* prp_dw_slab02n.dds
* prp_dw_torch01d.dds
* prp_dw_torch01n.dds
* prp_dw_vat01d.dds
* prp_dw_vat01n.dds
* prp_dw_window_01_d.dds
* prp_dw_window_01_e.dds
* prp_dw_window_01_n.dds
* prp_dw_window_01_s.dds
* prp_dwamph01d.dds
* prp_dwamph01n.dds
* prp_dwarfsign.dds
* prp_dwarfsign_n.dds
* prp_dwarfsign_s.dds
* prp_dwbed01d.dds
* prp_dwbed01n.dds
* prp_dwbed02d.dds
* prp_dwbed02n.dds
* prp_dwbed03d.dds
* prp_dwbed03n.dds
* prp_dwchest01d.dds
* prp_dwchest01n.dds
* prp_dwchest01s.dds
* prp_dwcloth01d.dds
* prp_dwcloth01n.dds
* prp_dwcloth02d.dds
* prp_dwcloth02n.dds
* prp_dwcouch01d.dds
* prp_dwcouch01n.dds
* prp_dwcryst01a_d.dds
* prp_dwcryst01a_e.dds
* prp_dwcryst01a_n.dds
* prp_dwcryst01a_s.dds
* prp_dwcryst01d.dds
* prp_dwcryst01e.dds
* prp_dwcryst01n.dds
* prp_dwcryst01s.dds
* prp_dwfirepit01d.dds
* prp_dwfirepit01n.dds
* prp_dwfrug_d.dds
* prp_dwfsign01_0d.dds
* prp_dwfsign01_0n.dds
* prp_dwfsign01_0s.dds
* prp_dwfsign02_0d.dds
* prp_dwfsign02_0n.dds
* prp_dwfsign02_0s.dds
* prp_dwgenspec01.dds
* prp_dwmet_d.dds
* prp_dwmet_n.dds
* prp_dwmet_s.dds
* prp_dwmetal01.dds
* prp_dwmetal01n.dds
* prp_dwoven01d.dds
* prp_dwoven01n.dds
* prp_dwovtls01d.dds
* prp_dwovtls01n.dds
* prp_dwrock01d.dds
* prp_dwrock01n.dds
* prp_dwrock01s.dds
* prp_dwrockt01d.dds
* prp_dwrockt01n.dds
* prp_dwrubble01d.dds
* prp_dwrubble01n.dds
* prp_dwrubble02d.dds
* prp_dwrubble02n.dds
* prp_dwsarco01d.dds
* prp_dwsarco01n.dds
* prp_dwsarco02d.dds
* prp_dwsign01d.dds
* prp_dwsign02d.dds
* prp_dwsign02n.dds
* prp_dwsign03d.dds
* prp_dwsign03n.dds
* prp_dwsign04d.dds
* prp_dwsign04n.dds
* prp_dwsign05d.dds
* prp_dwsign05n.dds
* prp_dwsign06d.dds
* prp_dwsign06n.dds
* prp_dwtable01d.dds
* prp_dwtable01n.dds
* prp_dwtable02d.dds
* prp_dwtable02n.dds
* prp_dwtable03d.dds
* prp_dwtable03n.dds
* prp_eagle_01_0_d.dds
* prp_eagle_01_0_n.dds
* prp_eagle_01_0_s.dds
* prp_elfstatue_01d.dds
* prp_elfstatue_01n.dds
* prp_elfstatue_01s.dds
* prp_elfstatue_02d.dds
* prp_elfstatue_02n.dds
* prp_elfstatue_02s.dds
* prp_elfstatue_03d.dds
* prp_elfstatue_03n.dds
* prp_elfstatue_03s.dds
* prp_elfstatue_04d.dds
* prp_elfstatue_04n.dds
* prp_elfstatue_04s.dds
* prp_endbark_d.dds
* prp_endbark_n.dds
* prp_endbark_s.dds
* prp_faderinfrcd_dr_d.dds
* prp_faderinfrcd_dr_n.dds
* prp_faderinfrcd_dr_s.dds
* prp_fadportal01_d.dds
* prp_fadportal01_n.dds
* prp_fadportal01_s.dds
* prp_fca_props_d.dds
* prp_fca_props_n.dds
* prp_fca_props_s.dds
* prp_fciwood_d.dds
* prp_fciwood_n.dds
* prp_fciwood_s.dds
* prp_ferbneple_dif.dds
* prp_ferbneple_norm.dds
* prp_ferprops_d.dds
* prp_ferprops_n.dds
* prp_ferprops_s.dds
* prp_fhe_window_01_d.dds
* prp_fhe_window_01_e.dds
* prp_fhe_window_01_n.dds
* prp_fhe_window_01_s.dds
* prp_fie_rock1_d.dds
* prp_fie_rock1_n.dds
* prp_fie_rock2_d.dds
* prp_fie_rock2_n.dds
* prp_fie_rock3_d.dds
* prp_fie_rock3_n.dds
* prp_fie_rock4_d.dds
* prp_fie_rock4_n.dds
* prp_fie_rock5_d.dds
* prp_fie_rock5_n.dds
* prp_fie_rock6_d.dds
* prp_fie_rock6_n.dds
* prp_fie_rock7_d.dds
* prp_fie_rock7_n.dds
* prp_fie_rock8_d.dds
* prp_fie_rock8_n.dds
* prp_fire01_0_d.dds
* prp_fleshtile_d.dds
* prp_fleshtile_h.dds
* prp_fleshtile_n.dds
* prp_fleshtile_s.dds
* prp_food01.dds
* prp_footpri_d.dds
* prp_footpri_n.dds
* prp_footpri_s.dds
* prp_greenrck_d.dds
* prp_greenrck_n.dds
* prp_haystack01_d.dds
* prp_haystack01_n.dds
* prp_haystack01_s.dds
* prp_haystack02_d.dds
* prp_haystack02_n.dds
* prp_haystack02_s.dds
* prp_hermithut_d.dds
* prp_hermithut_n.dds
* prp_hmf_dw1a_0d.dds
* prp_hmf_dw1a_0n.dds
* prp_hmf_dw1a_0s.dds
* prp_hmf_tp1b_0d.dds
* prp_hmf_tp1b_0n.dds
* prp_hmf_tp1b_0s.dds
* prp_hmf_tp2a_0d.dds
* prp_hmf_tp2a_0n.dds
* prp_hmf_tp2a_0s.dds
* prp_icicle_d.dds
* prp_icicle_n.dds
* prp_icicle_s.dds
* prp_ironblack_d.dds
* prp_ironblack_n.dds
* prp_ironblack_s.dds
* prp_ivyloose01_d.dds
* prp_ivyloose01_d2.dds
* prp_ivyloose01_n2.dds
* prp_ivyloose02_d.dds
* prp_ivywall01_d.dds
* prp_ivywall02_d.dds
* prp_ivywall02_d2.dds
* prp_ivywall02_n2.dds
* prp_lgtnking_01_0_lod.dds
* prp_lprop01_d.dds
* prp_lprop01_n.dds
* prp_lprop01_s.dds
* prp_mage01_d.dds
* prp_mage01_n.dds
* prp_mage01_s.dds
* prp_magicrock_d.dds
* prp_magicrock_n.dds
* prp_magicrock_s.dds
* prp_marble_d.dds
* prp_marble_n.dds
* prp_metal01_d.dds
* prp_metal01_n.dds
* prp_mirrorbronze_01d.dds
* prp_mirrorbronze_01n.dds
* prp_mirrorbronze_01s.dds
* prp_mirrormirror_01d.dds
* prp_mirrormirror_01n.dds
* prp_mirrormirror_01s.dds
* prp_mirrorstatue_01d.dds
* prp_mirrorstatue_01n.dds
* prp_mirrorstatue_01s.dds
* prp_mosstile_d.dds
* prp_mosstile_n.dds
* prp_mosstile_s.dds
* prp_nugplatter_d.dds
* prp_nugplatter_n.dds
* prp_nugplatter_s.dds
* prp_oilbowl_01_0_d.dds
* prp_oxa_0d.dds
* prp_oxa_0n.dds
* prp_oxa_0s.dds
* prp_paint1_d.dds
* prp_paint10_d.dds
* prp_paint11_d.dds
* prp_paint12_d.dds
* prp_paint13_d.dds
* prp_paint14_d.dds
* prp_paint2_d.dds
* prp_paint3_d.dds
* prp_paint4_d.dds
* prp_paint5_d.dds
* prp_paint6_d.dds
* prp_paint7_d.dds
* prp_paint9_d.dds
* prp_painting_01_d.dds
* prp_painting01_d.dds
* prp_painting01_n.dds
* prp_painting01_s.dds
* prp_painting02_d.dds
* prp_paintprt1_d.dds
* prp_paintprt2_d.dds
* prp_paintprt3_d.dds
* prp_paintprt4_d.dds
* prp_paintprt5_d.dds
* prp_paintprt6_d.dds
* prp_panel01_d.dds
* prp_panel01_n.dds
* prp_panel01_s.dds
* prp_panel02_d.dds
* prp_panel02_n.dds
* prp_panel02_s.dds
* prp_paragon_female_01d.dds
* prp_paragon_female_01s.dds
* prp_paragon_male_01d.dds
* prp_paragon_male_01n.dds
* prp_paragon_male_01s.dds
* prp_paragon_male_02d.dds
* prp_paragon_male_02n.dds
* prp_paragon_male_02s.dds
* prp_plant_0d.dds
* prp_plant_0n.dds
* prp_plant_0s.dds
* prp_planter_0d.dds
* prp_planter_0n.dds
* prp_planter_0s.dds
* prp_prt_dwarf_d.dds
* prp_prt_dwarf_s.dds
* prp_prt_humanf_d.dds
* prp_prt_humanf_s.dds
* prp_prt_humanm_d.dds
* prp_prt_humanm_s.dds
* prp_prt_n.dds
* prp_rckmoss_d.dds
* prp_rckmoss_n.dds
* prp_redcarp_d.dds
* prp_redcarp_s.dds
* prp_rock_d.dds
* prp_rock_n.dds
* prp_rock01_d.dds
* prp_rock01_n.dds
* prp_rock01_s.dds
* prp_rock01d.dds
* prp_rock01n.dds
* prp_rock02d.dds
* prp_rock03d.dds
* prp_rock03n.dds
* prp_rock06_d.dds
* prp_rock06_h.dds
* prp_rock06_n.dds
* prp_rock06_s.dds
* prp_rockmoss_d.dds
* prp_rockmoss_n.dds
* prp_rockmoss02_d.dds
* prp_rockmoss02_n.dds
* prp_rockmoss02_s.dds
* prp_root_d.dds
* prp_root_n.dds
* prp_root_s.dds
* prp_rootsb_d.dds
* prp_rootsb_n.dds
* prp_rootsb_s.dds
* prp_rug01_d.dds
* prp_rug01_n.dds
* prp_rug02_d.dds
* prp_rug02_n.dds
* prp_rug03_d.dds
* prp_rug03_n.dds
* prp_rug04_d.dds
* prp_rug04_n.dds
* prp_rug05_d.dds
* prp_rug05_n.dds
* prp_rug06_d.dds
* prp_rug06_n.dds
* prp_rugblue_d.dds
* prp_rugblue_n.dds
* prp_rugblue_s.dds
* prp_rugend_d.dds
* prp_rugend_n.dds
* prp_rugend_s.dds
* prp_ruggreen_d.dds
* prp_ruggreen_n.dds
* prp_ruggreen_s.dds
* prp_rugred_d.dds
* prp_rugred_n.dds
* prp_rugred_s.dds
* prp_sack01_d.dds
* prp_sack01_n.dds
* prp_sack01_s.dds
* prp_sackclth01_d.dds
* prp_sackclth01_n.dds
* prp_scafold1_0_lod.dds
* prp_scafold2_0_lod.dds
* prp_scafold3_0_lod.dds
* prp_scrolslf01_0d.dds
* prp_scrolslf01_0n.dds
* prp_scrolslf01_0s.dds
* prp_shrubleaves_d.dds
* prp_shrubleaves_n.dds
* prp_skybeam_01d.dds
* prp_skybeam_01e.dds
* prp_sngleshlve_d.dds
* prp_sngleshlve_s.dds
* prp_spdr_nst_egg_d.dds
* prp_spdr_nst_egg_n.dds
* prp_spdr_nst_egg_s.dds
* prp_spiderwebs_d.dds
* prp_spiderwebs_s.dds
* prp_spiderwebstile_d.dds
* prp_spiderwebstile_s.dds
* prp_stagestair_0_lod.dds
* prp_stagestair2_0_lod.dds
* prp_statuedwf_01_diff.dds
* prp_statuedwf_01_norm.dds
* prp_statuedwf_01_normb.dds
* prp_statuedwf_01_normc.dds
* prp_statueshield_01d.dds
* prp_statueshield_01n.dds
* prp_statueshield_01s.dds
* prp_steamvent_d.dds
* prp_steamvent_n.dds
* prp_steamvent_s.dds
* prp_steshelf01_0d.dds
* prp_steshelf01_0n.dds
* prp_steshelf01_0s.dds
* prp_stgladder1_0_lod.dds
* prp_stonea_0_lod.dds
* prp_stoneb_0_lod.dds
* prp_stonetrim01_d.dds
* prp_stonetrim01_n.dds
* prp_stonewall01_d.dds
* prp_stonewall01_n.dds
* prp_stump_02d.dds
* prp_stump_02n.dds
* prp_stump_d.dds
* prp_stump_n.dds
* prp_stump_s.dds
* prp_sulfgrnd_d.dds
* prp_sulfgrnd_n.dds
* prp_sulfgrnd_s.dds
* prp_sulfpool_d.dds
* prp_sulfpool_n.dds
* prp_sulfpool_s.dds
* prp_sulfvent_d.dds
* prp_sulfvent_n.dds
* prp_sulfvent_s.dds
* prp_table_01_0_lod.dds
* prp_table_01_d.dds
* prp_table_01_n.dds
* prp_tablestone_01_0_lod.dds
* prp_tapestry01_d.dds
* prp_tapestry01_n.dds
* prp_tapestry02_d.dds
* prp_tapestry02_n.dds
* prp_tarnishmirror_0_d.dds
* prp_tci_wind_lg2d.dds
* prp_tci_wind_lg2e.dds
* prp_tci_wind_lg2n.dds
* prp_tci_wind_lgd.dds
* prp_tci_wind_lge.dds
* prp_tci_wind_lgn.dds
* prp_tci_wind_smd.dds
* prp_tci_wind_sme.dds
* prp_tci_wind_smn.dds
* prp_tci_wind_sms.dds
* prp_tentberserk_01_0_lod.dds
* prp_tentcamping_01_0_lod.dds
* prp_tentchantry_01_0_lod.dds
* prp_tentduncan_01_0_lod.dds
* prp_tentking_01_0_lod.dds
* prp_tentloghain_01_0_lod.dds
* prp_tentmage_01_0_lod.dds
* prp_tentnoble_01_lod.dds
* prp_tevbrazier1_d.dds
* prp_tevbrazier1_n.dds
* prp_tevbrazier1_s.dds
* prp_throne_02_1.dds
* prp_throne_02_d.dds
* prp_throne_02_n.dds
* prp_torch_01_0_lod.dds
* prp_torch_02_0_lod.dds
* prp_torch_03_0_lod.dds
* prp_trashpile_d.dds
* prp_trashpile_n.dds
* prp_trashpile_s.dds
* prp_tree_d.dds
* prp_tree_n.dds
* prp_treea_01_0_lod.dds
* prp_treeb_01_0_lod.dds
* prp_treec_01_0_lod.dds
* prp_treeline_d.dds
* prp_treeline_n.dds
* prp_treemoss_d.dds
* prp_treemoss_n.dds
* prp_treemoss_s.dds
* prp_treemossblu_d.dds
* prp_tti_dirt_01_d.dds
* prp_tti_dirt_01_n.dds
* prp_tti_dirt_01_s.dds
* prp_tti_magestat_01_d.dds
* prp_tti_magestat_01_n.dds
* prp_tti_magestat_01_s.dds
* prp_tti_rubptc_01_d.dds
* prp_tti_rubptc_01_n.dds
* prp_tti_rubptc_01_s.dds
* prp_tti_towereagle_d.dds
* prp_tti_towereagle_n.dds
* prp_tti_towereagle_s.dds
* prp_tti_wallarchbar_d.dds
* prp_tti_wallarchbar_n.dds
* prp_tti_wallarchbar_s.dds
* prp_uprbooks_d.dds
* prp_uprbooks_n.dds
* prp_uprbooks_s.dds
* prp_vdarkspec_01_s.dds
* prp_wagoncover_01_lod.dds
* prp_wallarchiron_d.dds
* prp_wallarchiron_n.dds
* prp_wallarchiron_s.dds
* prp_washbasin_01n.dds
* prp_washbasin_01s.dds
* prp_washbasin_blood.dds
* prp_watchtower_01_0_lod.dds
* prp_wolfa_d.dds
* prp_wolfa_n.dds
* prp_wolfa_s.dds
* prp_wood01_d.dds
* prp_wood01_n.dds
* prp_wood2_dif.dds
* prp_wood2_n.dds
* prp_wood2_s.dds
* prp_woodbrk1_0_lod.dds
* prp_wooddr_d.dds
* prp_wooddr_n.dds
* prp_wooddr_s.dds
* prp_woodfnc_01_0_lod.dds
* prp_woodfnc_d.dds
* prp_woodfnc_n.dds
* prp_woodfnc_s.dds
* prp_woodgt_01_0_lod.dds
* prp_woodo_n.dds
* prp_woodpil1_0_d.dds
* prp_woodplank01_d.dds
* prp_woodplank01_n.dds
* prp_woodplank01_s.dds
* prp_woodrope_d.dds
* prp_woodrope_n.dds
* prp_woodrope_s.dds
* prp_wpnbarrelax_01d.dds
* prp_wpnbarrelax_01n.dds
* prp_wpnbarrelax_01s.dds
* prp_wpnbarrelsw_01d.dds
* prp_wpnbarrelsw_01n.dds
* prp_wpnbarrelsw_01s.dds
* prp_wpnstnd_d.dds
* prp_wpnstnd_n.dds
* prpbed_d.dds
* prpbed_n.dds
* prpbed_s.dds
* punchthroughmask.dds
* rmtst_probe_3679.dds
* rmtst_probe_3915.dds
* rmtst03_probe_3895.dds
* roofshingle02d.dds
* roofshingle02h.dds
* roofshingle02n.dds
* rope02d.dds
* rope02n.dds
* sb03_back.dds
* sb03_bcloud.dds
* sb03_cloud.dds
* sb03_front.dds
* sb03_perlin.dds
* scr_cave_l.dds
* scr_flatr_l.dds
* scr_rock01_l.dds
* scr_rock03_l.dds
* scr_rock06_l.dds
* scr_rock06red_d.dds
* scr_rock06red_l.dds
* secdoor_d.dds
* secdoor_n.dds
* secdoor_s.dds
* shutter01d.dds
* shutter01h.dds
* shutter01n.dds
* sighpost_d.dds
* sighpost_n.dds
* sighpost_s.dds
* snowpa01_d.dds
* snowpa01_n.dds
* snowpa01_s.dds
* snowpa02_d.dds
* snowpa02_n.dds
* snowpa02_s.dds
* sphere_color.dds
* sphere_normal.dds
* sphere_spec.dds
* spiderweb_d.dds
* spiderweb_s.dds
* spiderwebs_tile_d.dds
* spiderwebs_tile_s.dds
* spt_default_detail.dds
* stone_01d.dds
* stone_01n.dds
* stone_d.dds
* stone01_n.dds
* stonefloor03d.dds
* stonefloor03n.dds
* sys_tsgpumemoryover.dds
* tce_bigbannersd.dds
* tce_bigbannerss.dds
* tce_brconcrete_d.dds
* tce_brconcrete_h.dds
* tce_brconcrete_n.dds
* tce_brconcrete_s.dds
* tce_floor1_d.dds
* tce_floor1_h.dds
* tce_floor1_n.dds
* tce_floor1_s.dds
* tce_rubptc_01_0_lod.dds
* tce_stair_d.dds
* tce_stair_n.dds
* tce_stair_s.dds
* tce_stwall01_h.dds
* tce_stwall01_n.dds
* tce_stwall01_s.dds
* tce_stwall02_d.dds
* tce_testmaster_d.dds
* tce_testmaster_n.dds
* tce_testmaster_s.dds
* tce_trims_d.dds
* tce_trims_h.dds
* tce_trims_n.dds
* tce_trims_s.dds
* tce_wall02_d.dds
* tce_wall02_h.dds
* tce_wall02_n.dds
* tce_wall02_s.dds
* tce_wall06_d.dds
* tce_wall06_h.dds
* tce_wall06_n.dds
* tci_archtrim01_d.dds
* tci_archtrim01_n.dds
* tci_archtrim01_s.dds
* tci_ceilingmiddle_d.dds
* tci_ceilingmiddle_n.dds
* tci_ceilingmiddle_s.dds
* tci_dblwd_dr_d.dds
* tci_dblwd_dr_n.dds
* tci_dblwd_dr_s.dds
* tci_dh1_d.dds
* tci_dh1_n.dds
* tci_dh1_s.dds
* tci_eagle_d1.dds
* tci_eagle_h.dds
* tci_eagle_n.dds
* tci_floor1_d.dds
* tci_floor1_h.dds
* tci_floor1_n.dds
* tci_floor1_s.dds
* tci_icewall_d.dds
* tci_icewall_n.dds
* tci_lrgwd_dr_d.dds
* tci_lrgwd_dr_n.dds
* tci_lrgwd_dr_s.dds
* tci_middle_marble_d.dds
* tci_middle_marble_n.dds
* tci_middle_marble_s.dds
* tci_newwindow_01d.dds
* tci_newwindow_01e.dds
* tci_newwindow_01n.dds
* tci_newwindow_01s.dds
* tci_newwindow_02e.dds
* tci_newwindow_03e.dds
* tci_rinfrcd_dr_d.dds
* tci_rinfrcd_dr_n.dds
* tci_rinfrcd_dr_s.dds
* tci_rinfrcddbl_dr_d.dds
* tci_rinfrcddbl_dr_n.dds
* tci_rinfrcddbl_dr_s.dds
* tci_ruinbricks_d.dds
* tci_ruinbricks_n.dds
* tci_ruinbricks_s.dds
* tci_stair2_d.dds
* tci_stair2_h.dds
* tci_stair2_n.dds
* tci_stair2_s.dds
* tci_stair3_d.dds
* tci_stair3_n.dds
* tci_stair3_s.dds
* tci_stonedirt_d.dds
* tci_stonedirt_n.dds
* tci_stonedirt_s.dds
* tci_trim2_do.dds
* tci_trim2_h.dds
* tci_trim2_n.dds
* tci_trim2_s.dds
* tci_trims_d.dds
* tci_trims_h.dds
* tci_trims_n.dds
* tci_trims_s.dds
* tci_wall1_d.dds
* tci_wall1_h.dds
* tci_wall1_n.dds
* tci_wall1_s.dds
* tci_window_bright_e.dds
* tci_window_d.dds
* tci_window_dark_e.dds
* tci_window_day_e.dds
* tci_window_dim_e.dds
* tci_windowbroken_d.dds
* tci_windown_01_n.dds
* tci_wood01_d.dds
* tci_wood01_n.dds
* tci_wood01_s.dds
* tent_pole_d.dds
* tent_pole_n.dds
* tent_pole_s.dds
* tent_small_02n.dds
* testing.dds
* tfi_master_d.dds
* tfi_master_n.dds
* tfi_master_s.dds
* tti_master_d.dds
* tti_master_n.dds
* tti_master_s.dds
* tve_master_d.dds
* tve_master_n.dds
* tve_master_s.dds
* tvi_master_d.dds
* tvi_master_n.dds
* tvi_master_s.dds
* tvm_master_d.dds
* tvm_master_n.dds
* tvm_master_s.dds
* uh_checker_1k_d.dds
* uh_eye_nrma_0d.dds
* uh_eye_nrma_0m.dds
* uh_eye_nrma_0t.dds
* uh_eye_nrmi_0n.dds
* uh_eye_nrmo_0n.dds
* vfx_movearrow.dds
* vfx_movetarget.dds
* vfx_selbad.dds
* vfx_selbad_arrow.dds
* vfx_selbad_backstab.dds
* vfx_selbad_large.dds
* vfx_selbad_large_backstab.dds
* vfx_selbad_med.dds
* vfx_selbad_med_backstab.dds
* vfx_selbad2.dds
* vfx_selfrnd.dds
* vfx_selgood.dds
* vfx_selgood_large.dds
* vfx_selgood_med.dds
* vfx_selgood2.dds
* vfx_selparty.dds
* vfx_selparty_med.dds
* vfx_selparty2.dds
* vfx_selparty2_med.dds
* vis_mt_d.dds
* vis_mt02_d.dds
* vst_cliff_d.dds
* vst_mount_d.dds
* vst_mount_s.dds
* w_apothecary_01d.dds
* w_apothecary_01n.dds
* w_apothecary_01s.dds
* w_butcher_knife_01d.dds
* w_butcher_knife_01n.dds
* w_butcher_knife_01s.dds
* w_elven_light_01d.dds
* w_elven_light_01n.dds
* w_elven_light_01s.dds
* w_elven_stool_01d.dds
* w_elven_stool_01n.dds
* w_elven_stool_01s.dds
* w_hammer_01d.dds
* w_hammer_01n.dds
* w_hammer_01s.dds
* w_jars_01d.dds
* w_jars_01n.dds
* w_jars_01s.dds
* w_leaf_pile_01d.dds
* w_leaf_pile_01n.dds
* w_leaf_pile_01s.dds
* w_marble_pot_01d.dds
* w_marble_pot_01n.dds
* w_marble_pot_01s.dds
* w_phylactery_01ad.dds
* w_phylactery_01an.dds
* w_phylactery_01bd.dds
* w_phylactery_01bn.dds
* w_phylactery_01bs.dds
* w_sarcophagus_generic_01d.dds
* w_sarcophagus_generic_01n.dds
* w_sarcophagus_generic_01s.dds
* w_small_tree_01d.dds
* w_small_tree_01n.dds
* w_small_tree_01s.dds
* w_tongs_01d.dds
* w_tongs_01n.dds
* w_tongs_01s.dds
* wall_06_d.dds
* wall_06_n.dds
* wall_ivy01_d.dds
* wall_ivy01_n.dds
* wall_ivy01_s.dds
* wall_ivy02_d.dds
* wall_ivy02_n.dds
* wall_ivy02_s.dds
* wat_foam00d.dds
* wat_foam10d.dds
* wat_foam40d.dds
* wat_rdclf_falls_dist.dds
* wat_rdclf_falls_foam.dds
* wat_rdclf_falls_norm.dds
* wat_river00a.dds
* wat_river00n.dds
* wat_river00s.dds
* wat_river10a.dds
* wat_river10n.dds
* wat_river10s.dds
* wat_river11a.dds
* wat_river40a.dds
* wat_river40n.dds
* wat_river40s.dds
* wat_river41a.dds
* wat_white4c.dds
* water_bump_h.dds
* water_bump_n.dds
* water_d.dds
* water_n.dds
* water_s.dds
* waterpool_d.dds
* waterpool_n.dds
* waterpool_s.dds
* wood_messy_01d.dds
* wood_messy_01n.dds
* wood_messy_01s.dds
* wood1_d.dds
* wood1_n.dds
* wood1_s.dds
* wooddetail01d.dds
* wooddetail01n.dds
* woodpillar01d.dds
* woodpillar01h.dds
* woodpillar01n.dds
* woodpillar01s.dds
* woodplank_d.dds
* woodplank_h.dds
* woodplank_n.dds
* woodtrim_d.dds
* woodtrim_n.dds
* woodtrim_s.dds
* z_dust_little_w.dds

== Base game (high quality) ==

* 01_fire.dds
* 01_fire_f2.dds
* 01_fire_f2_blue.dds
* 02_fire.dds
* aflip_good.dds
* arc.dds
* arc_blur.dds
* ash_01.dds
* ash_02.dds
* ash_04_f.dds
* aur_missingvolume.dds
* aur_whitevol.dds
* b_caustic_flip.dds
* b_caustic_flip_n.dds
* beckmann.dds
* bee.dds
* bee_ball.dds
* bee_cyc.dds
* bee_cyc_g.dds
* bee_glow.dds
* bee_groud.dds
* bee_up2.dds
* bflipgood.dds
* bld_drian_m.dds
* bld_drian_tu2.dds
* bld_drian_tu2_a.dds
* bld_drian_tu3.dds
* bld_drian2.dds
* bld_pro_01.dds
* bld_pro_02.dds
* blood.dds
* blood_b.dds
* blood_conj_02.dds
* blood_conj_03.dds
* blood_conj_04.dds
* blood_cycle_sm.dds
* blood_loop2.dds
* blood_mud.dds
* blood_splatter_04.dds
* blood_w_s.dds
* blood3.dds
* bloodsmall5.dds
* blue_ground.dds
* blur_b.dds
* bm_leak_drop.dds
* bmm.80.dds
* bnn.80.dds
* bodyimp.dds
* bodyimp_v.dds
* branch2.dds
* butterfly01.dds
* butterfly02.dds
* c_ashwrath_0d.dds
* c_ashwrath_0n.dds
* c_ashwrath_0s.dds
* c_berkbeara_0d.dds
* c_berkbeara_0n.dds
* c_berkbeara_0s.dds
* c_blacbeara_0d.dds
* c_blacbeara_0n.dds
* c_blacbeara_0s.dds
* c_blgtwolfa_d.dds
* c_blgtwolfa_n.dds
* c_blgtwolfa_s.dds
* c_bronto_0d.dds
* c_bronto_0n.dds
* c_bronto_0s.dds
* c_bronto_0t.dds
* c_broodm1a_0d.dds
* c_broodm1a_0n.dds
* c_broodm1a_0s.dds
* c_broodm2a_0d.dds
* c_broodm2a_0n.dds
* c_broodm2a_0s.dds
* c_broodm3a_0d.dds
* c_broodm3a_0n.dds
* c_broodm3a_0s.dds
* c_broodm4a_0d.dds
* c_broodm4a_0n.dds
* c_broodm4a_0s.dds
* c_cata_d.dds
* c_cata_n.dds
* c_cata_s.dds
* c_cata_t.dds
* c_chickena_d.dds
* c_chickena_n.dds
* c_chickena_s.dds
* c_corspidra_0d.dds
* c_corspidra_0n.dds
* c_corspidra_0s.dds
* c_deepstkra_0d.dds
* c_deepstkra_0n.dds
* c_deepstkra_0s.dds
* c_deepstkra_0t.dds
* c_deera_0d.dds
* c_deera_0n.dds
* c_deera_0s.dds
* c_deera_0t.dds
* c_dog_tata.dds
* c_dog_tatb.dds
* c_dog_tatc.dds
* c_doga_0d.dds
* c_doga_0n.dds
* c_doga_0s.dds
* c_dragling_0d.dds
* c_dragling_0n.dds
* c_dragling_0s.dds
* c_dragling_0t.dds
* c_drake_0d.dds
* c_drake_0n.dds
* c_drake_0s.dds
* c_drake_0t.dds
* c_giaspidra_0d.dds
* c_giaspidra_0n.dds
* c_giaspidra_0s.dds
* c_giaspidra_0t.dds
* c_goata_0d.dds
* c_goata_0n.dds
* c_goata_0s.dds
* c_gretbeara_0d.dds
* c_gretbeara_0n.dds
* c_gretbeara_0s.dds
* c_hallaa_0d.dds
* c_hallaa_0n.dds
* c_hallaa_0s.dds
* c_mutta_0d.dds
* c_mutta_0n.dds
* c_mutta_0s.dds
* c_nuga_0d.dds
* c_nuga_0n.dds
* c_nuga_0s.dds
* c_owla_d.dds
* c_owla_n.dds
* c_owla_s.dds
* c_oxa_0d.dds
* c_oxa_0n.dds
* c_oxa_0s.dds
* c_oxa_0t.dds
* c_piga_0d.dds
* c_piga_0n.dds
* c_piga_0s.dds
* c_piga_0t.dds
* c_poispidra_0d.dds
* c_poispidra_0n.dds
* c_poispidra_0s.dds
* c_poispidra_0t.dds
* c_pridedem_bdy_0d.dds
* c_pridedem_bdy_0n.dds
* c_pridedem_bdy_0s.dds
* c_pridedem_hed_0d.dds
* c_pridedem_hed_0n.dds
* c_pridedem_hed_0s.dds
* c_ragedmon_0d.dds
* c_ragedmon_0e.dds
* c_ragedmon_0n.dds
* c_ragedmon_0s.dds
* c_rama_0d.dds
* c_rama_0n.dds
* c_rama_0s.dds
* c_rata_d.dds
* c_rata_n.dds
* c_rata_s.dds
* c_ravena_0d.dds
* c_ravena_0n.dds
* c_ravena_0s.dds
* c_shade_0d.dds
* c_shade_0n.dds
* c_shade_0s.dds
* c_squirrela_0d.dds
* c_squirrela_0n.dds
* c_squirrela_0s.dds
* c_squirrela_0t.dds
* c_wolfa_0d.dds
* c_wolfa_0n.dds
* c_wolfa_0s.dds
* c_wolfb_0d.dds
* c_wolfb_0n.dds
* c_wolfb_0s.dds
* cage_05.dds
* cage_06.dds
* caustic_flip.dds
* caustic_flip_a.dds
* caustic_flip_dis.dds
* chu_02.dds
* chu_06.dds
* ci_smoke03.dds
* ci_smoke05.dds
* cloud_f.dds
* cloud_f_bl.dds
* cloud_f_oil.dds
* cloud_f_w.dds
* cn_bdy_abma_0d.dds
* cn_bdy_abma_0n.dds
* cn_bdy_abma_0s.dds
* cn_bdy_adma_0d.dds
* cn_bdy_adma_0n.dds
* cn_bdy_adma_0s.dds
* cn_bdy_arh_0d.dds
* cn_bdy_arh_0n.dds
* cn_bdy_arh_0s.dds
* cn_bdy_cora_0d.dds
* cn_bdy_cora_0n.dds
* cn_bdy_cora_0s.dds
* cn_bdy_drga_0d.dds
* cn_bdy_drga_0n.dds
* cn_bdy_drga_0s.dds
* cn_bdy_glka_0d.dds
* cn_bdy_glka_0n.dds
* cn_bdy_glka_0s.dds
* cn_bdy_glka_0t.dds
* cn_bdy_glkb_0d.dds
* cn_bdy_glkb_0n.dds
* cn_bdy_glkb_0s.dds
* cn_bdy_glkc_0d.dds
* cn_bdy_glkc_0n.dds
* cn_bdy_glkc_0s.dds
* cn_bdy_graa_0d.dds
* cn_bdy_graa_0n.dds
* cn_bdy_graa_0s.dds
* cn_bdy_graa_0t.dds
* cn_bdy_hdra_0d.dds
* cn_bdy_hdra_0n.dds
* cn_bdy_hdra_0s.dds
* cn_bdy_hlka_0d.dds
* cn_bdy_hlka_0n.dds
* cn_bdy_hlka_0s.dds
* cn_bdy_hlka_0t.dds
* cn_bdy_hlkb_0d.dds
* cn_bdy_hlkb_0n.dds
* cn_bdy_hlkb_0s.dds
* cn_bdy_hlkc_0d.dds
* cn_bdy_hlkc_0n.dds
* cn_bdy_hlkc_0s.dds
* cn_bdy_lofa_0d.dds
* cn_bdy_lofa_0n.dds
* cn_bdy_ogra_0d.dds
* cn_bdy_ogra_0n.dds
* cn_bdy_ogra_0s.dds
* cn_bdy_reva_0d.dds
* cn_bdy_reva_0n.dds
* cn_bdy_reva_0s.dds
* cn_bdy_skla_0d.dds
* cn_bdy_skla_0n.dds
* cn_bdy_skla_0s.dds
* cn_bdy_snga_0d.dds
* cn_bdy_snga_0i.dds
* cn_bdy_snga_0n.dds
* cn_bdy_snga_0s.dds
* cn_bdy_snga_0t.dds
* cn_bdy_srk_0d.dds
* cn_bdy_srk_0n.dds
* cn_bdy_srk_0s.dds
* cn_bdy_stga_0d.dds
* cn_bdy_stga_0n.dds
* cn_bdy_stga_0s.dds
* cn_bdy_suca_0d.dds
* cn_bdy_suca_0e.dds
* cn_bdy_suca_0n.dds
* cn_bdy_suca_0s.dds
* cn_bdy_wera_0d.dds
* cn_bdy_wera_0n.dds
* cn_bdy_wera_0s.dds
* cn_bdy_wera_0t.dds
* cn_bdy_wsva_0d.dds
* cn_bdy_wsva_0n.dds
* cn_bdy_wsva_0s.dds
* cn_bra_graa_0d.dds
* cn_bra_graa_0n.dds
* cn_bra_graa_0s.dds
* cn_bra_wsva_0d.dds
* cn_bra_wsva_0n.dds
* cn_bra_wsva_0s.dds
* cn_eye_cora_0d.dds
* cn_eye_doga_0d.dds
* cn_eye_dogami_0n.dds
* cn_eye_draa_0d.dds
* cn_eye_drga_0d.dds
* cn_eye_hdra_0d.dds
* cn_eye_lofa_0d.dds
* cn_eye_ogra_0d.dds
* cn_eye_suca_0d.dds
* cn_eye_wera.dds
* cn_eye_wola_0d.dds
* cn_har_lofa_0d.dds
* cn_har_lofa_0n.dds
* cn_har_lofa_0s.dds
* cn_hed_abma_0d.dds
* cn_hed_abma_0n.dds
* cn_hed_abma_0s.dds
* cn_hed_abma_0t.dds
* cn_hed_adma_0d.dds
* cn_hed_adma_0n.dds
* cn_hed_adma_0s.dds
* cn_hed_arh_0d.dds
* cn_hed_arh_0n.dds
* cn_hed_arh_0s.dds
* cn_hed_cora_0d.dds
* cn_hed_cora_0n.dds
* cn_hed_cora_0s.dds
* cn_hed_dhla_0d.dds
* cn_hed_dhla_0n.dds
* cn_hed_dhla_0s.dds
* cn_hed_dhla_0t.dds
* cn_hed_glka_0d.dds
* cn_hed_glka_0n.dds
* cn_hed_glka_0s.dds
* cn_hed_glka_0t.dds
* cn_hed_glkb_0d.dds
* cn_hed_glkb_0n.dds
* cn_hed_glkb_0s.dds
* cn_hed_glkc_0d.dds
* cn_hed_glkc_0n.dds
* cn_hed_glkc_0s.dds
* cn_hed_hdra_0d.dds
* cn_hed_hdra_0n.dds
* cn_hed_hdra_0s.dds
* cn_hed_hlka_0d.dds
* cn_hed_hlka_0n.dds
* cn_hed_hlka_0s.dds
* cn_hed_hlka_0t.dds
* cn_hed_hlkb_0d.dds
* cn_hed_hlkb_0n.dds
* cn_hed_hlkb_0s.dds
* cn_hed_hlkc_0d.dds
* cn_hed_hlkc_0n.dds
* cn_hed_hlkc_0s.dds
* cn_hed_lofa_0d.dds
* cn_hed_lofa_0n.dds
* cn_hed_ogra_0d.dds
* cn_hed_ogra_0n.dds
* cn_hed_ogra_0s.dds
* cn_hed_reva_0d.dds
* cn_hed_reva_0e.dds
* cn_hed_reva_0n.dds
* cn_hed_reva_0s.dds
* cn_hed_skla_0d.dds
* cn_hed_skla_0n.dds
* cn_hed_skla_0s.dds
* cn_hed_skla_0t.dds
* cn_hed_snga_0d.dds
* cn_hed_snga_0i.dds
* cn_hed_snga_0n.dds
* cn_hed_snga_0s.dds
* cn_hed_snga_0t.dds
* cn_hed_srk_0d.dds
* cn_hed_srk_0n.dds
* cn_hed_srk_0s.dds
* cn_hed_suca_0d.dds
* cn_hed_suca_0e.dds
* cn_hed_suca_0n.dds
* cn_hed_suca_0s.dds
* cn_hed_wera_0d.dds
* cn_hed_wera_0n.dds
* cn_hed_wera_0s.dds
* cn_hed_wera_0t.dds
* cn_lea_graa_0d.dds
* cn_lea_graa_0n.dds
* cn_lea_graa_0s.dds
* cn_lea_wsva_0d.dds
* cn_lea_wsva_0n.dds
* cn_lea_wsva_0s.dds
* cn_low_hlka_0d.dds
* cn_low_hlka_0n.dds
* cn_low_hlka_0s.dds
* cn_low_hlka_0t.dds
* cn_lsw_reva_0d.dds
* cn_lsw_reva_0n.dds
* cn_lsw_reva_0s.dds
* cn_shd_reva_0d.dds
* cn_shd_reva_0n.dds
* cn_shd_reva_0s.dds
* cn_wng_adma_0d.dds
* cn_wng_adma_0n.dds
* cn_wng_adma_0s.dds
* cn_wng_hdra_0d.dds
* cn_wng_hdra_0n.dds
* cn_wng_hdra_0s.dds
* cr_center.dds
* cr_spe_01.dds
* crack.dds
* crack_g05.dds
* crack_ye.dds
* crack2.dds
* crack3.dds
* crate_03.dds
* crt_cycle.dds
* crt_cycle_2.dds
* crt_cycle_3.dds
* crt_cycle_4.dds
* crt_cycle_5.dds
* crt_cycle7.dds
* crt_spell.dds
* crt_star.dds
* crust_webs.dds
* crust_webs2.dds
* crust_webs3.dds
* crust_webs4.dds
* custic_dark.dds
* custic_light_f.dds
* custic_light_f2.dds
* custic001.dds
* custic00b.dds
* custic00b_a.dds
* custic00c.dds
* custic00c_a.dds
* custics002.dds
* cyc_air_big.dds
* cyc_cloud.dds
* cyc_cloud2.dds
* default_blackzero.dds
* default_specularmask.dds
* defaultnormal.dds
* df_arm_nuda_0d.dds
* df_arm_nuda_0n.dds
* df_arm_nuda_0s.dds
* df_arm_nuda_0t.dds
* dirty_bb.dds
* dirty_bb_nrm.dds
* dirty_stuff.dds
* dirty_stuff2.dds
* dis_02.dds
* dis_05.dds
* dis_ball.dds
* dis_ball_alph.dds
* dis_ball_in.dds
* dis_cu.dds
* dis_cu_alph.dds
* dis_vorta.dds
* dis_vorta_alp.dds
* discloud_alph.dds
* distor.dds
* distor_c1_alp.dds
* distor_cyl_alp.dds
* distor_cyl04_alp.dds
* distor_mask.dds
* distor_si.dds
* distortion_n.dds
* distortion_nh.dds
* dm_arm_nuda_0d.dds
* dm_arm_nuda_0n.dds
* dm_arm_nuda_0s.dds
* dm_arm_nuda_0t.dds
* dog_slaver.dds
* dot.dds
* dot_blur.dds
* dot_blur_a.dds
* dots.dds
* dots_02.dds
* dpl_black.dds
* dpl_black32.dds
* ele.dds
* ele_f2.dds
* enemytrap_reticle.dds
* evilbas_n.dds
* explo_shot.dds
* explo_smoke_blend.dds
* explo01.dds
* fire.dds
* fire_ball.dds
* fire_ball_blue.dds
* fire_f.dds
* fire_u_02.dds
* fire_u_06.dds
* flame_alpha.dds
* flame04.dds
* flare02.dds
* flesh.dds
* flesh2.dds
* fly.dds
* fx_0006_diff.dds
* fx_0014_diff.dds
* fx_0033_diff.dds
* fx_0034_diff.dds
* fx_1014_diff.dds
* fx_1018_diff.dds
* fx_1018_diff_a.dds
* fx_2003_diff.dds
* fx_ab_01.dds
* fx_arrow.dds
* fx_black_blast.dds
* fx_black_line.dds
* fx_blizz_flake.dds
* fx_blizz_swirl.dds
* fx_blood01.dds
* fx_blue_line.dds
* fx_center_snow_large.dds
* fx_chest.dds
* fx_circle.dds
* fx_cloud.dds
* fx_cloud01.dds
* fx_cloudbrown.dds
* fx_crescent01.dds
* fx_crescent02.dds
* fx_d_blank.dds
* fx_d_noise01.dds
* fx_d_noise02.dds
* fx_d_noise03.dds
* fx_d_ring01.dds
* fx_d_ring01_m.dds
* fx_d_sphere.dds
* fx_d_sphere_m.dds
* fx_d_spherem.dds
* fx_d_twirl.dds
* fx_d_twirl_m.dds
* fx_darkbolt.dds
* fx_dazz_halo.dds
* fx_dirt_blast.dds
* fx_dirt_spec.dds
* fx_dot.dds
* fx_dot01.dds
* fx_dust.dds
* fx_dust_bl.dds
* fx_dust_bl_h.dds
* fx_dust_sms01.dds
* fx_dust007.dds
* fx_dust05.dds
* fx_dust05_a.dds
* fx_dust06.dds
* fx_dust07.dds
* fx_energy_blast.dds
* fx_energy01.dds
* fx_energy02.dds
* fx_energy03.dds
* fx_equake.dds
* fx_exp_fing_cloud.dds
* fx_explosion02_flip.dds
* fx_explosion02_flipb.dds
* fx_f1c1.dds
* fx_f2c5.dds
* fx_f3c3.dds
* fx_fade_flip_cloud.dds
* fx_fade_skybox.dds
* fx_fadecloud_trans.dds
* fx_fadecloudb.dds
* fx_fire01.dds
* fx_fireball01.dds
* fx_fireringfb.dds
* fx_firetorchfb.dds
* fx_firetwister.dds
* fx_firetwister1.dds
* fx_fl_smoke.dds
* fx_fl_smoke_blend.dds
* fx_flamefb01.dds
* fx_flamefb02.dds
* fx_flamefb03.dds
* fx_floor_tile.dds
* fx_glow01.dds
* fx_glow02.dds
* fx_glow02_a.dds
* fx_glow03.dds
* fx_glyph.dds
* fx_glyph_neutral.dds
* fx_glyph_paral.dds
* fx_glyph_repul.dds
* fx_glyph_warding.dds
* fx_grass.dds
* fx_grass_b.dds
* fx_grass_small.dds
* fx_greasepool.dds
* fx_ground_exp.dds
* fx_headsmoke.dds
* fx_icebling.dds
* fx_iceboof.dds
* fx_icecloud.dds
* fx_icecrystal.dds
* fx_icestormcloud.dds
* fx_impact01.dds
* fx_impact011.dds
* fx_impact012.dds
* fx_impact013.dds
* fx_impact02.dds
* fx_kungfu_dust.dds
* fx_lens_flare.dds
* fx_lightning03.dds
* fx_lightningbolt01.dds
* fx_lightningbolt02.dds
* fx_link.dds
* fx_lit_half.dds
* fx_lowerlag.dds
* fx_m1c4.dds
* fx_m2c2.dds
* fx_m3c6.dds
* fx_markofdeath.dds
* fx_mfx_ad_wing.dds
* fx_mfx_def.dds
* fx_mfx_dmg.dds
* fx_noise01.dds
* fx_noise02.dds
* fx_rain01.dds
* fx_ray_line.dds
* fx_ring01.dds
* fx_rock_chips.dds
* fx_sa_comb_60.dds
* fx_sa_comb_60_1.dds
* fx_sa_comb_60_2.dds
* fx_sa_comb_60_3.dds
* fx_sa_comb_60_4.dds
* fx_sa_comb_70_1.dds
* fx_sa_comb_70_2.dds
* fx_sa_comb_80.dds
* fx_sa_comb_80_1.dds
* fx_sa_comb_80_2.dds
* fx_sa_comb01.dds
* fx_sa_dead.dds
* fx_sa_grun01.dds
* fx_sa_grun02.dds
* fx_sa_grun03.dds
* fx_sa_hrun01.dds
* fx_sa_hrun02.dds
* fx_sa_hrun03.dds
* fx_sa_hurl_40.dds
* fx_sa_hurl_40b.dds
* fx_sa_hurl_60.dds
* fx_sa_hurl_80.dds
* fx_sa_ogre_60.dds
* fx_sa_run_hrl.dds
* fx_sa_run_hum.dds
* fx_sa_torches.dds
* fx_sb_tear.dds
* fx_smoke.dds
* fx_smoke_cig.dds
* fx_smoke_vol.dds
* fx_smokebillow_fb.dds
* fx_smokebillow01.dds
* fx_smokeghost_flipbook.dds
* fx_smokelink01.dds
* fx_smokenewss.dds
* fx_smoketemp.dds
* fx_smoketrail01.dds
* fx_snow_fall.dds
* fx_snow_wsip.dds
* fx_snowflake01.dds
* fx_snowparticals.dds
* fx_snowvolume.dds
* fx_st_cloud.dds
* fx_st_cloud_a.dds
* fx_st_cloud_add.dds
* fx_st_cloudb.dds
* fx_tendrils01.dds
* fx_tent_64frm.dds
* fx_tree.dds
* fx_twirl_air.dds
* fx_twirl01.dds
* fx_twist.dds
* fx_upperlag.dds
* fx_vert_grad.dds
* fx_vol_light.dds
* fx_waterpour01.dds
* fx_web01.dds
* fx_whirlwind.dds
* fx_white.dds
* fx_woodgrain.dds
* fx_z.dds
* fxa_cen_aoe.dds
* fxa_cen_exo_smoke_blend.dds
* fxa_cen_light_sp.dds
* fxa_cen_red_c.dds
* fxa_cen_smoke.dds
* fxa_cen_smoke_add.dds
* fxa_cen_smoke_add_nrm.dds
* fxa_cen_snow.dds
* fxa_cen_splash.dds
* fxa_cen_volt.dds
* fxa_cen_volt2.dds
* fxa_cen_volt3.dds
* fxa_circle_dis_h.dds
* fxa_circle_dis_n.dds
* fxa_evl_smoke.dds
* fxa_lf_flower.dds
* fxa_pois_calt.dds
* fxa_pois_spin.dds
* fxa_pois_split.dds
* fxa_pois_split_blur.dds
* fxa_power_dirty.dds
* fxa_power_smoke.dds
* fxa_rocka.dds
* fxa_shield_spk.dds
* fxa_stun_spk.dds
* fxa_unholy_beams.dds
* fxa_unholy_bt.dds
* fxa_unholy_center.dds
* fxa_unholy_distortion.dds
* fxa_unholy_dusts.dds
* fxa_unholy_sharp.dds
* fxa_web_flare.dds
* fxc_lof_root.dds
* fxc_puke_ani.dds
* fxc_puke_blend.dds
* fxc_puke_hei.dds
* fxc_puke_shine.dds
* fxc_puke_sp.dds
* fxc_puke_sp_nrm.dds
* fxc_puke_sp_white.dds
* fxc_puke_vol.dds
* fxc_spider_web.dds
* fxc_water_drop.dds
* fxe_caustics_dif.dds
* fxe_cracked_nm.dds
* fxe_craked_glass.dds
* fxe_craked_glass_add.dds
* fxe_day_beams.dds
* fxe_day_beams_blured.dds
* fxe_day_beams_orz.dds
* fxe_dust_sunshine.dds
* fxe_fluff.dds
* fxe_fswater_ripple.dds
* fxe_ice_distor_dm.dds
* fxe_ice_distor_hm.dds
* fxe_ice_distor_nm.dds
* fxe_lava_explo.dds
* fxe_lava_spark.dds
* fxe_lava_stones.dds
* fxe_rippleout.dds
* fxe_shadow.dds
* fxe_snow_tiny.dds
* fxe_sunshine.dds
* fxe_tree_beam.dds
* fxe_water_color.dds
* fxe_water_disn.dds
* fxe_water_disnh.dds
* fxe_water_fall.dds
* fxe_water_form.dds
* fxe_water_pan_add.dds
* fxe_water_pan2.dds
* fxe_water_smoke2_add.dds
* fxe_water_smoke2_blend.dds
* fxe_water_smokes_add.dds
* fxe_water_sp.dds
* fxe_water_tiny.dds
* fxe_water_v_sp.dds
* fxe_waterblend.dds
* fxp_pillar_sym01.dds
* fxp_pillar_sym02.dds
* fxp_pillar_sym03.dds
* fxp_pillar_sym04.dds
* fxp_pillar_sym05.dds
* glow.dds
* glow4.dds
* glow4_a.dds
* glows.dds
* gore_default.dds
* hdistortion.dds
* head_flip_rev.dds
* head_flipv2.dds
* headgrab_flip.dds
* heallight3.dds
* hf_arm_nuda_0d.dds
* hf_arm_nuda_0n.dds
* hf_arm_nuda_0s.dds
* hf_arm_nuda_0t.dds
* hm_arm_nuda_0d.dds
* hm_arm_nuda_0n.dds
* hm_arm_nuda_0s.dds
* hm_arm_nuda_0t.dds
* hm_bak_lgtb_0d.dds
* hm_bak_lgtb_0n.dds
* hm_bak_lgtb_0s.dds
* hm_bak_lgtb_0t.dds
* hm_baked_0d.dds
* hm_baked_0n.dds
* hm_baked_0s.dds
* hm_hlf_meda_0d.dds
* hm_hlf_meda_0n.dds
* hm_hlf_meda_0s.dds
* hm_hlf_meda_0t.dds
* hro_anvil_crust01d.dds
* hro_anvil_lava01a.dds
* ice_crust.dds
* ice_shard.dds
* ice_shard_body.dds
* icicle01.dds
* lav_crust01a.dds
* lav_crust01d.dds
* lav_crust02d.dds
* lav_river00a.dds
* lav_river01a.dds
* lav_river03a.dds
* lava_alpha.dds
* lava_color.dds
* leave_001.dds
* leave_01.dds
* leave_03.dds
* leave_05.dds
* leave_06.dds
* leave_07.dds
* leave_f.dds
* lfx_glow01.dds
* lfx_noise2.dds
* lfx_temp01.dds
* lig3.dds
* lightni_5.dds
* lightning.dds
* lightning_bolt3.dds
* lightning_f.dds
* lightning_stone.dds
* lightning_stone_2.dds
* magma.dds
* matdef_dc_diffuse.dds
* matdef_dc_normal.dds
* matdef_dc_specular.dds
* matdef_dca_diffuse.dds
* matdef_dcb_diffuse.dds
* matdef_dcc_diffuse.dds
* matdef_dcd_diffuse.dds
* matdef_df_diffuse.dds
* matdef_df_normal.dds
* matdef_df_specular.dds
* matdef_dh_diffuse.dds
* matdef_dh_specshft.dds
* matdef_dw_diffuse.dds
* matdef_dw_normal.dds
* matdef_dw_specular.dds
* mnd_cycle_f2.dds
* mnd_cycle_f3.dds
* mud_cl.dds
* mud_f.dds
* mud_f_w.dds
* mud_sh.dds
* normals_streak.dds
* normals_streak_alpha.dds
* og_flsh_01.dds
* og_flsh_02.dds
* og_flsh_03.dds
* og_flsh_04.dds
* ogre_sl_01.1.dds
* ogre_sl_01.dds
* ogre_sl_02.2.dds
* ogre_sl_02.3.dds
* ogre_sl_02.dds
* ogre_sl_03.dds
* ogre_sl_04.dds
* ogre_sl_06.dds
* ogre_sl_06_sq.dds
* oil_256.dds
* oil_dot_2.dds
* oil_f2.dds
* oil_loop.dds
* oil_si.dds
* pf_arm_hvya_0d.dds
* pf_arm_hvya_0n.dds
* pf_arm_hvya_0s.dds
* pf_arm_hvya_0t.dds
* pf_arm_hvyb_0d.dds
* pf_arm_hvyb_0n.dds
* pf_arm_hvyb_0s.dds
* pf_arm_hvyb_0t.dds
* pf_arm_hvyc_0d.dds
* pf_arm_hvyc_0n.dds
* pf_arm_hvyc_0s.dds
* pf_arm_hvyc_0t.dds
* pf_arm_hvyd_0d.dds
* pf_arm_hvyd_0n.dds
* pf_arm_hvyd_0s.dds
* pf_arm_hvyd_0t.dds
* pf_arm_hvye_0d.dds
* pf_arm_hvye_0n.dds
* pf_arm_hvye_0s.dds
* pf_arm_lgta_0d.dds
* pf_arm_lgta_0n.dds
* pf_arm_lgta_0s.dds
* pf_arm_lgta_0t.dds
* pf_arm_lgtb_0d.dds
* pf_arm_lgtb_0n.dds
* pf_arm_lgtb_0s.dds
* pf_arm_lgtb_0t.dds
* pf_arm_lgtc_0d.dds
* pf_arm_lgtc_0n.dds
* pf_arm_lgtc_0s.dds
* pf_arm_lgtc_0t.dds
* pf_arm_lgtd_0d.dds
* pf_arm_lgtd_0n.dds
* pf_arm_lgtd_0s.dds
* pf_arm_lgtd_0t.dds
* pf_arm_meda_0d.dds
* pf_arm_meda_0n.dds
* pf_arm_meda_0s.dds
* pf_arm_meda_0t.dds
* pf_arm_medb_0d.dds
* pf_arm_medb_0n.dds
* pf_arm_medb_0s.dds
* pf_arm_medb_0t.dds
* pf_arm_medc_0d.dds
* pf_arm_medc_0n.dds
* pf_arm_medc_0s.dds
* pf_arm_medc_0t.dds
* pf_arm_medd_0d.dds
* pf_arm_medd_0n.dds
* pf_arm_medd_0s.dds
* pf_arm_medd_0t.dds
* pf_chd_grla_0d.dds
* pf_chd_grla_0n.dds
* pf_chd_grla_0s.dds
* pf_chd_grla_0t.dds
* pf_cth_coma_0d.dds
* pf_cth_coma_0n.dds
* pf_cth_coma_0s.dds
* pf_cth_coma_0t.dds
* pf_cth_comb_0d.dds
* pf_cth_comb_0n.dds
* pf_cth_comb_0s.dds
* pf_cth_comb_0t.dds
* pf_cth_comc_0d.dds
* pf_cth_comc_0n.dds
* pf_cth_comc_0s.dds
* pf_cth_comc_0t.dds
* pf_cth_comd_0d.dds
* pf_cth_comd_0n.dds
* pf_cth_comd_0s.dds
* pf_cth_comd_0t.dds
* pf_cth_come_0d.dds
* pf_cth_come_0n.dds
* pf_cth_come_0s.dds
* pf_cth_come_0t.dds
* pf_cth_comf_0d.dds
* pf_cth_comf_0n.dds
* pf_cth_comf_0s.dds
* pf_cth_comf_0t.dds
* pf_cth_comg_0d.dds
* pf_cth_comg_0n.dds
* pf_cth_comg_0s.dds
* pf_cth_comg_0t.dds
* pf_cth_comh_0d.dds
* pf_cth_comh_0n.dds
* pf_cth_comh_0s.dds
* pf_cth_comh_0t.dds
* pf_cth_comi_0d.dds
* pf_cth_comi_0n.dds
* pf_cth_comi_0s.dds
* pf_cth_comi_0t.dds
* pf_cth_comj_0d.dds
* pf_cth_comj_0n.dds
* pf_cth_comj_0s.dds
* pf_cth_comj_0t.dds
* pf_cth_comk_0d.dds
* pf_cth_comk_0n.dds
* pf_cth_comk_0s.dds
* pf_cth_comk_0t.dds
* pf_cth_fata_0d.dds
* pf_cth_fata_0n.dds
* pf_cth_fata_0s.dds
* pf_cth_fata_0t.dds
* pf_cth_nbla_0d.dds
* pf_cth_nbla_0n.dds
* pf_cth_nbla_0s.dds
* pf_cth_nbla_0t.dds
* pf_cth_nblb_0d.dds
* pf_cth_nblb_0n.dds
* pf_cth_nblb_0s.dds
* pf_cth_nblb_0t.dds
* pf_cth_nblc_0d.dds
* pf_cth_nblc_0n.dds
* pf_cth_nblc_0s.dds
* pf_cth_nblc_0t.dds
* pf_cth_nbld_0d.dds
* pf_cth_nbld_0n.dds
* pf_cth_nbld_0s.dds
* pf_cth_nbld_0t.dds
* pf_cth_nble_0d.dds
* pf_cth_nble_0n.dds
* pf_cth_nble_0s.dds
* pf_cth_nble_0t.dds
* pf_rob_appa_0d.dds
* pf_rob_appa_0n.dds
* pf_rob_appa_0s.dds
* pf_rob_appa_0t.dds
* pf_rob_appb_0d.dds
* pf_rob_appb_0n.dds
* pf_rob_appb_0s.dds
* pf_rob_appb_0t.dds
* pf_rob_chaa_0d.dds
* pf_rob_chaa_0n.dds
* pf_rob_chaa_0s.dds
* pf_rob_chaa_0t.dds
* pf_rob_chab_0d.dds
* pf_rob_chab_0n.dds
* pf_rob_chab_0s.dds
* pf_rob_chab_0t.dds
* pf_rob_enca_0d.dds
* pf_rob_enca_0n.dds
* pf_rob_enca_0s.dds
* pf_rob_enca_0t.dds
* pf_rob_encb_0d.dds
* pf_rob_encb_0n.dds
* pf_rob_encb_0s.dds
* pf_rob_encb_0t.dds
* pf_rob_mora_0d.dds
* pf_rob_mora_0n.dds
* pf_rob_mora_0s.dds
* pf_rob_mora_0t.dds
* pla_s.dds
* plasma.dds
* pls_hilight.dds
* pm_arm_hvya_0d.dds
* pm_arm_hvya_0n.dds
* pm_arm_hvya_0s.dds
* pm_arm_hvya_0t.dds
* pm_arm_hvyb_0d.dds
* pm_arm_hvyb_0n.dds
* pm_arm_hvyb_0s.dds
* pm_arm_hvyb_0t.dds
* pm_arm_hvyc_0d.dds
* pm_arm_hvyc_0n.dds
* pm_arm_hvyc_0s.dds
* pm_arm_hvyc_0t.dds
* pm_arm_hvyd_0d.dds
* pm_arm_hvyd_0n.dds
* pm_arm_hvyd_0s.dds
* pm_arm_hvyd_0t.dds
* pm_arm_hvye_0d.dds
* pm_arm_hvye_0n.dds
* pm_arm_hvye_0s.dds
* pm_arm_lgta_0d.dds
* pm_arm_lgta_0n.dds
* pm_arm_lgta_0s.dds
* pm_arm_lgta_0t.dds
* pm_arm_lgtb_0d.dds
* pm_arm_lgtb_0n.dds
* pm_arm_lgtb_0s.dds
* pm_arm_lgtb_0t.dds
* pm_arm_lgtc_0d.dds
* pm_arm_lgtc_0n.dds
* pm_arm_lgtc_0s.dds
* pm_arm_lgtc_0t.dds
* pm_arm_lgtd_0d.dds
* pm_arm_lgtd_0n.dds
* pm_arm_lgtd_0s.dds
* pm_arm_lgtd_0t.dds
* pm_arm_meda_0d.dds
* pm_arm_meda_0n.dds
* pm_arm_meda_0s.dds
* pm_arm_meda_0t.dds
* pm_arm_medb_0d.dds
* pm_arm_medb_0n.dds
* pm_arm_medb_0s.dds
* pm_arm_medb_0t.dds
* pm_arm_medc_0d.dds
* pm_arm_medc_0n.dds
* pm_arm_medc_0s.dds
* pm_arm_medc_0t.dds
* pm_arm_medd_0d.dds
* pm_arm_medd_0n.dds
* pm_arm_medd_0s.dds
* pm_arm_medd_0t.dds
* pm_bdy_duna_0d.dds
* pm_bdy_duna_0n.dds
* pm_bdy_duna_0s.dds
* pm_chd_boya_0d.dds
* pm_chd_boya_0n.dds
* pm_chd_boya_0s.dds
* pm_chd_boya_0t.dds
* pm_cth_coma_0d.dds
* pm_cth_coma_0n.dds
* pm_cth_coma_0s.dds
* pm_cth_coma_0t.dds
* pm_cth_comb_0d.dds
* pm_cth_comb_0n.dds
* pm_cth_comb_0s.dds
* pm_cth_comb_0t.dds
* pm_cth_comc_0d.dds
* pm_cth_comc_0n.dds
* pm_cth_comc_0s.dds
* pm_cth_comc_0t.dds
* pm_cth_comd_0d.dds
* pm_cth_comd_0n.dds
* pm_cth_comd_0s.dds
* pm_cth_comd_0t.dds
* pm_cth_come_0d.dds
* pm_cth_come_0n.dds
* pm_cth_come_0s.dds
* pm_cth_come_0t.dds
* pm_cth_comf_0d.dds
* pm_cth_comf_0n.dds
* pm_cth_comf_0s.dds
* pm_cth_comf_0t.dds
* pm_cth_comg_0d.dds
* pm_cth_comg_0n.dds
* pm_cth_comg_0s.dds
* pm_cth_comg_0t.dds
* pm_cth_comh_0d.dds
* pm_cth_comh_0n.dds
* pm_cth_comh_0s.dds
* pm_cth_comh_0t.dds
* pm_cth_comi_0d.dds
* pm_cth_comi_0n.dds
* pm_cth_comi_0s.dds
* pm_cth_comi_0t.dds
* pm_cth_comj_0d.dds
* pm_cth_comj_0n.dds
* pm_cth_comj_0s.dds
* pm_cth_comj_0t.dds
* pm_cth_comk_0d.dds
* pm_cth_comk_0n.dds
* pm_cth_comk_0s.dds
* pm_cth_comk_0t.dds
* pm_cth_fata_0d.dds
* pm_cth_fata_0n.dds
* pm_cth_fata_0s.dds
* pm_cth_fata_0t.dds
* pm_cth_nbla_0d.dds
* pm_cth_nbla_0n.dds
* pm_cth_nbla_0s.dds
* pm_cth_nbla_0t.dds
* pm_cth_nblb_0d.dds
* pm_cth_nblb_0n.dds
* pm_cth_nblb_0s.dds
* pm_cth_nblb_0t.dds
* pm_cth_nblc_0d.dds
* pm_cth_nblc_0n.dds
* pm_cth_nblc_0s.dds
* pm_cth_nblc_0t.dds
* pm_cth_nbld_0d.dds
* pm_cth_nbld_0n.dds
* pm_cth_nbld_0s.dds
* pm_cth_nbld_0t.dds
* pm_cth_nble_0d.dds
* pm_cth_nble_0n.dds
* pm_cth_nble_0s.dds
* pm_cth_nble_0t.dds
* pm_rob_appa_0d.dds
* pm_rob_appa_0n.dds
* pm_rob_appa_0s.dds
* pm_rob_appa_0t.dds
* pm_rob_appb_0d.dds
* pm_rob_appb_0n.dds
* pm_rob_appb_0s.dds
* pm_rob_appb_0t.dds
* pm_rob_chaa_0d.dds
* pm_rob_chaa_0n.dds
* pm_rob_chaa_0s.dds
* pm_rob_chaa_0t.dds
* pm_rob_chab_0d.dds
* pm_rob_chab_0n.dds
* pm_rob_enca_0d.dds
* pm_rob_enca_0n.dds
* pm_rob_enca_0s.dds
* pm_rob_enca_0t.dds
* pm_rob_encb_0d.dds
* pm_rob_encb_0n.dds
* pm_rob_encb_0s.dds
* pm_rob_encb_0t.dds
* pn_arm_dwpa_0d.dds
* pn_arm_dwpa_0n.dds
* pn_arm_dwpa_0s.dds
* pn_arm_dwpb_0d.dds
* pn_arm_dwpb_0n.dds
* pn_arm_dwpb_0s.dds
* pn_arm_masa_0d.dds
* pn_arm_masa_0n.dds
* pn_arm_masa_0s.dds
* pn_arm_masa_0t.dds
* pn_arm_masb_0d.dds
* pn_arm_masb_0n.dds
* pn_arm_masb_0s.dds
* pn_arm_masb_0t.dds
* pn_arm_masc_0d.dds
* pn_arm_masc_0n.dds
* pn_arm_masc_0s.dds
* pn_arm_masc_0t.dds
* pn_arm_masd_0d.dds
* pn_arm_masd_0n.dds
* pn_arm_masd_0s.dds
* pn_arm_masd_0t.dds
* pn_arm_mase_0d.dds
* pn_arm_mase_0n.dds
* pn_arm_mase_0s.dds
* pn_arm_mase_0t.dds
* pn_boo_dwpa_0d.dds
* pn_boo_dwpa_0n.dds
* pn_boo_dwpa_0s.dds
* pn_boo_dwpb_0d.dds
* pn_boo_dwpb_0n.dds
* pn_boo_dwpb_0s.dds
* pn_boo_hvya_0d.dds
* pn_boo_hvya_0n.dds
* pn_boo_hvya_0s.dds
* pn_boo_hvya_0t.dds
* pn_boo_hvyb_0d.dds
* pn_boo_hvyb_0n.dds
* pn_boo_hvyb_0s.dds
* pn_boo_hvyb_0t.dds
* pn_boo_hvyc_0d.dds
* pn_boo_hvyc_0n.dds
* pn_boo_hvyc_0s.dds
* pn_boo_hvyc_0t.dds
* pn_boo_hvyd_0d.dds
* pn_boo_hvyd_0n.dds
* pn_boo_hvyd_0s.dds
* pn_boo_hvyd_0t.dds
* pn_boo_hvye_0d.dds
* pn_boo_hvye_0n.dds
* pn_boo_hvye_0s.dds
* pn_boo_lgta_0d.dds
* pn_boo_lgta_0n.dds
* pn_boo_lgta_0s.dds
* pn_boo_lgta_0t.dds
* pn_boo_lgtb_0d.dds
* pn_boo_lgtb_0n.dds
* pn_boo_lgtb_0s.dds
* pn_boo_lgtb_0t.dds
* pn_boo_lgtc_0d.dds
* pn_boo_lgtc_0n.dds
* pn_boo_lgtc_0s.dds
* pn_boo_lgtc_0t.dds
* pn_boo_lgtd_0d.dds
* pn_boo_lgtd_0n.dds
* pn_boo_lgtd_0s.dds
* pn_boo_lgtd_0t.dds
* pn_boo_lgte_0d.dds
* pn_boo_lgte_0n.dds
* pn_boo_lgte_0s.dds
* pn_boo_lgte_0t.dds
* pn_boo_masa_0d.dds
* pn_boo_masa_0n.dds
* pn_boo_masa_0s.dds
* pn_boo_masa_0t.dds
* pn_boo_masb_0d.dds
* pn_boo_masb_0n.dds
* pn_boo_masb_0s.dds
* pn_boo_masb_0t.dds
* pn_boo_masc_0d.dds
* pn_boo_masc_0n.dds
* pn_boo_masc_0s.dds
* pn_boo_masc_0t.dds
* pn_boo_masd_0d.dds
* pn_boo_masd_0n.dds
* pn_boo_masd_0s.dds
* pn_boo_masd_0t.dds
* pn_boo_mase_0d.dds
* pn_boo_mase_0n.dds
* pn_boo_mase_0s.dds
* pn_boo_mase_0t.dds
* pn_boo_meda_0d.dds
* pn_boo_meda_0n.dds
* pn_boo_meda_0s.dds
* pn_boo_meda_0t.dds
* pn_boo_medb_0d.dds
* pn_boo_medb_0n.dds
* pn_boo_medb_0s.dds
* pn_boo_medb_0t.dds
* pn_boo_medc_0d.dds
* pn_boo_medc_0n.dds
* pn_boo_medc_0s.dds
* pn_boo_medc_0t.dds
* pn_boo_medd_0d.dds
* pn_boo_medd_0n.dds
* pn_boo_medd_0s.dds
* pn_boo_medd_0t.dds
* pn_eye_drka_0d.dds
* pn_eye_drka_0t.dds
* pn_eye_dsda_0d.dds
* pn_eye_dsea_0d.dds
* pn_eye_mora_0d.dds
* pn_eye_nrma_0d.dds
* pn_eye_nrma_0t.dds
* pn_eye_nrmi_0n.dds
* pn_eye_nrmo_0n.dds
* pn_eye_quna_0d.dds
* pn_eye_stna_0d.dds
* pn_glv_dwpa_0d.dds
* pn_glv_dwpa_0n.dds
* pn_glv_dwpa_0s.dds
* pn_glv_dwpb_0d.dds
* pn_glv_dwpb_0n.dds
* pn_glv_dwpb_0s.dds
* pn_glv_hvya_0d.dds
* pn_glv_hvya_0n.dds
* pn_glv_hvya_0s.dds
* pn_glv_hvya_0t.dds
* pn_glv_hvyb_0d.dds
* pn_glv_hvyb_0n.dds
* pn_glv_hvyb_0s.dds
* pn_glv_hvyb_0t.dds
* pn_glv_hvyc_0d.dds
* pn_glv_hvyc_0n.dds
* pn_glv_hvyc_0s.dds
* pn_glv_hvyc_0t.dds
* pn_glv_hvyd_0d.dds
* pn_glv_hvyd_0n.dds
* pn_glv_hvyd_0s.dds
* pn_glv_hvyd_0t.dds
* pn_glv_hvye_0d.dds
* pn_glv_hvye_0n.dds
* pn_glv_hvye_0s.dds
* pn_glv_lgta_0d.dds
* pn_glv_lgta_0n.dds
* pn_glv_lgta_0s.dds
* pn_glv_lgta_0t.dds
* pn_glv_lgtb_0d.dds
* pn_glv_lgtb_0n.dds
* pn_glv_lgtb_0s.dds
* pn_glv_lgtb_0t.dds
* pn_glv_lgtc_0d.dds
* pn_glv_lgtc_0n.dds
* pn_glv_lgtc_0s.dds
* pn_glv_lgtc_0t.dds
* pn_glv_lgtd_0d.dds
* pn_glv_lgtd_0n.dds
* pn_glv_lgtd_0s.dds
* pn_glv_lgtd_0t.dds
* pn_glv_masa_0d.dds
* pn_glv_masa_0n.dds
* pn_glv_masa_0s.dds
* pn_glv_masa_0t.dds
* pn_glv_masb_0d.dds
* pn_glv_masb_0n.dds
* pn_glv_masb_0s.dds
* pn_glv_masb_0t.dds
* pn_glv_masc_0d.dds
* pn_glv_masc_0n.dds
* pn_glv_masc_0s.dds
* pn_glv_masc_0t.dds
* pn_glv_masd_0d.dds
* pn_glv_masd_0n.dds
* pn_glv_masd_0s.dds
* pn_glv_masd_0t.dds
* pn_glv_mase_0d.dds
* pn_glv_mase_0n.dds
* pn_glv_mase_0s.dds
* pn_glv_mase_0t.dds
* pn_glv_meda_0d.dds
* pn_glv_meda_0n.dds
* pn_glv_meda_0s.dds
* pn_glv_meda_0t.dds
* pn_glv_medb_0d.dds
* pn_glv_medb_0n.dds
* pn_glv_medb_0s.dds
* pn_glv_medb_0t.dds
* pn_glv_medc_0d.dds
* pn_glv_medc_0n.dds
* pn_glv_medc_0s.dds
* pn_glv_medc_0t.dds
* pn_glv_medd_0d.dds
* pn_glv_medd_0n.dds
* pn_glv_medd_0s.dds
* pn_glv_medd_0t.dds
* pn_har_blda_0d.dds
* pn_har_blda_0n.dds
* pn_har_blda_0t.dds
* pn_har_stb_0n.dds
* pn_har_stb_0t.dds
* pn_hlf_d01a_0d.dds
* pn_hlf_d01a_0n.dds
* pn_hlf_d01a_0s.dds
* pn_hlf_d01b_0d.dds
* pn_hlf_d01b_0n.dds
* pn_hlf_d01b_0s.dds
* pn_hlf_m03a_0d.dds
* pn_hlf_m03a_0n.dds
* pn_hlf_m03a_0s.dds
* pn_hlf_m03a_0t.dds
* pn_hlf_s01a_0d.dds
* pn_hlf_s01a_0n.dds
* pn_hlf_s01a_0s.dds
* pn_hlf_s01a_0t.dds
* pn_hlf_s01b_0d.dds
* pn_hlf_s01b_0n.dds
* pn_hlf_s01b_0s.dds
* pn_hlf_s01b_0t.dds
* pn_hlf_s02a_0d.dds
* pn_hlf_s02a_0n.dds
* pn_hlf_s02a_0s.dds
* pn_hlf_s02a_0t.dds
* pn_hlf_s02b_0d.dds
* pn_hlf_s02b_0n.dds
* pn_hlf_s02b_0s.dds
* pn_hlf_s02b_0t.dds
* pn_hlf_t01a_0d.dds
* pn_hlf_t01a_0n.dds
* pn_hlf_t01a_0s.dds
* pn_hlf_t01b_0d.dds
* pn_hlf_t01b_0n.dds
* pn_hlf_t01b_0s.dds
* pn_hlf_t02a_0d.dds
* pn_hlf_t02a_0n.dds
* pn_hlf_t02a_0s.dds
* pn_hlh_crn_0d.dds
* pn_hlh_crn_0n.dds
* pn_hlh_crn_0s.dds
* pn_hlh_e01a_0d.dds
* pn_hlh_e01a_0n.dds
* pn_hlh_e01a_0s.dds
* pn_hlh_e01a_0t.dds
* pn_hlh_g01a_0d.dds
* pn_hlh_g01a_0n.dds
* pn_hlh_g01a_0s.dds
* pn_hlh_g01a_0t.dds
* pn_hlh_g01b_0d.dds
* pn_hlh_g01b_0n.dds
* pn_hlh_g01b_0s.dds
* pn_hlh_g01b_0t.dds
* pn_hlh_g02a_0d.dds
* pn_hlh_g02a_0n.dds
* pn_hlh_g02a_0s.dds
* pn_hlh_g02a_0t.dds
* pn_hlh_g02b_0d.dds
* pn_hlh_g02b_0n.dds
* pn_hlh_g02b_0s.dds
* pn_hlh_g02b_0t.dds
* pn_hlh_h01a_0d.dds
* pn_hlh_h01a_0n.dds
* pn_hlh_h01a_0s.dds
* pn_hlh_h01a_0t.dds
* pn_hlh_h01b_0d.dds
* pn_hlh_h01b_0n.dds
* pn_hlh_h01b_0s.dds
* pn_hlh_h01b_0t.dds
* pn_hlh_h02a_0d.dds
* pn_hlh_h02a_0n.dds
* pn_hlh_h02a_0s.dds
* pn_hlh_h02a_0t.dds
* pn_hlh_h02b_0d.dds
* pn_hlh_h02b_0n.dds
* pn_hlh_h02b_0s.dds
* pn_hlh_h02b_0t.dds
* pn_hlh_l01a_0d.dds
* pn_hlh_l01a_0n.dds
* pn_hlh_l01a_0s.dds
* pn_hlh_l01a_0t.dds
* pn_hlh_l01b_0d.dds
* pn_hlh_l01b_0n.dds
* pn_hlh_l01b_0s.dds
* pn_hlh_l01b_0t.dds
* pn_hlh_l02a_0d.dds
* pn_hlh_l02a_0n.dds
* pn_hlh_l02a_0s.dds
* pn_hlh_l02a_0t.dds
* pn_hlh_l02b_0d.dds
* pn_hlh_l02b_0n.dds
* pn_hlh_l02b_0s.dds
* pn_hlh_l02b_0t.dds
* pn_hlh_m01a_0d.dds
* pn_hlh_m01a_0n.dds
* pn_hlh_m01a_0s.dds
* pn_hlh_m01a_0t.dds
* pn_hlh_m01b_0d.dds
* pn_hlh_m01b_0n.dds
* pn_hlh_m01b_0s.dds
* pn_hlh_m01b_0t.dds
* pn_hlh_m02a_0d.dds
* pn_hlh_m02a_0n.dds
* pn_hlh_m02a_0s.dds
* pn_hlh_m02a_0t.dds
* pn_hlh_m02b_0d.dds
* pn_hlh_m02b_0n.dds
* pn_hlh_m02b_0s.dds
* pn_hlh_m02b_0t.dds
* pn_hlh_m04a_0d.dds
* pn_hlh_m04a_0n.dds
* pn_hlh_m04a_0s.dds
* pn_hlh_m04a_0t.dds
* pn_hlh_m04b_0d.dds
* pn_hlh_m04b_0n.dds
* pn_hlh_m04b_0s.dds
* pn_hlh_m04b_0t.dds
* pn_rob_tmpa_0d.dds
* pn_rob_tmpa_0n.dds
* pn_rob_tmpa_0s.dds
* prp_lightbeam.dds
* r_u_c.dds
* rage_tend_flip6x6.dds
* ring2.dds
* rip_flip.dds
* ripple_sliver2.dds
* rock.dds
* rock_01.dds
* rock_02.dds
* rock_03.dds
* rock_aa.dds
* rock_body.dds
* rock_c_01.dds
* rock_c_02.dds
* rock_c_03.dds
* rock_c_04.dds
* rock_group_02.dds
* rock_h_f.dds
* rock_re_up.dds
* rock_ref.dds
* rock_small.dds
* s_ballista_01.dds
* s_ballista_02.dds
* s_ballista_03.dds
* s_ballista_04.dds
* s_ballista_05.dds
* s_ballista_06.dds
* s_smoke_01.dds
* s_smoke_02.dds
* s_stand_01.dds
* s_stand_02.dds
* s_stand_03.dds
* s_stand_04.dds
* sb_fade_clouda.dds
* sb_fade_cloudb.dds
* sb_noise.dds
* seagull_f.dds
* shatter_01.dds
* shatter_02.dds
* sheild.dds
* shock_projectile_f.dds
* shock_projectile_f_c.dds
* shock_projectile_f_e.dds
* shock_projectile_f_s.dds
* sicesheet.dds
* single_star.dds
* skel_f2.dds
* skel_si.dds
* smoke_ciga_f.dds
* smoke_ciga_f2.dds
* smoke_ciga_f2_a.dds
* smoke_ciga_f4.dds
* smoke_f.dds
* smoke04.dds
* snow_01.dds
* snow_02.dds
* snow_04_f.dds
* space_si.dds
* spark_ring.dds
* spi_02.dds
* spider.dds
* spider2.dds
* star_b.dds
* star_blue.dds
* star_yellow.dds
* starline.dds
* starline2.dds
* start.dds
* stormcloud.dds
* stormcloud_small.dds
* streak_normal.dds
* streak_normal_alpha.dds
* streaks01.dds
* streaks02.dds
* sum_cloud.dds
* t_table_01.dds
* t_table_02.dds
* t_table_04.dds
* t_table_05.dds
* tal_01.dds
* tal_04.dds
* tau_star_g.dds
* tel_06.dds
* tell_03.dds
* testgenlock.dds
* testhurlock.dds
* testspritearmy.dds
* tree_01.dds
* tree_02.dds
* tree_04.dds
* tv_door_01.dds
* tv_door_02.dds
* tv_door_03.dds
* tv_door_04.dds
* twirl_air.dds
* uh_har_0d.dds
* uh_har_0t.dds
* uh_har_h01_0d.dds
* uh_har_h01_0t.dds
* uh_hed_bw1_0t.dds
* uh_hed_bw2_0t.dds
* uh_hed_chka_0d.dds
* uh_hed_chka_0n.dds
* uh_hed_chka_0s.dds
* uh_hed_chka_0t.dds
* uh_hed_dbga_0d.dds
* uh_hed_dbga_0n.dds
* uh_hed_dbga_0s.dds
* uh_hed_dbga_0t.dds
* uh_hed_dcpa_0d.dds
* uh_hed_dcpa_0n.dds
* uh_hed_dcpa_0t.dds
* uh_hed_dwfa_0d.dds
* uh_hed_dwfa_0n.dds
* uh_hed_elfa_0d.dds
* uh_hed_elfa_0n.dds
* uh_hed_emo_0n.dds
* uh_hed_fema_0d.dds
* uh_hed_fema_0n.dds
* uh_hed_infa_0d.dds
* uh_hed_infa_0n.dds
* uh_hed_kida_0d.dds
* uh_hed_kida_0n.dds
* uh_hed_maka_0t.dds
* uh_hed_masa_0d.dds
* uh_hed_masa_0n.dds
* uh_hed_mbd.dds
* uh_hed_mbw.dds
* uh_hed_mlw.dds
* uh_hed_mup.dds
* uh_hed_olda_0d.dds
* uh_hed_olda_0n.dds
* uh_hed_quna_0d.dds
* uh_hed_quna_0n.dds
* uh_hed_scr_0n.dds
* uh_hed_sica_0d.dds
* uh_hed_sica_0n.dds
* uh_hed_stb_0n.dds
* uh_hed_stb_0t.dds
* uh_hed_tata_0t.dds
* uh_hed_tatb_0t.dds
* uh_pct_dc1_0t.dds
* uh_pct_dn1_0t.dds
* uh_pct_h01_0t.dds
* uh_pct_h02_0t.dds
* uh_pmt_001_0t.dds
* uh_tat_av1_0t.dds
* uh_tat_av2_0t.dds
* uh_tat_av3_0t.dds
* uh_tat_dw1_0t.dds
* uh_tat_dw2_0t.dds
* uh_tat_ed1_0t.dds
* uh_tat_ed2_0t.dds
* uh_tat_ed3_0t.dds
* uh_tat_ed4_0t.dds
* uh_ulm_bas_0d.dds
* um_brd_0d.dds
* um_brd_0t.dds
* v_c_blood_05.dds
* v_c_blood_06.dds
* v_cage_01.dds
* v_cage_02.dds
* v_cage_03.dds
* v_cage_04.dds
* vfx_addcloud01.dds
* vfx_addcloud02.dds
* vfx_alphacloudanim01.dds
* vfx_bird_ra_up.dds
* vfx_bird_raven01.dds
* vfx_bird_raven02.dds
* vfx_bird_raven03.dds
* vfx_bird_raven04.dds
* vfx_blood_dot.dds
* vfx_blood_f.dds
* vfx_blood01.dds
* vfx_bugs_flies01.dds
* vfx_cloud_dark2.dds
* vfx_cloud_dark3.dds
* vfx_crack01.dds
* vfx_darkcloud01.dds
* vfx_darkring01.dds
* vfx_dust_01.dds
* vfx_dust_02.dds
* vfx_dust_03.dds
* vfx_fluff01.dds
* vfx_grad01.dds
* vfx_lavacom.dds
* vfx_lavacom02.dds
* vfx_lightnig_dot.dds
* vfx_lightnig_dot_ani.dds
* vfx_lightnig_dot2.dds
* vfx_lightning_f_02.dds
* vfx_lightning_f_05.dds
* vfx_lightning_f_06.dds
* vfx_lightning_f_07.dds
* vfx_lightning_f_08.dds
* vfx_protect01.dds
* vfx_protect02.dds
* vfx_ring01.dds
* vfx_ring02.dds
* vfx_sparkae.dds
* vfx_sparkae_02.dds
* vfx_sparkae_03.dds
* vfx_sparkae_w.dds
* vfx_sparkae2.dds
* vfx_splinters.dds
* vfx_swirlcloud.dds
* vfx_woodbits01.dds
* vfx_woodbits02.dds
* w_arr_la01d.dds
* w_arr_la01n.dds
* w_arr_la01s.dds
* w_axe_ax01a_0d.dds
* w_axe_ax01a_0n.dds
* w_axe_ax01a_0s.dds
* w_axe_ax01a_0t.dds
* w_axe_ax02a_0d.dds
* w_axe_ax02a_0n.dds
* w_axe_ax02a_0s.dds
* w_axe_ax02a_0t.dds
* w_axe_ax03a_0d.dds
* w_axe_ax03a_0n.dds
* w_axe_ax03a_0s.dds
* w_axe_ax03a_0t.dds
* w_axe_ax04a_0d.dds
* w_axe_ax04a_0n.dds
* w_axe_ax04a_0s.dds
* w_axe_ax04a_0t.dds
* w_axe_ax05a_0d.dds
* w_axe_ax05a_0n.dds
* w_axe_ax05a_0s.dds
* w_axe_ax05a_0t.dds
* w_axe_ax06a_0d.dds
* w_axe_ax06a_0n.dds
* w_axe_ax06a_0s.dds
* w_axe_ax06a_0t.dds
* w_axe_dsaxa_0d.dds
* w_axe_dsaxa_0n.dds
* w_axe_dsaxa_0s.dds
* w_axe_dsaxa_0t.dds
* w_bld_og01a_0d.dds
* w_bld_og01a_0n.dds
* w_bld_og01a_0s.dds
* w_cbw_cb01a_0d.dds
* w_cbw_cb01a_0n.dds
* w_cbw_cb01a_0s.dds
* w_cbw_cb01a_0t.dds
* w_cbw_cb02a_0d.dds
* w_cbw_cb02a_0n.dds
* w_cbw_cb02a_0s.dds
* w_cbw_cb02a_0t.dds
* w_cbw_cb03a_0d.dds
* w_cbw_cb03a_0n.dds
* w_cbw_cb03a_0s.dds
* w_cbw_cb03a_0t.dds
* w_cbw_cb04a_0d.dds
* w_cbw_cb04a_0n.dds
* w_cbw_cb04a_0s.dds
* w_cbw_cb04a_0t.dds
* w_cbw_cb05a_0d.dds
* w_cbw_cb05a_0n.dds
* w_cbw_cb05a_0s.dds
* w_cbw_cb05a_0t.dds
* w_cbw_cb06a_0d.dds
* w_cbw_cb06a_0n.dds
* w_cbw_cb06a_0s.dds
* w_cbw_cb06a_0t.dds
* w_cbw_dscba_0d.dds
* w_cbw_dscba_0n.dds
* w_cbw_dscba_0s.dds
* w_cbw_dscba_0t.dds
* w_censer_01d.dds
* w_censer_01n.dds
* w_censer_01s.dds
* w_censer_01t.dds
* w_dgr_dg01a_0d.dds
* w_dgr_dg01a_0n.dds
* w_dgr_dg01a_0s.dds
* w_dgr_dg01a_0t.dds
* w_dgr_dg02a_0d.dds
* w_dgr_dg02a_0n.dds
* w_dgr_dg02a_0s.dds
* w_dgr_dg02a_0t.dds
* w_dgr_dg03a_0d.dds
* w_dgr_dg03a_0n.dds
* w_dgr_dg03a_0s.dds
* w_dgr_dg03a_0t.dds
* w_dgr_dg04a_0d.dds
* w_dgr_dg04a_0n.dds
* w_dgr_dg04a_0s.dds
* w_dgr_dg04a_0t.dds
* w_dgr_dg05a_0d.dds
* w_dgr_dg05a_0n.dds
* w_dgr_dg05a_0s.dds
* w_dgr_dg05a_0t.dds
* w_dgr_dg06a_0d.dds
* w_dgr_dg06a_0n.dds
* w_dgr_dg06a_0s.dds
* w_dgr_dg06a_0t.dds
* w_dgr_dsdga_0d.dds
* w_dgr_dsdga_0n.dds
* w_dgr_dsdga_0s.dds
* w_flower_01.dds
* w_flower_02.dds
* w_flower_03.dds
* w_flower_04.dds
* w_gax_dsgaa_0d.dds
* w_gax_dsgaa_0n.dds
* w_gax_dsgaa_0s.dds
* w_gax_dsgaa_0t.dds
* w_gax_ga01a_0d.dds
* w_gax_ga01a_0n.dds
* w_gax_ga01a_0s.dds
* w_gax_ga01a_0t.dds
* w_gax_ga02a_0d.dds
* w_gax_ga02a_0n.dds
* w_gax_ga02a_0s.dds
* w_gax_ga02a_0t.dds
* w_gax_ga03a_0d.dds
* w_gax_ga03a_0n.dds
* w_gax_ga03a_0s.dds
* w_gax_ga03a_0t.dds
* w_gax_ga04a_0d.dds
* w_gax_ga04a_0n.dds
* w_gax_ga04a_0s.dds
* w_gax_ga04a_0t.dds
* w_gax_ga05a_0d.dds
* w_gax_ga05a_0n.dds
* w_gax_ga05a_0s.dds
* w_gax_ga05a_0t.dds
* w_gax_ga06a_0d.dds
* w_gax_ga06a_0n.dds
* w_gax_ga06a_0s.dds
* w_gax_ga06a_0t.dds
* w_gsw_dsgsa_0d.dds
* w_gsw_dsgsa_0n.dds
* w_gsw_dsgsa_0s.dds
* w_gsw_dsgsa_0t.dds
* w_gsw_gs01a_0d.dds
* w_gsw_gs01a_0n.dds
* w_gsw_gs01a_0s.dds
* w_gsw_gs01a_0t.dds
* w_gsw_gs02a_0d.dds
* w_gsw_gs02a_0n.dds
* w_gsw_gs02a_0s.dds
* w_gsw_gs02a_0t.dds
* w_gsw_gs03a_0d.dds
* w_gsw_gs03a_0n.dds
* w_gsw_gs03a_0s.dds
* w_gsw_gs03a_0t.dds
* w_gsw_gs04a_0d.dds
* w_gsw_gs04a_0n.dds
* w_gsw_gs04a_0s.dds
* w_gsw_gs04a_0t.dds
* w_gsw_gs05a_0d.dds
* w_gsw_gs05a_0n.dds
* w_gsw_gs05a_0s.dds
* w_gsw_gs05a_0t.dds
* w_gsw_gs06a_0d.dds
* w_gsw_gs06a_0n.dds
* w_gsw_gs06a_0s.dds
* w_gsw_gs06a_0t.dds
* w_lbw_dslba_0d.dds
* w_lbw_dslba_0n.dds
* w_lbw_dslba_0s.dds
* w_lbw_lb01a_0d.dds
* w_lbw_lb01a_0n.dds
* w_lbw_lb01a_0s.dds
* w_lbw_lb01a_0t.dds
* w_lbw_lb02a_0d.dds
* w_lbw_lb02a_0n.dds
* w_lbw_lb02a_0s.dds
* w_lbw_lb02a_0t.dds
* w_lbw_lb03a_0d.dds
* w_lbw_lb03a_0n.dds
* w_lbw_lb03a_0s.dds
* w_lbw_lb03a_0t.dds
* w_lbw_lb04a_0d.dds
* w_lbw_lb04a_0n.dds
* w_lbw_lb04a_0s.dds
* w_lbw_lb04a_0t.dds
* w_lbw_lb05a_0d.dds
* w_lbw_lb05a_0n.dds
* w_lbw_lb05a_0s.dds
* w_lbw_lb05a_0t.dds
* w_lbw_lb06a_0d.dds
* w_lbw_lb06a_0n.dds
* w_lbw_lb06a_0s.dds
* w_lbw_lb06a_0t.dds
* w_lsw_dslsa_0d.dds
* w_lsw_dslsa_0n.dds
* w_lsw_dslsa_0s.dds
* w_lsw_ls01a_0d.dds
* w_lsw_ls01a_0n.dds
* w_lsw_ls01a_0s.dds
* w_lsw_ls01a_0t.dds
* w_lsw_ls02a_0d.dds
* w_lsw_ls02a_0f.dds
* w_lsw_ls02a_0n.dds
* w_lsw_ls02a_0s.dds
* w_lsw_ls02a_0t.dds
* w_lsw_ls03a_0d.dds
* w_lsw_ls03a_0n.dds
* w_lsw_ls03a_0s.dds
* w_lsw_ls03a_0t.dds
* w_lsw_ls04a_0d.dds
* w_lsw_ls04a_0n.dds
* w_lsw_ls04a_0s.dds
* w_lsw_ls04a_0t.dds
* w_lsw_ls05a_0d.dds
* w_lsw_ls05a_0n.dds
* w_lsw_ls05a_0s.dds
* w_lsw_ls05a_0t.dds
* w_lsw_ls06a_0d.dds
* w_lsw_ls06a_0n.dds
* w_lsw_ls06a_0s.dds
* w_lsw_ls06a_0t.dds
* w_mal_dsmla_0d.dds
* w_mal_dsmla_0n.dds
* w_mal_dsmla_0s.dds
* w_mal_dsmla_0t.dds
* w_mal_ml01a_0d.dds
* w_mal_ml01a_0n.dds
* w_mal_ml01a_0s.dds
* w_mal_ml01a_0t.dds
* w_mal_ml02a_0d.dds
* w_mal_ml02a_0n.dds
* w_mal_ml02a_0s.dds
* w_mal_ml02a_0t.dds
* w_mal_ml03a_0d.dds
* w_mal_ml03a_0n.dds
* w_mal_ml03a_0s.dds
* w_mal_ml03a_0t.dds
* w_mal_ml04a_0d.dds
* w_mal_ml04a_0n.dds
* w_mal_ml04a_0s.dds
* w_mal_ml04a_0t.dds
* w_mal_ml05a_0d.dds
* w_mal_ml05a_0n.dds
* w_mal_ml05a_0s.dds
* w_mal_ml05a_0t.dds
* w_mal_ml06a_0d.dds
* w_mal_ml06a_0n.dds
* w_mal_ml06a_0s.dds
* w_mal_ml06a_0t.dds
* w_mce_dsmca_0d.dds
* w_mce_dsmca_0n.dds
* w_mce_dsmca_0s.dds
* w_mce_dsmca_0t.dds
* w_mce_mc01a_0d.dds
* w_mce_mc01a_0n.dds
* w_mce_mc01a_0s.dds
* w_mce_mc01a_0t.dds
* w_mce_mc02a_0d.dds
* w_mce_mc02a_0n.dds
* w_mce_mc02a_0s.dds
* w_mce_mc02a_0t.dds
* w_mce_mc03a_0d.dds
* w_mce_mc03a_0n.dds
* w_mce_mc03a_0s.dds
* w_mce_mc03a_0t.dds
* w_mce_mc04a_0d.dds
* w_mce_mc04a_0n.dds
* w_mce_mc04a_0s.dds
* w_mce_mc04a_0t.dds
* w_mce_mc05a_0d.dds
* w_mce_mc05a_0n.dds
* w_mce_mc05a_0s.dds
* w_mce_mc05a_0t.dds
* w_mce_mc06a_0d.dds
* w_mce_mc06a_0n.dds
* w_mce_mc06a_0s.dds
* w_mce_mc06a_0t.dds
* w_qui_bt1a_0d.dds
* w_qui_bt1a_0n.dds
* w_qui_bt1a_0s.dds
* w_qui_bt1a_0t.dds
* w_qui_db01a_0d.dds
* w_qui_db01a_0n.dds
* w_qui_db01a_0s.dds
* w_qui_db01a_0t.dds
* w_qui_dq01a_0d.dds
* w_qui_dq01a_0n.dds
* w_qui_dq01a_0s.dds
* w_qui_qu01a_0d.dds
* w_qui_qu01a_0n.dds
* w_qui_qu01a_0s.dds
* w_sbw_dssba_0d.dds
* w_sbw_dssba_0n.dds
* w_sbw_dssba_0s.dds
* w_sbw_dssba_0t.dds
* w_sbw_sb01a_0d.dds
* w_sbw_sb01a_0n.dds
* w_sbw_sb01a_0s.dds
* w_sbw_sb01a_0t.dds
* w_sbw_sb02a_0d.dds
* w_sbw_sb02a_0n.dds
* w_sbw_sb02a_0s.dds
* w_sbw_sb02a_0t.dds
* w_sbw_sb03a_0d.dds
* w_sbw_sb03a_0n.dds
* w_sbw_sb03a_0s.dds
* w_sbw_sb03a_0t.dds
* w_sbw_sb04a_0d.dds
* w_sbw_sb04a_0n.dds
* w_sbw_sb04a_0s.dds
* w_sbw_sb04a_0t.dds
* w_sbw_sb05a_0d.dds
* w_sbw_sb05a_0n.dds
* w_sbw_sb05a_0s.dds
* w_sbw_sb05a_0t.dds
* w_sbw_sb06a_0d.dds
* w_sbw_sb06a_0n.dds
* w_sbw_sb06a_0s.dds
* w_sbw_sb06a_0t.dds
* w_shd_dsla_0d.dds
* w_shd_dsla_0n.dds
* w_shd_dsla_0s.dds
* w_shd_dssa_0d.dds
* w_shd_dssa_0n.dds
* w_shd_dssa_0s.dds
* w_shd_kita_0d.dds
* w_shd_kita_0n.dds
* w_shd_kita_0s.dds
* w_shd_kita_0t.dds
* w_shd_kitb_0d.dds
* w_shd_kitb_0n.dds
* w_shd_kitb_0s.dds
* w_shd_kitb_0t.dds
* w_shd_lrda_0d.dds
* w_shd_lrda_0n.dds
* w_shd_lrda_0s.dds
* w_shd_lrda_0t.dds
* w_shd_lrdb_0d.dds
* w_shd_lrdb_0n.dds
* w_shd_lrdb_0s.dds
* w_shd_lrdb_0t.dds
* w_shd_srda_0d.dds
* w_shd_srda_0n.dds
* w_shd_srda_0s.dds
* w_shd_srda_0t.dds
* w_shd_srdb_0d.dds
* w_shd_srdb_0n.dds
* w_shd_srdb_0s.dds
* w_shd_srdb_0t.dds
* w_shd_twra_0d.dds
* w_shd_twra_0n.dds
* w_shd_twra_0s.dds
* w_shd_twra_0t.dds
* w_shd_twrb_0d.dds
* w_shd_twrb_0n.dds
* w_shd_twrb_0s.dds
* w_shd_twrb_0t.dds
* w_shd_twrc_0d.dds
* w_shd_twrc_0n.dds
* w_shd_twrc_0s.dds
* w_shd_twrc_0t.dds
* w_small_dagger_01d.dds
* w_small_dagger_01n.dds
* w_small_dagger_01s.dds
* w_small_dagger_01t.dds
* w_stf_dssta_0d.dds
* w_stf_dssta_0n.dds
* w_stf_dssta_0s.dds
* w_stf_dssta_0t.dds
* w_stf_st01a_0d.dds
* w_stf_st01a_0n.dds
* w_stf_st01a_0s.dds
* w_stf_st01a_0t.dds
* w_stf_st02a_0d.dds
* w_stf_st02a_0n.dds
* w_stf_st02a_0s.dds
* w_stf_st02a_0t.dds
* w_stf_st03a_0d.dds
* w_stf_st03a_0n.dds
* w_stf_st03a_0s.dds
* w_stf_st03a_0t.dds
* w_wnd_dswda_0d.dds
* w_wnd_dswda_0n.dds
* w_wnd_dswda_0s.dds
* w_wnd_dswda_0t.dds
* w_wnd_wd01a_0d.dds
* w_wnd_wd01a_0n.dds
* w_wnd_wd01a_0s.dds
* w_wnd_wd01a_0t.dds
* w_wnd_wd02a_0d.dds
* w_wnd_wd02a_0n.dds
* w_wnd_wd02a_0s.dds
* w_wnd_wd02a_0t.dds
* w_wnd_wd03a_0d.dds
* w_wnd_wd03a_0n.dds
* w_wnd_wd03a_0s.dds
* w_wnd_wd03a_0t.dds
* water_cycle3.dds
* water_drop.dds
* water_pan.dds
* water_pan_add.dds
* water_pan_add_blur.dds
* water_pan_add_blur2.dds
* wave_alp.dds
* wave_nor.dds
* weapon_stand_01.dds
* weapontrail_normal.dds
* weapontrail_streaks.dds
* y_crate_01.dds
* y_crate_02.dds
* y_crate_03.dds
* y_crate_04.dds
* y_crate_05.dds
* z_cl_offset.dds
* z_cloud.dds
* z_cloud_2.dds
* z_cloud_v.dds
* z_cloud_w_smok.dds
* z_cloud02.dds
* z_cloud02_offsetup.dds
* z_cloud03.1.dds
* z_cloud03.2.dds
* z_cloud03.dds
* z_cloud031.dds
* z_dust_little.dds
* z_dust2.dds
* z_dust2_b.dds
* z_dust3.dds
* z_dust4.dds
* z_dust5.dds
* z_dust8.dds
* z_dust8_si.dds
* z_dust8_si3.dds
* z_dust8_white.dds

== User interface ==

* atl_chanters_dxt5_00.dds
* atl_chargen_dxt1_00.dds
* atl_chargen_dxt5_00.dds
* atl_credits_dxt5_00.dds
* atl_credits_dxt5_01.dds
* atl_credits_dxt5_02.dds
* atl_credits_dxt5_03.dds
* atl_deathscree_dxt1_00.dds
* atl_deathscree_dxt5_00.dds
* atl_debug_dxt5_00.dds
* atl_fademap_dxt1_00.dds
* atl_fademap_dxt1_01.dds
* atl_fademap_dxt5_00.dds
* atl_fademap_dxt5_01.dds
* atl_guicommuni_dxt5_00.dds
* atl_guiscreens_dxt5_00.dds
* atl_itemupgrad_dxt5_00.dds
* atl_load_town_dxt5_00.dds
* atl_prccontent_dxt5_00.dds
* atl_prccontent_dxt5_01.dds
* atl_purchaseco_dxt5_00.dds
* atl_shared_dxt1_00.dds
* atl_shared_dxt1_01.dds
* atl_shared_dxt5_00.dds
* atl_shared_dxt5_01.dds
* atl_shared_dxt5_02.dds
* atl_startmenu2_dxt1_00.dds
* atl_startmenu2_dxt1_01.dds
* atl_startmenu2_dxt1_02.dds
* atl_startmenu2_dxt5_00.dds
* atl_startmenu2_dxt5_01.dds
* atl_startmenu2_dxt5_02.dds

== DLC (standard quality) ==

* craterr_halff.dds
* nrx3_bigcliff01_d.dds
* nrx3_bigcliff01_n.dds
* nrx3_bigrock01_d.dds
* nrx3_bigrock01_n.dds
* nrx3_bigrock02_d.dds
* nrx3_bigrock02_n.dds
* nrx3_brickround02_d.dds
* nrx3_brickround02_n.dds
* nrx3_cracked01_d.dds
* nrx3_jaggedrock01_d.dds
* nrx3_jaggedrock01_n.dds
* nrx3_sand01_d.dds
* nrx3_sand01_n.dds
* nrx3_sand01_s.dds
* nrx3rock_d.dds
* p_nrx3_boat01d.dds
* p_nrx3_boat01n.dds
* p_nrx3_boat01s.dds
* plc_cp3_doll1_d.dds
* plc_cp3_doll1_n.dds
* plc_cp3_doll1_s.dds
* plc_cp3_pet1_d.dds
* plc_cp3_pet1_n.dds
* plc_cp3_pet1_s.dds
* plc_cp3_stick1_d.dds
* plc_cp3_stick1_n.dds
* plc_cp3_stick1_s.dds
* prp_nrx3_bark_d.dds
* prp_nrx3_bark_n.dds
* prp_nrx3_branch_d.dds
* prp_nrx3_twall_d.dds
* prp_nrx3_win01d.dds
* prp_nrx3_win01e.dds
* prp_nrx3_win01n.dds
* prp_nrx3_win01s.dds
* prp_str_bark_d.dds
* prp_str_bark_n.dds
* prp_str_branch_d.dds
* prp_str_dbone_d.dds
* prp_str_dbone_n.dds
* prp_str_dbone_s.dds
* prp_str_mirrorstatue_01d.dds
* prp_str_mirrorstatue_01n.dds
* prp_str_mirrorstatue_01s.dds
* prp_str_rock_d.dds
* prp_str_rock_n.dds
* prp_str_slime_d.dds
* prp_str_slime_n.dds
* prp_str_slime_s.dds
* prp_str_tentical_d.dds
* prp_str_tentical_n.dds
* prp_str_twall_d.dds
* str_bigrock02_d.dds
* str_bigrock02_n.dds
* str_cracked01_d.dds
* str_cracked01_n.dds
* str_jaggedrock01_d.dds
* str_jaggedrock01_n.dds
* str_slime_d.dds
* str_slime_n.dds
* str_slime_s.dds
* str_slimebone_d.dds
* str_slimebone_n.dds
* str_slimebone_s.dds
* strcave01_d.dds
* strcave01_n.dds
* strmt01_d.dds
* strmt01_n.dds
* strmt02_d.dds
* strmt02_n.dds
* ter_cracked01_d.dds
* vistanrx3_01_d.dds
* vistanrx3_01_n.dds
* vistanrx3_02_d.dds
* vistanrx3_02_n.dds

== DLC (high quality) ==

* armor.dds
* arrow_f.dds
* bld_drian_tu5.dds
* bld_fin_f.dds
* bld_fin_f12.dds
* bld_fin_f7.dds
* blood_conj_03.dds
* blood_splatter_f.dds
* blood3.dds
* blur_b_a.dds
* butterfly.dds
* c_meye.dds
* c_mhead_0d.dds
* c_mhead_0n.dds
* c_mhead_0s.dds
* c_mhead2_0d.dds
* c_mhead2_0n.dds
* c_mhead2_0s.dds
* c_mother_0d.dds
* c_mother_0n.dds
* c_mother_0s.dds
* c_pridedemb_bdy_0d.dds
* c_pridedemb_bdy_0n.dds
* c_pridedemb_bdy_0s.dds
* c_pridedemb_hed_0d.dds
* c_pridedemb_hed_0i.dds
* c_pridedemb_hed_0n.dds
* c_pridedemb_hed_0s.dds
* c_shadeb_0d.dds
* c_shadeb_0i.dds
* c_shadeb_0n.dds
* c_shadeb_0s.dds
* c_stpigeon_0d.dds
* c_stpigeon_0n.dds
* c_stpigeon_0s.dds
* c_stridera_0d.dds
* c_stridera_0n.dds
* c_stridera_0s.dds
* cloud_f_bl.dds
* cn_bdy_aoga_0d.dds
* cn_bdy_aoga_0n.dds
* cn_bdy_aoga_0s.dds
* cn_bdy_arc_0d.dds
* cn_bdy_arc_0n.dds
* cn_bdy_arc_0s.dds
* cn_bdy_bwwa_0d.dds
* cn_bdy_bwwa_0n.dds
* cn_bdy_bwwa_0s.dds
* cn_bdy_chda_0d.dds
* cn_bdy_chda_0n.dds
* cn_bdy_chda_0s.dds
* cn_bdy_disa_0d.dds
* cn_bdy_disa_0n.dds
* cn_bdy_disa_0s.dds
* cn_bdy_disb_0d.dds
* cn_bdy_disb_0n.dds
* cn_bdy_disb_0s.dds
* cn_bdy_drga_0n.dds
* cn_bdy_drgb_0d.dds
* cn_bdy_drgb_0i.dds
* cn_bdy_drgb_0s.dds
* cn_bdy_gib_0d.dds
* cn_bdy_gib_0n.dds
* cn_bdy_gib_0s.dds
* cn_bdy_hdrb_0d.dds
* cn_bdy_hdrb_0i.dds
* cn_bdy_hdrb_0s.dds
* cn_bdy_sklg_0d.dds
* cn_bdy_sklg_0n.dds
* cn_bdy_sklg_0s.dds
* cn_bdy_stgb_0d.dds
* cn_bdy_stgb_0i.dds
* cn_bdy_stgb_0n.dds
* cn_bdy_stgb_0s.dds
* cn_bdy_wsvb_0d.dds
* cn_bdy_wsvb_0i.dds
* cn_bdy_wsvc_0d.dds
* cn_bdy_wsvc_0i.dds
* cn_bra_wsvb_0d.dds
* cn_bra_wsvc_0d.dds
* cn_eye_arc_0d.dds
* cn_eye_drgb_0d.dds
* cn_eye_hdrb_0d.dds
* cn_hed_aoga_0d.dds
* cn_hed_aoga_0n.dds
* cn_hed_aoga_0s.dds
* cn_hed_arc_0d.dds
* cn_hed_arc_0n.dds
* cn_hed_arc_0s.dds
* cn_hed_bwwa_0d.dds
* cn_hed_bwwa_0i.dds
* cn_hed_bwwa_0n.dds
* cn_hed_bwwa_0s.dds
* cn_hed_disa_0d.dds
* cn_hed_disa_0n.dds
* cn_hed_disa_0s.dds
* cn_hed_disb_0d.dds
* cn_hed_disb_0n.dds
* cn_hed_disb_0s.dds
* cn_hed_gib_0d.dds
* cn_hed_gib_0n.dds
* cn_hed_gib_0s.dds
* cn_hed_hdrb_0d.dds
* cn_hed_hdrb_0n.dds
* cn_wng_hdrb_0d.dds
* cn_wng_hdrb_0i.dds
* cn_wng_hdrb_0n.dds
* cn_wng_hdrb_0s.dds
* cr_spe_crack.dds
* cr_spe_glow.dds
* crate_03_a.dds
* crater_half.dds
* d15_b_shot.dds
* d15_b_shot_a.dds
* d15_b_shot2.dds
* d15_b_sp.dds
* d15_b_sp_color.dds
* d15_b_sp_d.dds
* d15_blood_link.dds
* d15_link_smo2.dds
* door_wood.dds
* flare3.dds
* fx_child_spit.dds
* fx_fire_b.dds
* fx_fireline01.dds
* fx_fireringfb_a.dds
* fx_fireringfb_b.dds
* fx_glyph_blurl.dds
* fx_larc_fb.dds
* fx_lb_fb.dds
* fx_lb00.dds
* fx_noise01_a.dds
* fx_ripple01.dds
* fx_twirl01_s.dds
* fxe_fire_out.dds
* h_cailanprca_0.dds
* h_grywrprca_0.dds
* half_dot.dds
* hole_s.dds
* lining_ciga_f.dds
* medicine_cone.dds
* normal_out_dot.dds
* oil_loop_a.dds
* pf_arm_lgte_0d.dds
* pf_arm_lgte_0s.dds
* pf_arm_lgte_0t.dds
* pf_cth_nblf_0d.dds
* pf_cth_nblf_0n.dds
* pf_cth_nblf_0s.dds
* pf_cth_nblf_0t.dds
* pf_cth_nblg_0d.dds
* pf_cth_nblg_0e.dds
* pf_cth_nblg_0s.dds
* pf_cth_nblg_0t.dds
* pf_rob_chac_0d.dds
* pf_rob_chac_0n.dds
* pf_rob_chac_0s.dds
* pf_rob_chac_0t.dds
* pla_another.dds
* pm_arm_lgte_0d.dds
* pm_arm_lgte_0s.dds
* pm_cth_nblf_0d.dds
* pm_cth_nblf_0n.dds
* pm_cth_nblf_0s.dds
* pm_cth_nblf_0t.dds
* pm_rob_chac_0d.dds
* pm_rob_chac_0n.dds
* pm_rob_chac_0s.dds
* pm_rob_chac_0t.dds
* pn_arm_bdaa_0d.dds
* pn_arm_bdaa_0i.dds
* pn_arm_bdaa_0n.dds
* pn_arm_bdaa_0s.dds
* pn_arm_dwpc_0d.dds
* pn_arm_dwpc_0n.dds
* pn_arm_dwpc_0s.dds
* pn_arm_dwpd_0d.dds
* pn_arm_dwpd_0i.dds
* pn_arm_dwpd_0s.dds
* pn_arm_masg_0d.dds
* pn_arm_masg_0n.dds
* pn_arm_masg_0s.dds
* pn_arm_masg_0t.dds
* pn_arm_mash_0d.dds
* pn_arm_mash_0i.dds
* pn_arm_mash_0s.dds
* pn_arm_masi_0d.dds
* pn_arm_masi_0s.dds
* pn_boo_dwpc_0d.dds
* pn_boo_dwpc_0n.dds
* pn_boo_dwpc_0s.dds
* pn_boo_dwpd_0d.dds
* pn_boo_dwpd_0i.dds
* pn_boo_dwpd_0s.dds
* pn_boo_masg_0d.dds
* pn_boo_masg_0n.dds
* pn_boo_masg_0s.dds
* pn_boo_masg_0t.dds
* pn_boo_mash_0d.dds
* pn_boo_mash_0s.dds
* pn_boo_masi_0d.dds
* pn_boo_masi_0s.dds
* pn_eye_disa_0d.dds
* pn_eye_disa_0n.dds
* pn_eye_disb_0d.dds
* pn_glv_dwpc_0d.dds
* pn_glv_dwpc_0n.dds
* pn_glv_dwpc_0s.dds
* pn_glv_dwpd_0d.dds
* pn_glv_dwpd_0i.dds
* pn_glv_lgte_0d.dds
* pn_glv_lgte_0s.dds
* pn_glv_lgte_0t.dds
* pn_glv_masg_0d.dds
* pn_glv_masg_0n.dds
* pn_glv_masg_0s.dds
* pn_glv_masg_0t.dds
* pn_glv_mash_0d.dds
* pn_glv_mash_0s.dds
* pn_glv_masi_0d.dds
* pn_glv_masi_0s.dds
* pn_hlf_bdaa_0d.dds
* pn_hlf_bdaa_0i.dds
* pn_hlf_bdaa_0n.dds
* pn_hlf_bdaa_0s.dds
* pn_hlf_d01c_0d.dds
* pn_hlf_d01c_0n.dds
* pn_hlf_d01c_0s.dds
* pn_hlf_d01d_0d.dds
* pn_hlf_d01d_0i.dds
* pn_hlf_d01d_0s.dds
* pn_hlf_s01c_0d.dds
* pn_hlf_s01c_0s.dds
* pn_hlf_t02b_0d.dds
* pn_hlf_t02b_0i.dds
* pn_hlf_t02b_0n.dds
* pn_hlf_t02b_0s.dds
* pn_hlh_m02c_0d.dds
* pn_hlh_m02c_0s.dds
* ring.dds
* ring_dot.dds
* ring_twis_sin.dds
* rock_w.dds
* rune1.dds
* rune2.dds
* rune3.dds
* rune4.dds
* rune5.dds
* shadow.dds
* skel_f.dds
* skel_h2_f.dds
* skel_hand_f.dds
* smoke_sigle.dds
* spi_f2.dds
* tau_star.dds
* tel_02.dds
* thorns.dds
* uh_hed_deda_0d.dds
* uh_hed_deda_0n.dds
* uh_pct_exp_0t.dds
* uh_tat_p01_0t.dds
* w_axe_ax07a_0d.dds
* w_axe_ax07a_0n.dds
* w_axe_ax07a_0s.dds
* w_axe_ax07a_0t.dds
* w_dgr_dsdgc_0d.dds
* w_dgr_dsdgc_0n.dds
* w_dgr_dsdgc_0s.dds
* w_gsw_dsgsb_0d.dds
* w_gsw_dsgsb_0n.dds
* w_gsw_dsgsb_0s.dds
* w_gsw_gs07a_0d.dds
* w_gsw_gs07a_0e.dds
* w_gsw_gs07a_0n.dds
* w_gsw_gs07a_0s.dds
* w_gsw_gs08a_0d.dds
* w_gsw_gs08a_0e.dds
* w_gsw_gs08a_0n.dds
* w_gsw_gs08a_0s.dds
* w_gsw_gs08a_0t.dds
* w_lbw_lb07a_0d.dds
* w_lbw_lb07a_0e.dds
* w_lbw_lb07a_0n.dds
* w_lbw_lb07a_0s.dds
* w_lbw_lb07a_0t.dds
* w_lsw_ls07a_0d.dds
* w_lsw_ls07a_0e.dds
* w_lsw_ls07a_0n.dds
* w_lsw_ls07a_0s.dds
* w_lsw_ls08a_0d.dds
* w_lsw_ls08a_0e.dds
* w_lsw_ls08a_0n.dds
* w_lsw_ls08a_0s.dds
* w_lsw_ls09a_0d.dds
* w_lsw_ls09a_0n.dds
* w_lsw_ls09a_0s.dds
* w_lsw_ls09a_0t.dds
* w_mal_ml07a_0d.dds
* w_mal_ml07a_0n.dds
* w_mal_ml07a_0s.dds
* w_mal_ml07a_0t.dds
* w_mce_mc07a_0d.dds
* w_mce_mc07a_0n.dds
* w_mce_mc07a_0s.dds
* w_mce_mc07a_0t.dds
* w_sbw_sb07a_0d.dds
* w_sbw_sb07a_0n.dds
* w_sbw_sb07a_0s.dds
* w_sbw_sb07a_0t.dds
* w_shd_dslb_0d.dds
* w_shd_dslb_0n.dds
* w_shd_dslb_0s.dds
* w_shd_elna_0d.dds
* w_shd_elna_0n.dds
* w_shd_elna_0s.dds
* w_shd_elna_0t.dds
* w_shd_seaa_0d.dds
* w_shd_seaa_0n.dds
* w_shd_seaa_0s.dds
* w_shd_seaa_0t.dds
* w_shd_seaa_d.dds
* w_shd_seaa_n.dds
* w_shd_seaa_s.dds
* w_shd_seaa_t.dds
* w_stf_st04a_0d.dds
* w_stf_st04a_0n.dds
* w_stf_st04a_0s.dds
* w_stf_st05a_0d.dds
* w_stf_st05a_0e.dds
* w_stf_st05a_0n.dds
* w_stf_st05a_0s.dds
* w_stf_st05a_0t.dds
* white.dds
* wispy_line2.dds
* wispy_smo_bright.dds
* wispy_smoke_darker.dds
* wispy_smoke_sin.dds
* wispy_smoke2.dds
* wood_chip.dds
* z_dust_blood.dds
* z_dust7.dds

Naming conventions

2022-07-25T20:28:47Z

Ashhawk: uem = eyes, uhm = heads

BioWare's resources follow a naming convention which allows for easy management and easy location of resources needed. When creating new resources it is a good idea to follow the existing naming convention (or your own scheme if you have a preferred one), to differentiate your work from that of others and to help you keep your resources organized.

For the most part the names you give your resources will matter only to you, there are very few situations where the toolset pays attention to the specific form that a resource name takes. So provided you're working on your own any naming convention that suits your particular style will suffice.

Although only one campaign is loaded at a time in game, unintended conflict can arise between the campaign and any core resource mods the player may have installed. If two design resources have the same name, only one will load. This is determined by the [[Source directory priorities]]. So, it's good to choose names that are likely to be unique.

Usually resources are separated by underscores into categories and have prefixes sorting them based on a certain main class, or suffixes giving them certain variations.

__TOC__

== Resource Naming Convention ==

Design resource names are free-form. As a matter of convenience and courtesy to players, you might prefer to follow a convention that reduces the risk of conflict between add-ins and improves compatibility with future Bioware releases. Bear in mind that only one resource with a given name will load in game.

For simple mods, it might be sufficient to use a unique resource name prefix which is unlikely to be used by anyone else. See [[Prefixes in use]].

Larger mods and campaigns may prefer a more professional approach which makes scripting more legible by identifying the resource type etc.

In either case, it would be wise to avoid a prefix that Bioware has already used, such as "gen".

The convention used in the main Single Player campaign of Dragon Age is as follows:

<pre>cir200cr_bloodmage</pre>

*Three-letter prefix indicating which large-scale area of the game the resource begins to (particular origin story, prelude, etc) or "gen" for global resources.
*three-digit number unique to a particular area, generally starting with 100 and incrementing in hundreds for major areas. Accessory areas are given numbers within the block of one hundred that their 'parent' area belongs to. "global" resources are often given the number 000.
*two-letter code indicating what general type of resource it is ("ar" for area, "al" for area list, "ip" for placeable, "cr" for creature, "im" for item, "tr" for trigger, "pt" for plot, "st" for stage, "cs" for cutscene, "wp" for waypoint). A major exception here is event scripts, which have exactly the same name as the resource they're the script for. Dialogue files are also generally named exactly the same as their owner resource. Merchants usually have the owner name, with the prefix "store_".
*An underscore.
*The remainder of the name is free-form and human-readable, a descriptive term to remind you at a glance what the resource is.

== Model File Naming Convention ==

=== Items ===

<pre>[MainClass]_[MODELTYPE]_[MODELSUBTYPE][MODELVARIATION]_[LOD].MMH / PHY

[ef]_[rob]_[enc][a]_[0].mmh (ef_rob_enca_0.mmh)</pre>

*Where [MainClass] is of General type of a Model. The Toolset will build the MainClass based on Race/Gender/Itemtype etc, so this must be correct. (see below)
*[MODELTYPE] as defined with [[2DA|2DAs]]. Typically a short name describing the Model ie. Wolf. See: [[ItemVariations.xls]]
*[MODELSUBTYPE] is optional as defined with [[2DA|2DAs]]. Typically a short name describing different Variations of a Model. See: [[ItemVariations.xls]]
*[MODELVARIATION] is optional as defined with [[2DA|2DAs]]. Typically one letter a, b, c describing further Variations. See: [[ItemVariations.xls]]
*[LOD] is optional for LOD Versions of Models, where its 0, 2 or 3 from highest to lowest LOD. Options are dependant on resourcetype, however 0 is always required if LOD is applicable.

=== Creatures ===

<pre>[MainClass]+[ModelName]_[LOD].MMH / PHY

[c]_[deepstkra]_[0].mmh (c_deepstkra_0.mmh)</pre>

*[MainClass] is the general type of the model. When no override is set in [[APR base.xls]], the toolset will generate it based on race and gender. (see below)
*[ModelName] is the Modelname (including mainclass) described in [[APR base.xls]]. When no Modelname is given, and Modeltype is P, the toolset will generate it based on [[NakedVariations.xls]] (unsure)
*[LOD] is optional for LOD Versions of Models, where its 0, 2 or 3 from highest to lowest LOD. Options are dependant on resourcetype, however 0 is always required if LOD is applicable.

This accounts for the game being able to locate a [[MMH]] via 2DA definitions. [[MSH]] / [[MAO]] / [[DDS]] Files are referenced by the MMH and each other but follow similar schemes.

=== Model Main Class Naming Convention ===

*base
*blk - black boxes of various sizes and proportions, used to obscure the portions of models that lie "outside" an interior level where the player shouldn't be able to see.
*c - creature
*cai - Cave Int.
*cav - Caves
*cdr - Cave Deep Road
*che - Chantry Exterior
*chi - Chantry Interior
*cn - Commmon Body Meshes
*cs
*df - dwarf female accessories and components
*dm - dwarf male accessories and components
*dne - dwarf noble exterior level pieces
*dni - dwarf noble interior level pieces
*dse - Dwarf Slum Exterior
*dsi - Dwarf Slum Interior
*dwe - Dwarven Exterior (Orzammar City)
*dwi - Dwarven Interior
*ef - elf female accessories and components
*el
*em - elf male accessories and components
*fca - Fereldan Castle
*fce - Fereldan Castle/City Exterior
*fci - Fereldan Castle Interior
*fde
*fdi - Fereldan Dungeon Interior
*fhe - Fereldan Human Exterior
*fhec
*fhi - Ferelden Human Interior
*fne - Ferelden noble exterior level pieces
*frt
*fti - Fereldan Town Interior
*ftr
*fve - Fereldan Village Exterior
*fx - Effects
*fxa
*fxc
*fxe
*fxg
*fxm
*fxp
*hf - human female accessories and components
*hm - human male accessories and components
*hro - Hero Sets
*kn
*lightrig
*material
*nm
*pf - Female specific Gear
*plc - placeables
*pm - Male or Genderless specific Gear
*pn -
*prp - props
*prv
*qm
*sb - Skybox
*sca
*sr
*tce - Tevinter Castle Exterior
*tci - Tevinter Castle Interior
*tfi - Tevinter Fade Interior
*tools - models used by the toolset
*trn
*tti - Tevinter Tower Interior
*tve - Tevinter Exterior
*tvi - Tevinter Interior
*tvm
*ue
*uem - Eyes
*uh - Face Bits
*uhm - Heads
*ul
*ulm - Eyelashes
*v
*vfx - Visual Effects
*vis - Vista Objects
*vst - Vista Objects
*w - weapon models
*water - waterfall pieces
*zz - models used in debugging

== Voice Over File Naming Convention ==

<pre>[LineID]_m.WAV</pre>

*with [LineID] replaced by the ID number for the conversation line's string table entry.

This accounts for being able to locate thousands of VO lines, when assigning them to their conversation line.

See [[voice over]] for more information on how to manage voice over recording.

== Animation File Naming Convention ==

<pre>mh.dg_5p_tn_l_45.ANI</pre>

The various parts of the animation name gives you information about the type of animation. This for example means "male human dialogue 5 paces turn left 45 degrees."

All humanoid animations prefix with mh. (male human). There is also a small list of fh (female human), These work across all races pretty much.

After the prefix you have the following:
*2p - a 2 person animation... usually lined up (i.e. give and receive, punch and punched, kiss and kissed)
*am - ambient... full animations that so specific actions (i.e. blacksmith, cheering, clean floor)
*cb - combat animations
*cu - custom animation, usually for a specific cutscene or purpose
*dg - dialog... animation fpr the purpose of use within dialogs (although we use all these animations)
*po - pose based animations - these are specific poses and gestures for talking dialogs
*wi - world interaction - similar to ambient but more about interacting with world objects (desks, leaning, sitting)

After the above second prefix the rest is usually descriptive (or some what). Key thing to note:
*en - enter animation... this is the animation that gets the actor doing the animation... usually from a standing neutral position
*lp - looping animation - this is the animation that loops to keep the actor in a pose or position
*ex - exit animation - this is the animation that gets the actor out of the lp animation... usually to a standing neutral position
*tw - twitch, an animation that plays from the lp animation

So, for example:
*mh.wi_sit_en - animation goes from standing neutral to sitting
*mh.wi_sit_lp - animation loops in the sitting pose
*mh.wi_sit_ex - animation goes from sitting to standing neutral
*mh.wi_sit_tw1 - an animation that plays from sit_lp, such as someone scratching their head

== Vegetation (Speedtree) File Naming Convention ==

<pre>tre c oakfixl.SPT</pre>

Vegetation is sorted in main categories via Prefix:

*bsh - Bushes
*gra - Grass
*tre - Trees

The last part is a short description of the vegetation type, ie Oak, which is a Oaktree.

== See Also ==

*[[Art Resources]]
*[[Designer Resources]]
*[[Compatibility]]

[[Category:Art resources]]

BITM base.xls

2022-07-17T21:22:25Z

Ashhawk: Added missing WeaponOffset column

{{Infobox items}}

Defines base items, such as "Weapon - Longsword", used in the item editor.

Several worksheets in this Excel file are not actual 2DAs, they are present only for informational purposes.

A note when editing:

*SourceData - This is the worksheet where the information for the 2da should be edited.
*BITM_base - This worksheet is a mirror of the data from SourceData (but only the columns that the game cares about)

== BITM_base worksheet ==

{{2da start|BITM_base}}
{{2da column| Label | string | }}
{{2da column| NameStrRef | int | {{undocumented}} }}
{{2da column| DescStrRef | int | {{undocumented}} }}
{{2da column| InvSlotWidth | int | {{undocumented}} }}
{{2da column| InvSlotHeight | int | {{undocumented}} }}
{{2da column| EquippableSlots | int | A bitfield indicating which slots the item can be equipped into. See the _EquipSlots worksheet for an explanation of these values. }}
{{2da column| WearR |int | Index into the [[parts.xls]] file. Indicates where right hand weapons are worn on the body.}}
{{2da column| WearL |int| Index into the parts.xls file. Indicates where left hand weapons are worn on the body.}}
{{2da column| WieldR|int| Index into the parts.xls file. Indicates where wielded right hand weapons are attached in combat.}}
{{2da column| WieldL |int| Index into the parts.xls file. Indicates where wielded left hand weapons are attached in combat.}}
{{2da column| Heraldry |bool| Whether or not items using this base type can have heraldry applied}}
{{2da column| WeaponOffset| float | {{undocumented}} }}
{{2da column| CanRotateIcon | bool | {{undocumented}} }}
{{2da column| TargetType | int | {{undocumented}} }}
{{2da column| Variation_WorkSheet | int | Items with Variants refer to M2DA_base.GDA by its ID }}
{{2da column| DefaultMaterial | int | {{undocumented}} }}
{{2da column| DefaultModel | string | {{undocumented}} }}
{{2da column| DefaultIcon | string | {{undocumented}} }}
{{2da column| DefaultResource | string | {{undocumented}} }}
{{2da column| WeaponWield | int | {{undocumented}} }}
{{2da column| WieldModel | string | {{undocumented}} }}
{{2da column| WieldModelOverlay | string | {{undocumented}} }}
{{2da column| CombatRating | float | {{undocumented}} }}
{{2da column| StrengthModifier | float | {{undocumented}} }}
{{2da column| BaseDamage | int | {{undocumented}} }}
{{2da column| StackSize | int | {{undocumented}} }}
{{2da column| Type| int| The meanings of these values can be found in the ItemTypes worksheet in this document.}}
{{2da column| Speed| int | Slow = 1, Medium = 2, Fast = 3. Note: Check [[AttackSpeeds.xls]] for details}}
{{2da column| Range|float| Distance is in meters.}}
{{2da column| Projectile | int| If the item can be fired as a projectile (e.g. arrows), this field should relate to a projectile in PRJ 2da.}}
{{2da column| ProjectileOffset| float| Height distance to move a projectile launch position relative to the hand of the user. }}
{{2da column| Ammo |int| Which base item type serves as ammo for this item}}
{{2da column| StorePanel | int | {{undocumented}} }}
{{2da column| ModalAbilityBlendTree |int| Specifies if the item is able to work with modal ability blend trees. This is currently only relevant for MAIN and OFFHAND slot items.}}
{{2da column| InvSoundType |int| ID sound materials defined in "[[Sound_Item_Materials.xls]]"}}
{{2da column| ArmorType| int| 2 - medium, 3 - heavy, 4 - massive, 5 - cloth}}
{{2da column| DoNotDrop |int| if true, the treasure system will never drop this item.}}
{{2da column| ReqProp1 | int | ID of the first property requirement for the item from [[properties.xls]] }}
{{2da column| ReqProp1Val | float | minimum property value to allow item to be equipped }}
{{2da column| ReqProp2 | int | ID of the second property requirement for the item from [[properties.xls]] }}
{{2da column| ReqProp2Val | float | minimum property value to allow item to be equipped }}
{{2da column| piercingtype| int| 1 bladed, 2 blunt, 3 ranged}}
{{2da column| RuneSlots |int| Mask for the rune slot (same as equipment slots)}}
{{2da column| RuneCount |int| Base number of runes. Note that 0 and even negative numbers can be increased into positive by the material types, so we use a rather large negative number to prevent runes on most items.}}
{{2da column| SoundVariation |int| Specifies the sound variation for each object type. Note that 0 means the default sound is used: cloth for armor, sharp weapon for weapons and generic for everything else.}}
{{2da column| IsHeavy | int | Considered to be heavy for dual wielding purposes. Requires dual wielding mastery to equip in the offhand. }}
{{2da column| ShowMaterial | int | If an item of this base type should show its material type in the inventory UI. }}
{{2da column| SuppressPropertyVFX | bool | Avoid displaying a VFX that would be added through item properties }}
{{2da end}}

== ItemStats worksheet ==

{{2da start|ItemStats}}
{{2da column| Label | string | }}
{{2da column| Attack | float | }}
{{2da column| Damage | float | }}
{{2da column| DamageRange | float | }}
{{2da column| Armor | float | }}
{{2da column| ArmorPenetration | float | }}
{{2da column| Defense | float | }}
{{2da column| BaseAimDelay | float | }}
{{2da column| Dspeed | float| Speed change within style from default anim speed.}}
{{2da column| CritChanceModifier | float | }}
{{2da column| AbilityCostModifier | float | }}
{{2da column| MissileDeflection | float | }}
{{2da column| OptimumRange | float | }}
{{2da column| SpellPower | float | }}
{{2da column| RngdPenalty | float | }}
{{2da column| AttributeMod | float | }}
{{2da column| Attribute0 | int | }}
{{2da column| Attribute1 | int | }}
{{2da end}}

== itemstatdefines worksheet ==

{{2da start|itemstatdefines}}
{{2da column| Label |string| This label must match the name of the column where this stat is found in the BITM_base 2da.}}
{{2da column| NameStrRef |int| }}
{{2da column| CreatureProp |int| This number is the ID of the creature property that this item stat affects. When the item is equipped, the creature property will automatically be modified by the value found for this stat in the BITM_base.}}
{{2da column| bShowInUI|int|}}
{{2da column| Precision |int|Number of decimal places to show in the UI}}
{{2da end}}

== ArmorData worksheet ==

{{2da start|ArmorData}}
{{2da column| Label | string| }}
{{2da column| Chest | float | }}
{{2da column| Boots | float | }}
{{2da column| Gloves | float | }}
{{2da column| Helmet | float | }}
{{2da column| Total| comment| }}
{{2da end}}

== _SourceData worksheet ==

This worksheet is not exported directly as a 2DA file.

* Name - If the rows or columns change, macros need updating
* (no label) - an ID column
* Label
* NameStrRef - A string ID that leads to a string with the name of this kind of item. For example, boots have an English string that reads "Boot".
* DescStrRef
* InvSlotWidth
* InvSlotHeight
* InvSoundType
* EquippableSlots - a bitfield indicating which inventory slots the item can be equipped in.
* WearR - Index into the parts.xls file. Indicates where right hand weapons are worn on the body.
* WearL - Index into the parts.xls file. Indicates where left hand weapons are worn on the body.
* WieldR - Index into the parts.xls file. Indicates where wielded right hand weapons are attached in combat.
* WieldL - Index into the parts.xls file. Indicates where wielded left hand weapons are attached in combat.
* CanRotateIcon
* TargetType
* Variation_WorkSheet
* DefaultModel
* DefaultIcon
* WeaponWield
* WieldModel
* CombatRating
* StrengthModifier - How strength damage is scaled when using this weapon.
* BaseDamage
* ArmourPenetration - Rules. Design-Materials. Armor penetrating capability of this weapon. Serves dual purpose. Also the field for the ARMOR value of Armor. This is also used for the shield base modifier
* ArmourValue
* Attribute - This is an index into the attribute.xls. It iis used by rules to determine the required attribute score.
* AttributeValue
* StackSize
* MinItemProps
* MaxItemProps
* PropColumn - This column references ItemProperties.xls (the ItemPropDef page). It assigns each item into a category. Tools then uses this to figure out which properties are allowed for each item type.
* StartingCharges
* QBBehaviour
* StorePanel
* StorePanelSort
* Type
* Speed
* BaseDamageReduction
* AttackExtra
* BaseDefenseBonus
* Type
* BaseArmorPenetration
* LightArmor
* AbilityScoreRequired
* BasePreReqAbility
* StaminaUpkeep
* BaseDamage
* StrengthModifierMultiplier
* AbilityScoreRequired2
* BasePreReqAbility2

== _EquipSlots worksheet ==

This worksheet is not exported directly as a 2DA file.

*LABEL
*MASK
*SET1
*SET2

[[Category:XLS files]]
[[Category:Items]]

Lighting Tutorial

2022-07-08T11:41:25Z

Ashhawk: Image formatting

Author: by mikemike37

Please also check out the [[Lighting]] information.

This is only one method of lighting your level - I suggest some experimentation, but given the lengthy lightmapping process, I'm sure you can use these guidelines to help prevent timewasting.

== Okay so I don't really care too much but I want some light. What's the fastest way to do that? ==

To have even and fairly bland lighting throughout your level and at the risk of some unexpected but not strong shadows:

# Create a new room named "Shared Lighting"
# Select the Shared Lighting room and Click Room Properties
# Have every room lit by lights from this source (use Add, click the rooms from the left).
# Insert > New Light
#* Light type: Point Static
#* Affects Characters: True
#* Affects Levels: True
#* Colour: 0.5, 0.5, 0.5
#* Colour Intensity: 0.8
#* Point Radius: 500 or more for larger levels
# Place such that your entire level is about halfway from the light source and its edge and a little way up.
# Copy and paste so you have 4 surrounding the entire level.
# Insert > New Light
#* Light type: Ambient - Baked
#* Colour: 0.5, 0.5, 0.5

== Lighting done "properly" ==

=== Introduction to Lighting Types (baked versus in-game lighting) ===

The most important difference to understand is the difference between baked lighting and "in-game" lighting. In the game, your character is illuminated by lights from various angles... but your character moves, so it follows that the strength of the light reflecting from your character must be calculated on-the-fly. These calculations performed by your graphics processor are pretty intensive, so it makes sense to avoid them where possible and free up your graphics processor for other cool visual stuff, like high poly models and large textures. So how can we reduce this load? using baked lighting.

The principle of baked lighting is as follows: for lights which do not move and for objects which do not move, we can calculate the reflection and save the results for the graphics processor to read, and not have to calculate. In Dragon Age, we do this by lightmapping using baked lights and static props. Everything you place in the level editor (NOT area editor) must necessarily be unable to move in-game.

I'll now explain the order in which I add lights, with an explanation of what I consider to be good practice. I write this with interior levels in mind.

=== Buttons ===

* '''Room Properties:''' allows you to describe to the engine which rooms are visible, are lit by and are connected to each given room.
* '''Render Lightmaps:''' will process all baked lights to the lightmaps. Time-consuming, good for finalising.
* '''Render Lightmaps for selected Chunks or Rooms:''' select only the rooms you want to lightmap. Less time-consuming, good for experimenting.
* '''Display Lightmaps On/Off:''' When enabled, this will show you the lightmap result. Always toggle off then back on to update the lightmap after processing. It will NOT show you "live" lighting, such as static lights. You have to sort of guess what that'll end up like.
* '''View Models Fully Lit:''' gives the same result as ambient at 1, 1, 1 - everything is well-illuminated. Good for moving things about.
* '''Render Light Probes:''' I'll look into this later.

=== Create a "shared lighting" room (interior only) - realtime, characters only ===

Using the method suggested on the builder's wiki, you can have all characters illuminated dimly in all directions in every room by using a "shared lighting" room.

# Create a new room
# Rename the room "Shared Lighting"
# Select the Shared Lighting room
# Click Room Properties
# Have every room lit by lights from this source.

Adding the lights:

# Insert > New Light
#* Light type: Point Static
#* Affects Characters: True
#* Affects Levels: False
#* Colour 0.3, 0.3, 0.3
#* Colour Intensity 0.8
#* Point Radius: 500
# Place such that your entire level is about halfway from the light source and its edge. You may like to place these above the level a little way since light typically comes from above (but not always...)
# Copy and paste so you have 4 surrounding the entire level.

=== Ambient Light - baked, level only ===

By adding this before any "specific" lighting, we can set the tone for the level and build up from there. You only need one ambient in the entire level and it affects all rooms regardless of any other settings.

As far as I can tell, Intensity is NOT used, so you're going entirely on colour here. Vary the colour and brightness to suit taste, but you don't want this to be too strong or you will lose the strength of contrast in your lighting since the dark areas won't be very dark. Below are suggested values.

# Select the Shared Lighting room
# Insert > New Light
#* Light type: Ambient - Baked
#* Colour: 0.2, 0.2, 0.2
#* Position, intensity does not matter at all. Leave at default is fine.

=== Static and animated Lights - realtime, characters and level ===

You should try lightmapping your level at this point (Render Lightmaps) and exporting to try it out in-game. You should have a pretty dark, but visible level throughout.

We now want to add in static and animated lights so that the characters are illuminated by things actually present in the level. With lighting, its a very good idea to start with the strongest lights first. With all of these lights, use Affect Characters: TRUE. Use Affects Level: TRUE sparingly - an object may only receive a maximum of 3 static lights. For this reason, avoid placing lights with an overlapping radius. Multiple static lights occupying the same space is to be avoided strongly.

The strongest lights, generally, will be natural light where you have it - so add light from windows and similar first. Use cool, pale colours (light blues) so as not to wash out the colour of the room.

Next add in "genuine" light sources. By this I mean things which you understand to actually generate light. Torches, fires, glowing stuff. For fires, its nice to use the animated light types. Play with the settings, or try copying from one of the DA levels. Fire generally makes yellow glows, not bright orange.

=== Baked Lights ===

If you've allowed a lot of static lights to illuminate your level, you may only need to add baked lights to things too small to warrant a static light, and to brighten up dark patches. However, you may want to make more extensive use of baked lighting since it allows for a greater control over your lighting by adding many baked lights without impacting the player's performance (since they're all calculated at the lightmapping stage). It also generally makes nicer, softer shadows.

=== Adding shadows where they "shouldn't exist" ===

This tip from !TimelordDC: Let's say you want to build a dark pit or a dark circular area within a big room. Place a model of the appropriate shape (doesn't matter which model) right above the area you want to darken and adjust the model properties to set Export To Game as FALSE and Lightmap as TRUE. Place a light directly above it to cast a strong shadow. Once you render lightmaps, you will see a dark shadow beneath the model but the model won't be present in-game. There is a bit of work to get it just right since the model can cast shadows from other lights too.

You can also darken areas using negative static lights. Experiment with these - you can see their effect in realtime.

=== Light Probes ===

Light Probes are used for reflections. This includes but is not limited to: reflections off of weapons/armour using fresnel and water. Place a Light Probe in each room of an indoor level, or one over each patch of water in an outdoor level. Currently, a bug prevents the light probes from generating more than one image. After Placing, use Render Lightprobes and toggle view lightmaps to ON to see what they look like.

=== "Corruption" Fix ===
Occasionally, the lightmap seems to become "corrupted". If you believe there is a mistake with it that shouldnt be there when you hit process lightmaps, but always is... then its possible you are using "two lightmaps". This is usually caused by having exported your level and then gone back to try and improve the lightmap. There are two ways to fix this:

==== Rename your layout ====

This will force the lightmap to start from scratch, but you will have to change the layout and will end up with a potentially messy set of folders all over the place.

==== Delete all the lightmap files ====
My Documents\BioWare\Dragon Age\Toolset\LvlWorkspace\lightmaps\LAYOUT

My Documents\BioWare\Dragon Age\Toolset\ProbeLightMaps\LAYOUT

My Documents\BioWare\Dragon Age\Toolset\resourcepostintermediatewin32\processed\addins\MODULE\layouts\win32\layouts\LAYOUT

My Documents\BioWare\Dragon Age\Toolset\resourcepostintermediatewin32\processed\addins\MODULE\layouts\win32\modelhierarchies\LAYOUT

My Documents\BioWare\Dragon Age\Toolset\resourcepostintermediatewin32\processed\addins\MODULE\layouts\win32\textures\dds\LAYOUT

(path of your level file)\LAYOUT.erf

(path of your level file)\LAYOUT.bak.erf

C:\DOCUME~1\Mike\LOCALS~1\Temp\DALightmap\LAYOUT (you can use Run... and type %TEMP% and hit OK)

(if you have posted to local) My Documents\BioWare\Dragon Age\addins\MODULE\core\override\toolsetexport\LAYOUT

== Troubleshooting ==

IMPORANT: if you have posted your layout to local, then the lightmap dds files in your override will start conflicting with those in your toolset. ALWAYS remove them whenever you change lighting, otherwise you will see the result of BOTH lightmaps being applied.

=== Nothing I do seems to make a difference in-toolset ===

Ensure you have disabled "view models fully lit" and you have enabled "Display Lightmaps On/Off?". If you have recently remapped, you will need to toggle display lightmaps off then back on again to refresh the display.

If you have posted to local and restarted your toolset, you will need to close your toolset, delete the exported files and restart your toolset.

=== Nothing I do seems to make a difference in-game ===

Check your area file is using the correct name and that it has been exported. Also check that you have "done all local posts" in your level after changing the lightmap.

=== My character in-game is entirely black and I'm getting a warning about shadow maps ===

If you haven't added any static lights, you will get an error saying "no static lights detected. Shadow maps will not be generated" (or similar). Its generally a good idea to have some static lights, since these will illuminate your character.

=== I have dark shapes/symbols over many different models in different ways (corruption) ===

This is caused by a model trying to use a portion of your lightmap that it shouldn't be. This can be caused by having lightmaps in your override and lightmapping a second time. To remove your old lightmaps, delete the exported files in your core/override/toolsetexport. If this doesn't fix, try DeletingLightmapFiles. Finally, if you still get the issue, its a problem with the model you are using - it has a bad lightmap UV unwrap.

[[File:Staticbunching.jpg|border]]

=== I have some kind of corruption on my lightmap throughout an entire room or level ===

Same problem as above, but without the distinctive "shapes". This is much more likely to be because you need to delete the exported lightmaps from your override.

<gallery mode="nolines" widths=422px heights=600px>
File:Corruptedshadowmap1.jpg|Extremely patchy lighting throughout level
File:Corruptedshadowmap2.jpg|Fixed
</gallery>

=== I have black patterns or triangles identically or similar over many of the same model ===

Some models seem to have a problem with lightmapping. look for a fix here or try using a different model.

<gallery mode="nolines" widths=550px heights=600px>
File:Badmodellightmap.jpg|fca_floor02_0
</gallery>

=== I have obvious seams between two or more models where they should be seamless ===

This is caused by the fact that one object may receive static light from no more than 3 sources. In the example, I have three tiles. In the first screenshot, I have three blue lights and one red light. The middle tile does not receive the red light at all, and so a seam becomes apparent. The tile closest to the red light is receiving the red light and light from two of the blue lights.

The fix here was to delete two of the blue lights and increase the intensity of the remaining blue light to compensate. Of course, this was a test setup, but the principle remains the same... ensure you have no more than three static lights overlapping ''anywhere'' in your level. Its a good idea to keep this down to just two lights where possible.

<gallery mode="nolines" widths=600px heights=600px>
File:BStatic_bunching11111.jpg|Four static lights in scene
File:Static_bunching_fixed.jpg|Two static lights in scene
</gallery>

=== I have one unusual shadow (symmetrical pattern) caused by static lights and it doesn't make sense ===

I am unsure if this was a problem with one particular model and/or the static light I was using, but if you get something like this try lightmapping after moving your lights to a new location.

<gallery mode="nolines" widths=498px heights=600px>
File:Onebigartifact.jpg|Bad shadow passing through prp_dni_torch03_0 (showing the result only - lights and problematic model are not shown)
</gallery>

=== The lights seem to go off or change badly every time I change rooms ===

You need to set up rooms to be visible and receive light from one another. Only adjacent rooms should receive light from one another, but always ensure all rooms which CAN be visible from a room ARE visible. You should also connect rooms.

=== I want to illuminate my room generally without "spotty" lights all over the place but I don't want to increase my ambient lighting ===

Try adding a large light way outside of the room. You run the risk of getting unexpected shadows as the light shines through your walls/ceilings, but apparently you can reduce these by increasing the light size under "soft shadows". I haven't tested this technique.

=== I have lots of tiny black dots all over my lightmaps ===

This problem seems to occur only in small rooms which have a ceiling. There are two solutions: accept the noise and use post-processing noise reduction on it... or take off the ceilings and render them separately.

For taking off the ceilings, please see this thread [http://social.bioware.com/forum/1/topic/74/index/4700291 here]

To edit the lightmap file yourself AFTER exporting it out:

# Render Lightmaps
# Post all to local
# Navigate to My Documents\BioWare\Dragon Age\addins\MODULE\core\override\toolsetexport\LAYOUT
# Find the erroneous lightmap dds
# Perform whatever surgery you deem necessary. I suggest using some sort of noise reduction filter. Ideally removing only "pepper" and not "salt".
# If you have photoshop I suggest creating an action, opening all erroneous dds files and automating the action on all opened files.

<gallery mode="nolines" widths=256px heights=256px>
File:Noisylightmapdds.jpg|Lightmap before noise reduction
File:Noisylightmapdds2.jpg|Lightmap after noise reduction
</gallery>

<gallery mode="nolines" widths=700px heights=385px>
File:Noisylightmap.jpg|Before noise reduction
File:Noisylightmap2.jpg|After noise reduction
</gallery>

=== My custom material does not seem to lightmap ===

Ensure your material is set to static, has a lightmap texture line and has unique textures (diffuse cannot be used as both diffuse and specular), and your object has a second UV layer and meta data. For more information on materials, check Texture tutorial (condensed)

== Credits ==

Thanks to Semper for clearing up some questions I had. !TimelordDC provided the shadows tip. Oh and a couple of bits from CID-78. Also thanks to the guys on the bioware wiki who provided the information I started with.
== Useful links ==
*[[Adding custom level tutorial]] - How to add your own level.
*[[Level Editor Tutorial]] and [[Level tutorial]] - General advises.
[[Category:Tutorials]]

Lighting Tutorial

2022-07-08T11:37:40Z

Ashhawk: Image formatting

Author: by mikemike37

Please also check out the [[Lighting]] information.

This is only one method of lighting your level - I suggest some experimentation, but given the lengthy lightmapping process, I'm sure you can use these guidelines to help prevent timewasting.

== Okay so I don't really care too much but I want some light. What's the fastest way to do that? ==

To have even and fairly bland lighting throughout your level and at the risk of some unexpected but not strong shadows:

# Create a new room named "Shared Lighting"
# Select the Shared Lighting room and Click Room Properties
# Have every room lit by lights from this source (use Add, click the rooms from the left).
# Insert > New Light
#* Light type: Point Static
#* Affects Characters: True
#* Affects Levels: True
#* Colour: 0.5, 0.5, 0.5
#* Colour Intensity: 0.8
#* Point Radius: 500 or more for larger levels
# Place such that your entire level is about halfway from the light source and its edge and a little way up.
# Copy and paste so you have 4 surrounding the entire level.
# Insert > New Light
#* Light type: Ambient - Baked
#* Colour: 0.5, 0.5, 0.5

== Lighting done "properly" ==

=== Introduction to Lighting Types (baked versus in-game lighting) ===

The most important difference to understand is the difference between baked lighting and "in-game" lighting. In the game, your character is illuminated by lights from various angles... but your character moves, so it follows that the strength of the light reflecting from your character must be calculated on-the-fly. These calculations performed by your graphics processor are pretty intensive, so it makes sense to avoid them where possible and free up your graphics processor for other cool visual stuff, like high poly models and large textures. So how can we reduce this load? using baked lighting.

The principle of baked lighting is as follows: for lights which do not move and for objects which do not move, we can calculate the reflection and save the results for the graphics processor to read, and not have to calculate. In Dragon Age, we do this by lightmapping using baked lights and static props. Everything you place in the level editor (NOT area editor) must necessarily be unable to move in-game.

I'll now explain the order in which I add lights, with an explanation of what I consider to be good practice. I write this with interior levels in mind.

=== Buttons ===

* '''Room Properties:''' allows you to describe to the engine which rooms are visible, are lit by and are connected to each given room.
* '''Render Lightmaps:''' will process all baked lights to the lightmaps. Time-consuming, good for finalising.
* '''Render Lightmaps for selected Chunks or Rooms:''' select only the rooms you want to lightmap. Less time-consuming, good for experimenting.
* '''Display Lightmaps On/Off:''' When enabled, this will show you the lightmap result. Always toggle off then back on to update the lightmap after processing. It will NOT show you "live" lighting, such as static lights. You have to sort of guess what that'll end up like.
* '''View Models Fully Lit:''' gives the same result as ambient at 1, 1, 1 - everything is well-illuminated. Good for moving things about.
* '''Render Light Probes:''' I'll look into this later.

=== Create a "shared lighting" room (interior only) - realtime, characters only ===

Using the method suggested on the builder's wiki, you can have all characters illuminated dimly in all directions in every room by using a "shared lighting" room.

# Create a new room
# Rename the room "Shared Lighting"
# Select the Shared Lighting room
# Click Room Properties
# Have every room lit by lights from this source.

Adding the lights:

# Insert > New Light
#* Light type: Point Static
#* Affects Characters: True
#* Affects Levels: False
#* Colour 0.3, 0.3, 0.3
#* Colour Intensity 0.8
#* Point Radius: 500
# Place such that your entire level is about halfway from the light source and its edge. You may like to place these above the level a little way since light typically comes from above (but not always...)
# Copy and paste so you have 4 surrounding the entire level.

=== Ambient Light - baked, level only ===

By adding this before any "specific" lighting, we can set the tone for the level and build up from there. You only need one ambient in the entire level and it affects all rooms regardless of any other settings.

As far as I can tell, Intensity is NOT used, so you're going entirely on colour here. Vary the colour and brightness to suit taste, but you don't want this to be too strong or you will lose the strength of contrast in your lighting since the dark areas won't be very dark. Below are suggested values.

# Select the Shared Lighting room
# Insert > New Light
#* Light type: Ambient - Baked
#* Colour: 0.2, 0.2, 0.2
#* Position, intensity does not matter at all. Leave at default is fine.

=== Static and animated Lights - realtime, characters and level ===

You should try lightmapping your level at this point (Render Lightmaps) and exporting to try it out in-game. You should have a pretty dark, but visible level throughout.

We now want to add in static and animated lights so that the characters are illuminated by things actually present in the level. With lighting, its a very good idea to start with the strongest lights first. With all of these lights, use Affect Characters: TRUE. Use Affects Level: TRUE sparingly - an object may only receive a maximum of 3 static lights. For this reason, avoid placing lights with an overlapping radius. Multiple static lights occupying the same space is to be avoided strongly.

The strongest lights, generally, will be natural light where you have it - so add light from windows and similar first. Use cool, pale colours (light blues) so as not to wash out the colour of the room.

Next add in "genuine" light sources. By this I mean things which you understand to actually generate light. Torches, fires, glowing stuff. For fires, its nice to use the animated light types. Play with the settings, or try copying from one of the DA levels. Fire generally makes yellow glows, not bright orange.

=== Baked Lights ===

If you've allowed a lot of static lights to illuminate your level, you may only need to add baked lights to things too small to warrant a static light, and to brighten up dark patches. However, you may want to make more extensive use of baked lighting since it allows for a greater control over your lighting by adding many baked lights without impacting the player's performance (since they're all calculated at the lightmapping stage). It also generally makes nicer, softer shadows.

=== Adding shadows where they "shouldn't exist" ===

This tip from !TimelordDC: Let's say you want to build a dark pit or a dark circular area within a big room. Place a model of the appropriate shape (doesn't matter which model) right above the area you want to darken and adjust the model properties to set Export To Game as FALSE and Lightmap as TRUE. Place a light directly above it to cast a strong shadow. Once you render lightmaps, you will see a dark shadow beneath the model but the model won't be present in-game. There is a bit of work to get it just right since the model can cast shadows from other lights too.

You can also darken areas using negative static lights. Experiment with these - you can see their effect in realtime.

=== Light Probes ===

Light Probes are used for reflections. This includes but is not limited to: reflections off of weapons/armour using fresnel and water. Place a Light Probe in each room of an indoor level, or one over each patch of water in an outdoor level. Currently, a bug prevents the light probes from generating more than one image. After Placing, use Render Lightprobes and toggle view lightmaps to ON to see what they look like.

=== "Corruption" Fix ===
Occasionally, the lightmap seems to become "corrupted". If you believe there is a mistake with it that shouldnt be there when you hit process lightmaps, but always is... then its possible you are using "two lightmaps". This is usually caused by having exported your level and then gone back to try and improve the lightmap. There are two ways to fix this:

==== Rename your layout ====

This will force the lightmap to start from scratch, but you will have to change the layout and will end up with a potentially messy set of folders all over the place.

==== Delete all the lightmap files ====
My Documents\BioWare\Dragon Age\Toolset\LvlWorkspace\lightmaps\LAYOUT

My Documents\BioWare\Dragon Age\Toolset\ProbeLightMaps\LAYOUT

My Documents\BioWare\Dragon Age\Toolset\resourcepostintermediatewin32\processed\addins\MODULE\layouts\win32\layouts\LAYOUT

My Documents\BioWare\Dragon Age\Toolset\resourcepostintermediatewin32\processed\addins\MODULE\layouts\win32\modelhierarchies\LAYOUT

My Documents\BioWare\Dragon Age\Toolset\resourcepostintermediatewin32\processed\addins\MODULE\layouts\win32\textures\dds\LAYOUT

(path of your level file)\LAYOUT.erf

(path of your level file)\LAYOUT.bak.erf

C:\DOCUME~1\Mike\LOCALS~1\Temp\DALightmap\LAYOUT (you can use Run... and type %TEMP% and hit OK)

(if you have posted to local) My Documents\BioWare\Dragon Age\addins\MODULE\core\override\toolsetexport\LAYOUT

== Troubleshooting ==

IMPORANT: if you have posted your layout to local, then the lightmap dds files in your override will start conflicting with those in your toolset. ALWAYS remove them whenever you change lighting, otherwise you will see the result of BOTH lightmaps being applied.

=== Nothing I do seems to make a difference in-toolset ===

Ensure you have disabled "view models fully lit" and you have enabled "Display Lightmaps On/Off?". If you have recently remapped, you will need to toggle display lightmaps off then back on again to refresh the display.

If you have posted to local and restarted your toolset, you will need to close your toolset, delete the exported files and restart your toolset.

=== Nothing I do seems to make a difference in-game ===

Check your area file is using the correct name and that it has been exported. Also check that you have "done all local posts" in your level after changing the lightmap.

=== My character in-game is entirely black and I'm getting a warning about shadow maps ===

If you haven't added any static lights, you will get an error saying "no static lights detected. Shadow maps will not be generated" (or similar). Its generally a good idea to have some static lights, since these will illuminate your character.

=== I have dark shapes/symbols over many different models in different ways (corruption) ===

This is caused by a model trying to use a portion of your lightmap that it shouldn't be. This can be caused by having lightmaps in your override and lightmapping a second time. To remove your old lightmaps, delete the exported files in your core/override/toolsetexport. If this doesn't fix, try DeletingLightmapFiles. Finally, if you still get the issue, its a problem with the model you are using - it has a bad lightmap UV unwrap.

[[File:Staticbunching.jpg|border]]

=== I have some kind of corruption on my lightmap throughout an entire room or level ===

Same problem as above, but without the distinctive "shapes". This is much more likely to be because you need to delete the exported lightmaps from your override.

<gallery mode="nolines" widths=422px heights=600px>
File:Corruptedshadowmap1.jpg|Extremely patchy lighting throughout level
File:Corruptedshadowmap2.jpg|Fixed
</gallery>

=== I have black patterns or triangles identically or similar over many of the same model ===

Some models seem to have a problem with lightmapping. look for a fix here or try using a different model.

<gallery mode="nolines" widths=550px heights=600px>
File:Badmodellightmap.jpg|fca_floor02_0
</gallery>

=== I have obvious seams between two or more models where they should be seamless ===

This is caused by the fact that one object may receive static light from no more than 3 sources. In the example, I have three tiles. In the first screenshot, I have three blue lights and one red light. The middle tile does not receive the red light at all, and so a seam becomes apparent. The tile closest to the red light is receiving the red light and light from two of the blue lights.

The fix here was to delete two of the blue lights and increase the intensity of the remaining blue light to compensate. Of course, this was a test setup, but the principle remains the same... ensure you have no more than three static lights overlapping ''anywhere'' in your level. Its a good idea to keep this down to just two lights where possible.

<gallery mode="nolines" widths=600px heights=600px>
File:BStatic_bunching11111.jpg|Four static lights in scene
File:Static_bunching_fixed.jpg|Two static lights in scene
</gallery>

=== I have one unusual shadow (symmetrical pattern) caused by static lights and it doesn't make sense ===

I am unsure if this was a problem with one particular model and/or the static light I was using, but if you get something like this try lightmapping after moving your lights to a new location.

<gallery mode="nolines" widths=498px heights=600px>
File:Onebigartifact.jpg|Bad shadow passing through prp_dni_torch03_0 (showing the result only - lights and problematic model are not shown)
</gallery>

=== The lights seem to go off or change badly every time I change rooms ===

You need to set up rooms to be visible and receive light from one another. Only adjacent rooms should receive light from one another, but always ensure all rooms which CAN be visible from a room ARE visible. You should also connect rooms.

=== I want to illuminate my room generally without "spotty" lights all over the place but I don't want to increase my ambient lighting ===

Try adding a large light way outside of the room. You run the risk of getting unexpected shadows as the light shines through your walls/ceilings, but apparently you can reduce these by increasing the light size under "soft shadows". I haven't tested this technique.

=== I have lots of tiny black dots all over my lightmaps ===

This problem seems to occur only in small rooms which have a ceiling. There are two solutions: accept the noise and use post-processing noise reduction on it... or take off the ceilings and render them separately.

For taking off the ceilings, please see this thread [http://social.bioware.com/forum/1/topic/74/index/4700291 here]

To edit the lightmap file yourself AFTER exporting it out:

# Render Lightmaps
# Post all to local
# Navigate to My Documents\BioWare\Dragon Age\addins\MODULE\core\override\toolsetexport\LAYOUT
# Find the erroneous lightmap dds
# Perform whatever surgery you deem necessary. I suggest using some sort of noise reduction filter. Ideally removing only "pepper" and not "salt".
# If you have photoshop I suggest creating an action, opening all erroneous dds files and automating the action on all opened files.

Example: lightmap before noise reduction

[[File:Noisylightmap.jpg|border]]
[[File:Noisylightmapdds.jpg|border]]

Example: lightmap after noise reduction

[[File:Noisylightmap2.jpg|border]]
[[File:Noisylightmapdds2.jpg|border]]

=== My custom material does not seem to lightmap ===

Ensure your material is set to static, has a lightmap texture line and has unique textures (diffuse cannot be used as both diffuse and specular), and your object has a second UV layer and meta data. For more information on materials, check Texture tutorial (condensed)

== Credits ==

Thanks to Semper for clearing up some questions I had. !TimelordDC provided the shadows tip. Oh and a couple of bits from CID-78. Also thanks to the guys on the bioware wiki who provided the information I started with.
== Useful links ==
*[[Adding custom level tutorial]] - How to add your own level.
*[[Level Editor Tutorial]] and [[Level tutorial]] - General advises.
[[Category:Tutorials]]

Lighting Tutorial

2022-07-08T11:03:15Z

Ashhawk: Cleaned up and added heading markup to generate a TOC and make it clearer to read

Author: by mikemike37

Please also check out the [[Lighting]] information.

This is only one method of lighting your level - I suggest some experimentation, but given the lengthy lightmapping process, I'm sure you can use these guidelines to help prevent timewasting.

== Okay so I don't really care too much but I want some light. What's the fastest way to do that? ==

To have even and fairly bland lighting throughout your level and at the risk of some unexpected but not strong shadows:

# Create a new room named "Shared Lighting"
# Select the Shared Lighting room and Click Room Properties
# Have every room lit by lights from this source (use Add, click the rooms from the left).
# Insert > New Light
#* Light type: Point Static
#* Affects Characters: True
#* Affects Levels: True
#* Colour: 0.5, 0.5, 0.5
#* Colour Intensity: 0.8
#* Point Radius: 500 or more for larger levels
# Place such that your entire level is about halfway from the light source and its edge and a little way up.
# Copy and paste so you have 4 surrounding the entire level.
# Insert > New Light
#* Light type: Ambient - Baked
#* Colour: 0.5, 0.5, 0.5

== Lighting done "properly" ==

=== Introduction to Lighting Types (baked versus in-game lighting) ===

The most important difference to understand is the difference between baked lighting and "in-game" lighting. In the game, your character is illuminated by lights from various angles... but your character moves, so it follows that the strength of the light reflecting from your character must be calculated on-the-fly. These calculations performed by your graphics processor are pretty intensive, so it makes sense to avoid them where possible and free up your graphics processor for other cool visual stuff, like high poly models and large textures. So how can we reduce this load? using baked lighting.

The principle of baked lighting is as follows: for lights which do not move and for objects which do not move, we can calculate the reflection and save the results for the graphics processor to read, and not have to calculate. In Dragon Age, we do this by lightmapping using baked lights and static props. Everything you place in the level editor (NOT area editor) must necessarily be unable to move in-game.

I'll now explain the order in which I add lights, with an explanation of what I consider to be good practice. I write this with interior levels in mind.

=== Buttons ===

* '''Room Properties:''' allows you to describe to the engine which rooms are visible, are lit by and are connected to each given room.
* '''Render Lightmaps:''' will process all baked lights to the lightmaps. Time-consuming, good for finalising.
* '''Render Lightmaps for selected Chunks or Rooms:''' select only the rooms you want to lightmap. Less time-consuming, good for experimenting.
* '''Display Lightmaps On/Off:''' When enabled, this will show you the lightmap result. Always toggle off then back on to update the lightmap after processing. It will NOT show you "live" lighting, such as static lights. You have to sort of guess what that'll end up like.
* '''View Models Fully Lit:''' gives the same result as ambient at 1, 1, 1 - everything is well-illuminated. Good for moving things about.
* '''Render Light Probes:''' I'll look into this later.

=== Create a "shared lighting" room (interior only) - realtime, characters only ===

Using the method suggested on the builder's wiki, you can have all characters illuminated dimly in all directions in every room by using a "shared lighting" room.

# Create a new room
# Rename the room "Shared Lighting"
# Select the Shared Lighting room
# Click Room Properties
# Have every room lit by lights from this source.

Adding the lights:

# Insert > New Light
#* Light type: Point Static
#* Affects Characters: True
#* Affects Levels: False
#* Colour 0.3, 0.3, 0.3
#* Colour Intensity 0.8
#* Point Radius: 500
# Place such that your entire level is about halfway from the light source and its edge. You may like to place these above the level a little way since light typically comes from above (but not always...)
# Copy and paste so you have 4 surrounding the entire level.

=== Ambient Light - baked, level only ===

By adding this before any "specific" lighting, we can set the tone for the level and build up from there. You only need one ambient in the entire level and it affects all rooms regardless of any other settings.

As far as I can tell, Intensity is NOT used, so you're going entirely on colour here. Vary the colour and brightness to suit taste, but you don't want this to be too strong or you will lose the strength of contrast in your lighting since the dark areas won't be very dark. Below are suggested values.

# Select the Shared Lighting room
# Insert > New Light
#* Light type: Ambient - Baked
#* Colour: 0.2, 0.2, 0.2
#* Position, intensity does not matter at all. Leave at default is fine.

=== Static and animated Lights - realtime, characters and level ===

You should try lightmapping your level at this point (Render Lightmaps) and exporting to try it out in-game. You should have a pretty dark, but visible level throughout.

We now want to add in static and animated lights so that the characters are illuminated by things actually present in the level. With lighting, its a very good idea to start with the strongest lights first. With all of these lights, use Affect Characters: TRUE. Use Affects Level: TRUE sparingly - an object may only receive a maximum of 3 static lights. For this reason, avoid placing lights with an overlapping radius. Multiple static lights occupying the same space is to be avoided strongly.

The strongest lights, generally, will be natural light where you have it - so add light from windows and similar first. Use cool, pale colours (light blues) so as not to wash out the colour of the room.

Next add in "genuine" light sources. By this I mean things which you understand to actually generate light. Torches, fires, glowing stuff. For fires, its nice to use the animated light types. Play with the settings, or try copying from one of the DA levels. Fire generally makes yellow glows, not bright orange.

=== Baked Lights ===

If you've allowed a lot of static lights to illuminate your level, you may only need to add baked lights to things too small to warrant a static light, and to brighten up dark patches. However, you may want to make more extensive use of baked lighting since it allows for a greater control over your lighting by adding many baked lights without impacting the player's performance (since they're all calculated at the lightmapping stage). It also generally makes nicer, softer shadows.

=== Adding shadows where they "shouldn't exist" ===

This tip from !TimelordDC: Let's say you want to build a dark pit or a dark circular area within a big room. Place a model of the appropriate shape (doesn't matter which model) right above the area you want to darken and adjust the model properties to set Export To Game as FALSE and Lightmap as TRUE. Place a light directly above it to cast a strong shadow. Once you render lightmaps, you will see a dark shadow beneath the model but the model won't be present in-game. There is a bit of work to get it just right since the model can cast shadows from other lights too.

You can also darken areas using negative static lights. Experiment with these - you can see their effect in realtime.

=== Light Probes ===

Light Probes are used for reflections. This includes but is not limited to: reflections off of weapons/armour using fresnel and water. Place a Light Probe in each room of an indoor level, or one over each patch of water in an outdoor level. Currently, a bug prevents the light probes from generating more than one image. After Placing, use Render Lightprobes and toggle view lightmaps to ON to see what they look like.

=== "Corruption" Fix ===
Occasionally, the lightmap seems to become "corrupted". If you believe there is a mistake with it that shouldnt be there when you hit process lightmaps, but always is... then its possible you are using "two lightmaps". This is usually caused by having exported your level and then gone back to try and improve the lightmap. There are two ways to fix this:

==== Rename your layout ====

This will force the lightmap to start from scratch, but you will have to change the layout and will end up with a potentially messy set of folders all over the place.

==== Delete all the lightmap files ====
My Documents\BioWare\Dragon Age\Toolset\LvlWorkspace\lightmaps\LAYOUT

My Documents\BioWare\Dragon Age\Toolset\ProbeLightMaps\LAYOUT

My Documents\BioWare\Dragon Age\Toolset\resourcepostintermediatewin32\processed\addins\MODULE\layouts\win32\layouts\LAYOUT

My Documents\BioWare\Dragon Age\Toolset\resourcepostintermediatewin32\processed\addins\MODULE\layouts\win32\modelhierarchies\LAYOUT

My Documents\BioWare\Dragon Age\Toolset\resourcepostintermediatewin32\processed\addins\MODULE\layouts\win32\textures\dds\LAYOUT

(path of your level file)\LAYOUT.erf

(path of your level file)\LAYOUT.bak.erf

C:\DOCUME~1\Mike\LOCALS~1\Temp\DALightmap\LAYOUT (you can use Run... and type %TEMP% and hit OK)

(if you have posted to local) My Documents\BioWare\Dragon Age\addins\MODULE\core\override\toolsetexport\LAYOUT

== Troubleshooting ==

IMPORANT: if you have posted your layout to local, then the lightmap dds files in your override will start conflicting with those in your toolset. ALWAYS remove them whenever you change lighting, otherwise you will see the result of BOTH lightmaps being applied.

=== Nothing I do seems to make a difference in-toolset ===

Ensure you have disabled "view models fully lit" and you have enabled "Display Lightmaps On/Off?". If you have recently remapped, you will need to toggle display lightmaps off then back on again to refresh the display.

If you have posted to local and restarted your toolset, you will need to close your toolset, delete the exported files and restart your toolset.

=== Nothing I do seems to make a difference in-game ===

Check your area file is using the correct name and that it has been exported. Also check that you have "done all local posts" in your level after changing the lightmap.

=== My character in-game is entirely black and I'm getting a warning about shadow maps ===

If you haven't added any static lights, you will get an error saying "no static lights detected. Shadow maps will not be generated" (or similar). Its generally a good idea to have some static lights, since these will illuminate your character.

=== I have dark shapes/symbols over many different models in different ways (corruption) ===

This is caused by a model trying to use a portion of your lightmap that it shouldn't be. This can be caused by having lightmaps in your override and lightmapping a second time. To remove your old lightmaps, delete the exported files in your core/override/toolsetexport. If this doesn't fix, try DeletingLightmapFiles. Finally, if you still get the issue, its a problem with the model you are using - it has a bad lightmap UV unwrap.

Example: dark shapes and squares

[[File:Staticbunching.jpg|border]]

=== I have some kind of corruption on my lightmap throughout an entire room or level ===

Same problem as above, but without the distinctive "shapes". This is much more likely to be because you need to delete the exported lightmaps from your override.

Example: extremely patchy lighting throughout level

[[File:Corruptedshadowmap1.jpg|border]]

Fixed:

[[File:Corruptedshadowmap2.jpg|border]]

=== I have black patterns or triangles identically or similar over many of the same model ===

Some models seem to have a problem with lightmapping. look for a fix here or try using a different model.

Example: fca_floor02_0

[[File:Badmodellightmap.jpg|border]]

=== I have obvious seams between two or more models where they should be seamless ===

This is caused by the fact that one object may receive static light from no more than 3 sources. In the example, I have three tiles. In the first screenshot, I have three blue lights and one red light. The middle tile does not receive the red light at all, and so a seam becomes apparent. The tile closest to the red light is receiving the red light and light from two of the blue lights.

The fix here was to delete two of the blue lights and increase the intensity of the remaining blue light to compensate. Of course, this was a test setup, but the principle remains the same... ensure you have no more than three static lights overlapping ''anywhere'' in your level. Its a good idea to keep this down to just two lights where possible.

Example: four static lights in scene

[[File:BStatic_bunching11111.jpg|border]]

Example: two static lights in scene

[[File:Static_bunching_fixed.jpg|border]]

=== I have one unusual shadow (symmetrical pattern) caused by static lights and it doesn't make sense ===

I am unsure if this was a problem with one particular model and/or the static light I was using, but if you get something like this try lightmapping after moving your lights to a new location.

Example: bad shadow passing through prp_dni_torch03_0 (showing the result only - lights and problematic model are not shown)

[[File:Onebigartifact.jpg|border]]

=== The lights seem to go off or change badly every time I change rooms ===

You need to set up rooms to be visible and receive light from one another. Only adjacent rooms should receive light from one another, but always ensure all rooms which CAN be visible from a room ARE visible. You should also connect rooms.

=== I want to illuminate my room generally without "spotty" lights all over the place but I don't want to increase my ambient lighting ===

Try adding a large light way outside of the room. You run the risk of getting unexpected shadows as the light shines through your walls/ceilings, but apparently you can reduce these by increasing the light size under "soft shadows". I haven't tested this technique.

=== I have lots of tiny black dots all over my lightmaps ===

This problem seems to occur only in small rooms which have a ceiling. There are two solutions: accept the noise and use post-processing noise reduction on it... or take off the ceilings and render them separately.

For taking off the ceilings, please see this thread [http://social.bioware.com/forum/1/topic/74/index/4700291 here]

To edit the lightmap file yourself AFTER exporting it out:

# Render Lightmaps
# Post all to local
# Navigate to My Documents\BioWare\Dragon Age\addins\MODULE\core\override\toolsetexport\LAYOUT
# Find the erroneous lightmap dds
# Perform whatever surgery you deem necessary. I suggest using some sort of noise reduction filter. Ideally removing only "pepper" and not "salt".
# If you have photoshop I suggest creating an action, opening all erroneous dds files and automating the action on all opened files.

Example: lightmap before noise reduction

[[File:Noisylightmap.jpg|border]]

[[File:Noisylightmapdds.jpg|border]]

Example: lightmap after noise reduction

[[File:Noisylightmap2.jpg|border]]

[[File:Noisylightmapdds2.jpg|border]]

=== My custom material does not seem to lightmap ===

Ensure your material is set to static, has a lightmap texture line and has unique textures (diffuse cannot be used as both diffuse and specular), and your object has a second UV layer and meta data. For more information on materials, check Texture tutorial (condensed)

== Credits ==

Thanks to Semper for clearing up some questions I had. !TimelordDC provided the shadows tip. Oh and a couple of bits from CID-78. Also thanks to the guys on the bioware wiki who provided the information I started with.
== Useful links ==
*[[Adding custom level tutorial]] - How to add your own level.
*[[Level Editor Tutorial]] and [[Level tutorial]] - General advises.
[[Category:Tutorials]]

User:Ashhawk

2022-02-01T17:31:16Z

Ashhawk: Created page with " == Projects == *Update dead BSN links *Add useful templates"

== Projects ==
*Update dead BSN links
*Add useful templates

Tutorials

2022-02-01T16:24:52Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

This page lists links to step-by-step tutorials, both on this wiki and on external sites.

==Introductory tutorials ==

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

{|align=right
|{{TutorialRef|<nowiki>Boxes like these contain links,</nowiki>|<nowiki>to topics taking you to further information</nowiki>}}
|-
|
|-
|{{sidebox|
*Boxes like this contain a checklist of important steps.
*They're intended as a reminder and as a navigational aid.
}}
|}

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

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

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

Various small Tutorials, in a unsorted manner.
*[[How-tos]]
*[[VFX Tutorial]]

== Demo module ==

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

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

== Custom content tutorials ==

* [[Adding custom armor tutorial]]
* [[Adding custom level tutorial]]
* [[Adding a new spell tutorial]]
* [[Adding a new weapon type tutorial]]
* [[Adding a custom model to the toolset tutorial]]
* [[Adding custom heraldry to a shield tutorial]]
* [[Adding custom items to custom modules tutorial]]
* [[Adding custom shield tutorial]]
* [[Creating item with note in Codex]]
* [[Creating a custom placeable from a model tutorial]]
* [[Creating recolors of existing items tutorial]]
* [[Customisation of original Dragon age armor]]
* [[Extending GDAs tutorial]]
* [[Overriding and creating tints tutorial]]
* [[Reskinning an item tutorial]]
* [[Usable campaign items tutorial]]
* [[Using DLC areas in your mods tutorial]]
* [[UI Tutorial (draft)]]
* [[Playing custom Player Character]]

== Character generation tutorials ==
*[[Backgrounds tutorial|Background/Origin Tutorial]]
*[[Add A New Class Tutorial]]
*[[High-Level Character Generation]]

== Companion Tutorials ==
*[[Basic follower tutorial]]: covers the basics of adding a follower to party (which has space)
*[[Follower tutorial]]: a more comprehensive tutorial for creating followers (script heavy)
*[[Follower tutorial (alternative)]]: an alternative to the main follower tutorial
*[[User:Satans_karma|Follower tutorial (satans_karma)]]: an alternative to the main follower tutorial
*[[Compatible_Companion_Mod_Creation|Advanced follower tutorial]]: a comprehensive tutorial for creating followers with a focus on compatibility (very script heavy)
*[[Follower_guidelines]] (contains general guidelines and compatibility information)

== Other Tutorials ==
*[[Adding a Location to the Single Player Campaign Tutorial]]
*[[Noob to pro]] (Step by step guide to making a new standalone campaign)
*[[Module Priority Tutorial]] How to set module. Priority for multiple mods with similar files, so they don't interfere
*[[Plot]] Information on configuring plot flags for journal and codex entries

== External Tutorials ==
*[http://dragonagemodding.wordpress.com Beyond Ferelden] has many in-depth tutorials by jwvanderbeck.
*[http://www.youtube.com/watch?v=TwQNRBFLhrE Playable Area and Conversation] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=CaHldJcUTz8 Simple Conversation Cameras] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=QOQJ2heQto4 Cutscene and Trigger] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=szWKgj2ZuXo Custom Level and Room Building] video tutorial by [http://social.bioware.com/64020/ st4rdog].
*[http://www.youtube.com/watch?v=DKJ7F14n8o8 Downloading and Installing the Toolset] video tutorial by [http://social.bioware.com/74287/ DragonAge22].
*[http://www.youtube.com/watch?v=iMPBsulv9xI Creating a Room] video tutorial by [http://social.bioware.com/74287/ DragonAge22].
*[http://www.youtube.com/watch?v=g3kx2CaarHo How to Make an Interior Level with Lighting] video tutorial by [http://social.bioware.com/group/60/ Darkworld Development Team].
*[http://www.youtube.com/watch?v=O6TeZeE1Lc8 Making a Room] video tutorial by BigDrip681.
*[http://social.bioware.com/5339/blog/576/ Custom Player Items In Single Player] by [http://social.bioware.com/5339/ weriK].
*[http://social.bioware.com/5339/blog/651/ The Secret Behind Item Statistics] by [http://social.bioware.com/5339/ weriK].
*[http://social.bioware.com/project/923/ Guide for installing/uninstalling/updating Mods] Beginner Guide to get started with using Mods by [http://social.bioware.com/237411/ Alexspeed].
*[http://www.jezelf.co.uk/tutorials.htm Photoshop Map making tutorials] Credits to Jason Elford, brought to DAT wiki by [http://social.bioware.com/48156/ Arixsus]
*[http://social.bioware.com/project/527/ Video Tutorials by SilentCid] Multiple in-depth video tutorials of the DA Toolset
*[http://www.youtube.com/view_play_list?p=EF29DD1AACEBA92A Qkrch's Video Tutorials] Toolset tutorial complete series for the experienced builder (Spanish & English)
*[http://www.theengineeringguild.co.uk/da-new-campaign-location-tutorial World Editing and Area Creation] Tutorial by [http://social.bioware.com/profile/7848 giskard44] where he walks you through a module creation process for an single player addin.
*[http://social.bioware.com/203442/blog/1352/ Custom Item Materials] by [http://social.bioware.com/203442/ Chains-Gore].
*[http://bg2redux.student.utwente.nl/trac/wiki/TutorialLightmapping Lighting Tutorial with Troubleshooting section] (aimed at beginners)
*[https://youtu.be/_q4mmFMmIK8 How to make a dress with crinoline]
*[https://youtu.be/370D7Lul9tk Skinning tutorial]
*[https://youtu.be/1QMcAX1cDyo Rigging tutorial]
*[https://youtu.be/m8DFXmIGJZc Creating Props using 3ds max]

== See Also ==

*[[Area layouts used in the single player module]]
*[[Compatibility]]
*[[Dragon Age 2]]

{{Languages|Tutorials}}
[[Category:Tutorials]]

Step by Step: Installing the Toolset

2022-02-01T16:22:48Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

== Step by Step: Installing the Toolset ==
The Step by Step series of articles are meant to be a 100% walk through of an activity, complete with pertinent details and screenshots of every step of the process.

 
=== Check Prerequisites ===
Do not attempt to install the toolkit without ensuring you have at least Windows XP with Service Pack 3, Windows Vista, or Windows 7. The SP3 requirement can be overlooked if you're technically savvy but for the smoothest experience I'd recommend installing the whole shebang.

Want to know why not? Check the [http://social.bioware.com/forum/1/topic/8/index/113400 Forums].

 
=== Install Python 2.5 ===
Python 2.5 is required for the light mapping inside the toolkit to function, and it is preferred that it be installed first. ActiveState's ActivePython is the best choice, and is available for free. The latest version as of November 15, 2009 (2009/11/15) is 2.5.4.4 and it can be found [https://www.activestate.com/activepython/downloads/ here].

Caveats:
* There are some who have had issues with the 64 bit version; I personally haven't. You may want to pick up the 32 bit version just in case.
* Install to the default directory to avoid any issues with the toolkit. C:\Python25 is the normal default.

 
=== Toolkit Installation ===
These instructions and screenshots are for v1.0.982.0 of the toolkit. They may or may not apply to later versions.

The toolkit is available from [http://social.bioware.com/toolset.php#downloads Bioware's Community Site]. It's 472Mb.

Double click the executable to install the toolkit. If you have an antivirus scanner installed on your computer don't be surprised if it doesn't pop up right away; the antivirus scanner has to process all 472MB of the executable before it will be allowed to run.

If you have Windows Vista or Windows 7 you'll be prompted by UAC to allow the installer to run. Choose yes if you obtained the toolset from the Bioware site.

 
==== Welcome Screen ====
[[Image:Talonius_Toolkit_Install_Screen_001.png|thumb|left|middle|360px|This is the installer's welcome screen.]] Once the installer has started you'll be greeted with the welcome screen.
Click the '''Next''' button.

 
==== End User License Agreement ====
[[Image:Talonius_Toolkit_Install_Screen_002.png|thumb|left|middle|360px|This screenshot shows the installer's EULA agreement screen.]]

You'll be greeted with the end user license agreement. You're creating content for someone's software using this application; I highly recommend you actually read the license.

Accept the license agreement by selecting '''I accept the terms of the License Agreement''' and click '''Next'''.

 
==== Dragon Age Installation Directory Confirmation ====
[[Image:Talonius_Toolkit_Install_Screen_003.png|thumb|left|middle|360px|This shows the screen confirming the location of Dragon Age on the PC the toolset is being installed on.]]

The third screen is asking you to confirm the installation directory of Dragon Age. The toolset requires Dragon Age to be installed; if the directory shown here isn't correct I would recommend reinstalling the game, then restarting the installation of the toolkit.

If the location is correct click '''Next''' to continue.

 
==== SQL Server 2005 Express Installation ====
[[Image:Talonius_Toolkit_Install_Screen_004.png|thumb|left|middle|360px|This screen shows the configuration options for SQL Server 2005 Express.]]

SQL Server Express is a free version of SQL Server offered by Microsoft. It is a relational database that the toolset uses to store information about the currently installed modules and campaigns. Most of the problems around the installation of the toolkit revolve around the installation of SQL Server Express 2005.

If you have no idea what any of these things mean it is recommended that you leave the default settings as they are.

If you have an existing SQL Server 2005 installation you wish to use uncheck '''Install MS SQL Express 2005 SP3'''. You'll then need to check '''Custom settings:''' and enter in the information for the database you already have.

The installer will attempt to connect to the SQL Server you specify and it will run a series of scripts against the database you provided. You should ensure that SQL Server is running on the appropriate machine and that you have no data you wish to save in the database you selected to install to.

Once the configuration is to your liking click '''Install''' to continue.

 
'''Examples:'''
* My SQL Server 2005 machine is named VORTEX, and it does not have any instances installed on it. The '''database server''' for it would simply be VORTEX. The '''database name''' would remain bw_dragonage_content unless you have a reason to change it.
* My workstation also has a copy of SQL Server 2008 on it with no instances. I could reference this installation one of two ways. The first would be as BRIAN-PC; the other would be by using the period by itself.
* It should be noted that the . in the database server refers to the local machine; this should be replaced by the name of the machine on which your installation of SQL Server resides. The \BWDATOOLSET refers to the database instance on that machine.

 
'''Problems?'''
* Visit the official forums and search there before posting; the most common issues have solutions already posted.
* Check the [[Installation troubleshooting]] page.
* A log file will be created in your Documents folder during the installation. This is good to have handy if you have issues during installation. The file in question is named "Install Dragon Age Toolset.txt".

 
==== Toolkit Installation ====
[[Image:Talonius_Toolkit_Install_Screen_005.png|thumb|left|middle|360px|This screenshot shows the installer as it progresses.]]

The installation will take some time. Grab a drink, use the restroom, put together a playlist for your listening pleasure.

 
==== Toolkit Installation Finished Verification ====
[[Image:Talonius_Toolkit_Install_Screen_006.png|thumb|left|middle|360px|A screenshot of a successful installation.]]

The last item in the window above should be ''Completed''. If there's anything else scroll up in the window until you find the error and copy and paste that error somewhere for safe keeping. Seek help in the forums or on the Internet, and restart the installation process.

Click '''Next''' to continue.

 
==== Toolkit Installation Finished ====
[[Image:Talonius_Toolkit_Install_Screen_007.png|thumb|left|middle|360px|The last screen of the toolkit installation.]]

You're done. Assuming no unexpected errors appeared during the installation process you should be ready to start editing.

Click '''Finish''' to complete the installation.

[[Category:StepByStep]]

Project management suggestions

2022-02-01T16:22:32Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

This page is intended as a collaborative repository for suggestions on how to improve the social site. Create a new section for each specific suggestion or related group of suggestions. Feel free to discuss them to some extent on this page, but bear in mind that discussions should be refactored every once in a while into a summary of the idea - the purpose of this page is to consolidate discussion into a more easily-referenced form.

See [[social site suggestions]] for other subject areas.

== Project "progress" status ==

It is too hard to tell if a project is done or in progress or abandoned.

There is no filter option or way to mark your project as completed and ready for use. It would be nice if projects could be given a completion attribute (i.e. planning, building, alpha testing, beta testing, released, etc).

Given that many players have no interest in pre-release marketing and discussion, search could usefully default to "released". Search for "not released" would also be helpful, if there are to be many status categories as suggested above.

Abandoned projects clutter up the list enormously. Projects should be automatically disabled or flagged if there is no activity in them for some threshold criteria length of time and they remain incomplete/never started.
:I'd throw in that it should be activity from the project owner themselves, since here's a good example of a popular long abandoned project that still has people posting comments all the time - http://social.bioware.com/project/602/. The owner has already so much as said in the comments that they now hate the game and have abandoned it. Yet the project is now more like a petition than anything else I suppose.

We also need a stronger separation between public projects and internal build team discussion. A Work-In-Progress (WIP) category would be one way of doing that. It should allow builders to discuss issues confidentially and share files without cluttering up the public project listings. A team might well need both a public project and a WIP project. WIP is not the same as the various Builder-to-Builder categories currently available, because the latter are for marketing and releases to the wider builder community.

If the WIP category is approved there should be no mechanical constraint on the file types that can be shared there unless there is some major security concern. In addition to the many valid DAO file types builders need to share all sorts of graphics, office documents, html, xml etc so having a defined list is just a problem waiting to happen.

== Other project filter options ==

Advanced Filter Options button. Currently the drop-down boxes for filtering are all independent of one another. If you want to browse in the groups there are 4 lists. Would be nice to have an advanced filtering options button that will pop up a little dialog box where you can make all your selections at once and then say GO!
* Filter or order by rating (e.g. 8+) would be essential (assuming a rating system is introduced) - separate from other order options.
* Filter by sub-category (see below) would be important.
* Filter by language (not all modules will be in English).
* Would be nice to be able to filter out completely all those projects with fewer than X members.
* Would be nice to be able to filter out completely all those projects that haven't had any activity at all (not even downloads) for X days.
* For playable modules, filter by start level.
* I would also like to see the author of the project without opening it up.

When you click on projects the list can only be viewed 10 items at a time, which is way too few.

Redundant filters: Some of the drop down options are not something anybody would be interested in listing them by or are duplicated by others (e.g. popularity? most views? what is the difference between those two?). Ordering by most views is unlikely to generate a significantly different ordering than sorting by last updated or popularity. All the older projects are likely to have more views than the any of the newer ones, so ordering by create date isn't going to be significantly different than ordering by most views. This isn't a major problem, frankly more options are better than fewer, but the ones you really need (which projects are "the best" and which are "not worth the effort", which are done which are still in progress) aren't there.

== Rating projects ==

=== Problems with the current rating system ===

* The modules that have been around the longest will have the most "+" while a brand new awesome module may never get noticed. This encourages builders to do a rush job just so they can be one of the first ones out there. Perhaps a weighted rating system, so that a very large/old mod can sit up their with a brand new smaller mod of equal caliber that just hasn't garnered the high amount of ratings yet.

* Excellent niche offerings are very hard to find. For example, builder assets are never going to get as many approvals as playable modules, because there are more players than builders. Search by category helps up to a point, but ultimately "popular" doesn't always mean "good".

* Provide a checkbox on a project that a host can check when he/she considers the content "done" and ready to be ranked with the others. This would allow you to post work-in-progress downloads to gather feedback, without the concern of getting low ranks because it is not done yet.

* Once you have given a project a "+", there is no way to remove that again, even if you discover later that the project didn't deserve it at all.

=== Variation and changes to the current rating system ===

* Have two ways to rate projects -- one similar to the NWVault's rating system (is it a good idea, do people like it, etc), and another where people could rate the "buggyness" or "stability" or "ease of setup" type things about the project.?

* Or perhaps just a screen with two or three categories to rate that get computed into some overall rating (e.g. Design/Idea 1-10, Stability/Ease of Use 1-10, Something Else 1-10). For me it would be far more useful to be able to filter and sort on these kinds of peer judged criteria than by "most views" or a generic "popularity" with unclear basis.

* Maybe projects need a sex rating system similar to what hollywood does (e.g. G, PG, PG13...XXX).

* Make an adult category. Let's face it, they tend to be some of the first and most abundant mods made on any game (even those without a proper toolset). Sometimes you just don't want to have to look at the index screen shots of all of the "Witches Gone Feral" mods when you're trying to find a mod to fix your crossbow.

* NWVault has a rating system where you give a 0-10 score, but the rating is hidden for ranking purposes until a specific minimum number of people have rated the project. The average number may be meaningless - in NWNvault, an absurdly high percentage of modules have a rating above 9.0, but still the relative ranking is pretty good - a module with a high score and a high download count is probably worth looking at...

* The NWVault rating system is good, but any competent statistician will tell you that the sample size is far too small to make detailed judgements on the results. So, anything voted 9+ is probably good - a very useful thing to know - but being #1 in the rankings rather than #10 is probably meaningless. I'm not sure what the latest research says about these things, but I suspect a slightly simpler system would be better - for example, a scale 1-10 (with no .25 intervals) and no guidelines on what the scores mean. NWVault calculates the average ranking by a complicated algorithm, which is open to troll voting. IMO it would be fairer to rank on the median score. It's useful to see a histogram of the scores, too, e.g. http://proleric.com/phpbb/viewtopic.php?f=15&t=39&start=0&view=viewpoll. Some people dismiss the voting system as a measure of how many friends you have, but I think that's too cynical - as long as you just see it as a way of sorting sheep from goats, and nothing more.

* if you intend to keep a simple voting system. Please give us the ability to remove a "+" and I am also in favore of a "-" button to push junk out of the way.(CID-78)

=== Download counting ===

You cannot update a file without losing the download count - it gets reset back to zero. This would need to be fixed - the ideal solution would be to count the number of people downloading files from the project, but at the very least allow people to update files without losing the download count. As it is, the download count is pointless and actually discourages builders from updating their files.

== Project classification ==

* If a project got incorrectly classified originally, or if a more appropriate category is added later, there is no way to re-classify the project. Allow module owners to change the category of their projects.

* The list of classifications is a mess, with builder-to-builder and builder-to-player categories mixed up. Also, the categories are not well chosen - the NWN modules category is just a pointless waste of space and several categories seem to be missing.
** Add more project categories (areas, scripts, machinima, tutorials, music, and so on)
** Separate builder-to-player content from builder-to-builder content. The biggest hurdle to mod creation is creating levels, so a level category would be particularly useful.
** Separate Work-in-Progress (WIP) content so that a project team can share files and discussion internally. This is not the same as builder-to-builder which is about delivering finished assets to the wider builder community. This category has special privacy needs and can be excluded from searches.

Categories to potentially remove or change:
* NWN module
* It is a bit confusing to have "Dragon Age Addons" as well as "DA Gameplay mods", as to most people those categories overlap. Maybe "campaigns" and "extensions" would be clearer.

* Replace the one-big-list project page with a splash page with links to separate categories. Include an "all mods" button so we can still get to the huge list if we want to. And allow mods to be in more than one category.

The list of project categories, in order, at the time of writing is

* Dragon Age addons
* NWN Modules
* Builder - DA Mods
* Builder - DA Textures
* DA Playable Modules
* Builder - DA Utilities
* Builder - DA VO files
* DA Gameplay Mods
* DA Item/Armor/Weapon Mods
* DA Character Mods

Whether or not these names are final, and even though it may not be all that relevant at the moment, I think the list should be sorted either by category or game, in alphabetical order, and that games only be represented in their short form. E.g.

* ...
* Modules - DA(:O)
* Modules - NWN
* ...
* Textures - DA(:O)
* ...

or

* ...
* DA(:O) - Modules
* DA(:O) - Textures
* DA(:O) - Utilities (what are those anyway?)
* DA(:O) - VO Files
* ...
* NWN - Modules
* ...

It would be worth looking at NWVault categories. Over time, some of them have become meaningless, but sub-categories like RPG, Hack & Slash etc are still useful. Language will be vital information for community modules!

Don't forget the ability to reassign a projects category at any time. especially so that old projects can benefit from new addons.

BioWare could also have a better definition for what belongs in each category and allow people to flag a project that doesn't match the category it was posted in.

=== Alternative approach to classification: tags instead of categories ===

Too many/too unspecific categories can cause similar projects to be categorized differently because they fit under too many categories. I would suggest only a very general level of categorization and leave the specifics to tags. For instance, allow only a single category for game modules but let the author assign Gameplay, Item, and Character (and any other) tags as applicable.

Two things that would definitely have to be considered for such a solution are:

* if the tags are gathered in one global list, some tags will not make any sense whatsoever for certain projects. On the other hand, category exclusive lists seems like a lot of database bloat, and what do you do when the tag(s) you're looking for are not (yet) in the category your project is in?

* if only the author can assign tags, risk of vandalism is greatly reduced, not to say eliminated. Meanwhile, allowing all users to add/remove tags to/from projects greatly increases the likelihood of the average project being more appropriately categorized (tagged).

== Subscribed projects view ==

Under ''View'', add "Subscribed projects" - once I have found projects that are sufficiently interesting to want to follow them, I want to be able to find them again easily. Not everyone knows of http://social.bioware.com/user_bw_projects_subscriptions.php

== Project Comments ==

The comments on Projects is horrible. If they can be made so you can have more than 10 per page and be able to jump to any page in the comments they'd be much better.

Please show the latest comments first. Currently when you go to view comments under a project, it shows the very first comments. It is supposed to show the newest comments first. In the case of a project that has 190 comments, for example, that means one has to click Next Page 19 times!

or simply give us a Last page >> and << First Page on Projects and Groups.

== Captchas in project forums ==

Could we drop having to solve a captcha to post in a project forum? It ties into the problem above about the comment system, which is all the captcha system probably reinforces, and seems kind of pointless given how somebody could just spam up the comments anyway.

== Extend valid file types for projects ==

I created (what is now) a DA Playable Modules project. In addition to uploading the module (DAZIP) file I want to upload the builder-to-builder (DADBDATA) file and the art resources (in this case just LVL files) so that the community could see how we made the module. However the valid types for a DA Playable Modules project do not allow these file types. I am loathe to made another project simply to accommodate these additional file types so I am requesting the project's file types be extended to allow all extensions associated with Dragon Age and ZIP/RAR in addition to the ones already allowed.

See: [http://social.bioware.com/project/334/discussion/586/ Little Red Riding Hood Redux] for the example

== Number of files for projects ==

The limit of 10 files per project isn't appropriate for WIP projects, which will need considerably more.

Can we have a Delete File button, too?

== Project/Group "Discussions" ==

Project and Group discussion areas should be replaced with full "Forum" functionality. The owner of the Group/Project should have the ability to assign Moderators. They should be able to set up Forum Areas, Sticky Posts, Moderate, and do all other things that a Moderator might otherwise be able to do. This would allow for a lot more flexibility and "site stickiness" for groups of people that do things together. Also, any upgrades to the forums functionality could be added to this construct at the same time, thereby eliminating the need for two sets of codebase for what is virtually the same activity.

If this is not possible, the closer we can get, the better.

== Seeking Help ==

BUG - The Browse Groups filter doesn't always work. For example, the Crown of Creation group [http://social.bioware.com/group/97/] is seeking help in four categories, but it only shows up in Browse Groups for the first category, Cinematics.

Also, searching for Friends by proficiency doesn't work at all.

{{EV|216207|[[User:BryanDerksen|BryanDerksen]]}}

[[Category:Feature requests]]

Plot GUID bug

2022-02-01T16:22:06Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

Verison 1.0 of the Dragon Age toolset has a subtle but potentially devastating bug. Put simply, the core plot resources that were included with the toolset had different internal identification numbers (GUIDs) than the versions that were used when the retail version of the game was created. The result is that whenever a core plot file is exported it overrides the plot in the preinstalled main campaign, and then none of the other resources in the game are able to reference it any more. The game's scripts and conversations are unable to determine the state of the affected plots, and are unable to update the state of the plot.

'''Version 1.01 of the toolset corrects this bug. See [[database migration]] for information on how to bring your content forward into the new corrected database.'''

== Symptoms ==

The resulting symptoms are many and varied, depending on where you are in the game and which core plot files have been exported. The most common symptoms include: Party Camp being empty (a result of the plot that tracks which party members have joined you being inaccessible), character generation failing (many options you choose during character generation are recorded in plots that are commonly referenced throughout the game), and party member approval ceasing to update properly.

== How to repair your game ==

The first thing you'll need to do is to remove the faulty exported plot files from your core override directory. You will find them here:

: My Documents\Bioware\Dragon Age\packages\core\override

Delete the contents of this directory. Once they're gone the game will revert back to using the resources that were originally included with the retail version.

If you have saved your game between exporting those core resources and now, the savegame will have faulty plot ID numbers recorded in it and remain broken. The savegame can be repaired manually but it will take a bit more work; if you've only lost a few hours of gameplay it may be simplest to just go back to a previous save and work from there.

Manual repair involves opening the savegame's .das file in the toolset; it is a [[GFF]]-formatted file and will be opened in the GFF editor. You'll need to find the plots' values and correct them.

== How to repair the toolset's database ==

You can fix some of the plot files by running the following SQL command on your toolset's database.

<pre>
UPDATE t_Plot SET GUID = '1c5a23c1-30e5-488a-bc18-a4163ebab35b' WHERE GUID = '1d9f7c93-cd25-4d2b-ad40-570702940982'
UPDATE t_Plot SET GUID = 'c9736a91-f424-4075-8e57-0d9ecd796597' WHERE GUID = '4f2c2ef2-3f00-4c4a-a0d1-d89f60f17e76'
UPDATE t_Plot SET GUID = '64f06db1-ed4b-49f1-8df3-26a0b1c2d06c' WHERE GUID = '244aa66e-e965-4340-9a92-247e46aaa0de'
UPDATE t_Plot SET GUID = '25bc6f5e-8da8-4793-8245-071233433332' WHERE GUID = '2aa159b2-a22e-4efa-aa25-590fa07e7a02'
UPDATE t_Plot SET GUID = '840c666e-a1fe-48cb-a260-ab1fe42fcfa7' WHERE GUID = 'caab223e-bb42-4b97-b984-0e619079470c'
UPDATE t_Plot SET GUID = 'be2ab95b-dd97-4d14-8907-4134675ebbbd' WHERE GUID = '0d7bc736-4f62-40bb-9559-ceab38410f67'
UPDATE t_Plot SET GUID = 'e8cebfa6-eb23-45eb-b704-df06d794c803' WHERE GUID = '10b213fb-92a5-4b52-bd1c-5f630a3499d5'
UPDATE t_Plot SET GUID = '1fd3a44c-147d-4af3-b5ee-7f62707359ff' WHERE GUID = '6195c7c8-385f-415a-beec-3a642a8900ab'
UPDATE t_Plot SET GUID = 'e8e833ac-06c0-4bf2-a326-1a7937542d75' WHERE GUID = 'b02a8c69-1126-43c9-af5f-0274b28ae773'
UPDATE t_Plot SET GUID = '02f47300-3c81-44d0-83b7-69186b7d6813' WHERE GUID = 'bf9a4701-e284-4a4b-bc14-32b4ce46753d'
UPDATE t_Plot SET GUID = 'b0b1de08-0c77-4706-bb5e-c49fa70756b5' WHERE GUID = '7783c5ca-49bf-4fa0-9dde-c696a6e1cde3'
UPDATE t_Plot SET GUID = '52901f57-0994-4f2f-86fd-b61793ba6b14' WHERE GUID = 'e41b7996-49bb-4a69-9f89-ea48049d4015'
UPDATE t_Plot SET GUID = 'ee97cff0-12d3-4c49-a774-13140d991475' WHERE GUID = 'c6fd6f4e-f99f-488f-b5e6-9bc2e92b2634'
UPDATE t_Plot SET GUID = '68f1b23e-b3ea-42f5-b363-abe7feb86a50' WHERE GUID = '83147f27-9833-42c1-b59f-95c232575c91'
UPDATE t_Plot SET GUID = '69fa27e2-5b81-420a-b040-f7885531a408' WHERE GUID = 'a16ccbd9-4842-4eae-be75-166a26e8c1c2'
UPDATE t_Plot SET GUID = 'f2ebb79c-8ef1-42ad-91dc-9e2d1bea74e2' WHERE GUID = '621e860f-c6c7-4659-b5ad-790071651593'
UPDATE t_Plot SET GUID = '296ed10d-de48-4602-b19f-9c6c3fc30611' WHERE GUID = '3201f04f-842a-4dba-b04c-6eda959db514'
UPDATE t_Plot SET GUID = '1820f284-3fc3-4b59-97a8-8f0113161f6c' WHERE GUID = 'ebb20b7c-9274-4cb1-af76-5a8abbf06b68'
UPDATE t_Plot SET GUID = 'f1722d10-291a-4474-bbd2-613033c343fd' WHERE GUID = '3f3ad0ce-6808-4cf9-9b6c-4c185eb93099'
UPDATE t_Plot SET GUID = '1c8fb9a0-415d-477b-b7ec-ae455efcd403' WHERE GUID = '0df43f85-e145-417c-9eba-f6d27399aed7'
UPDATE t_Plot SET GUID = '7d6c7fa8-d644-4111-a4c5-ce642e01e7f0' WHERE GUID = '29a292ca-f492-40cf-9e88-e09acb6f66f5'
</pre>

Note that we haven't verified that this will catch all of the resources that were affected, so you should still take care to empty your core override directory when playing the main campaign if you want to be sure nothing else will break.

A new version of the toolset is being worked on that will include a repaired core database, so you may prefer instead to just wait a few days for it to come out.

For a preview of the corrected core database, apply to join the group http://social.bioware.com/group/721/ and you'll be able to download a backup of it.

== How did this happen? ==

The root cause of the problem was a subtle flaw in how the toolset handled the [[builder to builder]] process for plot files. The builder to builder output files included the plot's GUID in them, but when the builder to builder file is loaded the toolset ignores the recorded GUID and generates a new random GUID for the plot file as if it had been newly created from scratch.

When the toolset's database was prepared for inclusion in the toolset installer, it was first created as a blank database and then the game's core resources were imported into it using the builder to builder process. This is where the GUIDs went out of synch. The problem wasn't caught in subsequent QA since the focus of testing was on whether the toolset was capable of exporting a playable version of the demo module, as the main campaign's resources weren't included. The toolset is capable of doing that just fine since there's no preexisting demo module resources for the exported plot files to have incompatibilities with.

== Forum thread ==

The problem was worked out in this thread on the toolset forum: http://social.bioware.com/forum/1/topic/8/index/114380

[[Category:Closed bugs]]

On NPC Mod Creation and Compatibility, while being the least intrusive to core game resources/ru

2022-02-01T16:21:45Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

The purpose of this wiki is to help the community tackle one of the most important problems we face: compatibility between all our mods, in particular those mods that introduce NPC followers.

I'll share with you my approach to handling companions, based on what I have done with my mod, [http://social.bioware.com/project/3152/ Quests and Legends], my experiments and experience. My goal has always been to be the least intrusive to the game core resources (meaning don't change them at all), while having the companion behave appropriately in most parts of the game.

What I'll talk about here works for Patch 1.02, but after some testing, it seems to be working fine also for those with Awakening and/or even Patch 1.03. So there's something going on with the flags probably of Patch 1.04 (they changed from these below?). This patch has always broken my game when I installed it so I don't know what the problem is there.

I've opened a discussion thread [http://social.bioware.com/project/3152/discussion/2722/ here]. Please join in with your questions/comments/suggestions.

Everything you see below is done WITHOUT changing game resources. Let us begin.

=Understanding the game mechanics and the module event script=

We first need to discuss how the game makes use of scripts, and in particular our module event scripts (every mod has one). Everytime something happens in the game, e.g., you open or close the inventory, talents, skills, or world map gui, all the module event scripts you have installed are fire and processed (probably in the order the mods where installed) as well as the core game scripts (typically these are processed first).

So if we want to capture the behavior of our NPC follower or a major event of the game it can be done here, e.g., the PC selected or dropped the follower in the partypicker, you begin travel, or the PC just finished talking to everyone at the gates in the climax, or the game is over and we're at the slideshow.

This game structure is indeed brilliant since it allows the main game and all mods installed to handle and process the same event, say EVENT_TYPE_BEGIN_TRAVEL or EVENT_TYPE_MODULE_HANDLE_GIFT or EVENT_TYPE_WORLD_MAP_CLOSED and so forth.

=What we can't and can do=

The only major resource we have to change is the partypicker, otherwise our NPC's won't show up. There is a way around this(item 4 below).

If you want your NPC to interject in the middle of a major dialog, that dialog resource has to be changed (I can't see any way around this one).

The thing to keep in mind is that every time something happens in the game, certain flags from core game resources are set. We can capture when these are set and continue the process appropriately.

In this way, I'll show you how '''we can do''' the following (I've done these for my mod Valeria, WITHOUT changing any core game resources, I'll use her as a reference):

1) Valeria banters with the party randomly WITHOUT changing any original game scripts.

2) Valeria accepts specific gifts WITHOUT changing the game scripts.

3) Valeria is in a nightmare area WITHOUT changing the game scripts.

4) Valeria has a dialog option to eliminate problems with partypicker compatibility. If she doesn't show up in the partypicker she can still be picked up or sent back to camp.

5) Valeria has her own dialog after major cutscenes (where appropriate) of the game WITHOUT changing resources of the game.

6) Valeria appears in all camps (basic camp, Arl Eamon's estates, post coronation), most cutscenes from the original game and at the city gates WITHOUT changing resources of the game.

7) Valeria behaves appropriately if the PC gets captured WITHOUT changing resources of the game.

8) Slideshow post coronation WITHOUT changing the resources of the game.

Everything on this wiki is currently written in such a way that only item 2, requires further modifications to make the scripts disjoint, so we can all use it(should you choose to) without conflicts and bugs.

General Note: The dynamic stage acl_1p is used in most dialogs you see below. Remember to check the "At current location" tick box. Actor1 should be PLAYER, Actor2 should be owner.

=What do we need?=

Well, basic knowledge of the toolset and scripting.

a) The NPC mod event handler, say "valeria_event_handler". The companion Valeria is given the tag, "valeria_npc"

b) A plot to hold all our NPC flags, call it "valeria_npc_hire". In the handler we should have the include:

'''#include "plt_valeria_npc_hire"'''

c) We need the following basic FLAGS: PARTY_VALERIA_IN_PARTY, PARTY_VALERIA_JOINED, VALERIA_CHECK_RUNIT

These are there to handle Valeria(is she in party?, has she joined? do we need to run the script? it has to be done if we're in a camp site. you'll see what script)

d) Other flags to set when needed: VALERIA_WYNNE_KILLED, VALERIA_RESPONSE_TO_BAD, VALERIA_ENTER_FADE, VALERIA_HAS_NIGHTMARE_A, VALERIA_HAS_NIGHTMARE_B, VALERIA_HAS_NIGHTMARE_C, VALERIA_SLOTH_DEMON_ATTACKS, VALERIA_SLOTH_DEMON_DEFEATED, VALERIA_WYNNE_KILLED_AT_CULLEN, VALERIA_DEN_CAPTURED_PC_CAPTURED, VALERIA_CLI_MAIN_PC_FINISHED_SETTING_FINAL_PARTY, VALERIA_EPI_JUMP_TO_SLIDE_SHOW, VALERIA_FIGHTING_ARCHDEMON

If you drop the valeria_ prefix (FOR YOUR MOD USE A DIFFERENT PREFIX EVERYWHERE) you'll recognize some flags from the original game. Everytime those are set, we'll need to set a corresponding flag in our NPC plot, so we run things only once.

I'll tell you which plots from the main game we need depending on what we're trying to do.

=Basic structure of the module event handler=
<dascript>
//core includes here

//core plot includes

//valeria function, plots etc, includes

#include "plt_valeria_npc_hire"

//constant definitions here

//function definitions here

(all this part 1)

void main()
{
object oPC = GetHero(),me=OBJECT_SELF,ohire;
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
//function calls here, other important checks (part 2)
//capture events
switch(nEventType)
{
.....(part 3)
}
}

//functions here (part 4)
</dascript>
For what follows, I'll break the event script into four parts for quick reference: Includes, (Main) Body, (Event) Handling, Functions

=Capturing Main Campaign Event/Flag Changes, the function check_plot_changed()=

The next script can be placed in the event handler, and allows us to capture and process main plot changes.

I'll do this structure a first time here

In 'includes' add:

<dascript>void check_plot_changed(object oVal);</dascript>

In 'body' add:

<dascript>
...
object oVal=UT_GetNearestObjectByTag(oPC,"valeria_npc");
...

check_plot_changed(oVal);
...
</dascript>

In 'functions' add:

<dascript>
//check if plot flags changed and act appropriately

void check_plot_changed(object oVal)
{
object oPC=GetHero(); //if Valeria has not joined return
//leave some room here for the slideshow script addition
//it has to go above this check, otherwise if you don't pick her up
//the script won't fire and the appropriate slides won't be shown
if (!WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_JOINED))
return;
//every other addition to this function should be made below this check
...
//here depending on which core flag changed, act appropriately
...

}
</dascript>

We will be changing this function appropriately below, depending on what we wish to do.

=Potential Disadvantage (not certain, it might cause lag in slow systems)=

Now that we know how the handlers behave (from mods and the core game) we need to discuss the possible problems with this approach.

It all comes down to lag (although I don't really experience it but I put it here for completeness).

Whenever we intercept an event in Event handling, all the commands in the event handler Body will fire. That might slow some low end systems down.

=Random banters=

==What we need==
A dialog resource, say "valeria_random_banter.dlg", a script "valeria_random_banters.nss" and a plot "valeria_random_banters"

You will notice that they are done in order of appearance in the .dlg file. Of course one can change that. Meaning if Alistair is in, all his banters will go through first, then Moriggan, then Leliana ,etc, the way I had them in my file. To change that you can add a random chance to see if you initiate dialog with the party member.(see the script below, it is trivial)

==valeria_random_banters.nss==
First create this script. You can see what flags you need in plt_valeria_random_banters below (basically a flag for each companion you want Valeria to banter with). Alternatively, you can use the core plots to check who is in the party, but I find this more efficient, since we got full control over the script and plot resource.

//file valeria_random_banters.nss
<dascript>
#include "wrappers_h"

#include "plt_valeria_random_banter"

void main()
{
WR_SetPlotFlag(PLT_VALERIA_RANDOM_BANTER, ALISTAIR_IN_PARTY, FALSE);
WR_SetPlotFlag(PLT_VALERIA_RANDOM_BANTER, MORRIGAN_IN_PARTY, FALSE);
WR_SetPlotFlag(PLT_VALERIA_RANDOM_BANTER, LELIANA_IN_PARTY, FALSE);
WR_SetPlotFlag(PLT_VALERIA_RANDOM_BANTER, WYNNE_IN_PARTY, FALSE);
WR_SetPlotFlag(PLT_VALERIA_RANDOM_BANTER, ZEVRAN_IN_PARTY, FALSE);
WR_SetPlotFlag(PLT_VALERIA_RANDOM_BANTER, DOG_IN_PARTY, FALSE);
object [] arParty = GetPartyList(GetHero());
int i;
int nSize = GetArraySize(arParty);
int which=Random(nSize)+1;
if(GetTag(arParty[which]) == "gen00fl_alistair")
WR_SetPlotFlag(PLT_VALERIA_RANDOM_BANTER, ALISTAIR_IN_PARTY, TRUE);
if(GetTag(arParty[which]) == "gen00fl_morrigan")
WR_SetPlotFlag(PLT_VALERIA_RANDOM_BANTER, MORRIGAN_IN_PARTY, TRUE);
if(GetTag(arParty[which]) == "gen00fl_leliana")
WR_SetPlotFlag(PLT_VALERIA_RANDOM_BANTER, LELIANA_IN_PARTY, TRUE);
if(GetTag(arParty[which]) == "gen00fl_wynne")
WR_SetPlotFlag(PLT_VALERIA_RANDOM_BANTER, WYNNE_IN_PARTY, TRUE);
if(GetTag(arParty[which]) == "gen00fl_zevran")
WR_SetPlotFlag(PLT_VALERIA_RANDOM_BANTER, ZEVRAN_IN_PARTY, TRUE);
if(GetTag(arParty[which]) == "gen00fl_dog")
WR_SetPlotFlag(PLT_VALERIA_RANDOM_BANTER, DOG_IN_PARTY, TRUE);
}

//to add a random chance for the party member to banter with Valeria you can simply change
...
if(GetTag(arParty[which]) == "gen00fl_dog" && Random(10)==1)
WR_SetPlotFlag(PLT_VALERIA_RANDOM_BANTER, DOG_IN_PARTY, TRUE);
...
</dascript>

This way it won't circle through all the banters of Alistair, then Morrigan's etc, but it will skip them with some probability (90%). This means the probability of an actual banter starting is .0025*.1=.00025 (1/400=.0025).

==Changes in valeria_event_handler==
I'll do this structure again(last time), the rest will be the same:

In 'includes' add:

<dascript>void valeria_banter();</dascript>

In 'body' add:

<dascript>
//valeria banter: run this only if valeria is in active party
if (WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY))
valeria_banter();
</dascript>

In 'functions' add:

<dascript>
void valeria_banter()
{
if(Random(400)!=1)//1 in 400 chance to start banter
return;
if(GetCombatState(GetHero()))//don't start if in combat
return;
object [] arParty = GetPartyList(GetHero());
int i;
int nSize = GetArraySize(arParty);
if(nSize<=2)//if only valeria and the PC no banter
return;
for(i=0;i<nSize;i++)
if(!ClearAmbientDialogs(arParty[i]))
return;
object oval=UT_GetNearestObjectByTag(GetHero(),"valeria_npc");
UT_Talk(oval,GetHero(),R"valeria_random_banter.dlg");
}
</dascript>

==Structure of the file valeria_random_banter.dlg==
Everything should be set to AMBIENT. First notice where we call the random_banter_script.

[[image:Banters1.JPG]]

Now, notice how we structure all the npc's we want Valeria to banter with. First is Alistair, if he's in the party, and so forth.

[[image:Banters2.JPG]]

Second is Morrigan and so forth.

[[image:Banters5.JPG]]

Notice that once a banter starts, it will never be shown again.

[[image:Banters3.JPG]]

An example with 3 NPC's (this is a dog banter with Valeria, and Zevran, if he's in the party(notice the condition C, using the valeria_random_banters flag) he joins in).

[[image:Banters4.JPG]]

=End game Slideshow=

==What we need==
The core plot file epipt_main, contains the variable EPI_JUMP_TO_SLIDE_SHOW, which is set once you talk to the guard post-coronation at the doors and the end slideshow begins.

Add the variable VALERIA_EPI_JUMP_TO_SLIDE_SHOW in the companion VALERIA_NPC_HIRE plot, so we only do this once. We also need the dlg file with the slide dialog and pretty pictures. I use my main dialog file for this, you don't have to: valeria_npc.dlg

To implement:

In includes, add:

<dascript>#include "plt_epipt_main"</dascript>

In the function check_plot_changed() add:

<dascript>
...
//valeria in the epilogue
if (WR_GetPlotFlag(PLT_EPIPT_MAIN,EPI_JUMP_TO_SLIDE_SHOW) && !WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_EPI_JUMP_TO_SLIDE_SHOW))
{
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_EPI_JUMP_TO_SLIDE_SHOW,TRUE);
BeginSlideshow(R"valeria_npc.dlg");
}
//it has to go above this check, otherwise if you don't pick her up
//the script won't fire and the appropriate slides won't be shown
if (!WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_JOINED))
return;

...
</dascript>

==Structure of the file valeria_npc.dlg==

Note the check to see if the end game slides have run. I'm assuming the game ends after, so this runs only once and it's done. If another mod has the same setup (with different names for plots, flags etc) that mod script should run and continue the slideshow until the bioware credits run.

[[image:Slideshow1.JPG]]

Now display the appropriate text and picture (it is set on the slideshow tab) depending on which flags from the companion mod are true (depending on whether the PC helped the companion and so forth)

[[image:Slideshow2.JPG]]

=Valeria at the gates in the climax=
In the climax, you get a last chance to switch your party, where everyone parades in front of you. Well... the right behavior is to first talk to Riordan, he opens the partypicker, you may choose whom you want and then the parade begins.

Once you close the partypicker, Valeria will speak before/or after everyone else is done, so it runs smoothly. Now since many mods might skrew up the partypicker (by not including certain chars), you might have Valeria not showing up. At this stage you won't be allowed to use the dialog option anymore, to get her to join.

You could be intrusive here and force her in the partypicker, but if everyone does it we're in trouble. So I don't recommend it (I did finally implement it this way recently). But, it is best to handle partypicker compatibility by including all waypoints for all NPC's in the char_stage.

==What we need==

The plot clipt_main contains the important flag CLI_MAIN_PC_FINISHED_SETTING_FINAL_PARTY, and as it says, it becomes true when the PC is done setting the final party. So, create in the VALERIA_NPC_HIRE plot the flag VALERIA_CLI_MAIN_PC_FINISHED_SETTING_FINAL_PARTY, so we do this only once.

To implement:

In includes, add:

<dascript>#include "plt_clipt_main"</dascript>

In the function check_plot_changed() add:

<dascript>
//valeria at the gates
if (WR_GetPlotFlag(PLT_CLIPT_MAIN,CLI_MAIN_PC_FINISHED_SETTING_FINAL_PARTY) && !WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_CLI_MAIN_PC_FINISHED_SETTING_FINAL_PARTY))
{
//the next 4 lines takes care of her, regardless of whether you added
//her to the party. this way she will show up when your companions
//defend the gate, choose another location of course
location ValeriaLoc;
object curArea=GetArea(oPC);
ValeriaLoc=Location(curArea, Vector(123.24, 717.48, 0.0), -64.92);
AddCommand(oVal, CommandJumpToLocation(ValeriaLoc));

WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_CLI_MAIN_PC_FINISHED_SETTING_FINAL_PARTY,TRUE);
if(WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY))
{
//this flag is important for the slideshow at the end
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_FIGHTING_ARCHDEMON,TRUE);
WR_SetFollowerState(oVal, FOLLOWER_STATE_ACTIVE);
SetLocalInt(oVal, CREATURE_REWARD_FLAGS, 0); //Allows the follower to gain XP
}
if(!WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY))
{
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_FIGHTING_ARCHDEMON,FALSE);
WR_SetFollowerState(oVal, FOLLOWER_STATE_AVAILABLE);
}
SetObjectActive(oVal,1);
UT_Talk(oVal,oPC);
}
</dascript>

==Changing the Valeria dialog appropriately: valeria_npc.dlg==
Use the flag here, and depending on whether the PC added Valeria to the party, follow a different path.

[[image:Gates1.JPG]]

She complains if she wasn't selected to fight the archdemon, and she has every right.

[[image:Gates2.JPG]]

=Valeria initiates dialog at any point we feel like. Example: Killing Wynne(NOOO!!!)=

I love this char, no-one should ever kill her, but if they do the char should lose approval unless it is that b... Morrigan, or Zevran etc.

==What we need==

Wynne could die in two places in the Circle: when you first pick her up or at Cullen.

The plot CIR000PT_MAIN contains the two important flags for this: WYNNE_KILLED and WYNNE_KILLED_AT_CULLEN. So, create in the VALERIA_NPC_HIRE plot the flags VALERIA_WYNNE_KILLED and VALERIA_WYNNE_KILLED_AT_CULLEN, so we do this only once.

To implement:

In includes, add:

<dascript>#include "plt_cir000pt_main"</dascript>

In the function check_plot_changed() add:

<dascript>
//fighting wynne
if (WR_GetPlotFlag(PLT_CIR000PT_MAIN,WYNNE_KILLED) && !WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_WYNNE_KILLED))
{
if(WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY))
{
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_RESPONSE_TO_BAD,TRUE);
AdjustFollowerApproval(oVal,-10,TRUE);
UT_Talk(oVal,oPC);
valeria_approval();
}
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_WYNNE_KILLED,TRUE);
}
//fighting wynne
if (WR_GetPlotFlag(PLT_CIR000PT_MAIN,WYNNE_KILLED_AT_CULLEN) && !WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_WYNNE_KILLED_AT_CULLEN))
{
if(WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY))
{
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_RESPONSE_TO_BAD,TRUE);
AdjustFollowerApproval(oVal,-10,TRUE);
UT_Talk(oVal,oPC);
valeria_approval();
}
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_WYNNE_KILLED_AT_CULLEN,TRUE);
}
</dascript>

The flag: VALERIA_RESPONSE_TO_BAD can be used in valeria_npc.dlg as shown below. The function valeria_approval() is explained in the gift handling section.

==Changes in valeria_npc.dlg==
Use the flag VALERIA_RESPONSE_TO_BAD, first to enter the bad reaction node in the dialog.

[[image:wynne1.JPG]]

Reset the flag

[[image:wynne2.JPG]]

Depending on which situation we're in display the appropriate node (once per game). Showing what happens when Wynne is killed when first meeting her. But you should never do that...

[[image:wynne3.JPG]]

=Valeria's behavior when the PC is captured(while saving Anora)=
While saving Anora, you might end up fighting Sir Cauthrien (or just surrender). If you lose you get captured and sent to prison. Valeria must be removed from the party otherwise she'll still be following the PC around. She cannot be chosen to go save the PC without changing the game resources, unless you capture it after the initial selection is done. Haven't done it but I'm guessing it could be done if you find the right flag.

==What we need==

The plot DENPT_CAPTURED contains the important flag for this: DEN_CAPTURED_PC_CAPTURED. So, create in the VALERIA_NPC_HIRE plot the flag VALERIA_DEN_CAPTURED_PC_CAPTURED, so we do this only once.

To implement:

In includes, add:

<dascript>#include "plt_denpt_captured"</dascript>

In the function check_plot_changed() add:

<dascript>
//pc captured by cauthrien
if (WR_GetPlotFlag(PLT_DENPT_CAPTURED,DEN_CAPTURED_PC_CAPTURED) && !WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_DEN_CAPTURED_PC_CAPTURED))
{
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_DEN_CAPTURED_PC_CAPTURED,TRUE);
if(WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY))
{
WR_SetFollowerState(oVal, FOLLOWER_STATE_AVAILABLE);
}
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY, FALSE);
}
</dascript>

=Valeria's behavior at camps=

There are four main areas, where upon entering, Valeria has to behave accordingly, without changing the game scripts.
These are: the usual camp(tag=cam100ar_camp_plains, the second time you enter it, it's the same area thereafter), eamon's estate (tag=den211ar_arl_eamon_estate_1), eamon's castle at redcliffe (tag=cli300ar_redcliffe_castle), and post coronation (tag=epi300ar_post_coronation). When you test this: To make sure these changes in your companion's behavior work, you have to go to a save game just before you first pick them up, otherwise the flags won't be set. See the joining script for Valeria.

==What we need==

First add the flag VALERIA_CHECK_RUNIT in the companion plot VALERIA_NPC_HIRE. This one will allow us to know when to run the script to remove Valeria from the active party and move her to her right place, when we enter any of theses areas.

We also need a function in the valeria_event_handler, call it, Handle_Valeria_In_Camp.

To implement:

In includes, add:

<dascript>...
void Handle_Valeria_In_Camp(object curArea);
...</dascript>

In the body, add:

<dascript>
...
object curArea=GetArea(oPC);
object oArea = GetObjectByTag("cam100ar_camp_plains");
//valeria in camp
object oVal=UT_GetNearestObjectByTag(oPC,"valeria_npc");
if (GetTag(curArea)!="cam100ar_camp_plains" && GetTag(curArea)!="den211ar_arl_eamon_estate_1" && GetTag(curArea)!="cli300ar_redcliffe_castle" && GetTag(curArea)!="epi300ar_post_coronation" && WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_JOINED))
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, VALERIA_CHECK_RUNIT,TRUE);
int runit=WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE, VALERIA_CHECK_RUNIT);
if (runit && (GetTag(curArea)=="cam100ar_camp_plains" || GetTag(curArea)=="den211ar_arl_eamon_estate_1" || GetTag(curArea)=="cli300ar_redcliffe_castle" || GetTag(curArea)=="epi300ar_post_coronation") && WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_JOINED))
Handle_Valeria_In_Camp(curArea);
...
</dascript>

==Module Events we need to capture==

The module events: EVENT_TYPE_WORLD_MAP_CLOSED, EVENT_TYPE_PARTYMEMBER_ADDED, EVENT_TYPE_MODULE_GETCHARSTAGE(change the partypicker), EVENT_TYPE_PARTYMEMBER_DROPPED, are important for handling Valeria's behavior. The checks and ifs you see below essentially capture all the possible actions by the PC and make Valeria act accordingly, e.g., go open the worldmap in camp(the partypicker pops up), if canceled the map, put valeria back in place and out of the party, and so forth. These things are done automatically by core game scripts (like camp_functions_h) and mods that modify them. We don't change anything with this approach.

Begin.
In Event Handling add:

<dascript>
...
//world map was closed and valeria was either chosen or not from the partypicker, she has to be taken care of since we're still in camp or we moved to another area.

case EVENT_TYPE_WORLD_MAP_CLOSED:
{
int nCloseType = GetEventInteger(ev, 0);
object oVal=UT_GetNearestObjectByTag(oPC,"valeria_npc");
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, VALERIA_CHECK_RUNIT,TRUE);
if (GetTag(curArea)==GetTag(oArea) && WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_JOINED) && WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY))
{
if (!nCloseType)//0 canceled, 1 means selected a pin
{
SetFollowerState(oVal, FOLLOWER_STATE_AVAILABLE);
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY, FALSE);
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, VALERIA_CHECK_RUNIT,TRUE);
}
else
{
//don't run the camp script for valeria now, set runit=0;

SetLocalInt(oVal, CREATURE_REWARD_FLAGS, 0); //Allows the follower to gain XP
SetLocalInt(oVal, AMBIENT_SYSTEM_STATE, 0);
SetFollowerState(oVal, FOLLOWER_STATE_ACTIVE); //Adds follower to the active party
AddCommand(oVal, CommandJumpToLocation(GetLocation(GetHero()))); //Ensures follower appears at PC's location.
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, VALERIA_CHECK_RUNIT,FALSE);
}
}
break;
}

//valeria was chosen from the partypicker

case EVENT_TYPE_PARTYMEMBER_ADDED:
{
object oFollower = GetEventObject(ev, 0);
if (GetTag(oFollower) == "valeria_npc")
{
SetImmortal(oFollower,0);
SetLocalInt(oFollower, CREATURE_REWARD_FLAGS, 0); //Allows the follower to gain XP
SetLocalInt(oFollower, AMBIENT_SYSTEM_STATE, 0);
SetFollowerState(oFollower, FOLLOWER_STATE_ACTIVE); //Adds follower to the active party
SetObjectActive(oFollower,1);
AddCommand(oFollower, CommandJumpToLocation(GetLocation(GetHero()))); //Ensures follower appears at PC's location.
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY, TRUE);
}
break;
}

//here we have dropped valeria from the party, using the partypicker

case EVENT_TYPE_PARTYMEMBER_DROPPED:
{
object oFollower = GetEventObject(ev, 0);

if (GetTag(oFollower) == "valeria_npc")
{
SetImmortal(oFollower,1);
SetFollowerState(oFollower, FOLLOWER_STATE_AVAILABLE); //Adds follower to the active party

WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY, FALSE);
}
break;

}

//here we change the partypicker to valeria_char_stage

case EVENT_TYPE_MODULE_GETCHARSTAGE:
{
SetPartyPickerStage("valeria_char_stage", "partypicker");
break;
}
</dascript>

==The Handle_Valeria_In_Camp script==

Here's the function to take care of Valeria's behavior appropriately. Use different locations for your companions of course.

<dascript>
void Handle_Valeria_In_Camp(object curArea)
{
object oPC=GetHero();

//spawn valeria in camp if she's joined
object oVal=UT_GetNearestObjectByTag(oPC,"valeria_npc");
location ValeriaLoc;

if(GetTag(curArea)=="cam100ar_camp_plains")
ValeriaLoc=Location(curArea, Vector(135.85, 123.18, -0.08), -71.33);

if(GetTag(curArea)=="den211ar_arl_eamon_estate_1")
ValeriaLoc=Location(curArea, Vector(28.1, 4.75, 0.0), 176.33);

if(GetTag(curArea)=="cli300ar_redcliffe_castle")
ValeriaLoc=Location(curArea, Vector(2.56,-14.84, 0.0), -130.38);

if(GetTag(curArea)=="epi300ar_post_coronation")
ValeriaLoc=Location(curArea, Vector(15.73,4.3, 0.0), 13.16);

if(!IsObjectValid(oVal))
{
oVal=CreateObject(OBJECT_TYPE_CREATURE, R"valeria_npc.utc", ValeriaLoc);
}
else
{
SetObjectActive(oVal,1);
AddCommand(oVal, CommandJumpToLocation(ValeriaLoc));
}
SetFollowerState(oVal, FOLLOWER_STATE_AVAILABLE);
if(GetTag(curArea)=="cam100ar_camp_plains")
Ambient_Start(oVal, AMBIENT_SYSTEM_ENABLED, AMBIENT_MOVE_NONE, AMBIENT_MOVE_PREFIX_NONE, 70, AMBIENT_ANIM_FREQ_ORDERED);
if(GetTag(curArea)=="den211ar_arl_eamon_estate_1" ||GetTag(curArea)=="cli300ar_redcliffe_castle" || GetTag(curArea)=="epi300ar_post_coronation")
Ambient_Start(oVal, AMBIENT_SYSTEM_ENABLED, AMBIENT_MOVE_NONE, AMBIENT_MOVE_PREFIX_NONE, 56, AMBIENT_ANIM_FREQ_ORDERED);
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY,FALSE);
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, VALERIA_CHECK_RUNIT,FALSE);
}
</dascript>

=Valeria has a dialog choice to remove or add her to the active party=

</rant on>
The partypicker is the only resource what you really have to change in order to make your companion show up. No way around this. However, as more mods come out, disregarding what others have done, and changing game resources at will and without knowing what they're doing very often, installing more than one mod messes the whole game up.
</rant off>

With that pleasant thought in mind, here's an option to make all our companions "compatible", in the sense that even if they don't show in the partypicker, you can still get them, or sent them back to camp.

==What we need==

In your npc dialog, say valeria_npc.dlg, we build an option as you see in the pretty pictures. You first notice that this option is available only if we haven't been through the last partypicker choosing at the gates in the climax (when we talk to Riordan).

[[image:camp1.JPG]]

Notice how we call the script valeria_come_with_me, to have her join the active party.

[[image:camp2.JPG]]

Notice how we call the script valeria_go_back_to_camp, to sent her back to camp(remove from active party).

[[image:camp3.JPG]]

==The come hither script==

<dascript>
#include "utility_h"

#include "plt_valeria_npc_hire"

void main()
{
object me=OBJECT_SELF;
SetImmortal(me,0);
SetLocalInt(me, CREATURE_REWARD_FLAGS, 0);
SetLocalInt(me, AMBIENT_SYSTEM_STATE, 0);
SetFollowerState(me, FOLLOWER_STATE_ACTIVE);
SetObjectActive(me,1);
AddCommand(me, CommandJumpToLocation(GetLocation(GetHero()))); //Ensures follower appears at PC's location.

WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY, TRUE);

}
</dascript>

==The go back to camp script==
Notice the checks to see if we are in one of the camps. You should have different locations for your companions of course.

<dascript>
#include "utility_h"
#include "sys_ambient_h"

#include "plt_valeria_npc_hire"

void main()
{
object me=OBJECT_SELF;
object curArea=GetArea(GetHero());
SetFollowerState(me, FOLLOWER_STATE_AVAILABLE);
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY,FALSE);
if(GetTag(curArea)=="cam100ar_camp_plains" || GetTag(curArea)=="den211ar_arl_eamon_estate_1" ||GetTag(curArea)=="cli300ar_redcliffe_castle")
{
location ValeriaLoc;
if(GetTag(curArea)=="cam100ar_camp_plains")
ValeriaLoc=Location(curArea, Vector(135.85, 123.18, -0.08), -71.33);
if(GetTag(curArea)=="den211ar_arl_eamon_estate_1")
ValeriaLoc=Location(curArea, Vector(28.1, 4.75, 0.0), 176.33);
if(GetTag(curArea)=="cli300ar_redcliffe_castle")
ValeriaLoc=Location(curArea, Vector(2.56,-14.84, 0.0), -130.38);
SetObjectActive(me,1);
AddCommand(me, CommandJumpToLocation(ValeriaLoc));
if(GetTag(curArea)=="cam100ar_camp_plains")
Ambient_Start(me, AMBIENT_SYSTEM_ENABLED, AMBIENT_MOVE_NONE, AMBIENT_MOVE_PREFIX_NONE, 70, AMBIENT_ANIM_FREQ_ORDERED);
if(GetTag(curArea)=="den211ar_arl_eamon_estate_1" ||GetTag(curArea)=="cli300ar_redcliffe_castle")
Ambient_Start(me, AMBIENT_SYSTEM_ENABLED, AMBIENT_MOVE_NONE, AMBIENT_MOVE_PREFIX_NONE, 56, AMBIENT_ANIM_FREQ_ORDERED);
}
else
{
SetObjectActive(me,0);
}
SetImmortal(me,1);
}
</dascript>

=Valeria has her own nightmare in the fade/Behavior in the Fade=

This tutorial and the gift handling are the hardest. There is so much stuff to do for this, I hope I don't forget anything. If someone tries it sent me message, tell me it worked. Otherwise I forgot something to tell you here probably. So let's take it slow.

==What we need==

When the PC first enters the fade, there are several important flags and module variables set automatically by the game. The plot resource of interest is CIR300PT_FADE and the flag ENTER_FADE, signals the PC is in Weisshaupt (where he/she meets the fake Duncan). This flag needs to be captured, so build the flag VALERIA_ENTER_FADE, into the NPC plot VALERIA_NPC_HIRE, in order to do this only once. There are three possible nightmares, each for each companion the PC had. We'll make it so our companion goes into the first available one.

We also need to capture the following flags from CIR300PT_FADE: SLOTH_DEMON_ATTACKS (that's the demon that put you to sleep, you fight him at the end of the fade), and SLOTH_DEMON_DEFEATED (when the demon is killed Valeria has to come back to the party, if she didn't help fight the demon).

So create in the plot VALERIA_NPC_HIRE the flags VALERIA_SLOTH_DEMON_ATTACKS, VALERIA_SLOTH_DEMON_DEFEATED (these are so we do it once), as well as, the following important flags for Valeria: VALERIA_HAS_NIGHTMARE_A, VALERIA_HAS_NIGHTMARE_B, VALERIA_HAS_NIGHTMARE_C (these three are to see to which area from the 3 possible Valeria is in)

First add this in includes:

<dascript>
...
#include "plt_valeria_fade_nightmare"
#include "plt_cir000pt_main"
#include "plt_cir300pt_fade"
...
</dascript>

==Changes in the function check_plot_changed==

Add the following lines in check_plot_changed, to capture important events in the PC's travels in the fade:

<dascript>
//enter the fade, remove valeria from party
if (WR_GetPlotFlag(PLT_CIR300PT_FADE,ENTER_FADE) && !WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_ENTER_FADE))
{
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_ENTER_FADE,TRUE);
//if she was in the party when the demon put you to sleep, she needs
//to have a nightmare area for her
if(WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY))
{
SetFollowerState(oVal, FOLLOWER_STATE_AVAILABLE); //Adds follower to the active party
//this flag is important, it tells us valeria has indeed a nightmare
//and will be used in her dialogs(see below)
WR_SetPlotFlag(PLT_VALERIA_FADE_NIGHTMARE,VALERIA_SLEEP,TRUE);
//which area to put valeria in. these module variables are set when
//first entering the fade and are positive if a companion nightmare
//area will have an actual companion in it (imagine going there with
//only 3 in the party, one area should be inactive, the value -1
//so circle through all 3 and see which one is the first available
//the core game scripts would put the other companions already in
//one of these, so we just find any available.
//so if say Rory(Ser Gilmore) and Valeria are in party, these scripts
//are disjoint and they would both behave appropriately
int fol1=GetLocalInt(GetModule(),CIR_FADE_FOLLOWER_1);
int fol2=GetLocalInt(GetModule(),CIR_FADE_FOLLOWER_2);
int fol3=GetLocalInt(GetModule(),CIR_FADE_FOLLOWER_3);
if(fol1<1)
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_HAS_NIGHTMARE_A,TRUE);
else if(fol2<1)
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_HAS_NIGHTMARE_B,TRUE);
else if(fol3<1)
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_HAS_NIGHTMARE_C,TRUE);
}
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY, FALSE);//not in party anymore anyways
}
//fighting the demon in the fade
//after the PC makes it to the inner sanctum, they get to talk to the
//demon and the battle begins. This is captured here. Notice that if
//we have talked to Valeria in the fade, she should be brought back
//to help in battle.
if (WR_GetPlotFlag(PLT_CIR300PT_FADE,SLOTH_DEMON_ATTACKS) && !WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_SLOTH_DEMON_ATTACKS) && WR_GetPlotFlag(PLT_VALERIA_FADE_NIGHTMARE, VALERIA_TALKED_TO_IN_FADE))
{
WR_SetFollowerState(oVal, FOLLOWER_STATE_ACTIVE);
SetImmortal(oVal,0);
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_SLOTH_DEMON_ATTACKS,TRUE);
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY,TRUE);
SetLocalInt(oVal, CREATURE_REWARD_FLAGS, 0); //Allows the follower to gain XP
SetLocalInt(oVal, AMBIENT_SYSTEM_STATE, 0);
SetObjectActive(oVal,1);
AddCommand(oVal, CommandJumpToLocation(GetLocation(GetHero()))); //Ensures follower appears at PC's location.
}
//demon in the fade defeated, this is captured here
//if valeria was with the PC when he first entered the fade
//she should come back to him regardless of him talking to her in the fade
if (WR_GetPlotFlag(PLT_CIR300PT_FADE,SLOTH_DEMON_DEFEATED) && !WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_SLOTH_DEMON_DEFEATED) && WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_SLEEP))
{
WR_SetFollowerState(oVal, FOLLOWER_STATE_ACTIVE);
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY,TRUE);
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_SLOTH_DEMON_DEFEATED,TRUE);
SetLocalInt(oVal, CREATURE_REWARD_FLAGS, 0); //Allows the follower to gain XP
SetLocalInt(oVal, AMBIENT_SYSTEM_STATE, 0);
SetObjectActive(oVal,1);
AddCommand(oVal, CommandJumpToLocation(GetLocation(GetHero()))); //Ensures follower appears at PC's location.
}
</dascript>

==The VALERIA_FADE_NIGHTMARE plot, it's journal and script==

Another important point, is that the game uses another plot for each companion. So we need to create the plot VALERIA_FADE_NIGHTMARE that will contain similar variables to the corresponding game plot for a companion. Name them: VALERIA_DEMON_HOSTILE, VALERIA_DEMON_KILLED, VALERIA_REALISES_DEMON, VALERIA_RETURNS_TO_PARTY, VALERIA_SLEEP (these have to do with her behavior when we meet her in her nightmare), VALERIA_TALKED_TO_IN_FADE (if we went to Valeria's nightmare and talked her out of it) .

Here is now the script for the plot VALERIA_FADE_NIGHTMARE (in the object inspector for the plot just change the standard plot_core script to this one). I call it: valeria_fade_subplot_script.nss

<dascript>
#include "utility_h"
#include "wrappers_h"
#include "plot_h"

#include "cir_constants_h"
#include "cir_functions_h"
#include "plt_valeria_fade_nightmare"
//this will look weird to you, but it shouldn't really(we're in the
//script not the definitions of the flags). when you see below you'll
//notice that certain flags from this plot are not set here, they are
//handled by global_plot_operations
//(just setting the flags to TRUE or FALSE nothing more)

#include "plt_valeria_npc_hire"
#include "plt_cir300pt_fade"

int StartingConditional()
{
event eParms = GetCurrentEvent(); // Contains all input parameters
int nType = GetEventType(eParms); // GET or SET call
string strPlot = GetEventString(eParms, 0); // Plot GUID
int nFlag = GetEventInteger(eParms, 1); // The bit flag # being affected
object oParty = GetEventCreator(eParms); // The owner of the plot table for this script
object oConversationOwner = GetEventObject(eParms, 0); // Owner on the conversation, if any
int nResult = FALSE; // used to return value for DEFINED GET events
object oPC = GetHero();
object oTarg;
object oVal = UT_GetNearestCreatureByTag(oPC,"valeria_npc");

plot_GlobalPlotHandler(eParms); // any global plot operations, including debug info

if(nType == EVENT_TYPE_SET_PLOT) // actions -> normal flags only
{
int nValue = GetEventInteger(eParms, 2); // On SET call, the value about to be written (on a normal SET that should be '1', and on a 'clear' it should be '0')
int nOldValue = GetEventInteger(eParms, 3); // On SET call, the current flag value (can be either 1 or 0 regardless if it's a set or clear event)
// IMPORTANT: The flag value on a SET event is set only AFTER this script finishes running!
switch(nFlag)
{
case VALERIA_DEMON_HOSTILE:
{
//when we speak to her, we might manage to make her realize she's in a nightmare, or not,
//if she realizes she'll help battling the demon pretending to be her sister
if(WR_GetPlotFlag(PLT_VALERIA_FADE_NIGHTMARE, VALERIA_REALISES_DEMON) == TRUE)
{ //Set to friendly
SetGroupId(oVal, GROUP_FRIENDLY);
WR_SetFollowerState(oVal, FOLLOWER_STATE_ACTIVE);
}
else
{ //If Valeria hasn't realised it is a demon set to neutral
SetGroupId(oVal, GROUP_NEUTRAL);
}
//Make Victoria into Incubus
//in the nightmare area I've created, 19741 is Victoria, Valeria's dead sister,
// and 19742 (initially inactive) is the Demon holding her
UT_TeamAppears(19741, FALSE);
UT_TeamAppears(19742, TRUE);
UT_TeamGoesHostile(19742, TRUE);
break;
}
case VALERIA_RETURNS_TO_PARTY:
{
WR_SetObjectActive(oVal, FALSE, BASE_ANIMATION_SLEEP, FADE_VFX_TELEPORT);
if(WR_GetPlotFlag(PLT_VALERIA_FADE_NIGHTMARE, VALERIA_REALISES_DEMON) == TRUE)
{ //Set to friendly
WR_SetFollowerState(oVal, FOLLOWER_STATE_UNAVAILABLE);
// WR_SetFollowerState(oVal, FOLLOWER_STATE_ACTIVE);
// WR_SetPlotFlag(PLT_VALERIA_FADE_NIGHTMARE,VALERIA_SLEEP,FALSE);
// WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_IN_PARTY,TRUE);
}
//the nightmare variables are set in the function check_plot_changed(see above),
//what we are setting here, are the plot variables that will change the
//actual area in the fade map to done. you can see those variables below
if (WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_HAS_NIGHTMARE_A))
{
WR_SetPlotFlag(PLT_CIR300PT_FADE_PORTAL, FADE_PORTAL_GREEN_1_COMPLETE, TRUE, TRUE);
}
else if (WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_HAS_NIGHTMARE_B))
{
WR_SetPlotFlag(PLT_CIR300PT_FADE_PORTAL, FADE_PORTAL_GREEN_2_COMPLETE, TRUE, TRUE);
}
else if (WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_HAS_NIGHTMARE_C))
{
WR_SetPlotFlag(PLT_CIR300PT_FADE_PORTAL, FADE_PORTAL_GREEN_3_COMPLETE, TRUE, TRUE);
}
break;
}
}
}
else // EVENT_TYPE_GET_PLOT -> defined conditions only
{

switch(nFlag)
{

}

}

plot_OutputDefinedFlag(eParms, nResult);

return nResult;
}
</dascript>

Forgot(told ye I would). Here's how to add the right journal entries, and also, how to define the plot properties (see the object inspector on the right). Notice this plot has to be a subplot to cir300pt_fade so what we get the correct Journal behavior as well (like the game does). Notice when the quest is done and we set this as the final entry (Final=Yes).
[[image:nightmare11.JPG]]

[[image:nightmare12.JPG]]

==Taking care of Valeria's dialog in her nightmare area==

I am using a stage for this, with the appropriate options set in the dialog. I won't go into it. You can do that.

The flags in VALERIA_FADE_NIGHTMARE are important here. Notice the check for the SLEEP flag here. Also notice we only run this dialog once.

[[image:nightmare1.JPG]]

Now you can do whatever you want, but I find this approach best. Notice the first of two options, checks to see if the PC has 3 ranks in persuasion. If that happens, Valeria snaps out of it right away.

[[image:nightmare2.JPG]]

Now notice how the REALISES_DEMON variable is set, so that Valeria will help in the battle with the demon acting as her sister.

[[image:nightmare3.JPG]]

Notice how we set the flag VALERIA_DEMON_HOSTILE in the plot valeria_fade_nightmare (see the script). It will initiate the battle.

[[image:nightmare4.JPG]]

Notice that if she's a mage she snaps out of it (second way). Notice how this links back up so we set the flag VALERIA_DEMON_HOSTILE in the plot valeria_fade_nightmare again.

[[image:nightmare5.JPG]]

Otherwise, you fight the demon alone. Notice how this links back so we set the flag VALERIA_DEMON_HOSTILE in the plot valeria_fade_nightmare again as we did above.

[[image:nightmare6.JPG]]

Set the VALERIA_TALKED_TO_IN_THE_FADE flag (so she'll help in the final demon battle). We show this option only once per game.

[[image:nightmare9.JPG]]

Set the VALERIA_RETURNS_TO_PARTY flag (removes Valeria from party). See the valeria_fade_nightmare plot script.

[[image:nightmare10.JPG]]

==Valeria Nightmare Area specifics==

Create a duplicate copy of a game companion nightmare area resource. I call it valeria_fade_nightmare(.are). Mine is using the predefined area layout lak526d for this (similar to Morrigan's nightmare I think, I probably duplicated her nightmare area and edited it). You need to do this so you'll have the fade pedistal in the area and atmosphere sounds, setting etc. You can remove some of the waypoints etc and edit it to what you want the nightmare to be. That's up to you can't help you there. Make sure the entry waypoint is tagged "start".

Set the script of the area to "valeria_nightmare". It's a copy of the core game resource tailored to what we want to do.
First here's the area script.

<dascript>
#include "utility_h"
#include "party_h"
#include "plt_valeria_fade_nightmare"
void main()
{
event evEvent = GetCurrentEvent(); // Event
int nEventType = GetEventType(evEvent); // Event Type
object oEventCreator = GetEventCreator(evEvent); // Event Creator
object oPC = GetHero();
object oParty = GetParty( oPC );
object oThis = OBJECT_SELF;
int bEventHandled = FALSE;
object oTarg, oFollower;
//I pass handling to the standard script first here for things like
// polymorphing handling (rat, golem etc), and standard behavior.
HandleEvent( evEvent, R"cir000ar_fade_core.ncs" );
switch ( nEventType )//we capture the following events though
{
case EVENT_TYPE_AREALOAD_PRELOADEXIT:
{
// When: for things you want to happen while the load screen is
// still up, things like moving creatures around.
int nIndex;
int nArraySize, nSpiritArraySize;
int bArcaneFormActive;
int bBurningFormActive;
int bGolemFormActive;
int bMouseFormActive;
int bSpiritFormActive;
int bPCHasArcaneForm;
int bPCHasBurningForm;
int bPCHasGolemForm;
int bPCHasMouseForm;
int bPCHasSpiritForm;
object [] arFireBases, arSpiritBases;

nArraySize = GetArraySize( arFireBases );
// VALERIA'S NIGHTMARE
if ( GetTag(oThis) == "valeria_fade_nightmare" && WR_GetPlotFlag(PLT_VALERIA_FADE_NIGHTMARE,VALERIA_RETURNS_TO_PARTY) == FALSE )
{
oFollower = Party_GetFollowerByTag("valeria_npc");
WR_SetObjectActive(oFollower, TRUE);
UT_LocalJump(oFollower,"valeria_spot");
//this is the waypoint Valeria appears in the area, so move her there(see pictures)
}
break;
}

case EVENT_TYPE_TEAM_DESTROYED:
{
int nTeamID = GetEventInteger(evEvent, 0); // Team ID
if(nTeamID==19742)
//capture when the demon dies and talk to Valeria
{
WR_SetPlotFlag(PLT_VALERIA_FADE_NIGHTMARE,VALERIA_DEMON_KILLED,TRUE);
oFollower = Party_GetFollowerByTag("valeria_npc");
UT_Talk(oFollower,oPC);
}

break;
}

}

}
</dascript>

My setup in the area. I don't know if you can see the inactive (red box) and active (yellow) Victoria versions.

[[image:nightmare7.JPG]]

The pedestal.

[[image:nightmare8.JPG]]

==So you think you're done, think again. Changes in Event Handling==

We finally need to capture when the PC selects the right nightmare area (the one area that contains Valeria, it will be loaded appropriately)

Add this in the Event Handling part of the module event script:

<dascript>
case EVENT_TYPE_BEGIN_TRAVEL://EVENT_TYPE_WORLD_MAP_USED:
{
string sSource = GetEventString(ev, 0); // the area tag the player is travelling from
string sTarget = GetEventString(ev, 1); // the area tag the player is travelling to
string sWPOverride = GetEventString(ev, 2);
//we pick to sent the PC clicking to the right nightmare area here
//it's funny actually, all tags for the core game nightmare companion
//map pins are given the same value "Fade_Follower". What distinguishes
//them is sWPOverride(thank god for that otherwise we'd be in trouble)
//if I remember correctly, the companion nightmare areas in the fade
//map, go 1,2,3 counterclockwise starting from the one on the left
//valeria_fade_nightmare is the name of the area for Valeria's
//nightmare, start is the waypoint tag
if(sWPOverride=="1" && sTarget=="Fade_Follower" && WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_HAS_NIGHTMARE_A))
DoAreaTransition("valeria_fade_nightmare","start");
if(sWPOverride=="2" && sTarget=="Fade_Follower" && WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_HAS_NIGHTMARE_B))
DoAreaTransition("valeria_fade_nightmare","start");
if(sWPOverride=="3" && sTarget=="Fade_Follower" && WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,VALERIA_HAS_NIGHTMARE_C))
DoAreaTransition("valeria_fade_nightmare","start");
break;
}
</dascript>

Phew, I hope, I didn't forget anything.

=Valeria first joining the party (This works for ANY follower you want to have join)=

In my mod, Valeria is allowed to have a class chosen the first time you meet her. So create in VALERIA_NPC_HIRE the flags ISMAGE,ISROGUE,ISWARRIOR and ISROGUEWARRIOR, if you want to do that, otherwise delete all the references to those flags. One of these is set to TRUE through dialog with Valeria. At the end of the dialog this script is called.

==The joining script==

Create the following script. I call it valeria_valjoin.nss
This script contains EVERYTHING you need to properly hire a follower without leveling him/her automatically.

Valeria in my mod is allowed to choose her class to Warrior, Rogue, Mage or Rogue-Warrior.

<dascript>
#include "sys_chargen_h"
#include "sys_rewards_h"

#include "plt_valeria_npc_hire"

void basic_blank_char(object oChar);//this function resets an NPC

void main()
{

object oPC=GetHero(), me=OBJECT_SELF;
WR_SetPlotFlag(PLT_VALERIA_NPC_HIRE, PARTY_VALERIA_JOINED, TRUE);

basic_blank_char(me);
//select race, otherwise skills tree wont show

Chargen_SelectRace(me,RACE_HUMAN);
int nClass;
//remove the rogue defaults, valeria's char is rogue when created

CharGen_ClearAbilityList(me,1);//remove talents
//CharGen_ClearAbilityList(me,2);//remove spells
//CharGen_ClearAbilityList(me,3);//remove skills

RemoveAbility(me, ABILITY_TALENT_DIRTY_FIGHTING);
RemoveAbility(me, ABILITY_SKILL_POISON_1);
//depending on which flags you set in the dialog that lead to this script, choose the appropriate class

if(WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,ISMAGE)==TRUE)
{
nClass=CLASS_WIZARD;
_AddAbility(me, ABILITY_SPELL_ARCANE_BOLT);
}

if(WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,ISROGUE)==TRUE)
{
nClass=CLASS_ROGUE;
_AddAbility(me, ABILITY_TALENT_DIRTY_FIGHTING);
_AddAbility(me, ABILITY_SKILL_POISON_1);
}

if(WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,ISWARRIOR)==TRUE)
{
nClass=CLASS_WARRIOR;
_AddAbility(me, ABILITY_TALENT_POWERFUL);
}

if(WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,ISROGUEWARRIOR)==TRUE)
{nClass=CLASS_ROGUE;}

//apply attributes, abilities and stats for the core class
//SetCreatureProperty(me,PROPERTY_SIMPLE_CURRENT_CLASS, n1-3.0,PROPERTY_VALUE_BASE);

Chargen_SelectCoreClass(me,nClass);
//add mage spells
//_AddAbility(me, ABILITY_TALENT_HIDDEN_ASSASSIN);//this works if it's available on the core class

if(WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,ISROGUEWARRIOR)==TRUE)
{
_AddAbility(me, ABILITY_TALENT_HIDDEN_WARRIOR);
_AddAbility(me, ABILITY_TALENT_DIRTY_FIGHTING);
_AddAbility(me, ABILITY_SKILL_POISON_1);
}
//tactics

Chargen_SetNumTactics(me);
Chargen_EnableTacticsPresets(me);
//SetFollowPartyLeader(me, TRUE);
//level needed for scaling

int nPackage = GetPackage(me);
int nTargetLevel;
int nPlayerLevel = GetLevel(oPC);
if(nPlayerLevel >= 13 || nPlayerLevel == 1 )
nTargetLevel = nPlayerLevel;
else
nTargetLevel = nPlayerLevel + 1;
int nMinLevel = GetM2DAInt(TABLE_PACKAGES, "MinLevel", nPackage);
if(nMinLevel > 0 && nMinLevel > nTargetLevel)
nTargetLevel = nMinLevel;
//xp until hero level

int nXp = RW_GetXPNeededForLevel(Max(nTargetLevel, 1));
RewardXP(me, nXp, TRUE, FALSE);

//add specialization

float count=1.;
if(GetLevel(GetHero())>=7)
{
SetCreatureProperty(me, 38, count); // 38 is the spec point ID
count=count+1.;
}
if(GetLevel(GetHero())>=14)
SetCreatureProperty(me, 38, count); // 38 is the spec point ID

//make available in party picker

SetFollowerState(me, FOLLOWER_STATE_ACTIVE);
SetFollowerState(me, FOLLOWER_STATE_AVAILABLE);
//dont fire player_core scaling

SetLocalInt(me, FOLLOWER_SCALED, 1);
SetLocalInt(me, AI_FLAG_STATIONARY, 0);
SetLocalInt(me, AMBIENT_SYSTEM_STATE, 0);
SetLocalInt(me, CREATURE_REWARD_FLAGS, 0);
//change script to player and send hire event

SetEventScript(me, RESOURCE_SCRIPT_PLAYER_CORE);
InitHeartbeat(me, CONFIG_CONSTANT_HEARTBEAT_RATE);
SendPartyMemberHiredEvent(me, FALSE);
SetFollowerApprovalEnabled(me,TRUE);
//open up party picker

SetPartyPickerGUIStatus(2);
ShowPartyPickerGUI(); //to allow Valeria to join in the active party
}

void basic_blank_char(object oChar)
{
// Initialize all creature properties to default value

SetCreatureProperty(oChar,PROPERTY_SIMPLE_LEVEL,1.0f,PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar,PROPERTY_SIMPLE_EXPERIENCE,0.0f,PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar,PROPERTY_ATTRIBUTE_STRENGTH, CHARGEN_BASE_ATTRIBUTE_VALUE, PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar,PROPERTY_ATTRIBUTE_DEXTERITY, CHARGEN_BASE_ATTRIBUTE_VALUE, PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar,PROPERTY_ATTRIBUTE_CONSTITUTION, CHARGEN_BASE_ATTRIBUTE_VALUE, PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar,PROPERTY_ATTRIBUTE_WILLPOWER, CHARGEN_BASE_ATTRIBUTE_VALUE, PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar,PROPERTY_ATTRIBUTE_INTELLIGENCE, CHARGEN_BASE_ATTRIBUTE_VALUE, PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar,PROPERTY_ATTRIBUTE_MAGIC, CHARGEN_BASE_ATTRIBUTE_VALUE, PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar,PROPERTY_ATTRIBUTE_ATTACK_SPEED_MODIFIER, 1.0f);
SetCreatureProperty(oChar,PROPERTY_ATTRIBUTE_DAMAGE_SCALE, 1.0f);
SetCreatureProperty(oChar,PROPERTY_ATTRIBUTE_RESISTANCE_MENTAL, 0.0f);
SetCreatureProperty(oChar,PROPERTY_ATTRIBUTE_RESISTANCE_PHYSICAL, 0.0f);
SetCreatureProperty(oChar,51, 1.0f);
SetCreatureProperty(oChar, PROPERTY_ATTRIBUTE_REGENERATION_HEALTH_COMBAT, REGENERATION_HEALTH_COMBAT_DEFAULT);
SetCreatureProperty(oChar, PROPERTY_ATTRIBUTE_REGENERATION_STAMINA_COMBAT, REGENERATION_STAMINA_COMBAT_DEFAULT);
SetCreatureProperty(oChar, PROPERTY_ATTRIBUTE_REGENERATION_HEALTH,REGENERATION_HEALTH_EXPLORE_DEFAULT, PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar, PROPERTY_ATTRIBUTE_REGENERATION_STAMINA, REGENERATION_STAMINA_EXPLORE_DEFAULT, PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar, PROPERTY_ATTRIBUTE_MISSILE_SHIELD,0.0);
SetCreatureProperty(oChar, 38,0.0);
SetCreatureProperty(oChar, PROPERTY_DEPLETABLE_HEALTH , 1.0f, PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar, PROPERTY_DEPLETABLE_MANA_STAMINA , 0.0f, PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar, PROPERTY_ATTRIBUTE_DEFENSE , 0.0f, PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar, PROPERTY_ATTRIBUTE_ATTACK, 0.0f, PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar, PROPERTY_ATTRIBUTE_DAMAGE_BONUS, 0.0f, PROPERTY_VALUE_BASE);
SetCreatureProperty(oChar, PROPERTY_ATTRIBUTE_FLANKING_ANGLE, 60.0f, PROPERTY_VALUE_BASE);

}
</dascript>
=Valeria Gift Handling=

When a gift item (Base Item Type set to gift) is given to a companion, the event EVENT_TYPE_MODULE_HANDLE_GIFT fires and is processed by core game scripts. So the easy way to handle this, is modify most notably sp_module_item_acq and the approval scripts.

As it turns out, ANY item set to gift item, will lead to this script firing and changing the companion's approval. The script has a list of companions and corresponding indices to each one, so it knows how to handle them(the original game ones), and the function that gives you the companion index or tag (like Approval_GetFollowerObject in approval_h) DOES NOT have a default value to return. That's fine of course, so people go in and can add their companion to all those scripts. We don't want to do that.

The unfortunate part for us, is that even if you give Valeria any gift, her approval will not be handled appropriately, since her tag is nowhere in those scripts. Moreover, if you give someone else a gift that should be unique for your companion, the gift will be lost forever since your companion is not in the checks from the core game scripts.

One way around this, that works fine if ONLY ONE mod does it (as I have), is everytime a gift is handed to a companion (from the original game or from a companion mod) we capture all possibilities as seen below in the code in Event handling and associated scripts.

So I will first illustrate how to do it for only one mod, and then we'll work on changing it so everyone can do it, aye?

==What we need==

When a gift is given to a companion and their approval goes up, a "plot" skill (like increased attributes or extra talents) must be given to the companion and the approval status should change. If approval drops below a certain level, the appropriate skills must be removed from the companion and so forth. Valeria appears in non of the corresponding game scripts so we have to take care of all of that. We'll build our own functions.

Moreover, the gifts are lost without any effect on the companion. Which means any gifts that should not be allowed to be given to Valeria, must be returned back in the inventory, or Valeria gifts, not allowed to be given to other companions, must also be returned to the inventory. It is a pain in the a...

Note to self: ask Bioware to build a StringToResource() conversion function, ack.

Let's start.
In 'includes' add the following function definitions:

<dascript>
...
//these are the plot ability id's from ABI_BASE
const int valeria_nAbility1war=90200;
const int valeria_nAbility2war=90201;
const int valeria_nAbility3war=90202;
const int valeria_nAbility4war=90218;
const int valeria_nAbility1thief=90209;
const int valeria_nAbility2thief=90210;
const int valeria_nAbility3thief=90211;
const int valeria_nAbility4thief=90221;
const int valeria_nAbility1mage=90215;
const int valeria_nAbility2mage=90216;
const int valeria_nAbility3mage=90217;
const int valeria_nAbility4mage=90223;
const int valeria_nAbility_warshow=90224;
const int valeria_nAbility_thiefshow=90227;
const int valeria_nAbility_mageshow=90229;
...
void valeria_approval();
void give_valeria_skill(object oval,int level);
void handle_valeria_gift(object oFollower,object oItem,int nApprovalChange);
resource get_gift_resource(string sGiftTag);
resource get_valeria_gift_resource(string sGiftTag);
...
</dascript>

==Handling the event EVENT_TYPE_MODULE_HANDLE_GIFT==

We capture here all possibilities in gift handling, based on the behavior of the core game scripts.

Add this to Event handling section:

<dascript>
case EVENT_TYPE_MODULE_HANDLE_GIFT:
{
//from my experiments, it is possible to have this script be fired
//before the core game script does(which mean the constant
//nApprovalChange has not been changed from the core game scripts.
//that introduces extra difficulties
//it happens for instance when you first load the game, and give
//Valeria a gift or say Alistair. This will bug their approval rating
//what you see below, is the solution to all those possibilities
//after tons of trial and error
//companion object
object oFollower = GetEventObject(ev, 0);
//gift object
object oItem = GetEventObject(ev, 1);
//this is the default(for that gift)approval change value from the game
int nApprovalChange = GetEventInteger(ev, 0);
//tag of the gift
string sGiftTag = GetTag(oItem);
//if the follower recieving the gift is not Valeria but we chose to
//give them a Valeria gift, they should refuse it, and throw it back
//in the inventory, i use 6 unique gifts for her in my mod
if(GetTag(oFollower)!="valeria_npc")
{
if(sGiftTag=="valeria_gift1" ||sGiftTag=="valeria_gift2" ||sGiftTag=="valeria_gift3" ||sGiftTag=="valeria_gift4" ||sGiftTag=="valeria_gift5" ||sGiftTag=="valeria_gift6")
{
//we adjust the follower approval to what is was
//this will cause the following wierd behavior, say Alistair
//is 3 points away from a plot skill upgrade, giving him the gift
//would give him the plot, and then remove it, so the message will
//show up. No way around this I'm afraid.
AdjustFollowerApproval(oFollower,-nApprovalChange,TRUE);
//return valeria only gifts, StringToResource function needed first
//here. It gets a LOT worse. there's a function about this, see below.
resource res=get_valeria_gift_resource(sGiftTag);
UT_AddItemToInventory(res, 1,GetHero(),"",TRUE);
PlaySoundSet(oFollower, SS_GIFT_NEGATIVE);
}
}
//if the gift is given to Valeria
if(GetTag(oFollower) == "valeria_npc")
{
//if she was not the character we were controlling
//while opening the inventory gui, that character WILL have their
//approval changed. So bring it back to what it was.
if(GetTag(GetMainControlled())!= "valeria_npc")
{
AdjustFollowerApproval(GetMainControlled(),-nApprovalChange,TRUE);
}
handle_valeria_gift(oFollower,oItem,nApprovalChange);
}
break;
}
</dascript>

==Valeria custom gift/approval scripts==

Add these functions in the 'functions' section.

===Gift function: get_valeria_gift_resource===

<dascript>
resource get_valeria_gift_resource(string sGiftTag)
{
resource res;
if (sGiftTag == "valeria_gift1")
res=R"valeria_gift1.uti";
if (sGiftTag == "valeria_gift2")
res=R"valeria_gift2.uti";
if (sGiftTag == "valeria_gift3")
res=R"valeria_gift3.uti";
if (sGiftTag == "valeria_gift4")
res=R"valeria_gift4.uti";
if (sGiftTag == "valeria_gift5")
res=R"valeria_gift5.uti";
if (sGiftTag == "valeria_gift6")
res=R"valeria_gift6.uti";
return res;
}
</dascript>

===Gift function: get_gift_resource (oh yes, all game gifts)===

We have to do this only for the gifts not being returned automatically by game scripts, like Alistair's Mother locket, Morrigan's Grimoire etc.

<dascript>
resource get_gift_resource(string sGiftTag)
{
resource res;
//alistair
// if (sGiftTag == GEN_IM_GIFT_ALISTAIR_AMULET)
// if (sGiftTag == GEN_IM_GIFT_DUNCAN_SHIELD)
if (sGiftTag == "gen_im_gift_runston")
res=R"gen_im_gift_runston.uti";
if (sGiftTag == "gen_im_gift_runston2")
res=R"gen_im_gift_runston2.uti";
if (sGiftTag == "gen_im_gift_stat")
res=R"gen_im_gift_stat.uti";
if (sGiftTag == "gen_im_gift_stat2")
res=R"gen_im_gift_stat2.uti";
if (sGiftTag == "gen_im_gift_stat3")
res=R"gen_im_gift_stat3.uti";
if (sGiftTag == "gen_im_gift_stat4")
res=R"gen_im_gift_stat4.uti";
//leliana
// if (sGiftTag == "gen_im_gift_nugg")
// if (sGiftTag == "gen_im_gift_flower_andraste")
if (sGiftTag == "gen_im_gift_chantam")
res=R"gen_im_gift_chantam.uti";
if (sGiftTag == "gen_im_gift_hlysymb")
res=R"gen_im_gift_hlysymb.uti";
if (sGiftTag == "gen_im_gift_hlysymb2")
res=R"gen_im_gift_hlysymb2.uti";
if (sGiftTag == "gen_im_gift_hlysymb3")
res=R"gen_im_gift_hlysymb3.uti";
if (sGiftTag == "gen_im_gift_hlysymb4")
res=R"gen_im_gift_hlysymb4.uti";
if (sGiftTag == "gen_im_gift_hlysymb5")
res=R"gen_im_gift_hlysymb5.uti";
if (sGiftTag == "gen_im_gift_shoe")
res=R"gen_im_gift_shoe.uti";
//loghain 13
if (sGiftTag == "gen_im_gift_map")
res=R"gen_im_gift_map.uti";
if (sGiftTag == "gen_im_gift_map2")
res=R"gen_im_gift_map2.uti";
if (sGiftTag == "gen_im_gift_map3")
res=R"gen_im_gift_map3.uti";
if (sGiftTag == "gen_im_gift_map4")
res=R"gen_im_gift_map4.uti";
if (sGiftTag == "gen_im_gift_map5")
res=R"gen_im_gift_map5.uti";
//morigan 18
// if (sGiftTag == "gen_im_gift_grimoire")
// if (sGiftTag == "gen_im_gift_flmgrimoire")
// if (sGiftTag == "gen_im_gift_mirror")
if (sGiftTag == "gen_im_gift_brooch")
res=R"gen_im_gift_brooch.uti";
if (sGiftTag == "gen_im_gift_locket")
res=R"gen_im_gift_locket.uti";
if (sGiftTag == "gen_im_gift_ncklace")
res=R"gen_im_gift_ncklace.uti";
if (sGiftTag == "gen_im_gift_ncklace2")
res=R"gen_im_gift_ncklace2.uti";
if (sGiftTag == "gen_im_gift_ncklace3")
res=R"gen_im_gift_ncklace3.uti";
if (sGiftTag == "gen_im_gift_ncklace4")
res=R"gen_im_gift_ncklace4.uti";
if (sGiftTag == "gen_im_gift_ncklace5")
res=R"gen_im_gift_ncklace5.uti";
//oghern 25
if (sGiftTag == "gen_im_gift_ale")
res=R"gen_im_gift_ale.uti";
if (sGiftTag == "gen_im_gift_fanbot")
res=R"gen_im_gift_fanbot.uti";
if (sGiftTag == "gen_im_gift_fanbot2")
res=R"gen_im_gift_fanbot2.uti";
if (sGiftTag == "gen_im_gift_fanbot3")
res=R"gen_im_gift_fanbot3.uti";
if (sGiftTag == "gen_im_gift_fanbot4")
res=R"gen_im_gift_fanbot4.uti";
if (sGiftTag == "gen_im_gift_fanbot5")
res=R"gen_im_gift_fanbot5.uti";
if (sGiftTag == "gen_im_gift_pitcher")
res=R"gen_im_gift_pitcher.uti";
//stern 32
// if (sGiftTag == "gen_im_gift_sword_sten")
if (sGiftTag == "gen_im_gift_mdpnt1")
res=R"gen_im_gift_mdpnt1.uti";
if (sGiftTag == "gen_im_gift_mdpnt2")
res=R"gen_im_gift_mdpnt2.uti";
if (sGiftTag == "gen_im_gift_smlpnt1")
res=R"gen_im_gift_smlpnt1.uti";
if (sGiftTag == "gen_im_gift_smlpnt2")
res=R"gen_im_gift_smlpnt2.uti";
if (sGiftTag == "gen_im_gift_totem")
res=R"gen_im_gift_totem.uti";
//wynne 37
if (sGiftTag == "gen_im_gift_book")
res=R"gen_im_gift_book.uti";
if (sGiftTag == "gen_im_gift_book2")
res=R"gen_im_gift_book2.uti";
if (sGiftTag == "gen_im_gift_book4")
res=R"gen_im_gift_book4.uti";
if (sGiftTag == "gen_im_gift_book5")
res=R"gen_im_gift_book5.uti";
if (sGiftTag == "gen_im_gift_tatbook")
res=R"gen_im_gift_tatbook.uti";
if (sGiftTag == "gen_im_gift_fanscrl")
res=R"gen_im_gift_fanscrl.uti";
if (sGiftTag == "gen_im_gift_wine")
res=R"gen_im_gift_wine.uti";
//zevran 44
// if (sGiftTag == GEN_IM_GIFT_DALISH_GLOVES)
// if (sGiftTag == GEN_IM_GIFT_ANTIVAN_BOOTS)
if (sGiftTag == "gen_im_gift_mgold")
res=R"gen_im_gift_mgold.uti";
if (sGiftTag == "gen_im_gift_msilver")
res=R"gen_im_gift_msilver.uti";
if (sGiftTag == "gen_im_gift_sgold")
res=R"gen_im_gift_sgold.uti";
if (sGiftTag == "gen_im_gift_ssilver")
res=R"gen_im_gift_ssilver.uti";
//other 48
if (sGiftTag == "gen_im_gift_armband")
res=R"gen_im_gift_armband.uti";
if (sGiftTag == "gen_im_gift_bracer")
res=R"gen_im_gift_bracer.uti";
if (sGiftTag == "gen_im_gift_brclet")
res=R"gen_im_gift_brclet.uti";
if (sGiftTag == "gen_im_gift_brclet2")
res=R"gen_im_gift_brclet2.uti";
if (sGiftTag == "gen_im_gift_cake")
res=R"gen_im_gift_cake.uti";
if (sGiftTag == "gen_im_gift_dppant")
res=R"gen_im_gift_dppant.uti";
if (sGiftTag == "gen_im_gift_earring")
res=R"gen_im_gift_earring.uti";
if (sGiftTag == "gen_im_gift_earring2")
res=R"gen_im_gift_earring2.uti";
if (sGiftTag == "gen_im_gift_hdband")
res=R"gen_im_gift_hdband.uti";
if (sGiftTag == "gen_im_gift_paintsky")
res=R"gen_im_gift_paintsky.uti";
if (sGiftTag == "gen_im_gift_ring")
res=R"gen_im_gift_ring.uti";
if (sGiftTag == "gen_im_gift_ring2")
res=R"gen_im_gift_ring2.uti";
if (sGiftTag == "gen_im_gift_ring3")
res=R"gen_im_gift_ring3.uti";
if (sGiftTag == "gen_im_gift_ring4")
res=R"gen_im_gift_ring4.uti";
if (sGiftTag == "gen_im_gift_ring5")
res=R"gen_im_gift_ring5.uti";
if (sGiftTag == "gen_im_gift_tiara")
res=R"gen_im_gift_tiara.uti";
if (sGiftTag == "gen_im_gift_trbneck")
res=R"gen_im_gift_trbneck.uti";
if (sGiftTag == "gen_im_gift_tyarn")
res=R"gen_im_gift_tyarn.uti";
//dog 66
if (sGiftTag == "gen_im_gift_dogbone")
res=R"gen_im_gift_dogbone.uti";
if (sGiftTag == "gen_im_gift_dogbone2")
res=R"gen_im_gift_dogbone2.uti";
if (sGiftTag == "gen_im_gift_dogbone3")
res=R"gen_im_gift_dogbone3.uti";
if (sGiftTag == "gen_im_gift_dogbone4")
res=R"gen_im_gift_dogbone4.uti";
if (sGiftTag == "gen_im_gift_dogbone5")
res=R"gen_im_gift_dogbone5.uti";
//71 without the special ones
return res;
}
</dascript>

A conversion function StringToResource starting to sound like a good idea right about now hehe.

===Approval function: valeria_approval===

You can change these bounds for the plot skills to anything you wish. I have them at 65,75,85 and 95.

<dascript>
void valeria_approval()
{
object oPC=GetHero();
object oFollower=UT_GetNearestObjectByTag(oPC, "valeria_npc");
// what you see here is something that needs to be done, in order you
//don't get bugs and lose Valeria's true approval rating
//give your PC an item before valeria joins, and use a local variable
//there to hold the true approval rating. i use the thief writ you get
//when you first release her by talking to Jaltair(guildmaster)
object [] thiefwrit=GetItemsInInventory(oPC,GET_ITEMS_OPTION_BACKPACK,0,"valeria_thief_contract");
object thiefwrit1=thiefwrit[0];
int nApproval=GetFollowerApproval(oFollower);
SetLocalInt(thiefwrit1,ITEM_COUNTER_1,nApproval);
int trueapproval=GetLocalInt(thiefwrit1,ITEM_COUNTER_1);
// up to to here
if(trueapproval<65)
{
give_valeria_skill(oFollower,0);
}
if(trueapproval>=65 && trueapproval<75)
{
// SetFollowerApprovalDescription
give_valeria_skill(oFollower,1);
}
if(trueapproval>=75 && trueapproval<85)
{
give_valeria_skill(oFollower,2);
}
if(trueapproval>=85 && trueapproval<95)
{
give_valeria_skill(oFollower,3);
}
//I only change the description if over 95 to friendly because the
//game won't do it, when we load the game (see below), we have to redo this...
if(trueapproval>=95)
{
int nStringRef = GetM2DAInt(TABLE_APPROVAL_NORMAL_RANGES, "StringRef", APP_RANGE_FRIENDLY);
SetFollowerApprovalDescription(oFollower, nStringRef);
give_valeria_skill(oFollower,4);
}
}
</dascript>

===Approval function: give_valeria_skill===

This one gives/takes the right plot skill, depending on current approval rating. I have to take care of all 4 possible class cases for Valeria. You'd probably need only one set of these.

<dascript>
void give_valeria_skill(object oval,int level)
{
int doit=0;
if(WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,ISROGUEWARRIOR))
{
doit=1;
}
//warrior
if(doit || WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,ISWARRIOR))
{
if(level==0)
{
RemoveAbility(oval, valeria_nAbility_warshow);
RemoveAbility(oval, valeria_nAbility1war);
RemoveAbility(oval, valeria_nAbility2war);
RemoveAbility(oval, valeria_nAbility3war);
RemoveAbility(oval, valeria_nAbility4war);
return;
}
AddAbility(oval, valeria_nAbility_warshow);
if(!HasAbility(oval, valeria_nAbility1war) && level==1)
{
AddAbility(oval, valeria_nAbility1war, TRUE);
RemoveAbility(oval, valeria_nAbility2war);
RemoveAbility(oval, valeria_nAbility3war);
RemoveAbility(oval, valeria_nAbility4war);
}
if(!HasAbility(oval, valeria_nAbility2war) && level==2)
{
AddAbility(oval, valeria_nAbility1war);
AddAbility(oval, valeria_nAbility2war, TRUE);
RemoveAbility(oval, valeria_nAbility3war);
RemoveAbility(oval, valeria_nAbility4war);
}
if(!HasAbility(oval, valeria_nAbility3war) && level==3)
{
AddAbility(oval, valeria_nAbility1war);
AddAbility(oval, valeria_nAbility2war);
AddAbility(oval, valeria_nAbility3war, TRUE);
RemoveAbility(oval, valeria_nAbility4war);
}
if(!HasAbility(oval, valeria_nAbility4war) && level==4)
{
AddAbility(oval, valeria_nAbility1war);
AddAbility(oval, valeria_nAbility2war);
AddAbility(oval, valeria_nAbility3war);
AddAbility(oval, valeria_nAbility4war, TRUE);
}
}
//rogue
if(doit || WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,ISROGUE)==TRUE)
{
if(level==0)
{
RemoveAbility(oval, valeria_nAbility_thiefshow);
RemoveAbility(oval, valeria_nAbility1thief);
RemoveAbility(oval, valeria_nAbility2thief);
RemoveAbility(oval, valeria_nAbility3thief);
RemoveAbility(oval, valeria_nAbility4thief);
return;
}
AddAbility(oval, valeria_nAbility_thiefshow);
if(!HasAbility(oval, valeria_nAbility1thief) && level==1)
{
AddAbility(oval, valeria_nAbility1thief, TRUE);
RemoveAbility(oval, valeria_nAbility2thief);
RemoveAbility(oval, valeria_nAbility3thief);
RemoveAbility(oval, valeria_nAbility4thief);
}
if(!HasAbility(oval, valeria_nAbility2thief) && level==2)
{
AddAbility(oval, valeria_nAbility1thief);
AddAbility(oval, valeria_nAbility2thief, TRUE);
RemoveAbility(oval, valeria_nAbility3thief);
RemoveAbility(oval, valeria_nAbility4thief);
}
if(!HasAbility(oval, valeria_nAbility3thief) && level==3)
{
AddAbility(oval, valeria_nAbility1thief);
AddAbility(oval, valeria_nAbility2thief);
AddAbility(oval, valeria_nAbility3thief, TRUE);
RemoveAbility(oval, valeria_nAbility4thief);
}
if(!HasAbility(oval, valeria_nAbility4thief) && level==4)
{
AddAbility(oval, valeria_nAbility1thief);
AddAbility(oval, valeria_nAbility2thief);
AddAbility(oval, valeria_nAbility3thief);
AddAbility(oval, valeria_nAbility4thief, TRUE);
}
}
//mage
if(WR_GetPlotFlag(PLT_VALERIA_NPC_HIRE,ISMAGE)==TRUE)
{
if(level==0)
{
RemoveAbility(oval, valeria_nAbility_mageshow);
RemoveAbility(oval, valeria_nAbility1mage);
RemoveAbility(oval, valeria_nAbility2mage);
RemoveAbility(oval, valeria_nAbility3mage);
RemoveAbility(oval, valeria_nAbility4mage);
return;
}
AddAbility(oval, valeria_nAbility_mageshow);
if(!HasAbility(oval, valeria_nAbility1mage) && level==1)
{
AddAbility(oval, valeria_nAbility1mage, TRUE);
RemoveAbility(oval, valeria_nAbility2mage);
RemoveAbility(oval, valeria_nAbility3mage);
RemoveAbility(oval, valeria_nAbility4mage);
}
if(!HasAbility(oval, valeria_nAbility2mage) && level==2)
{
AddAbility(oval, valeria_nAbility1mage);
AddAbility(oval, valeria_nAbility2mage, TRUE);
RemoveAbility(oval, valeria_nAbility3mage);
RemoveAbility(oval, valeria_nAbility4mage);
}
if(!HasAbility(oval, valeria_nAbility3mage) && level==3)
{
AddAbility(oval, valeria_nAbility1mage);
AddAbility(oval, valeria_nAbility2mage);
AddAbility(oval, valeria_nAbility3mage, TRUE);
RemoveAbility(oval, valeria_nAbility4mage);
}
if(!HasAbility(oval, valeria_nAbility4mage) && level==4)
{
AddAbility(oval, valeria_nAbility1mage);
AddAbility(oval, valeria_nAbility2mage);
AddAbility(oval, valeria_nAbility3mage);
AddAbility(oval, valeria_nAbility4mage, TRUE);
}
}
}
</dascript>

===Gift Handling function: handle_valeria_gift===

<dascript>
void handle_valeria_gift(object oFollower,object oItem,int nApprovalChange)
{
string sGiftTag = GetTag(oItem);
int nSoundSet;
int nApproval=GetFollowerApproval(oFollower);
//again read the true approval, see the valeria_approval script
object [] thiefwrit=GetItemsInInventory(GetHero(),GET_ITEMS_OPTION_BACKPACK,0,"valeria_thief_contract");
object thiefwrit1=thiefwrit[0];
int trueapproval=GetLocalInt(thiefwrit1,ITEM_COUNTER_1);
//this checks to see if the current approval is not the true, which
//means the core game scripts have changed her approval, so bring it
//back to what it was. also if approval is 100 take care for a really
//nusty nusty nusty bug.
if(nApproval!=trueapproval)
{
if(nApproval==100)
nApprovalChange=100-trueapproval;
if(GetMainControlled()==oFollower)
AdjustFollowerApproval(oFollower,-nApprovalChange,TRUE);
}

// accept only certain gifts, if it's not right return it
if (sGiftTag!="valeria_gift1" && sGiftTag!="valeria_gift2" && sGiftTag!="valeria_gift3" && sGiftTag!="valeria_gift4" && sGiftTag!="valeria_gift5" && sGiftTag!="valeria_gift6")
{
resource res=get_gift_resource(sGiftTag);
UT_AddItemToInventory(res, 1,GetHero(),"",TRUE);
PlaySoundSet(oFollower, SS_THREATEN);
return;
}
nApproval=GetFollowerApproval(oFollower);
//depending on the gift type, add random approval
//fruit, vegetable
if (sGiftTag=="valeria_gift1" || sGiftTag=="valeria_gift2")
{
nApprovalChange=1+Random(4);
}
//uncle Ertin's contract, Medal of Messira
if (sGiftTag=="valeria_gift3" || sGiftTag=="valeria_gift4")
{
nApprovalChange=5+Random(5);
}
//portrait of her family, her sister's locket
if (sGiftTag=="valeria_gift5" || sGiftTag=="valeria_gift6")
{
nApprovalChange=10+Random(5);
}
//play appropriate soundset response
if(nApprovalChange<=0)nSoundSet=SS_NO;
else if(nApprovalChange>0 && nApprovalChange<=4) nSoundSet=SS_YES;
else if(nApprovalChange>4 && nApprovalChange<=9) nSoundSet=SS_THANK_YOU;
else nSoundSet=SS_CHEER;

nApproval+=nApprovalChange;
if(nApproval<-100)nApproval=-100;
if(nApproval>100)nApproval=100;
nApprovalChange=nApproval-trueapproval;
AdjustFollowerApproval(oFollower,nApprovalChange,TRUE);
PlaySoundSet(oFollower,nSoundSet);
WR_DestroyObject(oItem);
SetLocalInt(thiefwrit1,ITEM_COUNTER_1,GetFollowerApproval(oFollower));

//if approval is 100 return everything
if(GetFollowerApproval(oFollower)==100 && trueapproval==100)
{
resource res=get_valeria_gift_resource(sGiftTag);
UT_AddItemToInventory(res, 1,GetHero(),"",TRUE);
PlaySoundSet(oFollower, SS_THREATEN);
}
//give extra skill, if her approval is high or take it away
trueapproval=GetLocalInt(thiefwrit1,ITEM_COUNTER_1);
if(trueapproval<65)
{
give_valeria_skill(oFollower,0);
}
if(trueapproval>=65 && trueapproval<75)
{
give_valeria_skill(oFollower,1);
}
if(trueapproval>=75 && trueapproval<85)
{
give_valeria_skill(oFollower,2);
}
if(trueapproval>=85 && trueapproval<95)
{
give_valeria_skill(oFollower,3);
}
if(trueapproval>=95)
{
int nStringRef = GetM2DAInt(TABLE_APPROVAL_NORMAL_RANGES, "StringRef", APP_RANGE_FRIENDLY);
SetFollowerApprovalDescription(oFollower, nStringRef);
give_valeria_skill(oFollower,4);
}
}
</dascript>

==Handling the Event EVENT_TYPE_MODULE_LOAD==

Add this in 'Event handling':

<dascript>
case EVENT_TYPE_MODULE_LOAD:
{
object [] thiefwrit=GetItemsInInventory(oPC,GET_ITEMS_OPTION_BACKPACK,0,"valeria_thief_contract");
object thiefwrit1=thiefwrit[0];
//get the true approval, and set the description appropriately
//has to be done, since the core game scripts do not have valeria in
//them to do it automatically
int trueapproval=GetLocalInt(thiefwrit1,ITEM_COUNTER_1);
if(trueapproval>=95)
{
int nStringRef = GetM2DAInt(TABLE_APPROVAL_NORMAL_RANGES, "StringRef", APP_RANGE_FRIENDLY);
SetFollowerApprovalDescription(oVal, nStringRef);
}
}
</dascript>

==Changing Valeria's approval in other parts of the game==

In many places of the game you might want to drop or increase approval.
Example: When you destroy the thief guild, Valeria is so pleased that her approval skyrockets. In a script you could have something like this:

<dascript>
object ofollow = UT_GetNearestObjectByTag(oPC,"valeria_npc");
AdjustFollowerApproval(ofollow,35,TRUE);
valeria_approval();
//which means all approval functions, constants etc have be included
//as a say valeria_approval_functions_h file to those scripts. Just
//combine the appropriate functions that I've shown you here to create
//that file.
</dascript>

Another way to do this (it's what the game uses of course), is through the approval plots. That allows you to change approval in dialogs as well. But then again, the game has full control of the approval scripts.

So I haven't done it, I always change her approval through scripts run from dialogs instead. I think you can easily add that though.

==The potential problem and solutions==

The aforementioned approach will have to be modified, so we can all use it. I have not thought about it hard.

Imagine if two mods do this, while the core game script runs only once. We would reduce say, Alistair's approval twice as much, as the approval value of the gift.

This occurs when we capture the event EVENT_TYPE_MODULE_HANDLE_GIFT:

<dascript>
case EVENT_TYPE_MODULE_HANDLE_GIFT:
{
object oFollower = GetEventObject(ev, 0);
object oItem = GetEventObject(ev, 1);
int nApprovalChange = GetEventInteger(ev, 0);
string sGiftTag = GetTag(oItem);
if(GetTag(oFollower)!="valeria_npc")//<--HERE
{
if(sGiftTag=="valeria_gift1" ||sGiftTag=="valeria_gift2" ||sGiftTag=="valeria_gift3" ||sGiftTag=="valeria_gift4" ||sGiftTag=="valeria_gift5" ||sGiftTag=="valeria_gift6")
{
AdjustFollowerApproval(oFollower,-nApprovalChange,TRUE);
resource res=get_valeria_gift_resource(sGiftTag);
UT_AddItemToInventory(res, 1,GetHero(),"",TRUE);
PlaySoundSet(oFollower, SS_GIFT_NEGATIVE);
}
}
...
break;
}
</dascript>

A possible solution is the following but I have not implemented it.
Have about 7-8 variables, as many as the original game npcs, and keep track of EVERYONE's approval. That way you can check to see if their approval has NOT changed from what its true value was before the gift handling event fired. If
1) Alistair's approval changed it means the core script run and we need to bring his approval to what it was.
2) his approval did not change it means either:
a)the core script hasn't run yet or
b) another mod run with the approach above and took his approval back.

There's an easy way to find out if another mod is present (2b), so you probably don't need all that. If you check the inventory for the item, if it is still there, it means another mod already returned it.
I'll see if I can implement this at some point and update the wiki appropriately.

I'm sure if we think hard enough we can solve this easily and possibly in a more efficient way. I'll assume for now I'm done with the wiki and take a rest.

Model list

2022-02-01T16:21:31Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

{{Infobox level editor}}
The idea behind showing these models is to give the player a quick view of the actual model that corresponds with a model file name. Most of the files have meaningful names however the builder will still find that he/she has to place the model in the level to see what it looks like. These will allow the builder to quickly view model images and thus save them time in level building.

== DATool ==
[http://social.bioware.com/project/41/ DATool] is a small utility written by [http://social.bioware.com/108/ Adinos] that allows the viewing and retexturing of the models from Dragon Age. If you do not see an image below for the model you're curious about try DATool.

== Naming conventions ==

See Main Article: [[Naming conventions#Model File Naming Convention|Naming conventions]]

== Introductional Notes ==

* Black models are used to surround indoor areas so that players can see inside the walls when the camera is outside them.
* All screen shots are taken with a level of 64 x 64 size (smallest size possible). This allows you to see a relative scale of the model. Most are placed within the level area but some are much larger than the area.
* Many of these images are not exactly to scale, the idea is to see what the image looks like rather than to see the exact size to scale.
* Some model images such as ceilings and roofs will be taken from underneath looking into the sky.
* Some model images look the same but are of different size.
* Some models extend below the grounds surface when placed.
* The models in this sheet are architectural and environmental. Models that are props, placeables, fx, body parts etc can all be viewed in other areas of the toolset.

== Black Boxes ==

<gallery>
File:Blk 01 0.jpg|Blk 01 0
File:Blk 02 0.jpg|Blk 02 0
File:Blk 03 0.jpg|Blk 03 0
File:Blk 04 0.jpg|Blk 04 0
File:Blk 05 0.jpg|Blk 05 0
File:Blk 06 0.jpg|Blk 06 0
File:Blk 07 0.jpg|Blk 07 0
File:Blk 08 0.jpg|Blk 08 0
</gallery>

== Cave ==

<gallery>
File:Cai lrgcrna 0.jpg | cai lrgcrna 0
File:Cai lrgcrnb 0.jpg | cai lrgcrnb 0
File:Cai lrgdoor02 0.jpg | cai lrgdoor02 0
File:Cai lrgdoor03 0.jpg | cai lrgdoor03 0
File:Cai lrgdoor 0.jpg | cai lrgdoor 0
File:Cai lrgfloorb 0.jpg | cai lrgfloorb 0
File:Cai lrgroofa 0.jpg | cai lrgroofa 0
File:Cai lrgroofb 0.jpg | cai lrgroofb 0
File:Cai lrgwalla 0.jpg | cai lrgwalla 0
File:Cai lrgwallaweb2 0.jpg | cai lrgwallaweb2 0
File:Cai lrgwallaweb 0.jpg | cai lrgwallaweb 0
File:Cai lrgwallb 0.jpg | cai lrgwallb 0
File:Cai pillara 0.jpg | cai pillara 0
File:Cai pillaraweb 0.jpg | cai pillaraweb 0
File:Cai rock01 0.jpg | cai rock01 0
File:Cai totci01 0.jpg | cai totci01 0
File:Cai tuncurve02 0.jpg | cai tuncurve02 0
File:Cai tuncurve03 0.jpg | cai tuncurve03 0
File:Cai tunmed01 0.jpg | cai tunmed01 0
File:Cai tunn401 0.jpg | cai tunn401 0
File:Cai tunnend02 0.jpg | cai tunnend02 0
File:Cai tunnstrt01 0.jpg | cai tunnstrt01 0
File:Cai tunnstrt02 0.jpg | cai tunnstrt02 0
File:Cai tunnstrt03 0.jpg | cai tunnstrt03 0
File:Cai tunnstrt04 0.jpg | cai tunnstrt04 0
File:Cai tunnt01 0.jpg | cai tunnt01 0
File:Cai tunslope01 0.jpg | cai tunslope01 0
</gallery>

<gallery>
File:Cav bridge.jpg | cav bridge
File:Cav brkhallb 0.jpg | cav brkhallb 0
File:Cav brknwall c 0.jpg | cav brknwall c 0
File:Cav caiboulder01 0.jpg | cav caiboulder01 0
File:Cav caiboulder02 0.jpg | cav caiboulder02 0
File:Cav caiboulder03 0.jpg | cav caiboulder03 0
File:Cav caiplatform01 0.jpg | cav caiplatform01 0
File:Cav caiplatform02 0.jpg | cav caiplatform02 0
File:Cav caiplatform03 0.jpg | cav caiplatform03 0
File:Cav caiplatform04 0.jpg | cav caiplatform04 0
File:Cav caiwall01 0.jpg | cav caiwall01 0
File:Cav caiwall02 0.jpg | cav caiwall02 0
File:Cav caiwall03 0.jpg | cav caiwall03 0
File:Cav caiwall04 0.jpg | cav caiwall04 0
File:Cav caiwall05 0.jpg | cav caiwall05 0
File:Cav caiwall06 0.jpg | cav caiwall06 0
File:Cav caverocks01 0.jpg | cav caverocks01 0
File:Cav caverocks02 0.jpg | cav caverocks02 0
File:Cav caverocks03 0.jpg | cav caverocks03 0
File:Cav caverocks04 0.jpg | cav caverocks04 0
File:Cav cliffa.jpg | cav cliffa
File:Cav cliffb.jpg | cav cliffb
File:Cav cliffc.jpg | cav cliffc
File:Cav cliffe.jpg | cav cliffe
File:Cav cliffh.jpg | cav cliffh
File:Cav cliffk.jpg | cav cliffk
File:Cav dwhole01.jpg | cav dwhole01
File:Cav floor01.jpg | cav floor01
File:Cav floor02.jpg | cav floor02
File:Cav floor03.jpg | cav floor03
File:Cav floor04.jpg | cav floor04
File:Cav hallplug01.jpg | cav hallplug01
File:Cav lrgcrna.jpg | cav lrgcrna
File:Cav lrgcrnb.jpg | cav lrgcrnb
File:Cav lrgdoor.jpg | cav lrgdoor
File:Cav lrgdoor02.jpg | cav lrgdoor02
File:Cav lrgdoor03.jpg | cav lrgdoor03
File:Cav lrgfloor.jpg | cav lrgfloor
File:Cav lrgwalla.jpg | cav lrgwalla
File:Cav pillar.jpg | cav pillar
File:Cav rock01.jpg | cav rock01
File:Cav rockfloor01 0.jpg | cav rockfloor01 0
File:Cav rockfloor02 0.jpg | cav rockfloor02 0
File:Cav rockfloor03 0.jpg | cav rockfloor03 0
File:Cav rockwall01 0.jpg | cav rockwall01 0
File:Cav rockwall02 0.jpg | cav rockwall02 0
File:Cav rockwall03 0.jpg | cav rockwall03 0
File:Cav rockwall08 0.jpg | cav rockwall08 0
File:Cav rockwall09 0.jpg | cav rockwall09 0
File:Cav rockwall10 0.jpg | cav rockwall10 0
File:Cav roof.jpg | cav roof
File:Cav stalactite01 0.jpg | cav stalactite01 0
File:Cav stalactite02 0.jpg | cav stalactite02 0
File:Cav stalactite04 0.jpg | cav stalactite04 0
File:Cav stalactite05 0.jpg | cav stalactite05 0
File:Cav stalagmite01 0.jpg | cav stalagmite01 0
File:Cav stalagmite05 0.jpg | cav stalagmite05 0
File:Cav stalagmite06 0.jpg | cav stalagmite06 0
File:Cav stalagpillar05 0.jpg | cav stalagpillar05 0
File:Cav todwi.jpg | cav todwi
File:Cav tuncurve01.jpg | cav tuncurve01
File:Cav tuncurve02.jpg | cav tuncurve02
File:Cav tunend.jpg | cav tunend
File:Cav tunend02.jpg | cav tunend02
File:Cav tunfour.jpg | cav tunfour
File:Cav tunslope01.jpg | cav tunslope01
File:Cav tunslope02.jpg | cav tunslope02
File:Cav tunslope03.jpg | cav tunslope03
File:Cav tunstr01.jpg | cav tunstr01
File:Cav tunstr02.jpg | cav tunstr02
File:Cav tuntee.jpg | cav tuntee
File:Cav tunwhite.jpg | cav tunwhite
File:Cav wallhole c 0.jpg | cav wallhole c 0
</gallery>

== Cave Deep Road ==

<gallery>
File:Cdr dwi deepr brkn 0.jpg|cdr dwi deepr brkn 0
File:Cdr dwi deepr cave1 0.jpg|cdr dwi deepr cave1 0
File:Cdr dwi deepr cave2 0.jpg|cdr dwi deepr cave2 0
File:Cdr dwi deepr cent 0.jpg|cdr dwi deepr cent 0
File:Cdr dwi deepr cntr 0.jpg|cdr dwi deepr cntr 0
File:Cdr dwi deepr crn 0.jpg|cdr dwi deepr crn 0
File:Cdr dwi deepr door 0.jpg|cdr dwi deepr door 0
File:Cdr dwi deepr exit 0.jpg|dr dwi deepr exit 0
File:Cdr dwi deepr guls 0.jpg|dr dwi deepr guls 0
File:Cdr dwi deepr tsec 0.jpg|dr dwi deepr tsec 0
</gallery>

== Chantry Exterior ==

<gallery>
File:Che chapllar01 0.jpg|che chapllar01 0
File:Che chapllar02 0.jpg|che chapllar02 0
File:Che largebase 0.jpg|che largebase 0
File:Che largeglass 0.jpg|che largeglass 0
File:Che largetop 0.jpg|che largetop 0
File:Che smallbase 0.jpg|che smallbase 0
File:Che smallglass 0.jpg|che smallglass 0
File:Che smalltop 0.jpg|che smalltop 0
</gallery>

== Chantry Interior ==

<gallery>
File:Chi chaarch.jpg | Chi chaarch
File:Chi chaarch01.jpg | Chi chaarch01
File:Chi chaarea 0.jpg | Chi chaarea 0
File:Chi chaarea 1.jpg | Chi chaarea 1
File:Chi chaarea 2.jpg | Chi chaarea 2
File:Chi chaarea 3.jpg | Chi chaarea 3
File:Chi chaceiling01.jpg | Chi chaceiling01
File:Chi chaceiling02.jpg | Chi chaceiling02
File:Chi chadesign01.jpg | Chi chadesign01
File:Chi chadesign01a.jpg | Chi chadesign01a
File:Chi chadesign02.jpg | Chi chadesign02
File:Chi chadesign03.jpg | Chi chadesign03
File:Chi chadesign04.jpg | Chi chadesign04
File:Chi chafloor01.jpg | Chi chafloor01
File:Chi chafloor03.jpg | Chi chafloor03
File:Chi chapillar01.jpg | Chi chapillar01
File:Chi chapillar03.jpg | Chi chapillar03
File:Chi chapillar04.jpg | Chi chapillar04
File:Chi chapltfrm.jpg | Chi chapltfrm
File:Chi chapltfrm 0.jpg | Chi chapltfrm 0
File:Chi chascafold.jpg | Chi chascafold
File:Chi chascafold02.jpg | Chi chascafold02
File:Chi chasun.jpg | Chi chasun
File:Chi chawall01.jpg | Chi chawall01
File:Chi chawall01a.jpg | Chi chawall01a
File:Chi chawall02.jpg | Chi chawall02
File:Chi chawall02a.jpg | Chi chawall02a
File:Chi chawall03.jpg | Chi chawall03
File:Chi chawall03a.jpg | Chi chawall03a
File:Chi chawall04.jpg | Chi chawall04
File:Chi chawall06.jpg | Chi chawall06
File:Chi chawall07.jpg | Chi chawall07
File:Chi chawall08.jpg | Chi chawall08
File:Chi chawall08a.jpg | Chi chawall08a
File:Chi chawall09.jpg | Chi chawall09
File:Chi chawall10.jpg | Chi chawall10
File:Chi chawall11.jpg | Chi chawall11
File:Chi chawin01.jpg | Chi chawin01
File:Chi chawindow.jpg | Chi chawindow
File:Chi smblkwalla.jpg | Chi smblkwalla
</gallery>

== Dwarf Slum Exterior ==

<gallery>
File:Dse home01 0.jpg |Dse home01 0
File:Dse home02 0.jpg |Dse home02 0
File:Dse home03 0.jpg |Dse home03 0
File:Dse home04 0.jpg |Dse home04 0
File:Dse home05 0.jpg |Dse home05 0
File:Dse home06 0.jpg |Dse home06 0
File:Dse home07 0.jpg |Dse home07 0
File:Dse home08 0.jpg |Dse home08 0
File:Dse pillar01 0.jpg |Dse pillar01 0
File:Dse pillar02 0.jpg |Dse pillar02 0
</gallery>

== Dwarf Slum Interior ==

<gallery>
File:Dsi dtroom cnri01.jpg | dsi dtroom cnri01
File:Dsi dtroom cnro01.jpg | dsi dtroom cnro01
File:Dsi dtroom door01.jpg | dsi dtroom door01
File:Dsi dtroom door02.jpg | dsi dtroom door02
File:Dsi dtroom flor01.jpg | dsi dtroom flor01
File:Dsi dtroom halel02.jpg | dsi dtroom halel02
File:Dsi dtroom haler02.jpg | dsi dtroom haler02
File:Dsi dtroom strt01.jpg | dsi dtroom strt01
File:Dsi slumroof 01.jpg | dsi slumroof 01
File:Dsi slumroof 02.jpg | dsi slumroof 02
File:Dsi slumroom cnri01.jpg | dsi slumroom cnri01
File:Dsi slumroom cnro01.jpg | dsi slumroom cnro01
File:Dsi slumroom door01.jpg | dsi slumroom door01
File:Dsi slumroom door02.jpg | dsi slumroom door02
File:Dsi slumroom flor01.jpg | dsi slumroom flor01
File:Dsi slumroom flor02.jpg | dsi slumroom flor02
File:Dsi slumroom hal301.jpg | dsi slumroom hal301
File:Dsi slumroom hal401.jpg | dsi slumroom hal401
File:Dsi slumroom halb01.jpg | dsi slumroom halb01
File:Dsi slumroom hale01.jpg | dsi slumroom hale01
File:Dsi slumroom halel01.jpg | dsi slumroom halel01
File:Dsi slumroom halel02.jpg | dsi slumroom halel02
File:Dsi slumroom haler01.jpg | dsi slumroom haler01
File:Dsi slumroom haler02.jpg | dsi slumroom haler02
File:Dsi slumroom halr 0.jpg | dsi slumroom halr 0
File:Dsi slumroom hals01.jpg | dsi slumroom hals01
File:Dsi slumroom stair01.jpg | dsi slumroom stair01
File:Dsi slumroom stair02.jpg | dsi slumroom stair02
File:Dsi slumroom stair03.jpg | dsi slumroom stair03
File:Dsi slumroom stair04.jpg | dsi slumroom stair04
File:Dsi slumroom strt01.jpg | dsi slumroom strt01
File:Dsi slumroom strt02.jpg | dsi slumroom strt02
File:Dsi slumroom tomb01.jpg | dsi slumroom tomb01
</gallery>

== Fereldan Castle ==

<gallery>
File:Fca arch01 0.jpg | fca arch01 0
File:Fca arch02 0.jpg | fca arch02 0
File:Fca arch03 0.jpg | fca arch03 0
File:Fca archfade01 0.jpg | fca archfade01 0
File:Fca archfade02 0.jpg | fca archfade02 0
File:Fca balcony01 0.jpg | fca balcony01 0
File:Fca balcony02 0.jpg | fca balcony02 0
File:Fca balcony03 0.jpg | fca balcony03 0
File:Fca balcony04 0.jpg | fca balcony04 0
File:Fca c redbridge 0.jpg | fca c redbridge 0
File:Fca c redbridge 1.jpg | fca c redbridge 1
File:Fca c redcastle 1.jpg | fca c redcastle 1
File:Fca ceiling01 0.jpg | fca ceiling01 0
File:Fca ceiling02 0.jpg | fca ceiling02 0
File:Fca ceiling03 0.jpg | fca ceiling03 0
File:Fca ceiling04 0.jpg | fca ceiling04 0
File:Fca ceiling05 0.jpg | fca ceiling05 0
File:Fca chimney 0.jpg | fca chimney 0
File:Fca corr01 0.jpg | fca corr01 0
File:Fca corr02 0.jpg | fca corr02 0
File:Fca corr03 0.jpg | fca corr03 0
File:Fca corr04 0.jpg | fca corr04 0
File:Fca corr05 0.jpg | fca corr05 0
File:Fca corr06 0.jpg | fca corr06 0
File:Fca corr07 0.jpg | fca corr07 0
File:Fca corr08 0.jpg | fca corr08 0
File:Fca corrdr01 0.jpg | fca corrdr01 0
File:Fca corrdr02 0.jpg | fca corrdr02 0
File:Fca corrtop01 0.jpg | fca corrtop01 0
File:Fca corrtop02 0.jpg | fca corrtop02 0
File:Fca corrtop03 0.jpg | fca corrtop03 0
File:Fca corrtop04 0.jpg | fca corrtop04 0
File:Fca corrtop05 0.jpg | fca corrtop05 0
File:Fca corrtop06 0.jpg | fca corrtop06 0
File:Fca corrtop07 0.jpg | fca corrtop07 0
File:Fca corrtop08 0.jpg | fca corrtop08 0
File:Fca corrtop09 0.jpg | fca corrtop09 0
File:Fca corrtop10 0.jpg | fca corrtop10 0
File:Fca corrtop11 0.jpg | fca corrtop11 0
File:Fca corrtop12 0.jpg | fca corrtop12 0
File:Fca corrwall01 0.jpg | fca corrwall01 0
File:Fca corrwall02 0.jpg | fca corrwall02 0
File:Fca corrwall03 0.jpg | fca corrwall03 0
File:Fca corrwall04 0.jpg | fca corrwall04 0
File:Fca door01 0.jpg | fca door01 0
File:Fca door02 0.jpg | fca door02 0
File:Fca door03 0.jpg | fca door03 0
File:Fca door04 0.jpg | fca door04 0
File:Fca door05 0.jpg | fca door05 0
File:Fca floor01 0.jpg | fca floor01 0
File:Fca floor02 0.jpg | fca floor02 0
File:Fca keystone01 0.jpg | fca keystone01 0
File:Fca lrgwall01 0.jpg | fca lrgwall01 0
File:Fca lrgwall02 0.jpg | fca lrgwall02 0
File:Fca lrgwall03 0.jpg | fca lrgwall03 0
File:Fca lrgwall04 0.jpg | fca lrgwall04 0
File:Fca lrgwall05 0.jpg | fca lrgwall05 0
File:Fca lrgwall06 0.jpg | fca lrgwall06 0
File:Fca lrgwall07 0.jpg | fca lrgwall07 0
File:Fca lrgwall08 0.jpg | fca lrgwall08 0
File:Fca outwall01 0.jpg | fca outwall01 0
File:Fca outwall02 0.jpg | fca outwall02 0
File:Fca pillar01 0.jpg | fca pillar01 0
File:Fca pillar02 0.jpg | fca pillar02 0
File:Fca pillar03 0.jpg | fca pillar03 0
File:Fca pillar04 0.jpg | fca pillar04 0
File:Fca pillar05 0.jpg | fca pillar05 0
File:Fca pillar06 0.jpg | fca pillar06 0
File:Fca stand 0.jpg | fca stand 0
File:Fca tower01 0.jpg | fca tower01 0
File:Fca wall01 0.jpg | fca wall01 0
File:Fca wall02 0.jpg | fca wall02 0
File:Fca wall03 0.jpg | fca wall03 0
File:Fca wall04 0.jpg | fca wall04 0
File:Fca wallplug01 0.jpg | fca wallplug01 0
File:Fca wallplug02 0.jpg | fca wallplug02 0
File:Fca wallplug03 0.jpg | fca wallplug03 0
File:Fca wallplug04 0.jpg | fca wallplug04 0
File:Fca wallplug05 0.jpg | fca wallplug05 0
File:Fca wdbeam01 0.jpg | fca wdbeam01 0
File:Fca wdbeam02 0.jpg | fca wdbeam02 0
File:Fca wdbeam03 0.jpg | fca wdbeam03 0
</gallery>

== Fereldan Castle Exterior ==

<gallery>
File:Fce estwall 05 0.jpg|fce estwall 05 0
File:Fce estwall 05 1.jpg|fce estwall 05 1
File:Fce pubsgn01 0.jpg|fce pubsgn01 0
</gallery>

== Fereldan Castle Interior ==

<gallery>
File:Fci archf 01.jpg | fci archf 01
File:Fci bwall 02.jpg | fci bwall 02
File:Fci bwall 05.jpg | fci bwall 05
File:Fci castarch 01.jpg | fci castarch 01
File:Fci castarch 02.jpg | fci castarch 02
File:Fci castarch 05.jpg | fci castarch 05
File:Fci castctop door01.jpg | fci castctop door01
File:Fci ceila 05.jpg | fci ceila 05
File:Fci ceila 14.jpg | fci ceila 14
File:Fci ceila 15.jpg | fci ceila 15
File:Fci ceila 16.jpg | fci ceila 16
File:Fci ceila 24.jpg | fci ceila 24
File:Fci ceila 34.jpg | fci ceila 34
File:Fci floor 01.jpg | fci floor 01
File:Fci floor 04.jpg | fci floor 04
File:Fci part 02.jpg | fci part 02
File:Fci part 06.jpg | fci part 06
File:Fci part 08.jpg | fci part 08
File:Fci pil 01.jpg | fci pil 01
File:Fci pil 05.jpg | fci pil 05
File:Fci roof 02.jpg | fci roof 02
File:Fci roof 04.jpg | fci roof 04
File:Fci roof 06.jpg | fci roof 06
File:Fci rubble 01.jpg | fci rubble 01
File:Fci rubble 02.jpg | fci rubble 02
File:Fci tower 01.jpg | fci tower 01
File:Fci wall 01.jpg | fci wall 01
File:Fci wall 02.jpg | fci wall 02
File:Fci wall 04.jpg | fci wall 04
File:Fci wall 05.jpg | fci wall 05
File:Fci wall 07.jpg | fci wall 07
File:Fci wall 10.jpg | fci wall 10
File:Fci wall 12.jpg | fci wall 12
File:Fci wall 14.jpg | fci wall 14
File:Fci wall 15.jpg | fci wall 15
File:Fci wall 16.jpg | fci wall 16
File:Fci wall 24.jpg | fci wall 24
File:Fci wall 30.jpg | fci wall 30
File:Fci wall 34.jpg | fci wall 34
</gallery>

<gallery>
File:Frt main 0.jpg|frt main 0
File:Frt main plc 0.jpg|frt main plc 0
File:Frt main rest 0.jpg|frt main rest 0
File:Frt main wall 0.jpg|frt main wall 0
</gallery>

== Fereldan Dungeon Interior ==

<gallery>
File:Fdi dun3wy 0.jpg | fdi dun3wy 0
File:Fdi dun4pillars 0.jpg | fdi dun4pillars 0
File:Fdi dun4wy 0.jpg | fdi dun4wy 0
File:Fdi dun90deg 0.jpg | fdi dun90deg 0
File:Fdi dunbars 0.jpg | fdi dunbars 0
File:Fdi duncell 0.jpg | fdi duncell 0
File:Fdi duncorn 01 0.jpg | fdi duncorn 01 0
File:Fdi dundoor 01 0.jpg | fdi dundoor 01 0
File:Fdi dundoor 02 0.jpg | fdi dundoor 02 0
File:Fdi dunend 0.jpg | fdi dunend 0
File:Fdi dunfloor01 0.jpg | fdi dunfloor01 0
File:Fdi dungate 0.jpg | fdi dungate 0
File:Fdi dunnarr 01 0.jpg | fdi dunnarr 01 0
File:Fdi dunnarr 02 0.jpg | fdi dunnarr 02 0
File:Fdi dunrock01 0.jpg | fdi dunrock01 0
File:Fdi dunrock02 0.jpg | fdi dunrock02 0
File:Fdi dunrock03 0.jpg | fdi dunrock03 0
File:Fdi dunrock04 0.jpg | fdi dunrock04 0
File:Fdi dunroof01 0.jpg | fdi dunroof01 0
File:Fdi dunroof02 0.jpg | fdi dunroof02 0
File:Fdi dunstair01 0.jpg | fdi dunstair01 0
File:Fdi dunstair02 0.jpg | fdi dunstair02 0
File:Fdi dunstrait 0.jpg | fdi dunstrait 0
File:Fdi dunwall01 0.jpg | fdi dunwall01 0
File:Fdi dunwall02 0.jpg | fdi dunwall02 0
</gallery>

== Fereldan Human Exterior ==

<gallery>
File:Fhe balccrna 0.jpg | fhe balccrna 0
File:Fhe balccrnb 0.jpg | fhe balccrnb 0
File:Fhe balcmid 0.jpg | fhe balcmid 0
File:Fhe barnscaffa 0.jpg | fhe barnscaffa 0
File:Fhe barnscaffb 0.jpg | fhe barnscaffb 0
File:Fhe bridgebase 0.jpg | fhe bridgebase 0
File:Fhe bridgestn 0.jpg | fhe bridgestn 0
File:Fhe canopy01 0.jpg | fhe canopy01 0
File:Fhe canopy02 0.jpg | fhe canopy02 0
File:Fhe cantlvr 0.jpg | fhe cantlvr 0
File:Fhe chandrs 0.jpg | fhe chandrs 0
File:Fhe chim 0.jpg | fhe chim 0
File:Fhe coop 0.jpg | fhe coop 0
File:Fhe cotta 0.jpg | fhe cotta 0
File:Fhe cottb 0.jpg | fhe cottb 0
File:Fhe cottc 0.jpg | fhe cottc 0
File:Fhe cottd 0.jpg | fhe cottd 0
File:Fhe cotte 0.jpg | fhe cotte 0
File:Fhe decfull 0.jpg | fhe decfull 0
File:Fhe dechlf 0.jpg | fhe dechlf 0
File:Fhe doorfrs 0.jpg | fhe doorfrs 0
File:Fhe fence01 0.jpg | fhe fence01 0
File:Fhe midbev 0.jpg | fhe midbev 0
File:Fhe midins 0.jpg | fhe midins 0
File:Fhe midrnd 0.jpg | fhe midrnd 0
File:Fhe midslant 0.jpg | fhe midslant 0
File:Fhe midsm 0.jpg | fhe midsm 0
File:Fhe midsq 0.jpg | fhe midsq 0
File:Fhe midtall 0.jpg | fhe midtall 0
File:Fhe rampplank 0.jpg | fhe rampplank 0
File:Fhe rivrbnk 0.jpg | fhe rivrbnk 0
File:Fhe rockb2 0.jpg | fhe rockb2 0
File:Fhe roofcrn 0.jpg | fhe roofcrn 0
File:Fhe roofcrnsm 0.jpg | fhe roofcrnsm 0
File:Fhe roofcrntht 0.jpg | fhe roofcrntht 0
File:Fhe roofpl 0.jpg | fhe roofpl 0
File:Fhe roofplpk 0.jpg | fhe roofplpk 0
File:Fhe roofthtpk 0.jpg | fhe roofthtpk 0
File:Fhe roofwin 0.jpg | fhe roofwin 0
File:Fhe rubble 0.jpg | fhe rubble 0
File:Fhe scaff 0.jpg | fhe scaff 0
File:Fhe shuta 0.jpg | fhe shuta 0
File:Fhe shutb 0.jpg | fhe shutb 0
File:Fhe slum01 0.jpg | fhe slum01 0
File:Fhe slum02 0.jpg | fhe slum02 0
File:Fhe slum04 0.jpg | fhe slum04 0
File:Fhe slum05 0.jpg | fhe slum05 0
File:Fhe stiltl 0.jpg | fhe stiltl 0
File:Fhe stiltm 0.jpg | fhe stiltm 0
File:Fhe stiltn 0.jpg | fhe stiltn 0
File:Fhe stilts 0.jpg | fhe stilts 0
File:Fhe truss 0.jpg | fhe truss 0
File:Fhe walkl02 0.jpg | fhe walkl02 0
File:Fhe walkl 0.jpg | fhe walkl 0
File:Fhe walkm02 0.jpg | fhe walkm02 0
File:Fhe walkm 0.jpg | fhe walkm 0
File:Fhe wall01 0.jpg | fhe wall01 0
File:Fhe wall02 0.jpg | fhe wall02 0
File:Fhe wall03 0.jpg | fhe wall03 0
File:Fhe walljoint 0.jpg | fhe walljoint 0
File:Fhe winl 0.jpg | fhe winl 0
File:Fhe wins 0.jpg | fhe wins 0
File:Fhe wtrwhl 0.jpg | fhe wtrwhl 0
</gallery>

<gallery>
File:Fhec bgcliffa 0.jpg |fhec bgcliffa 0
File:Fhec bgcliffb 0.jpg |fhec bgcliffb 0
File:Fhec bgcliffc 0.jpg |fhec bgcliffc 0
File:Fhec redmill02 0.jpg |fhec redmill02 0
File:Fhec redmill 0.jpg |fhec redmill 0
File:Fhec redvilla 0.jpg |fhec redvilla 0
File:Fhec redvillb 0.jpg |fhec redvillb 0
File:Fhec redvillc 0.jpg |fhec redvillc 0
File:Fhec redvilld 0.jpg |fhec redvilld 0
File:Fhec redville 0.jpg |fhec redville 0
File:Fhec redvillf 0.jpg |fhec redvillf 0
File:Fhec redvillk 0.jpg |fhec redvillk 0
File:Fhec redvilll 0.jpg |fhec redvilll 0
File:Fhec redvillm 0.jpg |fhec redvillm 0
File:Fhec tavernbody 0.jpg |fhec tavernbody 0
File:Fhec tavernroof1 0.jpg |fhec tavernroof1 0
File:Fhec tavernroof2 0.jpg |fhec tavernroof2 0
File:Fhec tavernroof3 0.jpg |fhec tavernroof3 0
File:Fhec tavernsup 0.jpg |fhec tavernsup 0
File:Fhec windmillbody 0.jpg|fhec windmillbody 0
File:Fhec windmilldoor 0.jpg|fhec windmilldoor 0
File:Fhec windmilltop 0.jpg |fhec windmilltop 0
File:Fhec windmillwhl 0.jpg |fhec windmillwhl 0
</gallery>

== Fereldan Human Interior ==

<gallery>
File:Fhi ceiling2 0.jpg | fhi ceiling2 0
File:Fhi ceiling 0.jpg | fhi ceiling 0
File:Fhi ceilingangle 0.jpg | fhi ceilingangle 0
File:Fhi floorstone1x3a 0.jpg | fhi floorstone1x3a 0
File:Fhi floorstone1x3b 0.jpg | fhi floorstone1x3b 0
File:Fhi floorstone3x3 0.jpg | fhi floorstone3x3 0
File:Fhi floorstone 0.jpg | fhi floorstone 0
File:Fhi floorstoneedge 0.jpg | fhi floorstoneedge 0
File:Fhi floorstonestrip 0.jpg | fhi floorstonestrip 0
File:Fhi floorwood1x3 0.jpg | fhi floorwood1x3 0
File:Fhi floorwood3x3 0.jpg | fhi floorwood3x3 0
File:Fhi floorwood 0.jpg | fhi floorwood 0
File:Fhi floorwoodstrip 0.jpg | fhi floorwoodstrip 0
File:Fhi pillarbracket 0.jpg | fhi pillarbracket 0
File:Fhi pillarstone 0.jpg | fhi pillarstone 0
File:Fhi pillarwood2 0.jpg | fhi pillarwood2 0
File:Fhi pillarwood3 0.jpg | fhi pillarwood3 0
File:Fhi pillarwood 0.jpg | fhi pillarwood 0
File:Fhi prp barleft 0.jpg | fhi prp barleft 0
File:Fhi prp barright 0.jpg | fhi prp barright 0
File:Fhi prp bendbox 0.jpg | fhi prp bendbox 0
File:Fhi prp bendboxlg 0.jpg | fhi prp bendboxlg 0
File:Fhi prp box 0.jpg | fhi prp box 0
File:Fhi prp boxcandles 0.jpg | fhi prp boxcandles 0
File:Fhi prp boxsm 0.jpg | fhi prp boxsm 0
File:Fhi prp cabinet 0.jpg | fhi prp cabinet 0
File:Fhi prp cratelid 0.jpg | fhi prp cratelid 0
File:Fhi prp crateopen 0.jpg | fhi prp crateopen 0
File:Fhi prp mid 0.jpg | fhi prp mid 0
File:Fhi prp shelfwall l 0.jpg | fhi prp shelfwall l 0
File:Fhi prp shelfwall m 0.jpg | fhi prp shelfwall m 0
File:Fhi prp wheel 0.jpg | fhi prp wheel 0
File:Fhi stairswood 0.jpg | fhi stairswood 0
File:Fhi stiarsdown 0.jpg | fhi stiarsdown 0
File:Fhi upper 0.jpg | fhi upper 0
File:Fhi upperanglel 0.jpg | fhi upperanglel 0
File:Fhi upperangler 0.jpg | fhi upperangler 0
File:Fhi upperbeam 0.jpg | fhi upperbeam 0
File:Fhi upperhalf 0.jpg | fhi upperhalf 0
File:Fhi upperpillar 0.jpg | fhi upperpillar 0
File:Fhi upperpillarwd 0.jpg | fhi upperpillarwd 0
File:Fhi wallarchway 0.jpg | fhi wallarchway 0
File:Fhi wallbasict 0.jpg | fhi wallbasict 0
File:Fhi wallcornerin 0.jpg | fhi wallcornerin 0
File:Fhi wallcornerout 0.jpg | fhi wallcornerout 0
File:Fhi wallcrackl 0.jpg | fhi wallcrackl 0
File:Fhi wallcrackr 0.jpg | fhi wallcrackr 0
File:Fhi walldoor 0.jpg | fhi walldoor 0
File:Fhi wallfireplace 0.jpg | fhi wallfireplace 0
File:Fhi wallhalf 0.jpg | fhi wallhalf 0
File:Fhi wallinset 0.jpg | fhi wallinset 0
File:Fhi wallpillar 0.jpg | fhi wallpillar 0
File:Fhi wallrailhalf 0.jpg | fhi wallrailhalf 0
File:Fhi wallrailing 0.jpg | fhi wallrailing 0
File:Fhi wallshelf 0.jpg | fhi wallshelf 0
File:Fhi wallshort 0.jpg | fhi wallshort 0
File:Fhi wallstone 0.jpg | fhi wallstone 0
File:Fhi walluppershort 0.jpg | fhi walluppershort 0
File:Fhi wallwindow 0.jpg | fhi wallwindow 0
</gallery>

== Fereldan Town Interior ==

<gallery>
File:Fti balckbox 0.jpg | fti balckbox 0
File:Fti balckboxlong 0.jpg | fti balckboxlong 0
File:Fti ceilingangle 0.jpg | fti ceilingangle 0
File:Fti ceilingangles 0.jpg | fti ceilingangles 0
File:Fti ceilingpanles 0.jpg | fti ceilingpanles 0
File:Fti ceilingrustic25 0.jpg | fti ceilingrustic25 0
File:Fti ceilingrustic 0.jpg | fti ceilingrustic 0
File:Fti cwind up curve 0.jpg | fti cwind up curve 0
File:Fti cwind up flat 0.jpg | fti cwind up flat 0
File:Fti cwindmilldoor 0.jpg | fti cwindmilldoor 0
File:Fti cwindmillfloor 0.jpg | fti cwindmillfloor 0
File:Fti cwindmillfw 0.jpg | fti cwindmillfw 0
File:Fti cwindmillfwall 0.jpg | fti cwindmillfwall 0
File:Fti door 0.jpg | fti door 0
File:Fti doorrustic 0.jpg | fti doorrustic 0
File:Fti fireplace a 0.jpg | fti fireplace a 0
File:Fti fireplace b 0.jpg | fti fireplace b 0
File:Fti floorstone 0.jpg | fti floorstone 0
File:Fti floorstonestrip 0.jpg | fti floorstonestrip 0
File:Fti floortrim 0.jpg | fti floortrim 0
File:Fti floorwood2 0.jpg | fti floorwood2 0
File:Fti floorwood3 0.jpg | fti floorwood3 0
File:Fti floorwood 0.jpg | fti floorwood 0
File:Fti floorwoodsmall2 0.jpg | fti floorwoodsmall2 0
File:Fti floorwoodsmall3 0.jpg | fti floorwoodsmall3 0
File:Fti floorwoodsmall 0.jpg | fti floorwoodsmall 0
File:Fti pillarpanels 0.jpg | fti pillarpanels 0
File:Fti pillarstone 0.jpg | fti pillarstone 0
File:Fti prp barl 0.jpg | fti prp barl 0
File:Fti prp barmid 0.jpg | fti prp barmid 0
File:Fti prp barr 0.jpg | fti prp barr 0
File:Fti prp barrusticm 0.jpg | fti prp barrusticm 0
File:Fti stairswood 0.jpg | fti stairswood 0
File:Fti upper 0.jpg | fti upper 0
File:Fti upperanglel 0.jpg | fti upperanglel 0
File:Fti upperangler 0.jpg | fti upperangler 0
File:Fti upperbeam 0.jpg | fti upperbeam 0
File:Fti upperboarda 0.jpg | fti upperboarda 0
File:Fti upperboardb 0.jpg | fti upperboardb 0
File:Fti upperboardc 0.jpg | fti upperboardc 0
File:Fti upperplain 0.jpg | fti upperplain 0
File:Fti uppershort 0.jpg | fti uppershort 0
File:Fti upperwoodbeam 0.jpg | fti upperwoodbeam 0
File:Fti wall 0.jpg | fti wall 0
File:Fti wallarchrustic 0.jpg | fti wallarchrustic 0
File:Fti wallbarrel 0.jpg | fti wallbarrel 0
File:Fti wallcapa 0.jpg | fti wallcapa 0
File:Fti wallcapb 0.jpg | fti wallcapb 0
File:Fti wallhalf 0.jpg | fti wallhalf 0
File:Fti wallinset 0.jpg | fti wallinset 0
File:Fti wallpanels 0.jpg | fti wallpanels 0
File:Fti wallpanelshalf 0.jpg | fti wallpanelshalf 0
File:Fti wallrailing 0.jpg | fti wallrailing 0
File:Fti wallrailinghalf 0.jpg | fti wallrailinghalf 0
File:Fti wallrustic 0.jpg | fti wallrustic 0
File:Fti wallrustichalf 0.jpg | fti wallrustichalf 0
File:Fti wallshelfa 0.jpg | fti wallshelfa 0
File:Fti wallshelfb 0.jpg | fti wallshelfb 0
File:Fti wallstone 0.jpg | fti wallstone 0
File:Fti wallstonehalf 0.jpg | fti wallstonehalf 0
File:Fti wallwinrustic 0.jpg | fti wallwinrustic 0
</gallery>

== Fereldan Village Exterior ==

<gallery>
File:Fve roofcrn 0.jpg|fve roofcrn 0
File:Fve scaff 0.jpg|fve scaff 0
File:Fve stiltm 0.jpg|ve stiltm 0
File:Fve stiltn 0.jpg|fve stiltn 0
File:Fve stilts 0.jpg|fve stilts 0
File:Fve tavchim 0.jpg|fve tavchim 0
File:Fve windmill 0.jpg|fve windmill 0
</gallery>

== "Hero" Sets ==

These tiles consist of models that were custom-made for certain situations in the main campaign.

<gallery>
File:Hro anvil la01.jpg | hro anvil la01
File:Hro anvil la02.jpg | hro anvil la02
File:Hro brknwll dirt 0.jpg | hro brknwll dirt 0
File:Hro brknwll snow 0.jpg | hro brknwll snow 0
File:Hro cave anvil.jpg | hro cave anvil
File:Hro cave brdrooml.jpg | hro cave brdrooml
File:Hro deadtrencha 0.jpg | hro deadtrencha 0
File:Hro deadtrenchbr 0.jpg | hro deadtrenchbr 0
File:Hro den city1 1.jpg | hro den city1 1
File:Hro den city 1.jpg | hro den city 1
File:Hro den fdrak vst 1.jpg | hro den fdrak vst 1
File:Hro den fdrakdoor 0.jpg | hro den fdrakdoor 0
File:Hro den fdrakeag 0.jpg | hro den fdrakeag 0
File:Hro den fdrakmain 0.jpg | hro den fdrakmain 0
File:Hro den fdraktower 0.jpg | hro den fdraktower 0
File:Hro den fdrakyarddoor 0.jpg | hro den fdrakyarddoor 0
File:Hro den fortdrakon 0.jpg | hro den fortdrakon 0
File:Hro denfdrakonvtop 1.jpg | hro denfdrakonvtop 1
File:Hro dni asmblycore01.jpg | hro dni asmblycore01
File:Hro dni asmblysect01.jpg | hro dni asmblysect01
File:Hro dni asmblysect02.jpg | hro dni asmblysect02
File:Hro dni asmblysect04.jpg | hro dni asmblysect04
File:Hro dni asmblytwr01.jpg | hro dni asmblytwr01
File:Hro dni wr bdl 0.jpg | hro dni wr bdl 0
File:Hro dni wr bdr 0.jpg | hro dni wr bdr 0
File:Hro dni wr ce 0.jpg | hro dni wr ce 0
File:Hro dni wr cn 0.jpg | hro dni wr cn 0
File:Hro dni wr cnl 0.jpg | hro dni wr cnl 0
File:Hro dni wr dl 0.jpg | hro dni wr dl 0
File:Hro dni wr dr 0.jpg | hro dni wr dr 0
File:Hro dni wr fl 0.jpg | hro dni wr fl 0
File:Hro fci throne 0.jpg | hro fci throne 0
File:Hro hrt000a 0.jpg | hro hrt000a 0
File:Hro hrt000b 0.jpg | hro hrt000b 0
File:Hro hrt000c 0.jpg | hro hrt000c 0
File:Hro lak100water 0.jpg | hro lak100water 0
File:Hro lava04 0.jpg | hro lava04 0
File:Hro lava05 0.jpg | hro lava05 0
File:Hro lava06 0.jpg | hro lava06 0
File:Hro lava07 0.jpg | hro lava07 0
File:Hro lava08 0.jpg | hro lava08 0
File:Hro partypkr arch.jpg | hro partypkr arch
File:Hro partypkr floor.jpg | hro partypkr floor
File:Hro taiglava 01.jpg | hro taiglava 01
File:Hro taiglava 02.jpg | hro taiglava 02
File:Hro taiglava 03.jpg | hro taiglava 03
File:Hro taiglava 04.jpg | hro taiglava 04
File:Hro taigwater 01.jpg | hro taigwater 01
File:Hro taigwater 02.jpg | hro taigwater 02
File:Hro tci webwall 0.jpg | hro tci webwall 0
File:Hro treewalla 0.jpg | hro treewalla 0
File:Hro treewallb 0.jpg | hro treewallb 0
File:Hro tvi domepit 0.jpg | hro tvi domepit 0
File:Hro tvi webroof 0.jpg | hro tvi webroof 0
</gallery>

== Tevinter Castle Exterior ==

<gallery>
File:Tce elgstr03 0.jpg |tce elgstr03 0
File:Tce kinloch 1.jpg |tce kinloch 1
File:Tce rubptc 01 0.jpg |tce rubptc 01 0
File:Tce rubptc 01 1.jpg |tce rubptc 01 1
File:Tce wallsm 0.jpg |tce wallsm 0
</gallery>

== Tevinter Castle Interior ==

<gallery>
File:Tci bwall 01.jpg | tci bwall 01
File:Tci bwall 02.jpg | tci bwall 02
File:Tci bwall 03.jpg | tci bwall 03
File:Tci dirt 01.jpg | tci dirt 01
File:Tci lrgstair 01.jpg | tci lrgstair 01
File:Tci magestatue01 0.jpg | tci magestatue01 0
File:Tci magestatue02 0.jpg | tci magestatue02 0
File:Tci pil 08.jpg | tci pil 08
File:Tci pil 12.jpg | tci pil 12
File:Tci pil 13.jpg | tci pil 13
File:Tci pil 15.jpg | tci pil 15
File:Tci pil 16.jpg | tci pil 16
File:Tci smdoorw 01.jpg | tci smdoorw 01
File:Tci smdrfrme01 0.jpg | tci smdrfrme01 0
File:Tci smroof 01.jpg | tci smroof 01
File:Tci smroof 03.jpg | tci smroof 03
File:Tci smstair 01.jpg | tci smstair 01
File:Tci smwall 01.jpg | tci smwall 01
File:Tci smwall 02.jpg | tci smwall 02
File:Tci smwall 05.jpg | tci smwall 05
File:Tci smwall 06.jpg | tci smwall 06
File:Tci wall 01.jpg | tci wall 01
File:Tci wall 03.jpg | tci wall 03
File:Tci wall 21.jpg | tci wall 21
</gallery>

== Tevinter Fade Interior ==

<gallery>
File:Tfi doorplug 0.jpg | tfi doorplug 0
File:Tfi floorcori 0.jpg | tfi floorcori 0
File:Tfi floorcoricorn 0.jpg | tfi floorcoricorn 0
File:Tfi floorcorn 0.jpg | tfi floorcorn 0
File:Tfi flooredge 0.jpg | tfi flooredge 0
File:Tfi floorfar 0.jpg | tfi floorfar 0
File:Tfi floorinner 0.jpg | tfi floorinner 0
File:Tfi floorjunction 0.jpg | tfi floorjunction 0
File:Tfi floormid 0.jpg | tfi floormid 0
File:Tfi floorring 0.jpg | tfi floorring 0
File:Tfi floortile 0.jpg | tfi floortile 0
File:Tfi floortinter1 0.jpg | tfi floortinter1 0
File:Tfi halfpillar1 0.jpg | tfi halfpillar1 0
File:Tfi halfpillar1 01.jpg | tfi halfpillar1 01
File:Tfi halfpillar2 0.jpg | tfi halfpillar2 0
File:Tfi pillarfull1 0.jpg | tfi pillarfull1 0
File:Tfi pillarfull3 0.jpg | tfi pillarfull3 0
File:Tfi stairupinner 0.jpg | tfi stairupinner 0
File:Tfi support1 0.jpg | tfi support1 0
File:Tfi wallarchdbl 0.jpg | tfi wallarchdbl 0
File:Tfi wallblock1 0.jpg | tfi wallblock1 0
File:Tfi wallblock2 0.jpg | tfi wallblock2 0
File:Tfi wallblock 0.jpg | tfi wallblock 0
File:Tfi wallblocksm1 0.jpg | tfi wallblocksm1 0
File:Tfi wallblocksm2 0.jpg | tfi wallblocksm2 0
File:Tfi wallblocksm 0.jpg | tfi wallblocksm 0
File:Tfi wallcorridor1 0.jpg | tfi wallcorridor1 0
File:Tfi wallfar 0.jpg | tfi wallfar 0
File:Tfi wallfarhalf 0.jpg | tfi wallfarhalf 0
File:Tfi wallfull1 0.jpg | tfi wallfull1 0
File:Tfi wallfull2 0.jpg | tfi wallfull2 0
File:Tfi wallfulldoor1 0.jpg | tfi wallfulldoor1 0
File:Tfi wallfulldoor2 0.jpg | tfi wallfulldoor2 0
File:Tfi wallfulldoorb 0.jpg | tfi wallfulldoorb 0
File:Tfi wallhalf1 0.jpg | tfi wallhalf1 0
File:Tfi wallhalf2 0.jpg | tfi wallhalf2 0
File:Tfi wallhalfdoor1 0.jpg | tfi wallhalfdoor1 0
File:Tfi wallhalfdoor2 0.jpg | tfi wallhalfdoor2 0
File:Tfi wallhalfdoorb 0.jpg | tfi wallhalfdoorb 0
File:Tfi wallhigh1 0.jpg | tfi wallhigh1 0
File:Tfi wallmid1 0.jpg | tfi wallmid1 0
File:Tfi wallmid2 0.jpg | tfi wallmid2 0
File:Tfi wallmid3 0.jpg | tfi wallmid3 0
</gallery>

== Tevinter Tower Interior ==

<gallery>
File:tti doorarchl 0.jpg | tti doorarchl 0
File:tti doordblarchl1 0.jpg | tti doordblarchl1 0
File:tti doordblarchl2 0.jpg | tti doordblarchl2 0
File:tti doorplug 0.jpg | tti doorplug 0
File:tti floordais 0.jpg | tti floordais 0
File:tti floorfar 0.jpg | tti floorfar 0
File:tti floorfar d 0.jpg | tti floorfar d 0
File:tti floorhole d 0.jpg | tti floorhole d 0
File:tti floorinner 0.jpg | tti floorinner 0
File:tti floorinner d 0.jpg | tti floorinner d 0
File:tti floormid 0.jpg | tti floormid 0
File:tti floormid d 0.jpg | tti floormid d 0
File:tti floorring 0.jpg | tti floorring 0
File:tti floorring d 0.jpg | tti floorring d 0
File:tti halfpillar2 0.jpg | tti halfpillar2 0
File:tti pillarsupport 0.jpg | tti pillarsupport 0
File:tti plynthpillar 0.jpg | tti plynthpillar 0
File:tti railing 0.jpg | tti railing 0
File:tti signal 0.jpg | tti signal 0
File:tti stairdownfar 0.jpg | tti stairdownfar 0
File:tti stairdowninner 0.jpg | tti stairdowninner 0
File:tti stairdownmid 0.jpg | tti stairdownmid 0
File:tti stairup 0.jpg | tti stairup 0
File:tti stairupinner 0.jpg | tti stairupinner 0
File:tti stairupmid1 0.jpg | tti stairupmid1 0
File:tti support1 0.jpg | tti support1 0
File:tti top01 01.jpg | tti top01 01
File:tti towerstair d 0.jpg | tti towerstair d 0
File:tti towerstiar 0.jpg | tti towerstiar 0
File:tti wallarchdbl 0.jpg | tti wallarchdbl 0
File:tti wallblock 0.jpg | tti wallblock 0
File:tti wallblocksm 0.jpg | tti wallblocksm 0
File:tti wallcolumn 0.jpg | tti wallcolumn 0
File:tti wallfar 0.jpg | tti wallfar 0
File:tti wallfull1 0.jpg | tti wallfull1 0
File:tti wallfull2 0.jpg | tti wallfull2 0
File:tti wallfulldoor1 0.jpg | tti wallfulldoor1 0
File:tti wallfulldoor2 0.jpg | tti wallfulldoor2 0
File:tti wallfullhalf1 0.jpg | tti wallfullhalf1 0
File:tti wallfullhigh 0.jpg | tti wallfullhigh 0
File:tti wallhalf2 0.jpg | tti wallhalf2 0
File:tti wallhalfdoor1 0.jpg | tti wallhalfdoor1 0
File:tti wallhalfdoor2 0.jpg | tti wallhalfdoor2 0
File:tti wallhigh1 0.jpg | tti wallhigh1 0
File:tti wallhigh2 0.jpg | tti wallhigh2 0
File:tti wallhigharch1 0.jpg | tti wallhigharch1 0
File:tti wallhigharch2 0.jpg | tti wallhigharch2 0
File:tti wallpartition1 0.jpg | tti wallpartition1 0
File:tti walltall 0.jpg | tti walltall 0
File:tti walltowertop 0.jpg | tti walltowertop 0
</gallery>

== Tevinter Exterior ==

<gallery>
File:tve b twr1 0.jpg | tve b twr1 0
File:tve b twr1 1.jpg | tve b twr1 1
File:tve bttr 02 0.jpg | tve bttr 02 0
File:tve bttr 02 1.jpg | tve bttr 02 1
File:tve elgtwr 02 0.jpg | tve elgtwr 02 0
File:tve elgtwr 02 1.jpg | tve elgtwr 02 1
File:tve elgtwr 02b 0.jpg | tve elgtwr 02b 0
File:tve elgtwr 02b 1.jpg | tve elgtwr 02b 1
File:tve elgtwr 03 0.jpg | tve elgtwr 03 0
File:tve elgtwr 03 1.jpg | tve elgtwr 03 1
File:tve elgtwr 04 0.jpg | tve elgtwr 04 0
File:tve elgtwr 04 1.jpg | tve elgtwr 04 1
File:tve elgtwr 05 0.jpg | tve elgtwr 05 0
File:tve elgtwr 05 1.jpg | tve elgtwr 05 1
File:tve elgtwr 06 0.jpg | tve elgtwr 06 0
File:tve elgtwr 06 1.jpg | tve elgtwr 06 1
File:tve lwall 01 0.jpg | tve lwall 01 0
File:tve lwall 01 1.jpg | tve lwall 01 1
File:tve pil 01 0.jpg | tve pil 01 0
File:tve pil 01 1.jpg | tve pil 01 1
File:tve pil 03 0.jpg | tve pil 03 0
File:tve pil 03 1.jpg | tve pil 03 1
File:tve pil 04 0.jpg | tve pil 04 0
File:tve pil 04 1.jpg | tve pil 04 1
File:tve pil 05 0.jpg | tve pil 05 0
File:tve pil 05 1.jpg | tve pil 05 1
File:tve pil 06 0.jpg | tve pil 06 0
File:tve pil 06 1.jpg | tve pil 06 1
File:tve pil 07 0.jpg | tve pil 07 0
File:tve roof 01 0.jpg | tve roof 01 0
File:tve roof 03 0.jpg | tve roof 03 0
File:tve roof 04 0.jpg | tve roof 04 0
File:tve sroof 01 0.jpg | tve sroof 01 0
File:tve sroof 03 0.jpg | tve sroof 03 0
File:tve sroof 04 0.jpg | tve sroof 04 0
File:tve stair 01 0.jpg | tve stair 01 0
File:tve swall 02 0.jpg | tve swall 02 0
File:tve swall 03 0.jpg | tve swall 03 0
File:tve swall 06 0.jpg | tve swall 06 0
File:tve swall 08 0.jpg | tve swall 08 0
File:tve swall 09 0.jpg | tve swall 09 0
File:tve swall 10 0.jpg | tve swall 10 0
File:tve wall 01 0.jpg | tve wall 01 0
File:tve wall 02 0.jpg | tve wall 02 0
File:tve wall 03 0.jpg | tve wall 03 0
File:tve wall 04 0.jpg | tve wall 04 0
</gallery>

== Tevinter Interior ==

<gallery>
File:Tvi archwall 01 0.jpg|Tvi archwall 01 0
File:Tvi archwall 02 0.jpg|Tvi archwall 02 0
File:Tvi brkhalla c 0.jpg|Tvi brkhalla c 0
File:Tvi brkhalla root 0.jpg|Tvi brkhalla root 0
File:Tvi brknwall c 0.jpg|Tvi brknwall c 0
File:Tvi centredeco 0.jpg|Tvi centredeco 0
File:Tvi dbldoor 01 0.jpg|Tvi dbldoor 01 0
File:Tvi dome 01 0.jpg|Tvi dome 01 0
File:Tvi dome 02 0.jpg|Tvi dome 02 0
File:Tvi domeentrance 0.jpg|Tvi domeentrance 0
File:Tvi domefloor 1 0.jpg|Tvi domefloor 1 0
File:Tvi domefloor 2 0.jpg|Tvi domefloor 2 0
File:Tvi floor 1 0.jpg|Tvi floor 1 0
File:Tvi floor 2 0.jpg|Tvi floor 2 0
File:Tvi focalpoint 0.jpg|Tvi focalpoint 0
File:Tvi jaildrfrm 0.jpg|Tvi jaildrfrm 0
File:Tvi jailwall 0.jpg|Tvi jailwall 0
File:Tvi lrgstair 0.jpg|Tvi lrgstair 0
File:Tvi pil 01 0.jpg|Tvi pil 01 0
File:Tvi pil 01a 0.jpg|Tvi pil 01a 0
File:Tvi pil 02 0.jpg|Tvi pil 02 0
File:Tvi pil 03 0.jpg|Tvi pil 03 0
File:Tvi pil 04 0.jpg|Tvi pil 04 0
File:Tvi pil 05 0.jpg|Tvi pil 05 0
File:Tvi pil 06 0.jpg|Tvi pil 06 0
File:Tvi pil 07 0.jpg|Tvi pil 07 0
File:Tvi pil 08 0.jpg|Tvi pil 08 0
File:Tvi pil 09 0.jpg|Tvi pil 09 0
File:Tvi pil 09b 0.jpg|Tvi pil 09b 0
File:Tvi pil 10 0.jpg|Tvi pil 10 0
File:Tvi pil 11 0.jpg|Tvi pil 11 0
File:Tvi pil 12 0.jpg|Tvi pil 12 0
File:Tvi pil 13 0.jpg|Tvi pil 13 0
File:Tvi pil 14 0.jpg|Tvi pil 14 0
File:Tvi pil 14b 0.jpg|Tvi pil 14b 0
File:Tvi pil 15 0.jpg|Tvi pil 15 0
File:Tvi pil 16 0.jpg|Tvi pil 16 0
File:Tvi pil 17 0.jpg|Tvi pil 17 0
File:Tvi pil 18 0.jpg|Tvi pil 18 0
File:Tvi pil 19 0.jpg|Tvi pil 19 0
File:Tvi pil 20 0.jpg|Tvi pil 20 0
File:Tvi smdoorw 01 0.jpg|Tvi smdoorw 01 0
File:Tvi smdoorw 02 0.jpg|Tvi smdoorw 02 0
File:Tvi smdrfrme 0.jpg|Tvi smdrfrme 0
File:Tvi smroof 01 0.jpg|Tvi smroof 01 0
File:Tvi smroof 02 0.jpg|Tvi smroof 02 0
File:Tvi smroof 03 0.jpg|Tvi smroof 03 0
File:Tvi smroof 04 0.jpg|Tvi smroof 04 0
File:Tvi smstair 01 0.jpg|Tvi smstair 01 0
File:Tvi smwall 01 0.jpg|Tvi smwall 01 0
File:Tvi smwall 02 0.jpg|Tvi smwall 02 0
File:Tvi smwall 03 0.jpg|Tvi smwall 03 0
File:Tvi smwall 04 0.jpg|Tvi smwall 04 0
File:Tvi smwall 05 0.jpg|Tvi smwall 05 0
File:Tvi smwall 06 0.jpg|Tvi smwall 06 0
File:Tvi smwall 07 0.jpg|Tvi smwall 07 0
File:Tvi topwall 02 0.jpg|Tvi topwall 02 0
File:Tvi topwall 03 0.jpg|Tvi topwall 03 0
File:Tvi topwall 04 0.jpg|Tvi topwall 04 0
File:Tvi treewall 0.jpg|Tvi treewall 0
File:Tvi wall 01 0.jpg|Tvi wall 01 0
File:Tvi wall 01a 0.jpg|Tvi wall 01a 0
File:Tvi wall 01b 0.jpg|Tvi wall 01b 0
File:Tvi wall 02 0.jpg|Tvi wall 02 0
File:Tvi wall 03 0.jpg|Tvi wall 03 0
File:Tvi wall 04 0.jpg|Tvi wall 04 0
File:Tvi wall 05 0.jpg|Tvi wall 05 0
File:Tvi wall 06 0.jpg|Tvi wall 06 0
File:Tvi wall 07 0.jpg|Tvi wall 07 0
File:Tvi wallhole c 0.jpg|Tvi wallhole c 0
File:Tvi webwall c 0.jpg|Tvi webwall c 0
</gallery>

== Tevinter Road ==

<gallery>
File:Tvm arch 0.jpg|Tvm arch 0
File:Tvm bridge 01 0.jpg|Tvm bridge 01 0
File:Tvm bridge 02 0.jpg|Tvm bridge 02 0
File:Tvm bridge 03 0.jpg|Tvm bridge 03 0
File:Tvm bridge 04 0.jpg|Tvm bridge 04 0
File:Tvm elgtwr 01 0.jpg|Tvm elgtwr 01 0
File:Tvm pil 04 0.jpg|Tvm pil 04 0
File:Tvm pil 05 0.jpg|Tvm pil 05 0
File:Tvm swall 01 0.jpg|Tvm swall 01 0
File:Tvm swall 07 0.jpg|Tvm swall 07 0
</gallery>

== Vista Objects ==

:Main article: [[Vista object]]s

These objects are intended to be put far outside the walkable area of an exterior level to act as distant "horizon" objects.

== Environmental Props ==

The following images are environmental props from the 'prp' subsection of 'models'. Props are models that can be placed in your levels to dress them up. They are not interactive (as in they cannot have inventory or be 'used' in any way.) If the module maker requires items to be placed in the module that can be interacted with they must use '[[Placeable]]s' rather than 'Props' The images below are by no means all of the props, just some of the large environmental ones. There is a large variety of props so you are encouraged to go through the whole list of prop models to enhance the look of your level. Also the images below are not to scale they are merely intended so that the module maker can quickly scan them to see if any of them catch his or her fancy.

<gallery>
File:Prp blood05 0.jpg | prp blood05 0
File:Prp bloodstains 0.jpg | prp bloodstains 0
File:Prp boat making 0.jpg | prp boat making 0
File:Prp boulder01 0.jpg | prp boulder01 0
File:Prp boulder03b 0.jpg | prp boulder03b 0
File:Prp boulder05b 0.jpg | prp boulder05b 0
File:Prp boulder05c 0.jpg | prp boulder05c 0
File:Prp boulder10b 0.jpg | prp boulder10b 0
File:Prp bridge 0.jpg | prp bridge 0
File:Prp bridge 1.jpg | prp bridge 1
File:Prp carvtr1,3,4 0.jpg | prp carvtr1,3,4 0
File:Prp caverocks01to04 0.jpg | prp caverocks01to04 0
File:Prp cliffb 0.jpg | prp cliffb 0
File:Prp dalishtent01 0.jpg | prp dalishtent01 0
File:Prp dalishtent04 0.jpg | prp dalishtent04 0
File:Prp deadtree 0.jpg | prp deadtree 0
File:Prp dirt 0.jpg | prp dirt 0
File:Prp dni arch01 0.jpg | prp dni arch01 0
File:Prp dni archc01 0.jpg | prp dni archc01 0
File:Prp dni archd01 0.jpg | prp dni archd01 0
File:Prp dni pillar01 0.jpg | prp dni pillar01 0
File:Prp dni pillar02 0.jpg | prp dni pillar02 0
File:Prp dni plug01 0.jpg | prp dni plug01 0
File:Prp dni plug02 0.jpg | prp dni plug02 0
File:Prp dni plug03 0.jpg | prp dni plug03 0
File:Prp dni plug04 0.jpg | prp dni plug04 0
File:Prp dni support01 0.jpg | prp dni support01 0
File:Prp dni wall01 0.jpg | prp dni wall01 0
File:Prp dni wall02 0.jpg | prp dni wall02 0
File:Prp drkspstuf 01 0.jpg | prp drkspstuf 01 0
File:Prp drkspstuf 0203 0.jpg | prp drkspstuf 0203 0
File:Prp drkspstuf 0405 0.jpg | prp drkspstuf 0405 0
File:Prp drkspstuf 06 0.jpg | prp drkspstuf 06 0
File:Prp drkspstuf 07 0.jpg | prp drkspstuf 07 0
File:Prp drkspstuf 0809 0.jpg | prp drkspstuf 0809 0
File:Prp drkspstuf 1011 0.jpg | prp drkspstuf 1011 0
File:Prp dstotem 01 0.jpg | prp dstotem 01 0
File:Prp dstotem 02 0.jpg | prp dstotem 02 0
File:Prp dstotem 03 0.jpg | prp dstotem 03 0
File:Prp dummystraw 01 0.jpg | prp dummystraw 01 0
File:Prp dwcitydoor 0.jpg | prp dwcitydoor 0
File:Prp dwf obelisk1,2,3 0.jpg | prp dwf obelisk1,2,3 0
File:Prp dwiarch 01 0.jpg | prp dwiarch 01 0
File:Prp dwmrktdiv 0.jpg | prp dwmrktdiv 0
File:Prp dwmrktfr01 0.jpg | prp dwmrktfr01 0
File:Prp dwpaint01&02 0.jpg | prp dwpaint01&02 0
File:Prp dwrock01 0.jpg | prp dwrock01 0
File:Prp dwslab01&02 0.jpg | prp dwslab01&02 0
File:Prp dwstat01 0.jpg | prp dwstat01 0
File:Prp eagle 01 0.jpg | prp eagle 01 0
File:Prp eggshels01 0.jpg | prp eggshels01 0
File:Prp elfstatue01to04 0.jpg | prp elfstatue01to04 0
File:Prp fadportal01 0.jpg | prp fadportal01 0
File:Prp fci window 02.jpg | prp fci window 02
File:Prp fcihold 02.jpg | prp fcihold 02
File:Prp fence01 0.jpg | prp fence01 0
File:Prp ferldr 02 0.jpg | prp ferldr 02 0
File:Prp fern01to08 0.jpg | prp fern01to08 0
File:Prp fertrsrepile 0.jpg | prp fertrsrepile 0
File:Prp fie rock1 0.jpg | prp fie rock1 0
File:Prp fie rock1l 0.jpg | prp fie rock1l 0
File:Prp fie rock2 0.jpg | prp fie rock2 0
File:Prp fie rock2l 0.jpg | prp fie rock2l 0
File:Prp fie rock3 0.jpg | prp fie rock3 0
File:Prp fie rock3l 0.jpg | prp fie rock3l 0
File:Prp fie rock4 0.jpg | prp fie rock4 0
File:Prp fie rock5 0.jpg | prp fie rock5 0
File:Prp fie rock6 0.jpg | prp fie rock6 0
File:Prp fie rock7 0.jpg | prp fie rock7 0
File:Prp fie rock8 0.jpg | prp fie rock8 0
File:Prp fie rock9 0.jpg | prp fie rock9 0
File:Prp filthpile 0.jpg | prp filthpile 0
File:Prp fire01to03 0.jpg | prp fire01to03 0
File:Prp fireplace1 0.jpg | prp fireplace1 0
File:Prp flakes01to03 0.jpg | prp flakes01to03 0
File:Prp fleshpod01to11 0.jpg | prp fleshpod01to11 0
File:Prp flesthorn01to02 0.jpg | prp flesthorn01to02 0
File:Prp forge01 0.jpg | prp forge01 0
File:Prp forgesmall01&02 0.jpg | prp forgesmall01&02 0
File:Prp fti window 01.jpg | prp fti window 01
File:Prp furdoor0.jpg | prp furdoor0
File:Prp gmage01 0.jpg | prp gmage01 0
File:Prp haybale01 0.jpg | prp haybale01 0
File:Prp haystack01 0.jpg | prp haystack01 0
File:Prp hermet0 0.jpg | prp hermet0 0
File:Prp icicle01&02 0.jpg | prp icicle01&02 0
File:Prp icicle03&04 0.jpg | prp icicle03&04 0
File:Prp icicle05 0.jpg | prp icicle05 0
File:Prp icicle06&07 0.jpg | prp icicle06&07 0
File:Prp jail01to04 0.jpg | prp jail01to04 0
File:Prp leafpile&02 0.jpg | prp leafpile&02 0
File:Prp lgnartfact09to19 0.jpg | prp lgnartfact09to19 0
File:Prp lgtnking 01 0.jpg | prp lgtnking 01 0
File:Prp logginpile 0.jpg | prp logginpile 0
File:Prp longweb 01 0.jpg | prp longweb 01 0
File:Prp lrglogs 0.jpg | prp lrglogs 0
File:Prp magicrock0to04 0.jpg | prp magicrock0to04 0
File:Prp markettent01 0.jpg | prp markettent01 0
File:Prp mnstrstat2 0.jpg | prp mnstrstat2 0
File:Prp monsterstatue 0.jpg | prp monsterstatue 0
File:Prp paragon01to05 0.jpg | prp paragon01to05 0
File:Prp poolwater 0.jpg | prp poolwater 0
File:Prp portcullis01 0.jpg | prp portcullis01 0
File:Prp rcktopiary 01to04 0.jpg | prp rcktopiary 01to04 0
File:Prp reliquary 0.jpg | prp reliquary 0
File:Prp rockfloor01,b,c,d 0.jpg | prp rockfloor01,b,c,d 0
File:Prp rockfloor02,b,c 0.jpg | prp rockfloor02,b,c 0
File:Prp rockfloor03,b,c,d 0.jpg | prp rockfloor03,b,c,d 0
File:Prp rockpile 01 0.jpg | prp rockpile 01 0
File:Prp rockwall01,b 0.jpg | prp rockwall01,b 0
File:Prp rockwall02,03 0.jpg | prp rockwall02,03 0
File:Prp rockwall04b,04c 0.jpg | prp rockwall04b,04c 0
File:Prp rockwall05b,05c 0.jpg | prp rockwall05b,05c 0
File:Prp rockwall08c 0.jpg | prp rockwall08c 0
File:Prp rockwall09c,10c 0.jpg | prp rockwall09c,10c 0
File:Prp root01,02,03 0.jpg | prp root01,02,03 0
File:Prp root04,05,06 0.jpg | prp root04,05,06 0
File:Prp roots,b 0.jpg | prp roots,b 0
File:Prp rtplub01 0.jpg | prp rtplub01 0
File:Prp rtplub02 0.jpg | prp rtplub02 0
File:Prp rubble,01 0.jpg | prp rubble,01 0
File:Prp rubble01,02 0.jpg | prp rubble01,02 0
File:Prp scaffold1,2,3 0.jpg | prp scaffold1,2,3 0
File:Prp sctdr02frm 0.jpg | prp sctdr02frm 0
File:Prp shieldstatue01 0.jpg | prp shieldstatue01 0
File:Prp smlogs 0.jpg | prp smlogs 0
File:Prp smrock01to04 0.jpg | prp smrock01to04 0
File:Prp snow01to09 0.jpg | prp snow01to09 0
File:Prp snowp01to05 0.jpg | prp snowp01to05 0
File:Prp spiritapp 0.jpg | prp spiritapp 0
File:Prp spkewll 0.jpg | prp spkewll 0
File:Prp sprtpil 0.jpg | prp sprtpil 0
File:Prp stage,2 0.jpg | prp stage,2 0
File:Prp stagestair,2,3 0.jpg | prp stagestair,2,3 0
File:Prp stalactite01 0.jpg | prp stalactite01 0
File:Prp stalactite03 0.jpg | prp stalactite03 0
File:Prp stalactite04 0.jpg | prp stalactite04 0
File:Prp stalactite05 0.jpg | prp stalactite05 0
File:Prp stalagmite01to04 0.jpg | prp stalagmite01to04 0
File:Prp stalagmite05to08 0.jpg | prp stalagmite05to08 0
File:Prp stalagpillar05 0.jpg | prp stalagpillar05 0
File:Prp stalagrock01 0.jpg | prp stalagrock01 0
File:Prp stalagrock02 0.jpg | prp stalagrock02 0
File:Prp statandraste 0.jpg | prp statandraste 0
File:Prp statmstr02,04,05 0.jpg | prp statmstr02,04,05 0
File:Prp statuferel 01,02 0.jpg | prp statuferel 01,02 0
File:Prp steamv02,03 0.jpg | prp steamv02,03 0
File:Prp stnwell 0.jpg | prp stnwell 0
File:Prp stonea 0.jpg | prp stonea 0
File:Prp stonea,b,c,d 0.jpg | prp stonea,b,c,d 0
File:Prp sulpol01to04 0.jpg | prp sulpol01to04 0
File:Prp sulvent01to03 0.jpg | prp sulvent01to03 0
File:Prp tentbeserk 01 0.jpg | prp tentbeserk 01 0
File:Prp tentcamping 01 0.jpg | prp tentcamping 01 0
File:Prp tentchantry 01 0.jpg | prp tentchantry 01 0
File:Prp tentduncan 01 0.jpg | prp tentduncan 01 0
File:Prp tentking 01 0.jpg | prp tentking 01 0
File:Prp tentloghain 01 0.jpg | prp tentloghain 01 0
File:Prp tentmage 01 0.jpg | prp tentmage 01 0
File:Prp tentnoble 01 0.jpg | prp tentnoble 01 0
File:Prp tevstalrg1 01,02.jpg | prp tevstalrg1 01,02
File:Prp tevstau01,02,03 0.jpg | prp tevstau01,02,03 0
File:Prp torturewrack 0.jpg | prp torturewrack 0
File:Prp trashpile01 0,01.jpg | prp trashpile01 0,01
File:Prp treea.b.c 01 0.jpg | prp treea.b.c 01 0
File:Prp treeline1 0.jpg | prp treeline1 0
File:Prp treewall water 0.jpg | prp treewall water 0
File:Prp tti bsupport01 0.jpg | prp tti bsupport01 0
File:Prp tti bsupport02 0.jpg | prp tti bsupport02 0
File:Prp tti dirto 0.jpg | prp tti dirto 0
File:Prp tti magestat01 0.jpg | prp tti magestat01 0
File:Prp tti pole02 0.jpg | prp tti pole02 0
File:Prp tti rub08,09,11 0.jpg | prp tti rub08,09,11 0
File:Prp tti rubptc01 0.jpg | prp tti rubptc01 0
File:Prp tti twreagle02 0.jpg | prp tti twreagle02 0
File:Prp tti wallarchbar 0.jpg | prp tti wallarchbar 0
File:Prp tti windowhigh1.jpg | prp tti windowhigh1
File:Prp turbine 01 0.jpg | prp turbine 01 0
File:Prp vines 0.jpg | prp vines 0
File:Prp wall02b 0.jpg | prp wall02b 0
File:Prp wall03 0.jpg | prp wall03 0
File:Prp wall04 0.jpg | prp wall04 0
File:Prp wall04b 0.jpg | prp wall04b 0
File:Prp wall05 0.jpg | prp wall05 0
File:Prp wall05b 0.jpg | prp wall05b 0
File:Prp wallarchiron 0.jpg | prp wallarchiron 0
File:Prp wallcarv 01to04 0.jpg | prp wallcarv 01to04 0
File:Prp walldiv01 0.jpg | prp walldiv01 0
File:Prp walllyrium01 0.jpg | prp walllyrium01 0
File:Prp walllyrium02 0.jpg | prp walllyrium02 0
File:Prp walllyrium03 0.jpg | prp walllyrium03 0
File:Prp walllyrium04 0.jpg | prp walllyrium04 0
File:Prp walllyrium05 0.jpg | prp walllyrium05 0
File:Prp watchtower 01 0.jpg | prp watchtower 01 0
File:Prp wndobtmdim 01.jpg | prp wndobtmdim 01
File:Prp wndobtmdrk 01.jpg | prp wndobtmdrk 01
File:Prp wndobtmdrk 02.jpg | prp wndobtmdrk 02
File:Prp wndotopdim 01.jpg | prp wndotopdim 01
File:Prp woodbrk1 0.jpg | prp woodbrk1 0
File:Prp wooden buoy 0.jpg | prp wooden buoy 0
File:Prp woodfnc 01 0.jpg | prp woodfnc 01 0
File:Prp woodgt 01 0.jpg | prp woodgt 01 0
File:Prp woodledge 0.jpg | prp woodledge 0
File:Prp woodledge 02 0.jpg | prp woodledge 02 0
File:Prp woodlift 0.jpg | prp woodlift 0
File:Prp woodpil1 0.jpg | prp woodpil1 0
File:Prp woodplank01to03 0.jpg | prp woodplank01to03 0
File:Prp woodruble01 0.jpg | prp woodruble01 0
File:Prp wpole01,02.jpg | prp wpole01,02
File:Prp wreckboat 01.jpg | prp wreckboat 01
</gallery>

== Banners, Flags, Standards, Signs, Tapestry, Wall Hangings, Rugs, Carpets ==

The images below are all 'Props (prp)' which are found under the 'Models' in the palette window.
The images are not to scale but are intended to show what the prop looks like. Props are not interactive and are used to dress up levels. If the module maker requires interactive items in their module level they must use 'placeables' rather than 'props'

<gallery>
File:Prp bannergry 01 0.jpg | prp bannergreen 01 0 prp bannerred 01 0 prp banneryellow 01 0
File:Prp bannergy 03 0.jpg | prp bannergreen 03 0 prp banneryellow 03 0
File:Prp bannerlarge 0.jpg | prp bannerlarge 0
File:Prp bannerry 04 0.jpg | prp bannerred 04 0 prp banneryellow 04 0
File:Prp bluecarpet 0.jpg | prp bluecarpet 0
File:Prp bnner02,3-0.jpg | prp bnner02,3-0
File:Prp bnner02b 0.jpg | prp bnner02b 0
File:Prp bttll stnd01,3,4 0.jpg | prp bttll stnd01,3,4 0
File:Prp bttll stnd05,6,7,8 0.jpg | prp bttll stnd05,6,7,8 0
File:Prp carpet1to2cl 0.jpg | prp carpet1to2cl 0
File:Prp carpet1to3b 0.jpg | prp carpet1to3b 0
File:Prp carpet3to4c 0.jpg | prp carpet3to4c 0
File:Prp carpetb,g,r l 0.jpg | prp carpetb,g,r l 0
File:Prp crssd swrd 1to02 0.jpg | prp crssd swrd 1to02 0
File:Prp curt02,05,08 0.jpg | prp curt02,05,08 0
File:Prp ds banner 01,02,03 0.jpg | prp ds banner 01,02,03 0
File:Prp dwfbanr1to6 0.jpg | prp dwfbanr1to6 0
File:Prp dwfrug1to5 0.jpg | prp dwfrug1to5 0
File:Prp dwfsign01,02 0.jpg | prp dwfsign01,02 0
File:Prp dwhrld01.jpg | prp dwhrld01
File:Prp dwpaint01,02 0.jpg | prp dwpaint01,02 0
File:Prp dwsign01to06 0.jpg | prp dwsign01to06 0
File:Prp elrug1to6 0.jpg | prp elrug1to6 0
File:Prp ferpaint01to04 0.jpg | prp ferpaint01to04 0
File:Prp flagking&chantry01 0.jpg | prp flagking&chantry01 0
File:Prp hbannerg,r,y 01 0.jpg | prp hbannerg,r,y 01 0
File:Prp painting 01 0.jpg | prp painting 01 0
File:Prp redcarpet 0.jpg | prp redcarpet 0
File:Prp roadsin1 0.jpg | prp roadsin1 0
File:Prp rollcarpet01to03 0.jpg | prp rollcarpet01to03 0
File:Prp strawmat 0.jpg | prp strawmat 0
File:Prp wallhang01to06 0.jpg | prp wallhang01to06 0
File:Prp wallhang07to09 0.jpg | prp wallhang07to09 0
File:Prp wallhangf01to03 0.jpg | prp wallhangf01to03 0
</gallery>

[[Category:Level layouts]]

Making a new, playable module

2022-02-01T16:21:07Z

Ashhawk: BSN link flagged for maintenance

{{BSN link}}

Anyone who cares has probably gotten the toolset up and running, but in case you were struggling like me, here are some notes to save you a little time, hair, and anguish. You can sell those back to a vendor for a few copper.

== Installing the Toolset ==

You can find the Wiki's main installation notes at [[Installing the toolset|Installing the toolset]]. First off, some installation notes:

* Make sure you have Activepython 2.5.x.x installed (or Python 2.5.x.x with Win32 extensions). You want those in BEFORE you get your toolset installed, and it does need to be the 2.5 version.
* There's also an updated LightMapper script. You get the LightMapper [http://social.bioware.com/project/717/| here].

More on these later, but most likely you will get to know the LightMapper very well.

== Creating a Module ==

[[File:Manage modules.jpg|right]]

The first thing you should do is [[Creating_a_module|create a module]]. As you can see, you start with "Manage Modules," NOT with File-> New. When you installed the Dragon Age Toolset, you were also asked to install a SQL database, and this is where many Dragon Age resources are stored. This means that if you want to point to actual folders for reference, custom level files and so forth, you should make a folder yourself and put those resources in for you to mangle, er, use. Remember that 1) it's difficult to delete your module, unless you want to trash your SQL database and 2) even though modules are all called "addins," any module can either stand alone or be used to enhance an existing module. They are simply addins of the core of the game, not of any particular campaign.

'''Takeaways'''
* The Toolset uses a SQL database system to store information.
* Remember that it's difficult to delete modules or change their names because they are stored in the database.
* New modules are used as both addins or standalone campaigns.
* Use the Manage Modules menu to control many of the basic functions of your module.
* Under Content Module, select Core Game Resources to use as a base for a standalone module.

== Setting Up Your New Module ==

This is the quick and dirty way to make a brand new module. We'll get into adjusting the details as we go through this series.

=== Getting a basic usable character ===

I found it easiest to just cut and paste from Bryan Derksen's script from the Demo to start. Open up the Demo with Manage Modules and select the Script Palette in the Palette window on the right and you'll see some little gray can icons in the folder "Demo." Choose "Demo_Module" and you'll see the starting script for the Toolset Demo.

* You can copy and paste the basics of that script (Thanks Bryan Derksen!) into a script of your own. Just highlight his script and CTRL-C to copy.
* To set up basic character creation, create a new script by going into the File menu and selecting New > Script. Paste the text you just copied from the demo in, or use this more basic template:

<pre>
#include "log_h"
#include "utility_h"
#include "wrappers_h"
#include "events_h"

void main()
{
event ev = GetCurrentEvent();
int nEventType = GetEventType(ev);
string sDebug;
object oPC = GetHero();
object oParty = GetParty(oPC);
int nEventHandled = FALSE;

switch(nEventType)
{
case EVENT_TYPE_MODULE_START:
{
PreloadCharGen();
StartCharGen(GetHero(),0);
break;
}
}
if (!nEventHandled)
{
HandleEvent(ev, RESOURCE_SCRIPT_MODULE_CORE);
}
}
</pre>

* Then open up Manage Modules on your own Module and select Properties.
* Right under the name of your module, there's a field labeled "Script" - use this to enter the starting script for your module.

Now you have good old fashioned Character Generation! We'll look at how to modify that a little later, as script writing is something you'll most likely get to delve deep into at some point in the future. Note that without Character Generation of this sort, you'll end up with a fairly ugly fellow named Jaden (Sorry Jaden) who has 0 for all stats and 1 HP.

'''Takeaways'''
* Use File > New to create new resources that you will need for your module.
* You can look at examples from the Demo, Single Player, or any other module for guidance.
* You have to have a ''script'' to make a new character in your module.
* A number of fairly basic features like character generation and moving between levels are controlled by scripting.

=== Setting up a basic level ===

There's your Character, but now he needs a place to go. You can muck with the Level Editor for custom levels, but right now it may be more pain than I want to give you, so I'll talk about it a little later. For now, we'll stick with the default areas. Here's what you do:

* Go to File > New > Area and go through the motions of making a new area.
* Once you have it, go to the Area Palette. All the Palettes are on the right side of the screen, and the Area Palette is the first one - it looks like a little bed.
* Open up your area by double clicking on its little gray icon.
* The Object Inspector on the lower right shows your open resource's properties. Under your new area's properties, choose an Area Layout to make a map that you can walk around. Any layout will do, try opening them up and looking around.
* First things first, you need to tell the module where your character will start. On the left-hand side, you'll see "Waypoints" - right-click there and insert a new one.
* Edit the name and tag of your Waypoint in its properties.

You can also change its color to Start if that matters to you - I find it a little easier to recognize that way. There's a starting area now and a starting Waypoint, and this means you can adjust your module to include these.

* Once more, enter Manage Modules and choose Properties.
* Set the Starting Area to the area you just created.
* Set the Starting Waypoint to the Waypoint that you just made.

[[File:Level ss.jpg]]

'''Takeaways'''
* The Palettes, in the upper right, let you manage resources for a specific aspect of the game - scripts, NPCs, plots, etc.
* The Object Inspector, in the lower right, lets you see and edit properties of a specific resource.

=== Navigating the Toolset ===

Here's your first taste of mouse navigation in the toolset as well - by default: you can rotate with the Middle Mouse button, zoom with Scroll Wheel, and hold CTRL+left click to pan from side to side. Sorry, I'm not sure about one-button mouse options.

== Exporting Resources ==

There you have it, you're done! Right? Not just yet - remember this info is stored in the database. Now you need to bring it into the game.

* Go to Tools > Export.
* Choose "Export without Dependent Resources". In general, you want to export as few resources as possible.
* The Log Window at the bottom will show the status of your action, including where the Campaign resource gets exported and if there were errors - hopefully not.
* Now when you go to DA, you'll be able to go to Other Campaigns and select your custom campaign!

[[File:Campaign ss.jpg]]

'''Takeaways'''
* Use Tools > Export to make actual files usable by the game for your module.
* You should export after making changes to any areas, so that changes you make in the toolset are reflected in your game.

Location of game build

2022-02-01T16:20:03Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

On toolset start up, you may encounter the following error message:

{{dashedborder|Location of game build either not specified or the update program was never run to copy the build onto your computer.

Run the toolset configuration program and verify your settings or search the toolset wiki http://social.bioware.com/wiki/datoolset to help with this issue.

This toolset must now exit.}}

When the toolset starts up, it looks for the existence of the game. It looks in a specified location for the game. When this error is thrown, it means the game has not been found. There are two possible reasons for this.
#The game is not installed, or
#It is looking in the wrong place for the game
If the game is not installed, you need to do that. The more likely case is that the toolset has been told to look in the wrong place for the game, and you need to correct that using the [[Configure Toolset]] utility.

Navigate to the directory where you have installed the toolset. Typically the location would be something like:
C:\Program Files\Dragon Age\Tools\
In the Tools directory, double click on ConfigureToolset.exe to launch the utility.

The first screen that comes up will be called "Game Builds", with a field called "Win32 Game Build". This needs to point to the directory where Dragon Age is installed. Either type the path into this field, or click the button next to it to browse to the directory. Once this field is displaying the correct directory, click next, and then Finish.

Launch the toolset again, and it should not give you this error anymore.

[[Category:Error messages]]

Level Editor Tutorial

2022-02-01T16:19:52Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

=Building your room (Interior Level)=
How to create/lightmap a [[Level]] for use in an Interior [[Area]]:
Objective: Following along with this tutorial, you should be able to create a simple room from scratch in 10 minutes or less

This was lifted from a posting by St4rdog http://social.bioware.com/forum/1/topic/8/index/150840
It needs some additional formatting love, but is as good starting place for people to create usable
interior levels

File > New > Level > Room Level

* Click on "New Area" in top-left list > Object Inspector in bottom-right > Layout Name > anything under 8 characters no spaces or special characters (*,&,%, etc).
* Click the Setup Start Point icon, then click anywhere to make a start point.
* Select the Area, then add the Start Point Name in the Object Inspector.
*Right-click in 3D view and select Insert > New Room.
*Click Models (blue box) in the Palette in the top-right. These folders contain everything such as floor tiles, walls, etc.
*Enable Grid Snap with the magnet icon to make sure they line up.
*The "prp" folder contains things like beds/barrels to clutter your Level.
Hint: Use [[DATool]] (3rd party tool downloadable at http://social.bioware.com/project/41/ )to browse
through these quickly to find the floors/walls you want.
*Any gaps you can see between models (such as wall sections) will be visible in game. When you have time to refine the layout, you can remove most hairline gaps by setting exact X Y Z coordinates in the toolset (though sometimes 0.99 or 1.01 looks better than 1.00). Larger gaps may require the use of tileset assets such as pillars. The black box tileset (blk) can be placed outside a room to cover up any defects.
Hint: If you need lots of wall sections quickly, place one at a convenient location e.g. (0,0). Copy (Ctrl-C) then Paste (Ctrl-V)
as many as you need. In the Object Inspector, change the coordinates of successive sections to (0,8), (0,16) etc or drag manually
if you can do that quicker.

Note: If you get "Cannot spawn models into the selected parent object" when trying to place a model
then you don't have "New Room" selected.

==Working with multiple rooms==

In general it is best to define each building room as a new room in the level. This becomes important when you work on lighting. To physically connect rooms you need to slide them together to get the doors to line up, they do not line up automatically. It takes some trial and error but becomes easier with practice.

Use the Room Properties icon to specify which rooms are connected etc.

==Pathfinding==

Click the Generate Pathfinding icon. Green dots indicate where the player will be allowed to walk.

For this to work, the area properties must name a valid start point, and it needs to be bounded by walls or other obstacles.

Hint: you may need to place another startpoint in any room that can't be reached from the main startpoint. That would apply, for example, to
rooms reached by transition doors within the area.

==Adding lights==

Two very simple alternatives are given here.

The first is minimal, with shadows.

The second makes no shadows, but ensures that faces are never in darkness.

=== Method 1 ===

* Right-click on "New Room" in top-left list > Insert > New Light

* Move it up off the floor a little (e.g. Z = 2). In Object Inspector > Affects Characters TRUE > "Color Intensity" 2 or more > "Light Type" Point - Static (lc) > Choose any bright color (this light illuminates both the level and the characters).

*Copy and paste. In Object Inspector >"Light Type" Ambient - Baked (you must have an ambient light, and this approach stops your shadows being pitch black) > Choose a dark blue colour and keep the Color Intensity under 2/3.

Note: I'm not sure what the mix of Baked/Static light is supposed to be.
If you just put a Baked + Ambient it complains about not having Static, but if
you put a Static + Ambient it seems to work fine, but the wiki says Static is
the most expensive.

=== Method 2 ===

* Right-click on "New Room" in top-left list > Insert > New Light anywhere in the room.

* Raise it up off the floor a little (e.g. Z = 2).

* In Object Inspector > "Light Type" Ambient - Baked > Colour 1,1,0.86 > leave the colour intensity at 1 (this ambient light will light the level but not the characters).

* Copy and paste. In Object Inspector > "Light Type" Point - Static > Affects Characters TRUE > Affects Level FALSE > Colour 0.70,0.70,0.65 > Colour Intensity 1.7 Point Radius 10000 (this will light your characters).

* Copy and paste until you have 3-4 static character lights.

* Arrange the character lights in a circle outside all of the rooms.

=== Light Probe ===

Whether you use method 1 or 2,

* Right-click on "New Room" in top-left list > Insert > New Light Probe

Note : you need a light probe to make character and water lighting work properly. The exact position doesn't seem to matter much.

==Rendering Lightmaps==

*Press the Render Lightmaps icon (you need ActivePython 2.5 installed to default location, installation instructions for python can be found [[Installing_the_toolset#Lightmapper|here]]). When it's done click the Display Lightmaps On/Off icon in the top-left to refresh the results.
*Uncheck the "View Models Fully Lit" icon in the lop-left. You should see shadows from any objects you've dropped in.

Note: Lightmap-atlas messages might appear the first time you render. That seems normal.
Sometimes re-rendering the lightmaps messes them up badly when Display Lightmaps On/Off is on. It
doesn't seem to use the latest lightmaps. Try pressing Display Lightmaps On/Off a few times to
update it. If they're still messed up sometimes one of these fixes it (don't know which)
unloading/reloading your Area or Level/changing your Area's layout property/posting your Level to
Local.

==Adding the Minimap==

Select the area. Right click, then select Minimap > Minimap Selection Tool. The default green box appears. Right click on the area again, Minimap > Post Minimap to Local. It's possible to handcraft or refine the minimap, as detailed under [[Custom minimaps]].

==Exporting==

*Press the Do All Local Posts icon to the right of the lightmapping icons. It will export the name you typed into the "New Area" "Layout Name".
*If that doesn't work, select the area then Edit > Post Selection To Local.
*If there's a complaint about walkable/player start then delete your old start then place a new one on a flat area.
*Save your .lvl file. It's not used by the game and the name/location doesn't matter. Only the exported/posted files are used.

==Using this in an Area==

File > New > Area > Any Name

*In the Object Inspector > Area Layout you should get a "..." box (make sure it's Checked Out) > click then select your "Layout Name" which should now be there.

* Now you have a pretty lightmapped level inside an area.

=Building your terrain (Exterior Level)=
How to create/lightmap a [[Level]] for use in an Exterior [[Area]]:
Objective: Following along with this tutorial, you should be able to create a simple terrain from scratch.

File>New>Level

* Choose Terrain (Landscape) Level and then click Next.

* Accept the default values for the purpose of this tutorial and click Next and then click Finish. You can learn more about what the different terrain options do at the [[Level editor]] page.

You should now see a flat, dark piece of terrain. To move around you hold down the mouse wheel. If you want to rotate the view press the Alt key while holding down the mouse wheel. You will want some light so you can see what you are doing, so we will generate a light source next.

Tip: When choosing the size of your terrain level think about where you are going to put horizon and vista objects, like distant mountains and tree lines. You may need to allow for extra space around your adventure area to place those items.

==Grid Size==

If you want to work with a larger grid than the one provided by default you can change the grid size by going to:

Tools/Options/Level Editor/Grid Square Size.

This will not change the actual dimensions of the terrain level that you created, it only changes the size of the squares in the grid.

==Define an area==

Must be done before rendering the lightmap.

* Click on the purple [[File:Purpleplus.png]]-sign and click Define Area. Start in one corner and draw the green square to define the area that you will export.
* Fill in the box Layout Name, max seven characters.
* Fill in the box Name.

==Lighting==

* Right click on Terrain World to the upper left and choose Insert>New Light. This will spawn a light source in your area. Make sure you change the Light Type to Ambient - Baked (L). Be sure to click on the Render Lightmaps button if you want to see how your ambient light is working.

Now that the terrain is lit we can modify it.

==Modifying Terrain==

The [[Terrain mesh]] tools allow you to modify the terrain by changing elevations, smoothing edges, flatting terrain, or painting textures.

==Water==

First use the [[Terrain mesh]] tools to make a hole. It doesn't have to be deep. Then right-click on Terrain world and select Insert -> New Water Mesh. Double Click on the Water Mesh to zoom to it. By default it gets placed in a corner. Using the 3 Axis Movement tool [[File:moveTool.png]] grab the water and drag it to your hole. Depending on the size of the hole, you might have to adjust the water mesh size by changing the Size X and Size Y property values. Once you have the mesh placed, it's time to create the light probe. Right-click near the water mesh and select Insert -> New Light Probe. Using the move tool again, drag the light probe so that is roughly centered over the water mesh and slightly above it. Click on Render Lightmaps, then Render Light Probs. You might have to toggle Display Lightmaps, but you should now see your water looking like water and reflecting things around it.

See also [[Bug: Water plane missing in-game]] for an important workaround.

==Placing Models==

* Click the blue box in the Palette Window to access the models that come with the game. The [[Model list]] shows pictures of many of the models available.

* The [[Model]] page has more details on how to work with models.

Tip 1: I had to change the Snap Options to make the models go where I wanted them. The settings I use were 0.10 for Snap to Grid and Snap Z Size. I also had to turn off Enable Snap to Surface whenever I wanted to change the vertical position of something (like creating the second floor of a building). Enable Snap to Surface is not applied globally, so once you turn it off and position an object vertically, turning it back on will not move that object unless you select it (or have it selected when you turn it back on).

Tip 2: When placing premade cottages be aware that the door frames you can see attached to those buildings DO NOT have built in door hooks (see [[Area tutorial]] for information on placing doors). You can place a door frame model (for example, fhe_doorfrs_0) over the built in door frame to generate a door hook. The door frame model has to be placed from the Level Editor.

==Adding Vegetation and Wind==

The [[Vegetation]] page includes a list with pictures of the various plants available for placement. If you do not see the plants once you place them with the Scatter Object Tool then you may need to adjust your SpeedTree Rendering Distance Selector. This is a drop-down that you will see in the Tool Bar. It lists the distances at which plants will be visible. I set it to Very Far and left it there.

Each level can have one active wind object in it. The location of the wind object doesn't matter. The wind object defines how wind behaves on this level, which is used for such things as flapping banners and swaying trees.

Image:Level editor wind object.png

The Wind Object may be found by right clicking on Terrain World and selecting:

Insert>New Wind Object

==Visual Effects (VFX)==

Placeable visual effects like flames or smoke are considered to be art assets in the Dragon Age toolset, so you need to place them from within the Level Editor.

The [[VFX Tutorial]] provides guidance on creating and placing visual effects.

==Path finding and Obstructions==

The path finding process lays down a grid of points that are marked "accessible" if they can be reached from a path finding start spot via passable terrain. This is essentially a flood-fill algorithm.

You must create an [[Exportable area]] before you can generate any path finding data.

* Click on the purple + in the tool bar ([[File:IconAddExportableArea.png]]). This will open an Area Properties window. The [[Level editor]] page has more details on this process, so I will just keep these steps very basic.
* Name your Exportable Area in the Layout Name field of the Area Properties window. The name of an exportable area layout is limited to seven characters. BioWare uses the following naming system:
** Three-letter prefix that describes the region or plot the layout is for. For example, "ost" for Ostagar and environs.
** Three-digit number that uniquely identifies the layout within that region. Increments of one hundred are commonly used for major areas to allow sub-regions to be grouped together.
** A single character identifying variants of the layout. For example, a "d" suffix for the "daytime" version of an exterior layout. "d" is also often used to mean "default", for areas where day and night are irrelevant (deep in a cave, for example).
* Define your walkable area. Do this by clicking the Define Area button in the Area Properties window. The green box must include any areas that you want players to be able to walk. If you click in a corner of the level the green box will appear there. You can then expand it by dragging the corner.
* Close the Area Properties window.

In most cases you will want to block off certain areas of your terrain.
* Turn on the Build Terrain Blocking tool. It is the middle mountain icon.
* Using left-click to place and right-click to end chains/delete, place down blocks or 'walls' around areas you don't want the player to enter
* Be sure to provide visual clues if it isn't obvious why the player can't walk there.

Now that you have your exportable area you can generate path finding data.

* Place a Starting Point in your level. I found that path finding does not work if you place the Starting Point before you have an Exportable Area. To place a Starting Point click on Setup Start Point in the tool bar.
* Record the name of your Starting Point by clicking on it and looking at the name in the Object Inspector. Do not change the name - changing the name can prevent path finding from working.
* Click Exportable Area Properties in the tool bar to open the Area Properties window. Put the Start Point name in the appropriate field and close the window.

You should now be ready to generate pathfinding data by clicking on the Generate Pathfinding for Active Area button in the tool bar.

==Converting Levels into Areas==

Click on Do All Local Posts (you can avoid problems by generating a lightmap and pathfinding before doing local posts). This can be found in the menu at Tools>Export>Do All Local Posts

Your level has now been converted and can be used to make an area. The [[Area tutorial]] will walk you through what to do next.

[[Category:Tutorials]]

Known issues

2022-02-01T16:19:41Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

This page is somewhat redundant as it duplicates things from pages such as [[Installation troubleshooting]]. However, it is gathering place for issues related to specific builds, along with plans to fix them.

We're now moving detailed bug reports to individual pages, grouped in the category [[:Category:Toolset bugs|Toolset bugs]]. See [[Reporting a bug]] for instructions on how to submit bugs. This page will remain as a high-level summary of current known issues.

==Final Build==
===Toolset Issues===
*[[Bug: Out of memory message]]
*[[Bug: New level doesn't work correctly]]
*[[Bug: Bulder to Player with new level issue]]

==Build 1.0.1008.0 (Installer Version 1.01)==
===Installer Issues===

*[[Bug: Cannot open file for writing C:\Program Files\BioWare\...]]

====[[Unable to connect to the database]]====
Unfortunately this will always be a potential issue, as it is an issue with connecting to SQL Server 2005 Express, which can fail in as many ways as there are users. The latest help can be found [[Unable to connect to the database|here]].

===Toolset Issues===

*[[Bug: SpeedTree rendering distance]] - it has been reported that in at least one case a user can't set his tree rendering distance above 20m.
*[[Bug: ConfigureToolset application fails to set a registry key ]]. This bug requires a workaround if you need to use ConfigureToolset to change your database settings.
*[[Bug: Computer names with non-English characters can cause checkout problems]]. This can cause checked-out resources to be recognized as checked out to the wrong user, making them impossible to edit.
*[[Bug: Unable to save a new module]]. This can occur for users with long usernames.
*[[Bug: Water plane missing in-game]]. Level art that's posted when not in the single player module is missing its water planes.

==Build 1.0.982.19 (Installer Version 1.00)==
===Installation Issues===
*[[Bug: Endless reboot cycles after install under Windows XP SP 2]]
*[[Installation into a directory with a long path name]] (this arose with Steam installations in particular)
*[[Bug: Installer hangs at the stage of Execute:regsvr32.exe /s "C:\Dragon Age\tools\Engine.dll"]]
*[[Bug: Cannot open file for writing C:\Program Files\BioWare\...]]

====[[Unable to connect to the database]]====
Unfortunately this will always be a potential issue, as it is an issue with connecting to SQL Server 2005 Express, which can fail in as many ways as there are users. The latest help can be found [[Unable to connect to the database|here]].

===Toolset Issues===

*[[Bug: GFF and ERF editors require a keyfile]]
*[[Bug: FaceFX not appearing in menus]]
*[[Bug: Lightmapper causes shading artifacts along chunk boundaries]]
*[[Bug: Water plane missing in-game]] - If you create a level with a water plane in it, the water is appearing properly in the toolset, but is non-existent in the game.
*[[Bug: Toolset freezes when exporting or compiling]]

====Exporting resources can cause the main campaign to fail, and can corrupt savegames made after installation====
*See [[Plot GUID bug]], or http://social.bioware.com/forum/1/topic/8/index/114380 for more details, and for information on how to clean up after this error strikes.

An incompatibility has been discovered between the core resources in the database released with the toolset and the core resources used by the existing main campaign. This can cause the main campaign to stop working correctly after any resources are exported from the toolset.

{{Dashedborder|This is fixed in version 1.01 of the toolset. The underlying problem was identified and fixed, and a new set of core resources has been put into the database that does not give this problem anymore.}}

== Older known issues (Beta issues, needs cleanup) ==

=== Build 925 issues ===

When working on a multiple-monitor system, it is possible that rearranging the monitors will cause the previously-recorded default location of popup windows such as "manage modules" to be off the edge of the display area where it can't be seen or manipulated. This can lock up the toolset, since the toolset won't respond until the popup is dismissed. To reset the position of the popup windows, delete the file "My Documents\BioWare\Dragon Age\Toolset\Layouts3.xml". It will be recreated the next time the toolset is run using default values.

=== Build 888 issues ===

Build 888 and subsequent builds has some built-in assumptions that it will be installed in "Program Files\Dragon Age". If it's installed elsewhere, the resource processor (used during certain resource exports, the generation of VO, FaceFX, and other activities) will become confused and fail with log messages such as "Unable to load C:\Programme\Dragon Age\tools\ResourceBuild/Settings/ResourceBuilder.xml" or "Failed to copy template 'C:\Program Files\Dragon Age\tools\ResourceBuild\Processors\VO_template_project.fdp' to 'C:\DOCUME~1\Owner\LOCALS~1\Temp\DragonAgePlaceholderVO\VO_template_project.fdp'" To correct this, go to the Tools -> Options -> Environment -> Resource Build Path setting and correct the path listed there to point to the resource builder's actual location.

This appears to have been resolved in 1.0.982.0

=== Build 773 issues ===

*If you use resource history to view past revisions of a large conversation and then try to diff two of them, the toolset will crash. You can diff small conversations correctly. It's not known exactly what the cutoff between "large" and "small" conversations are as far as this bug is concerned.

*Under Vista, the default install of MSSQL doesn't support multiple different user accounts on the same machine. Attempting to start the toolset from the wrong user account will pop up an error advising that you use the configuration tool to correct the database settings, but the database settings are not in error - it's the database server itself that's refusing to cooperate. One possible solution is to use SQL Server Management Studio Express to set up MSSQL properly.

* When loading a saved game file, areas and objects contained therein are loaded from the save rather than the game resource. This means that if you save your game inside an area, make changes to the area and export them using the toolset, and then reload your game, none of the changes will appear. The changes will only appear if you start a new game. This affects objects such as waypoints, creatures, placeables, and so on.

{{languages}}
[[Category:Toolset installation]]

Item tutorial

2022-02-01T16:18:46Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

{{Infobox items}}

In Dragon Age, "items" are things that a player can take into his inventory and carry around with him through the game. They are distinct and very different from placeables, which are interactive objects that are visible in the game area. Items cannot be placed directly on the area map, they can only be added to the inventory of placeables or creatures in the area. They can also be put in a player's inventory using scripting, a common occurrence for "plot" items. This tutorial doesn't cover any of that; see the tutorials on creatures, placeables, or scripting for more detail. This tutorial just covers the creation of items themselves.

Note that due to the large number of items the toolset has to deal with, the item list displayed while editing creature and merchant inventories is cached. If you create a new item you'll need to refresh the toolset to see them in these lists (the "refresh" option is listed under the View menu).

== A longsword ==

First, select the item palette from the palette menu ([[Image:IconItem.png]]). Right-click on the empty item list and select "New -> Item" (alternately, go to the file menu and select "New -> Item" from there) and a new item resource will be created. You'll need to name it; we're going to create a sword for starters so we'll call it "longsword". This is just the internal name used by the game to keep track of the item, not the name the player will see, so you can pick whatever naming scheme makes things easiest for you.

The default base item type is "Weapon - Longsword", which is what we want for this particular item and so we'll leave it at that. Most of the other properties can be left as defaults, too. The ones you'll want to change right off the bat are:

*Name - the name of the item that the player actually sees in-game. We'll use "Longsword".
*Description - a short block of text that the player can see if he "examines" the item. A basic "This is a longsword." will suffice.
*Icon - the small image that's displayed next to the item's entry in the inventory, and in the equipped item slot when the player has the item equipped. A set of icons is included in the core resources, all prefixed with "ico_"; we'll use "ico_longsword.dds" for this item.

Since not all longswords look the same, you may wish to choose from a set of alternate models for your item. The "Item Variation" field does this. Unlike Neverwinter Nights, swords cannot be customized by putting together several different parts.

MaterialProgression and MaterialType are of particular significance to weapons and armor; they determine the general quality of the item (magical effects are added in other properties)

!! need to look up some details on materials for this !!

[[Image:Item editing longsword.png]]

The "Attributes" section includes a base cost field (measured in copper pieces - silver and gold are calculated automatically), whether the item is damaged or intact, and a variety of advanced properties that can be set for magical weapons.

You have to set the base cost manually. As far as I can see, the base cost of official items is determined by the Item Variation. So, if we're making a sword of variation Longsword 2, have a look at the offical longswords in the Object Inspector. It turns out that gen_im_wep_mel_lsw_oth is Longsword 2, so we can copy the base cost (1500 cp). Don't worry about material or item properties - the game automatically adjusts the buy/sell cost for that (see [[Item#Item_Cost]]).

"Item Properties" brings up a display for adding properties that go into effect whenever the item is equipped. These are any special power, effects, or stat variations beyond the basic item attributes. There are two general classes of properties that can be added; abilities and restrictions. Abilities are properties that enhance the item's function in some way - increased damage against certain targets, bonuses to the character's attributes, and so forth. Restrictions are limitations that can be put on who can use the item - for example, only certain classes, or only characters with certain skills or talents. There are also visual effect properties. Each property also has an associated power, which determines how "strong" the property is - generally, how much of a bonus it gives.

An item can have up to five properties on it, including both abilities and restrictions in the total.

[[Image:Item properties.png]]

You can also assign an item an "OnHit Effect".

== A shield ==

== A suit of armor ==

== A potion ==

== Inventory Subgroup ==

The Inventory Subgroup (located in the item properties) is a number that designates which category the item belongs to. For quick reference, a list of the more common items can be found [http://social.bioware.com/wiki/datoolset/index.php/Inventory[here]]

[[Category:Items]]
[[Category:Tutorials]]

Installing the toolset

2022-02-01T16:18:38Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

The Dragon Age Toolset installer comes with several pieces of third-party software that are needed for the toolset to function. They are:

* DirectX 9.0c
* Visual C Runtime Library
* Microsoft SQL Server Express 2005 Edition
* Nvidia PhysX drivers version ONLY PhysX_9.09.0203_SystemSoftware
* Phyton Version: ActivePython-2.5.5.7-win32-x86. Extremely important for Lightmapping

These components will be installed along with the toolset by the toolset's installer.

== Location ==

The first screen you'll get to after starting the installer and passing the title page is the install location selector. The toolset can only install the program into a specific subdirectory of the Dragon Age game directory, so you won't be able to alter the installation path; it's for informational purposes.

'''Note:''' MSSQL Express 2005 is bundled with this toolset and is required for it to function. Unfortunately, MSSQL Express 2005's installer has a limitation that prevents it from installing to a directory path that's longer than 58 characters.[http://support.microsoft.com/kb/935371]

However, this limitation no longer affects the installation, since version 1.01 of the toolset installer installs the SQL instance to a shorter path to avoid this issue. It now installs to Program Files\DAODB\. See [[installation into a directory with a long path name]] for details.

== Components ==

The next screen after location has been selected is where you can choose which components to install. There are only two selectable components here; Core Resources (the toolset itself) and Microsoft SQL Server Express. To run the toolkit you'll obviously need to install the Core Resources option. SQL Server is presented as a separate option so that if you already have a database server installed on your system you can use that instead of installing a whole new one.

If you don't have an SQL server installed, or if you don't know whether you have one installed, it's safe to go with the default and install SQL Server Express. SQLServer's installer will check the existing components and, finding that all required components are already in place, won't do anything after you click "finish."

== Manual database selection ==

If you choose not to install SQL Server Express, the installer will ask for a database server and database name to install the toolset's resource database to instead. The default server is <code>.\BWDATOOLSET</code> and the default database name is <code>bw_dragonage_content</code>.

== Installation ==

Once you have selected these options the Dragon Age toolset will begin the installation process. This can take a while. When the install process is finished you'll be given the option to read a readme.txt file.

The toolset will create a start menu folder named "Dragon Age". The start menu folder will include a link to start the toolset, a link to the toolset's uninstaller, and a link to the toolset's external configuration utility.

The installer will write a log file in your My Documents folder. If installation fails this log file will be helpful for debugging purposes.

If you are installing over a previous version of the toolset, you may need to update the format of your old database to make it compatible with the new version of the toolset. See [[database migration]] for details.

=== Lightmapper ===

The [[lightmap|lightmapper]] is the tool used to calculate lighting in level layouts. You only need to use it if you're going to be creating or modifying level layouts. The lightmapper included with the toolset requires Python to run but Python isn't currently bundled with the toolset, so if you don't already have it installed you'll need to do the following:

# Install [http://www.python.org/ftp/python/2.5.4/python-2.5.4.msi Python 2.5.4 ]
# Install the [http://sourceforge.net/projects/pywin32/files/pywin32/Build%20214/pywin32-214.win32-py2.5.exe/download win32 extensions] for Python 2.5 '''OR'''
# Install [http://downloads.activestate.com/ActivePython/releases/2.5.5.7/ActivePython-2.5.5.7-win32-x86.msi ActiveState Python 2.5.5.7] '''Note''': The Community Edition of this release is no longer available! If you have not purchased a Business or Enterprise license from ActiveState you will need to use the python.org release and the pywin32 extensions (2014-04-13).

The easiest way to do this is to download and install ActiveState python which comes with the needed extensions. Just click through the defaults on the installer and you will be ready to go. If you want to use python.org installer, maker sure to install it first, then install the win32 extensions.

* If you don't have Python installed and try to run the lightmapper, you'll receive a standard Windows error message indicating that "EclipseRay.exe has stopped working.

* Note for 64 bit machines: There appears to be a bug with the 64-bit version of ActiveState Python 2.5 for Windows that prevents the lightmapper from functioning. Install the 32-bit version instead, it works. The 32-bit version is the one linked above.

* Do not install both ActivePython and Python.org. This will most likely cause you to get an Error Code 1 when rendering lightmaps.

* If you get an error code of -1073741819 this means you either have the 64 bit version or you have a version higher than 2.5. Uninstall and use the installers from the links above.

* If you get an error code of -1073741515, try copying the python25.dll (from your python installation directory) into the <dragon age install directory>\tools\lightmapper folder and restarting the toolset.

=== NVIDIA PhysX ===

Currently, the Toolset relies on a version of PhysX which may not be readily accessible to some users, specifically 9.09.0408. It is not included in the latest NVIDIA drivers, and it can render certain parts of the Toolset, specifically pathfinding and lightmapping, partially or totally inoperable.

If you have the game install disc, the correct PhysX installer is included on it. If not, you can download and install it from [http://www.nvidia.com/object/physx_9.09.0408_whql.html NVIDIA's web site].

== Configuration ==

The external configuration utility [[ConfigureToolset.exe]] (found in the Dragon Age\tools directory) is used to configure the toolset's database connection and to tell the toolset where the game's executable is. You shouldn't need to run the configuration utility during routine usage of the toolset, and if the defaults set up by your installer work you may not need to run it at all.

The default database string is "<code>Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_dragonage_content;Data Source=.\SQLEXPRESS</code>". For advanced configuration, click on the ellipsis button ([[Image:ellipsis.png|link=]]) to open the data link properties window.

==== Moving the database files from the default location ====

By default, the database data and log files are loaded into C:\Program Files\DAODB\data and are called bw_dragonage_content.mdf and bw_dragonage_content.ldf.

For Vista and Win7 installations, the Program Files path will be whatever is commonly used. If you cannot find the folder, do a search for .mdf files and you should get to the required folder.

If you have customized your database during installation, replace the bw_dragonage_content with your database name.

As you start working on your module and checking in resources, the database will grow in size.
If you want to move the database files elsewhere to free up space on C:, do the steps below.
* Make sure you have backed up your dragon age database - See [[Database_backup_and_restore]] for information on how to do it
* Open Microsoft SQL Server Management Studio Express - If you don't have it, you can download it [http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796 here]
* Open a New Query window either by clicking New Query button on the toolbar or going to File -> New -> Query with Current Connection or using the shortcut Ctrl+N
* Type the following into the query window and execute (F5) to detach the dragon age database from the data files
use master
go
sp_detach_db 'bw_dragonage_content'
go
* Move the database files to the new location
* Type the following into the query window and execute (F5) to attach the dragon age database to the data files
use master
go
sp_attach_db 'bw_dragonage_content','<path to the .mdf file>\bw_dragonage_content.mdf','<path to the .ldf file>\bw_dragonage_content.ldf'
go
* To check the path to the data files, you can type the following into the query window and execute it
use bw_dragonage_content
go
sp_helpfile
go

This [http://support.microsoft.com/kb/224071 Microsoft KB article] has more details, if required.

== Uninstallation ==

An uninstaller shortcut is available from the same start menu folder as the toolset itself. It will autodetect the location you installed the toolset in, display it to you to confirm that this is correct, and then after you click "next" it will ask which components to uninstall.

* Core Resources - uninstalled by default, this is the toolset itself.
* Database - Since the uninstaller can't automatically determine if you're using SQLServer Express purposes other than just the Dragon Age toolset, SQLServer is ''not'' uninstalled automatically by default. To have the uninstaller remove the database server as well, unselect this checkbox.

The uninstaller is generated on installation and therefore isn't signed. This may cause Vista to complain under some circumstances but shouldn't affect the uninstaller's functioning.

== Troubleshooting ==

See [[installation troubleshooting]] for a list of common problems that can occur during installation and how to correct or work around them.

If you experience a crash, logs can be found in <code>My Documents\BioWare\Dragon Age\Toolset\logs</code>. The log filenames will include the date on which the log file was created. Sending in a log will help greatly with bug fixing.

== Documentation ==

Documentation is currently provided via the wiki at:

http://social.bioware.com/wiki/datoolset/

{{Languages}}
[[Category:Toolset installation]]

How-tos

2022-02-01T16:18:35Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

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.

See also [[Useful Scripts]] for "how-tos" that specifically involve [[script]]ing.

See [[compiling 2DAs]] for methods of converting Excel source files into GDAs.

__TOC__
== 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

Or, for a custom module, COPY TO

%My Documents%\BioWare\Dragon Age\addins\%Module Name%\core\override\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*

== External Tutorials ==
[http://bg2redux.student.utwente.nl/trac/wiki/How%20to%3A%20Add%20New%20Music%20and%20Sounds How to: Add New Music and Sounds] by Cuvieronius of the [http://www.gamersnexus.net/bgr-home Baldur's Gate Redux] Team.

[http://social.bioware.com/forum/Dragon-Age-Toolset/Toolset---Cutscenes/Cutscene-Music-to-replace-in-game-vanilla-question-Solved-2847712-1.html How to: Insert Original Edited Music into a Cutscene] by DahliaLynn.
[[Category:Tutorials]]

Getting Started

2022-02-01T16:18:21Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

== Installing the Toolset ==

* [http://dragonage.bioware.com/ Install the game.] Ensure that Dragon Age is installed before dabbling in the toolset, as it relies on the game's resources and engine, and cannot function without them.
* [[Creating an account|Create an account.]] In order to contribute to pages on the DA Builder Wiki or participate on the BioWare Social Network, you will need to create an online user account.
* [http://social.bioware.com/user_bw_games_register.php Register the game.] In addition, you will need to register your copy of Dragon Age before gaining access to game-owner only content, including the toolset.
* [https://dragonagekeep.com/en_US/downloads Download the toolset.] The Dragon Age toolset contains the same functionality used by BioWare to craft the official campaign, and provides the power and flexibility to create your own custom content and adventures.
* [[Installing the toolset|Install the toolset.]] Refer to this page for general information and step-by-step instructions to installing the toolset.
* [[Installation troubleshooting|Troubleshooting.]] Refer to this page for specific information on how to resolve issues in the event that toolset installation goes awry.
* [[Known issues|Known issues.]] Refer to this page for a currently documented list of known issues and bugs in the current version of the toolset.

== Overview of the Toolset ==

*[[Overview of the toolset|Overview of the toolset:]] A quite good overview of interface layout and toolset resource management.

*[[Comparisons with other toolkits|Comparisons with other toolkits:]] A brief feature overview of the Dragon Age toolset for users familiar with similar software (e.g., the NWN Aurora Toolset).

== Starting the Toolset ==

{| align=right
|[[File:Titlebar components.png|thumb|300px|right|How to determine which module is currently open]]
|-
|{{Warnbox|Do not edit Single Player or Core Resources with custom content!|300px}}
|}
Before using the Toolset, it is important to take note of what [[Module|module]] the toolset has open. A module is a "container" in which game resources are stored in; you will only be able to see the resources for the currently open module (and any modules that it is marked as depending on). The default module when first starting the Toolset is the "Demo" module, which is a very small and simple module intended to show several common resource types in a basic pre-built adventure that you can experiment with safely.

The main Dragon Age: Origins campaign resources are stored in a module named "Single Player". If you're just starting out with the toolset, it can be dangerous to edit these, as you could inadvertently corrupt your main campaign. Take care when exploring not to edit any of those resources without knowing what you're doing.

The first basic steps in the Toolset shall be to create your own [[Module]]. The only possible type of Module is "Addin", but note that this name is somewhat misleading; it is possible to have "standalone addins" that are completely separate from any other module (such as the main campaign).

*See: [[Module]] - For a general overview of how a Module works, and what awaits you.

== Using the Toolset ==

As described in the overview linked to above, the game uses a wide variety of resource types. A "resource" is something that you can create, such as a script or a creature, and you will often need to combine many different resources together to accomplish a particular design goal. The toolset consists of many independent tools for working with these different types of resources. These tools can be well discussed separately.

The next best step for learning the toolset would be to look into the categories on the [[Main Page]], which link deeper into each topic and the tools involved with them. If you are having questions at a specific part of the toolset give this Wiki a search for it. This can be very specific, and always worth a try. You may also find the [http://social.bioware.com/forum/1/subindex/70 toolset forums] to be useful in solving specific problems the documentation here may not cover.

A list of certain Interest, and the 3 Resource types:
*[[Design]] - Talks mainly about Designer Resources, such as Items, Monsters, NPC's, Vendors, etc.
*[[Art]] - Talks mainly about Art Resources, such as Models, Textures, Facemorphs, etc.
*[[2DA]] - Talks about the 2DA Resourcetype, which is sets of Gamewide usable variables and references.

=== Tips and tricks ===
*[[Shortcuts]] - Assorted toolset shortcuts.
*[[Common Problems]] - Little things that most people will need to know but that are not necessarily obvious.

== Specials ==

It is currently not possible to delete a module by normal means.

If you run into a problem that the documentation doesn't cover and that you can't fix, contact toolsetsupport@bioware.com

== Removing Custom Content ==

This section describes how to remove all custom content from the game.

To be on the safe side, before you start, you might want to

* disable all the unofficial add-ins on the DLC screen in game
* play a recently saved game (using the Force Load option) to confirm that it works reasonably well without the add-ins
* back up your Documents > Bioware folder

Since you can't be certain that all authors have followed best practice, you'll need to clean out all the folders that can be customised.

In Documents > Bioware > Dragon Age,

* In the AddIns folder, delete all the folders except Demo, Single Player and anything starting with dao_prc (the official DLC).
* Delete any files In the AddIns > Single Player folder and sub-folders (you might get away with just deleting the Single Player folder, but caution never hurts).
* Delete any files from the modules and packages folders.

== Dragon Age 2 ==

See [[Dragon Age 2]] for more information.

{{Languages}}

GFF editor

2022-02-01T16:18:16Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

[[Image:GFF editor.png|thumb]]

The GFF editor is a tool for opening and editing [[GFF]] files, such as savegames. See [[GFF]] for information about the GFF file format.

== Out of memory error ==

The GFF editor that comes with the toolset is not very efficiently programmed, unfortunately. When opening GFF files as small as 7 megabytes or so (which savegames can easily reach) the editor's memory usage can skyrocket above 3 gigabytes and potentially cause the editor to crash.

While the memory usage itself can't be worked around presently (it's an inherent flaw in the editor), it is possible to make the editor less prone to crashing when it reaches such large memory sizes using a trick developed by Krayzie_3334.[http://social.bioware.com/11689/blog/707/]

# Download [http://www.ntcore.com/ CFF Explorer],
# Open Dragonagetoolset.exe with CFF (make a backup first)
# In the Left-Hand Pane, Left Click ( Highlight ) "File Header"
# In the Right-Hand Pane Click on the "Click here" box.
# In the "Characteristics Window" Check the "App can handle >2GB address space" box.
# Click OK
# File -> Save & Exit.

Please note that the above workaround requires that you have at least 4 gigabytes of RAM.

Dragon Age 2

2022-02-01T16:06:12Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

No toolset has been announced for Dragon Age 2 at the time of writing.

Nevertheless, some of the information in this wiki will help DA2 modders, who may wish to share their knowledge here, too.

==Clarity==

Obviously, since this wiki was originally written for DAO, by default it refers to DAO, not DA2.

The same applies to the [http://social.bioware.com/forum/1/subindex/70 Toolset Forum] and [http://social.bioware.com/browse_bw_projects.php Projects], where DA2 modders are most welcome.

So, it would help everyone if DA2 projects, forum posts, wiki articles, sections and comments were clearly labelled as DA2, to avoid confusion.

Ideally, information which only applies to DAO should be labelled, too, but that isn't going to happen comprehensively, so make no assumptions!

==Overview : how DA2 differs from DAO==

This information is evolving. Early days!

* Since there is no toolset or source material for DA2, it is not possible to work with [[Design | design resources]].

* However, it is possible to make simple changes to the exported DA2 resources (areas, creatures, conversations etc) that ship with the game.

* It may also be possible to make new resources with the DAO toolset, export them, and package them for DA2.

* The official exported resource files are held in [[ERF]] containers. DA2 uses version 3.0 for both main game content and DLC, whereas DAO uses version 2.0 for main game and expansion resources and version 2.2 for DLC.

* The exported resource file format is [[GFF]]. DA2 uses versions 4.1 and 4.0, while DAO uses version 4.0. Both games also use version 3.2 for some content types.

* The DAO toolset does not support ERF 3.0 or GFF 4.1 (see next section for alternate tools). With an available version 2.0 erf file, courtesy of Thought Process, the DAO toolset can be used to compile scripts that can be used in DA2. Similar custom erf files could likely be made to enable using models from DA2 in the DAO toolset to create new creature templates, though these will likely require hand editing in a stand-alone gff editor for use in DA2. Since many DA2 file types are the same as their DAO counterparts (with perhaps minor differences), those files will likely work as exported from the DAO toolset; if not, there are ways to tweak them manually.

* [[List of file types|Resource formats]] are generally the same (or similar) for both DAO and DA2.

* One exception is that the DAO conversation format (.dlg) has been replaced by .cnv in DA2. However, they share the same basic node structure, and it may be possible to convert dlg files to cnv.

==Builder Resources==

Some of the basic tools are

* [https://www.nexusmods.com/dragonage/mods/4512 pyGFF] for working with GFF files
* [https://www.nexusmods.com/dragonage/mods/214 GDApp] for editing 2DA files and exporting them to Excel
* [http://social.bioware.com/project/4419/ ERFv3 Packer] for putting files into the new format ERF container

See also [http://code.google.com/p/dragon-age-open-house/wiki/BSN_DA2IndexBuilders Community Index].

== Followers ==

* gen00fl_bethany
* gen00fl_carver
* gen00fl_varric
* gen00fl_anders
* gen00fl_aveline
* gen00fl_isabela
* gen00fl_merrill
* gen00fl_fenris

Database

2022-02-01T16:05:51Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

The toolset uses a named SQL instance, so you want to connect with your client using the format:

.\BWDATOOLSET

This is the default, but it's possible to install or configure the toolset to use a different database. To find out what your database server is called, go to control panel->Administrative Tools->Services and look for a service that is called something like: "SQL Server". The name of the server is the name you need to use for this.

The toolset uses a registry setting for the database connection. The toolset configuration tool normally edits this so you shouldn't ever need to do it manually, but it can be found at HKLM\Software\Bioware\Dragon Age\Toolset\Common\MSSQL_IO\ServerName
(64 bit needs HKLM\Software\Wow6432Node\Bioware\Dragon Age\Toolset\Common\MSSQL_IO\ServerName ).

== Backing up your database ==

Backing up a database is not as simple as just copying a file. You'll need to export the data from the database in a more portable form.

There are currently three approaches to backing up your database.

=== SQL Express Management Studio ===

Go to Microsoft and download the SQL Express Management Studio for free.

This will allow you to have a more friendly GUI interface into the toolset's database. It also means you can cause damage to the database as well, so be cautious with this tool. After registering your server you can backup your database to a file, in the same manner that the initial database has been packaged for the installer. In the future you can then restore that backup over top of the newly created database and then apply the migration scripts.

=== Batch file and command line ===

You can create a batch file with the backup command in in.

You can then run the batch files to backup your database and restore it, with you controlling the file names and such.

The toolset comes with a simple batch file for backups and restores, you can find it in the Dragon Age\tools\DatabaseUtilities\Backup_Restore directory. Edit the "config.ini" file to set the names and locations for database backup and restore files.

=== Builder to builder export ===

In the toolset you can go to the menu and select Tools->Export Database (Database Export)
This will allow you to save out the entire source data into an xml file.
When you reinstall you can then go to tools->Database Import and bring all the data back in.
This one is a bit more work in that it will recreate everything and not put everything back the way it was.
A small difference but still a difference.

== Useful queries ==

=== Conversation Search ===

<pre>
SELECT m.Name, uri.Folder, uri.ResRefName, st.Text, cl.Icon, st.StringID
FROM dbo.v_ModuleTree mt
JOIN dbo.t_Module m ON m.ID = mt.AssociatedModuleID AND mt.ModuleID = @ModuleID
JOIN dbo.v_UserResourceInfo uri ON uri.ModuleID = mt.AssociatedModuleID
JOIN dbo.t_ConversationLine cl ON cl.ModuleResRefVersionID = uri.ModuleResRefVersionID
JOIN dbo.t_StringText st ON cl.TextStringID = st.StringID AND cl.ModuleResRefVersionID = st.ModuleResRefVersionID
WHERE st.Text LIKE '%' + @Search + '%'
AND ( cl.Icon = @Icon OR @Icon = -1 )
ORDER BY m.Name, uri.Folder, uri.ResRefName, cl.Icon
OPTION ( force ORDER )
</pre>

=== Script Search ===

<pre>
SELECT m.Name, uri.Folder, uri.ResRefName, uri.resrefid,
'... ' + substring( s.text, patindex('%' + @Search + '%', s.Text) -30, len(@Search)+60 ) + ' ...' as matched_on
FROM dbo.v_ModuleTree mt INNER JOIN
dbo.t_Module m ON m.ID = mt.AssociatedModuleID AND mt.ModuleID = @ModuleID INNER JOIN
dbo.v_UserResourceInfo uri ON uri.ModuleID = mt.AssociatedModuleID INNER JOIN
dbo.t_Script s ON s.ModuleResRefVersionID = uri.ModuleResRefVersionID
WHERE (s.Text LIKE '%' + @Search + '%')
ORDER BY m.Name, uri.Folder, uri.ResRefName OPTION (force ORDER)
</pre>

== Creating a blank database from scratch ==

To set up a blank new database (or if you'd like to examine the schema that an existing database is built on), there are two SQL scripts that need to be run.

*[[Content Create Script.sql]] sets up the tables. If you have a slow connection note that this page is over half a megabyte in size.
*[[Core Data Script.sql]] puts some basic core data into the tables that the toolset needs in order to run.

[[File:SQL Server Management Studio Express database roles.png|thumb|The interface for working with roles in your database]]

Before running them you'll have to ensure that your database has the following three roles:

* bw_db_read
* bw_db_write
* bw_db_lock

You may get three warnings that begin "Cannot add rows to sys.sql_dependencies for the stored procedure because it depends on the missing table...". These are not a problem, the script is creating stored procedures that refer to tables that only get added later in the SQL script.

Note: as of version 1.01 of the toolset, upon first being installed the toolset will default to the "Demo" module when it can't find the previously-open module in the database. This script doesn't create the Demo module, so the toolset will give an error message and fail to run. To fix this, open the [[DefaultSettings.xml]] file in Dragon Age\tools and change

<CampaignID>3</CampaignID>

to

<CampaignID>2</CampaignID>

(CampaignID 2 is the Single Player module.)

You'll then be able to start the toolset and change modules as you please.

If you wish to attempt to import the core and single player campaign resources you can find a [[DADBDATA]] file containing them at [http://social.bioware.com/project/1331/#files].

Also:
For international users (If Your sql server 2005 uses different database collations by default):

When creating db_dragonage_content please remember to change collation from Your local one to:

'''SQL_Latin1_General_CP1_CI_AS'''

this is the only collation that guarantees You that those .sql batch scripts will work properly.

== Setting up SQL Express 2005 manually ==

See [[Manual database installation]].

== Troubleshooting ==

[[Installation troubleshooting]] has information for troubleshooting database issues that arise during installation, and that might also be applicable post-installation.

[[Category:Database]]

Creating an account/ru

2022-02-01T16:03:04Z

Ashhawk: BSN link flagged for maintenance

{{BSN link}}

{{rupage|Создание учётной записи Bioware|Основная информация}}

== Создание учётной записи в социальной сети Bioware ==

Чтобы редактировать страницы этой энциклопедии, чтобы создавать проекты и принимать участие в обсуждениях в [http://social.bioware.com социальной сети Bioware], вам необходимо создать учётную запись пользователя Bioware. Эта учётная запись вам также понадобится, чтобы скачать тулсет с его [http://social.bioware.com/toolset.php официальной страницы].

Ниже выберите пункт, наиболее подходящий вам.

=== У меня есть учётная запись на форумах Bioware (на основе имени пользователя) ===

С помощью имеющейся учётной записи вы сможете войти в социальную сеть Bioware, но всё-таки потребуется указать дополнительные данные.

* Пройдите по ссылке: http://social.bioware.com/login.php.
* Введите используемые на форумах BioWare логин и пароль.
* Следуйте инструкциям для завершения настройки своей учётной записи.
** Большая часть информации обнаружится и заполнится автоматически, включая отображаемое имя.

В дальнейшем вы сможете входить в социальную сеть Bioware используя адрес электронной почты и новый пароль, или же dfib cnfhst данные с форумов Bioware. Также вы сможете войти на старые форумы используя адрес электронной почты.

=== У меня есть учётная запись на форумах Bioware (на основе адреса электронной почты) ===

Этот вариант возможен, если на форумах вы зарегистрировались недавно. Во время регистрации вам должно было быть предложено создать учётную запись EA.

* Пройдите по ссылке: http://social.bioware.com/login.php.
* Введите используемые на форумах BioWare адрес электронной почты и пароль.
* Следуйте инструкциям для завершения настройки своей учётной записи.
** Большая часть информации обнаружится и заполнится автоматически, без запроса.

=== У меня есть учётные записи из Spore, Madden'07 и т.п. ===

Если вы раньше создавали учётные записи EA через их игры (Spore, Madden'07), у вас должна быть учётная запись EA, позволяющая работать в социальной сети Bioware.

* Пройдите по ссылке: http://social.bioware.com/login.php.
* Введите используемые адрес электронной почты и пароль вашей учётной записи EA.
* Следуйте инструкциям для завершения настройки своей учётной записи.
** Большая часть информации обнаружится и заполнится автоматически, без запроса.

С помощью этой учётной записи вы также можете войти на наши старые форумы.

=== У меня есть учётная запись "'''Extranet.bioware.com'''" ===

Учётный записи Extranet больше не используются. Перейдите к предыдущим пунктам, либо приступите к созданию новой учётной записи.

=== У меня нет учётной записи ни на форумах BioWare, ни в EA ===

* Пройдите по ссылке: http://social.bioware.com/signup.php.
* Следуйте инструкциям для создания новой учётной записи.
** Выберите отображаемое имя для сайта, оно должно быть уникальным.

== Возможные проблемы ==

* Если выяснится, что отображаемое имя пользователя уже используется и это ваше отображаемое имя с учётной записи с форумов Bioware, вы должны войти, используя данные с учётной записи на форумах Bioware, для подтверждения ваших прав.

* Для получения дополнительной информации смотрите [http://social.bioware.com/help.php справку социальной сети Bioware].

{{Languages|Creating an account}}

Creating an account

2022-02-01T15:59:35Z

Ashhawk: BSN link flagged for maintenance

{{BSN link}}

== Creating a Social site account ==

In order to edit pages on this wiki or create projects on the main [http://social.bioware.com social website], you require a user account. This user account is the same one used in the [[Main_Page|DA toolset]] as well as in the final Dragon Age game build.

Choose the section below that most closely matches your situation.

=== I have a BioWare forums account (username-based) ===

BioWare forums accounts still work for authentication, but the new site requires a few additional details before you can proceed.

* go to: http://social.bioware.com/login.php
* log in using your BioWare forums username and password
* follow the instructions to complete the setup of your account
** most of your personal details will be detected and filled in, including display name

You will then be able to log in in future using either your email address and the new password you choose, or your old BioWare forums credentials. You will also be able to log into our old forums sites using your email address.

=== I have a BioWare forums account (email address-based) ===

This should be the case if you created your BioWare forums account recently. You should have been prompted to set up an EA account during that signup.

* go to: http://social.bioware.com/login.php
* log in using your BioWare forums email address and password
* follow the instructions to complete the setup of your account
** most of your personal details will be detected and used automatically without prompting

=== I have an EA account from Spore/etc ===

If you have previously created an EA account through any recent EA game (i.e. Spore, Madden '07, etc), you already have a master account that will work

* go to: http://social.bioware.com/login.php
* log in using your EA account email address and password
* follow the instructions to complete the setup of your account
** most of your personal details will be detected and used automatically without prompting

You will also be able to log into our older forums websites using this account.

=== I do not have either a BioWare forums account or an EA account ===

* go to: http://social.bioware.com/signup.php
* follow the instructions to create your new account
** you will be prompted to choose a display name for the website; this must be unique.

=== I have an extranet.bioware.com account ===

Extranet accounts are no longer used. Forget about it entirely and proceed as per one of the above sections.

== Troubleshooting ==

* if you are prompted that the display name is already in use, and it's your own BioWare forums account, you must enter your old BioWare forums password to confirm ownership.

* See [http://social.bioware.com/help.php the Social Site help FAQ] for additional assistance.

{{languages}}
[[Category:Toolset installation]]

Console

2022-02-01T15:57:48Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

Up in the View Menu other windows you will see one called "Console".

This is where you would enter console commands that allow the toolset to interact with the game engine. It is mostly (if not always) used when you have an area open in the Area Editor.

The console commands were built to work with the game not the toolset but some of them do work with the toolset alone.

Your toolset will crash when using some of them so make sure you save your work before trying them.

== Using the console in-game ==

The in-game console is normally not accessible. To enable it run the game with a command line parameter "-enabledeveloperconsole". Then, when the game is running, press the tilde key (~) to bring up the console. This is a prompt in the upper left corner of the screen. The console was used extensively in development for debugging and testing purposes, but in the finished version of the game there's only one console command available; "runscript".

The runscript command does exactly as it says - it runs a script, given as a name typed after a space. So for example:

<pre>
>runscript killallhostiles
</pre>

will cause the script named "killallhostiles" to be run.

You can pass the script additional parameters if you like. These parameters will be stored in the [[module]] variable RUNSCRIPT_VAR. RUNSCRIPT_VAR is a simple string, your script will need to parse it itself.

'''Caution:''' Using scripts like killallhostiles may break scripted plot situations, so you should avoid using it outside of custom content testing.

For example,

<pre>
>runscript usespecificobject demo100pl_lever
</pre>

calls the script "usespecificobject" and puts "demo100pl_lever" into the module RUNSCRIPT_VAR. The script can then call

<dascript>
string sParam = GetLocalString(GetModule(),"RUNSCRIPT_VAR");
</dascript>

to retrieve it.

If you need more than one parameter, pick a separator (a space is usually most appropriate) and split up the string in RUNSCRIPT_VAR appropriately. For example:

<dascript>
//parse out first parameter - the object to use.
nSpaceLoc = FindSubString(sParam," ");
sTemp = SubString(sParam,0,nSpaceLoc);
oDestination = GetObjectByTag(sTemp);
</dascript>

== Console text is invisible in some game installs ==

This problem is caused in some systems by the DVD's installer failing to install the fonts.erf file. Fonts.erf is included on the game disk, so you should be able to redo this part of the installation and properly install fonts.erf by running datasetup.exe manually (which is on the game disk in the "data" directory). This should not be an issue for Steam users since a different installer is involved in Steam installations.

If you still have trouble obtaining fonts.erf from your installation, install the [http://social.bioware.com/page/da-character-creator Character Creator] and then copy fonts.erf from ''Dragon Age Origins Character Creator\packages\core\data''.

Alternatively, install the free 7-zip program, right click on ''data\DataSetup.exe'', select ''7-Zip -> Open archive'', and then extract fonts.erf from ''$0"\packages\core\data\"''.

You can also get the font from the [http://dragonagenexus.com/downloads/file.php?id=1110 Make CONSOLE commands visible] file.

Community support ideas

2022-02-01T15:57:44Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

Unfortunately the team at BioWare that prepared the toolset for public use doesn't have enough resources to address every request or suggestion for improvement. The following is a collection of ideas for improvements that BioWare couldn't get to but that could quite possibly be done by community contributions instead.

; Better, more consistent camera control settings: At BioWare the various different editors of the toolset are used by various different specialists, each focused on their own area of expertise. This has led to different camera controls schemes being used in the area and level editors, for example. The [[camera control]] schemes are set in the [[DefaultSettings.xml]] file. Community-contributed versions of DefaultSettings with more consistent control schemes would be most welcome, or perhaps even a third-party application to make it easier to edit camera controls without XML expertise.

; Voice over management tools : BioWare was unable to release their [[voice over]] and [[localization]] software. The information needed for managing voice over work can be extracted from module [[talk table]]s; it would likely be very useful if there were some sort of application available to make recording VO for dialogue lines easier.

; String ID migration tools : One of the knottier problems that the toolset has with [[builder to builder]] export and import is keeping [[string ID]] numbers from colliding. It frequently has to renumber string IDs as a result. The toolset is able to find and correct all of the string ID references used internally when it does this, but it is unable to automatically find and correct the filenames of voice over wav files and [[FaceFX]] files (these files include the string ID number in their filenames as a way of associating them with their respective lines). A log file is generated during the builder to builder process that records what string ID changes were done, an application that uses this log to rename files could be quite useful.

; Other text tools : the ability to search and replace text in a module's talk table or in its scripts could be useful, especially if there are scripts that refer to specific string IDs (see string ID migration, above).

; Model import tools : Due to legal constraints BioWare was unable to release the export scripts they used to turn 3DSMax models into the format the game uses. Third-party converters and plugins for 3DSMax or for other 3D modeling programs will be essential for full-blown content creation. See [[MMH]] and [[MSH]] for model file specifications.

; Conflict detector : It should be relatively straightforward to extract a list of all the string IDs and [[resref]]s used by any given module. Given that, it should be possible to create an application to automatically compare a set of modules and determine if there are any conflicts between them.

; Variable 2DA management : One of the major differences in how scripting functions between NWN and DA is that you need to pre-define [[local variable]]s in a variable [[2DA]] before they can be used. Changing this would require a major overhaul of how the engine works and so isn't really an option, but perhaps applications could be written to ease local variable management if it proves to be a long-term hassle. In theory one could perhaps scan through all the scripts in a module looking for local variable assignment functions and then try to automatically add the local variables used to local variable 2DAs.(One alternative to local variables can be found in the unlimited variable storage project[http://social.bioware.com/project/1787/]. With a single include file and a simple function call in your module script, you can have unlimited variable and array storage with no need to declare anything in a 2da.)

[[Category:Community feature suggestions]]

Chargenmorphcfg.xml

2022-02-01T15:57:26Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

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

=File Structure=

The contents of the default file are as follows:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[[Category:Character generation]]

Character Save Values

2022-02-01T15:57:08Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

=== Overview ===
This page details character save game values.

=== File Locations ===
For savegame locations under Vista they are, by default under "<user's document directory>\\Bioware\\Dragon Age\\Characters\\<Name of the Character the save is for>\\<save slot>\\<savename>.das". As the save name is part of the save file name (though not the folders) it should be pretty easy to find the proper folder name provided one named one's save something distinguishable.

If you get an "Toolset out of memory"-error when trying to open your savegame there is a temporary unofficial workaround available [http://social.bioware.com/11689/blog/707/ here], if your system is equipped with 4+gb ram.

=== Player Character Stats ===
Found under SAVEGAME_PLAYERCHAR->SAVEGAME_PLAYERCHAR_CHAR->SAVEGAME_CREATURE_STATS->SAVEGAME_STATLIST

For party members the same values should hold. Navigate to:
SAVEGAME_PARTYLIST->SAVEGAME_PARTYPOOLMEMBERS-><number>->SAVEGAME_CREATURE_STATS->SAVEGAME_STATLIST

Note: The following values are recorded by the game in a FIFO order, meaning the moment the game needs to generate a specific key, it will do that.
This way you can have index X in position Y in one save, and in the other the same index X will be in position Z. While changing the keys, pay attention to the proper SAVEGAME_STATPROPERTY_INDEX and not the SAVEGAME_STATLIST index.[[File:STATPROPERTY INDEX.png|thumb|Correct Index]]

{| border="1"
|-
|'''STAT_PROPERTY_INDEX''' || '''Effect''' || '''Maximum Displayed Value'''
|-
| 1 || Strength || 1000
|-
| 2 || Dexterity || 1000
|-
| 3 || Willpower || 1000
|-
| 4 || Magic || 1000
|-
| 5 || Cunning || 1000
|-
| 6 || Constitution || 1000
|-
| 7 || Health || N/A, Clipping Above 1000
|-
| 8 || Mana || N/A, Clipping Above 1000
|-
| 9 || Attack || 1000
|-
| 10 || Defense || 1000
|-
| 11 || Armor || 1000
|-
| 12 || Damage Scale (?) || 10
|-
| 13 || Spellpower Bonus || 1000
|-
| 14 || Health Regen || 50
|-
| 15 || Level || 25
|-
| 16 || Melee Dodge % || N/A
|-
| 18 || AI Behaviour (aggressive/defensive tactics) (?) || N/A
|-
| 19 || Experience Points || N/A
|-
| 20 || Flanking Angle || Degrees
|-
| 21 || Melee Crit % || N/A
|-
| 22 || Deflect Missiles % || N/A
|-
| 23 || Ranged Crit % (?) || N/A
|-
| 24 || Ranged Aim Speed (?) || N/A
|-
| 27 || Character Class || 1 - Warrior, 2 - Mage, 3 - Rogue, 17 - Dog
|-
| 28 || Combat Health Regen || 20
|-
| 29 || Mana Regen || 50
|-
| 30 || Combat Mana Regen || 20
|-
| 32 || Mental Resistance || 100
|-
| 33 || Physical Resistance || 100
|-
| 34 || Attribute Points || 100
|-
| 35 || Skill points || 100
|-
| 36 || Spell and Talent points || 100
|-
| 37 || Background (Magi, Noble, etc) || 1 - Dalish (Elf Only), 2 - Commoner (Dwarf only), 3 - City (Elf Only), 4 - Magi, 5 - Noble (Dwarf or Human), 6 - Grey Warden (IN AWAKENING)
|-
| 38 || Specialization points || 2
|-
| 39 || + Melee Damage || N/A
|-
| 40 || Reduced Hostility || Higher numbers equals faster decay in threat
|-
| 41 || Fatigue || N/A, Negative values possible down to -25
|-
| 42 || Fire Damage Resistance || 75
|-
| 43 || Cold Damage Resistance || 75
|-
| 44 || Lightning Damage Resistance || 75
|-
| 45 || Nature Damage Resistance || 75
|-
| 46 || Spirit Damage Resistance || 75
|-
| 49 || Off Hand Damage || -99 or -97 for characters without Dual Weapon Talents. Seen as 7.85625 on Leliana.
|-
| 50 || Estimated Damage Done || N/A
|-
| 51 || Healing Received % || N/A
|-
| 52 || Resist Magic % || N/A
|-
| 53 || Armor Penetration || 100
|-
| 54 || Backstab/Melee Critical Damage || N/A
|-
| 55 || Fire Damage modifier % || N/A
|-
| 56 || Spirit Damage modifier % || N/A
|-
| 57 || Cold Damage modifier % || N/A
|-
| 58 || Nature Damage modifier % || N/A
|-
| 59 || Lightning Damage modifier % || N/A
|}

Values here can go above their displayed values, they simply are just not shown. Editing specialization points allows one to have more than 2 specializations. Having all 4 specializations seems to work, one can get all the spells/talents and all the icons display properly, however it is unknown if there are long term game effects.

Note a: Available stat points max out at 100. Once you've spent all of them you'll need to enter the level up screen again in order to spend any left over.
b: Index 35 (skill points) only shows up when the save file already has an extra skill point/s.

Typically the structure of the stat properties are:
* STRUCT value of ATTR
* SAVEGAME_STATPROPERTY_BASE, FLOAT32, ''value''
* SAVEGAME_STATPROPERTY_MODIFIER, FLOAT32, ''value''
* SAVEGAME_STATPROPERTY_INDEX, UINT16, ''value''

For health/mana has an additional properties of:
* SAVEGAME_STATPROPERTY_CURRENT, FLOAT32, ''value''
** Current health of the PC/NPC
* SAVEGAME_STATPROPERTY_COMREGEN, INT32, ''value''
** Pointer to Combat Regen rate. Do not edit.
* SAVEGAME_STATPROPERTY_REGEN, INT32, ''value''
** Pointer to Regen rate. Do not edit.

Attribute, Skill, Spell/Talent, Specialization Points have a structure of:
* STRUCT value of SMPL
* SAVEGAME_STATPROPERTY_BASE, FLOAT32, ''value''
* SAVEGAME_STATPROPERTY_INDEX, UINT16, ''value''

=== Player Character Skills and Talents ===

The lists of skills, talents and spells are found under: 
SAVEGAME_PLAYERCHAR->SAVEGAME_PLAYERCHAR_CHAR->SAVEGAME_CREATURE_STATS-> 
And then:
:SAVEGAME_SPELLLIST for spells.
:SAVEGAME_TALENTLIST for talents.
:SAVEGAME_SKILLLIST for skills.

Adding rogue or warrior talents to a mage is possible. However it is necessary to first add the proper class to gain access to the talent tree and talent wanted. 
E.g. to add ‘Dual-Weapon Mastery’ the rogue or warrior class will first have to be added. Talent-id 4020 (rogue) or 4022 (warrior). Then all the prerequisites: talent-id 6 (Dual-Weapon Training), 8 (Dual-Weapon Finesse) and 5 (Dual-Weapon Expert). Finally the Dual-Weapon Mastery’ talent can be added (talent-id 3036) and the mage can now dual wield main hand weapons.

====Skills====

{| border="1"
|-
|'''Tier 1''' || '''Value''' || '''Tier 2''' || '''Value''' || '''Tier 3''' || '''Value''' || '''Tier 4''' || '''Value '''
|-
| Coercion || 100011 || Improved Coercion || 100012 || Expert Coercion || 100013 || Master Coercion || 100014
|-
| Stealing || 100021 || Improved Stealing || 100022 || Expert Stealing || 100023 || Master Stealing || 100024
|-
| Trap-Making || 100041 || Improved Trap-Making || 100042 || Expert Trap-Making || 100043 || Master Trap-Making || 100044
|-
| Survival || 100051 || Improved Survival || 100052 || Expert Survival || 100053 || Master Survival || 100054
|-
| Herbalism || 100061 || Improved Herbalism || 100062 || Expert Herbalism || 100063 || Master Herbalism || 100064
|-
| Poison-Making || 100071 || Improved Poison-Making || 100072 || Expert Poison-Making || 100073 || Master Poison-Making || 100074
|-
| Combat Training || 100100 || Improved Combat Training || 100101 || Expert Combat Training || 100102 || Master Combat Training || 100103
|-
| Combat Tactics || 100110 || Improved Combat Tactics || 100111 || Expert Combat Tactics || 100112 || Master Combat Tactics || 100113
|}

====Mage====

* Main: 4023
*'''Specializations'''
** Blood Mage: 4017
** Shapeshifter: 4018
** Arcane Warrior: 4012
** Spirit Healer: 4025
*'''Mage Normal'''
** Arcane Bolt: 200254
** Arcane Shield: 200255
** Staff Focus: 200256
** Arcane Mastery: 200257
*'''Blood Mage'''
** Blood Magic: 10700
** Blood Sacrifice: 10701
** Blood Wound: 10702
** Blood Control: 10703
*'''Arcane Warrior'''
** Combat Magic: 17023
** Aura of Might: 17020
** Shimmering Shield: 17022
** Fade Shroud: 17021
*'''Shapeshifter'''
** Spider Shape: 17008
** Bear Shape: 17010
** Flying Swarm: 17007
** Master Shapeshifter: 17009
*'''Spirit Healer'''
** Group Heal: 10509
** Revival: 10504
** Lifeward: 10506
** Cleansing Aura: 10507
*'''Primal'''
** Line I
*** Flame Blast: 10001
*** Flaming Weapons: 10204
*** Fireball: 10003
*** Inferno: 10002
** Line II
*** Rock Armor: 11002
*** Stonefist: 12004
*** Earthquake: 11116
*** Petrify: 11124
** Line III
*** Winter's Grasp: 13001
*** Frost Weapons: 11007
*** Cone of Cold: 13002
*** Blizzard: 13000
** Line IV
*** Lightning: 14001
*** Shock: 14000
*** Tempest: 14002
*** Chain Lightning: 10211
*'''Creation'''
** Line I
*** Heal: 10104
*** Rejuvenate: 10200
*** Regeneration: 10210
*** Mass Rejuvenation: 10207
** Line II
*** Heroic Offense: 10206
*** Heroic Aura: 10202
*** Heroic Defense: 10203
*** Haste: 10208
** Line III
*** Glyph of Paralysis: 11001
*** Glyph of Warding: 10601
*** Glyph of Repulsion: 17000
*** Glyph of Neutralization: 17028
** Line IV
*** Spell Wisp: 11006
*** Grease: 11113
*** Spellbloom: 11005
*** Stinging Swarm: 12008
*'''Spirit'''
** Line I
*** Spell Shield: 10400
*** Dispel Magic: 10401
*** Anti-Magic Ward: 10900
*** Anti-Magic Burst: 11003
** Line II
*** Mana Drain: 10704
*** Mana Cleanse: 11004
*** Spell Might: 17001
*** Mana Clash: 11000
** Line III
*** Walking Bomb: 12005
*** Death Syphon: 10500
*** Virulent Walking Bomb: 12011
*** Animate Dead: 10508
** Line IV
*** Mind Blast: 12006
*** Force Field: 17019
*** Telekinetic Weapons: 10209
*** Crushing Prison: 11123
*'''Entropy'''
** Line I
*** Weakness: 11106
*** Paralyze: 11107
*** Miasma: 11122
*** Mass Paralysis: 11110
** Line II
*** Vulnerability Hex: 11112
*** Affliction Hex: 11111
*** Misdirection Hex: 11114
*** Death Hex: 11100
** Line III
*** Disorient: 11115
*** Horror: 11108
*** Sleep: 11121
*** Walking Nightmare: 11109
** Line IV
*** Drain Life: 15002
*** Death Magic: 17002
*** Curse of Mortality: 11101
*** Death Cloud: 15003

====Warrior====
* Main: 4022
* '''Specializations'''
** Champion: 4013
** Templar: 4021
** Berserker: 4016
** Reaver: 4019
** Spirit Warrior: 401000
** Guardian: 401001
* '''Champion'''
** War Cry: 3037
** Rally: 3038
** Motivate: 42
** Superiority: 3039
* '''Templar'''
** Righteous Strike: 23
** Cleanse Area: 3017
** Mental Fortress: 52
** Holy Smite: 25
* '''Berserker'''
** Berserk: 700
** Resilience: 48
** Constraint: 3006
** Final Blow: 3009
* '''Reaver'''
** Devour: 3065
** Frightening Appearance: 3066
** Aura of Pain: 3067
** Blood Frenzy: 713
* '''Spirit Warrior'''
** Beyond the Veil: 401100
** Soulbrand: 401101
** Fade Burst: 401102
** Blessing of the Fade: 401103
* '''Guardian'''
** Guardian's Shield: 401110
** Fortifying Presence: 401111
** Master Guardian : 401112
** Aura of the Stalwart Defender: 401113
* '''Warrior Base'''
** Line 1
*** Powerful: 14
*** Threaten: 808
*** Bravery: 17
*** Deathblow: 3021
** Line 2
*** Precise Striking: 19
*** Taunt: 3041
*** Disengage: 3016
*** Perfect Striking: 20
* '''Weapon & Shield'''
** Line 1
*** Shield Bash: 617
*** Shield Pummel: 1
*** Overpower: 3073
*** Assault: 38
** Line 2
*** Shield Defense: 704
*** Shield Balance: 37
*** Shield Wall: 12
*** Shield Expertise: 36
** Line 3
*** Shield Block: 3074
*** Shield Cover: 13
*** Shield Tactics: 3030
*** Shield Mastery: 2
* '''Two Handed'''
** Line 1
*** Pommel Strike: 3024
*** Indomitable: 28
*** Stunning Blows: 3000
*** Critical Strike: 3
** Line 2
*** Sunder Arms: 3025
*** Shattering Blows: 3001
*** Sunder Armor: 4
*** Destroyer: 3032
** Line 3
*** Mighty Blow: 3028
*** Powerful Swings: 718
*** Two-Handed Strength: 27
*** Two-Handed Sweep: 3031

====Rogue====
* Main: 4020
* '''Specializations'''
** Assassin: 4014
** Bard: 4015
** Ranger: 4029
** Duelist: 4030
'''Dragon Age: Origins - Awakening'''
** Legionnaire Scout: 401004
** Shadow: 401005
* '''Assassin'''
** Mark of Death: 3060
** Exploit Weakness: 56
** Lacerate: 3059
** Feast of the Fallen: 3058
* '''Duelist'''
** Dueling: 709
** Upset Balance: 3050
** Keen Defense: 3049
** Pinpoint Strike: 3051
* '''Bard'''
** Song of Valor: 3045
** Distraction: 701
** Song of Courage: 705
** Captivating Song: 1000
* '''Ranger'''
**Summon Wolf: 1004
**Summon Bear: 91
**Summon Spider: 93
**Master Ranger:92
'''Dragon Age: Origins - Awakening'''
* '''Legionnaire Scout'''
**Mark of the Legion: 401300
**Strength of Stone: 401301
**Endure Hardship: 401302
**Blessing of the Ancestors: 401303
* '''Shadow'''
**Shadow Form: 401310
**Decoy: 401311
**Shadow Striking: 401312
**Pandemonium: 401313
* '''Rogue Normal'''
** Line 1
*** Dirty Fighting: 603
*** Combat Movement: 21
*** Coup de Grace: 3002
*** Feign Death: 3023
** Line 2
*** Below the Belt: 3026
*** Deadly Strike: 708
*** Lethality: 777
*** Evasion: 3069
** Line 3
*** Deft Hands: 100001
*** Improved Tools: 100002
*** Mechanical Expertise: 100003
*** Device Mastery: 100004
** Line 4
*** Stealth: 100075
*** Stealthy Item Use: 100076
*** Combat Stealth: 100077
*** Master Stealth: 100078
** Line 5 (Dragon Age: Origins - Awakening)
*** Heartseeker: 400200
*** Ghost: 400201
*** Weak Points: 400202
*** Flicker: 400203
* '''Dual Weapon'''
** Line 1
*** Dual-Weapon Training: 6
*** Dual-Weapon Finesse: 8
*** Dual-Weapon Expert: 5
*** Dual-Weapon Mastery: 3036
** Line 2
*** Dual Striking: 11
*** Riposte: 9
*** Cripple: 10
*** Punisher: 7
** Line 3
*** Dual-Weapon Sweep: 3044
*** Flurry: 3035
*** Momentum: 717
*** Whirlwind: 3043
** Line 4 (Dragon Age: Origins - Awakening)
*** Twin Strikes: 402100
*** Find Vitals: 402101
*** Low Blow: 402102
*** Unending Fury: 402103
* '''Archery'''
** Line 1
*** Melee Archer: 34
*** Aim: 500
*** Defensive Fire: 33
*** Master Archer: 35
** Line 2
*** Pinning Shot: 803
*** Crippling Shot: 805
*** Critical Shot: 804
*** Arrow of Slaying: 802
** Line 3
*** Rapid Shot: 3071
*** Shattering Shot: 3072
*** Suppressing Fire: 801
*** Scatter Shot: 800
** Line 4 (Dragon Age: Origins - Awakening)
*** Accuracy: 402000
*** Arrow Time: 402001
*** Burst Shot: 402002
*** Rain of Arrows: 402003

Bug:Leliana's head morph has her eyes in her mouth

2022-02-01T15:56:45Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

*'''Version found:''' N/A 
*'''Status:''' Open

== Description ==


The head morph for Leliana, available at [http://social.bioware.com/project/1331/], has her eyes tucked down inside her mouth. This is caused by the "unique shape" slider for Leliana.

The uem_chf_05a_0.mmh file had duplicated node data for the mshh entry. While all of the other MMH files for the unique shapes have only six nodes, the Leliana one has seven. The sixth and seventh nodes are duplicates. For whatever reason, all of the other unique shapes had their mesh labeled EyesM1, but only the Leliana one had EyesM2.

== Workarounds ==


This project has some files created by EJ42 that fixes the problem and allows Leliana's head morph to be modified normally: [http://social.bioware.com/project/1703/]

[[Category:Toolset bugs]]
[[Category:Morphs]]

Bug: missing talktables

2022-02-01T15:47:21Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

*'''Version found:''' 1.01
*'''Status:''' Open

== Description ==
If you are creating new resources with appropriate entries within the string editor, your exported talktable will not get recognized because your resources won't get flagged right. This means that the ID entries of your talktable are not overwriting the text you entered inside the toolset. That's not so important for all english speaking natives but for foreigners who are using special symbols in their alphabet. These letters are not displayed right without functional talktables. To avoid this you have to use an external tool anakin5 provided.

== Workarounds ==
Just use the tool, drag'n drop your file(s) at the executable and you're done.
[http://social.bioware.com/project/1586/#files]

[[Category:Toolset bugs]]

Art Resources

2022-02-01T15:43:01Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

{{MarkedForReview}}
Art Resources are all Art created and stored in the Dragon Age file system. Creators of world maps will need Art Resources to shape them with Models, while creators of face morphs need Models of Faces. With that ,they are also creating Art Resources.
This is Part of the [[Art]] Category.

== Overview ==

Art Resources are the part of the Game which is what you hear and see. However the properties of each of the things is not. What they are instead is a property of a [[Designer Resources|Designer Resource]]. A sword, which is a [[Designer Resources|Designer Resource]], for example has attack properties, and another of these properties tell which [[Model]] it uses.

Art Resources are almost solely required by [[Designer Resources]], and as such do not make its way into the Game directly.

Any Resource is stored in the Dragon Age file systems [[ERF]] files. They are created by external Tools and the Dragon Age Toolset, by multiple ways. The most common and diverse Resource is that of [[Model|Models]].
The file name Scheme for Resources follows a general [[Naming conventions|naming structure]], due to its Amount and easier Management. It is also split into many [[ERF]] Files for different kinds of Resources.

=== File Structure ===

[[ERF]] files for Dragon Age are stored in the folder and sub-folders:

<pre>[Dragon Age Install Directory]\packages\core\</pre>

* Browsing the [[ERF]] files supplied with the toolset
* [[List of file types]]

== Modding and Creating ==

When talking Art Resources, its creation requires mostly knowing only about the resource type in question. Anything about creation, exporting, formats is explained for each on their own.

A common activity in modding is overriding existing Art Resources. This is the process of recreating a special type and mimicking the file name of the original, so that the [[Designer Resources|Designer Resource]] ,or anything that previously read that File, will now pick the modded one. Art Resources, along with [[2DA|2DA Resources]], need to be manually arranged into the file system. This is normally an Override Folder of some sort, and those Resources are initially stored as single Files.

Generally, the Game and the Toolset reads multiple override Folders [[Source directory priorities|after a list of priorities]], so it would not matter. However when the Art Resource should be integrated into a [[Module|custom module]], it should be placed alongside the override folder of that [[Module]]. The reason is that the Toolset creates [[DAZIP]] files ([[Builder to player]] installable packages) where you select which folder to integrate. Thus the Resources needed for the [[Module]] should not be scattered around the file system.

Only the [[Builder to player]] functionality packs those Resources into [[ERF|ERF Files]] again.

:''See also: [[Tutorials]]''

== Resource Types ==

=== Models ===

: ''See Main Article: [[Model]]''

=== Materials / Textures / Tints ===

: ''See Main Article: [[Material editor]]''

In closer relation to Models see Article: [[Model]]

=== Animations ===

: ''See Main Article: [[Animation blend tree editor]]''

=== Morphs ===

: ''See Main Article: [[Morph]]''

Face morphs, are generated with the face-morphing tool.

You can download the source files for all the morphs in the main campaign from here: [http://social.bioware.com/project/1331/#files]

=== FaceFX ===

: ''See Main Article: [[FaceFX]]''

Handles facial expressions and lip-synching.

=== Visual effects ===

: ''See Main Article : [[VFX editor]]''

You can download the source files for all the visual effects in the main campaign from here: [http://social.bioware.com/project/1331/#files]

=== Audio ===

: ''See Main Article : [[Sound and music]]''

=== Level/Area layouts ===

: ''See Main Article: [[Level editor]]''

You can download the source files for all the level layouts in the main campaign from here: [http://social.bioware.com/project/1331/#files]

Note that [[level]]s and [[area layout]]s are are distinct from [[area]]s created in the [[Area editor]]

See also the [[Area layout visual index]] for an image of each area layout included with the Toolset.

[[Category:Art resources]]

Art

2022-02-01T15:42:26Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

{{MarkedForReview}}
Game Art in general is created via various external Applications, [[3rd_party_extensions]] ,and with the Dragon Age Toolset. Which you will need depends only on the type of Resource.

Sound and Music is covered in the Article: [[Sound and music]]

== Overview ==

[[Image:Overview.png|right|]]

Creating content to be usable with the Toolset can probably be separated into 2 fields. That is the actual Resource type, and telling the Toolset about it.

For example a Model in itself is only a set of files, while 2DA's assign ID's and kind of like a place in the "Shelf" which is what you are seeing in the Toolset. Otherwise it would not be able to tell what a given Model is supposed to be. Furthermore, the Toolset will get to know Properties once it knows which kind of Model it is.

* Art Resources are the Files that exist in the file system.
* Two-dimensional Arrays ([[2DA|2DA's]]) are compiled Excel Tables, containing various Data about the Resources.

Art Resources are, with the exception of Level layouts, only indirectly linked to what you see in game. A Model has to be applied to a Item, a Face morph to a NPC, etc. This whole Art category ends for the most part once the Resources are available to be used in the Toolset. Anything you make with the art resources there is a matter of [[Design]].

The diagram illustrates the general outline of how each of these types of resource is edited, processed, and used by the game.

== Module Foundation ==

:''See Main Article: [[Module]]''

Resources are not created into the blue, as each has to be created on top of a so called Module. Art Resources and 2DAs are not directly tied to a Module, however they are referenced by Designer Resources which instead are. When creating an installable package, an Resources has to be present in the correct Modules override folder. There are multiple Override Folders which the Game reads, however it is important to choose the correct one for the Module to be separated and Toolset functions to work later on.

* Art Resources and 2DA Files have to be placed into the Modules directory by hand.
* The Toolset is responsible for exporting Designer Resources out of the Database into the corresponding Module directory.

== Art Resources ==

:''See Main Article: [[Art Resources]]''



Art Resources are all Art created and stored into the Dragon Age file system. Creators of world maps will need Art Resources to shape them with Models, while creators of face morphs need models of faces. With that, they are also creating Art Resources.

Art Resources include the following, but not exclusively:

* [[Animation blend tree editor|Animations]]
* [[Model|Models]]
* [[Sound and music|Sounds and Music]]
* [[Morph|Morphs]]
* etc.

Any Art Resource is also made available to the Game Design Process, where Game Designers create [[Designer Resources]] like Characters.

=== Models (Art Resource) ===

: ''See Main Article: [[Model]]''

Models are the smallest Pieces in Art Creation, that make up any visible Entity in the Game, consolidated into the complete visible appearance of the Gameworld by the Worlddesigner.

Walls, Houses, Creatures are all made up of one or multiple Models. They are as such 3d Meshes, created using external modelling Applications, which export them into a gamereadable Format.

=== Level/Area layouts (Art Resource) ===

:''See Main Article: [[Level editor]]''

Level layouts (also called Area layouts) are another Art Resource in itself. They are a simple world Design, that includes nothing more than wide Terrain with Trees, Lakes, Bridges, and pratically a playground where any game can take place. Dragon Age play-areas are based on such Layouts.

Models is what makes up a layout for the most Part. Terrain, Lakes, and Weather are however unique to the Level Editor and can only be created with it.

Note that Level layouts are non interactive. Interactive Areas are build based on these layouts, and described in the Article [[Area]].

== Two-dimensional Arrays ==
: ''See Main Article: [[2DA]]''

2DA's contain various Data not only for Art Resources, but for the whole game as well. 2DA's are packed into [[GDA]] [[List of file types|file type]], which are generated from XLS (Excel) files. The original XLS files supplied with the Toolset can be found in:
<pre>[Dragon Age install directory]\tools\source\2da</pre>

For converting XLS files into GDA files, see [[compiling 2DAs]].

== Art sources for the Single Player campaign ==

Many Art Resources are processed and binarized, therefore not in the final product in its source form.

For size reasons the sources for the levels, head morphs, and visual effects projects used in the Single Player campaign were not included with the toolset installer. You can find these available for download at [http://social.bioware.com/project/1331/#files the Single player and core resource source files] project.

[[Category:Art resources]]

Category:Articles containing BioWare Social Network links

2022-02-01T15:41:23Z

Ashhawk: Created page with "Articles in this category contain links to the now-defunct BioWare Social Network, which need to be updated. Place articles here by using the <nowiki>{{BSN link}}</nowiki> te..."

Articles in this category contain links to the now-defunct BioWare Social Network, which need to be updated.

Place articles here by using the <nowiki>{{BSN link}}</nowiki> template.
[[Category:Maintenance]]

Adding custom level tutorial

2022-02-01T15:37:23Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

Author: Ladyofpayne
*3ds max (gmax) no older than 2011 year - Eshme Import/Export DAO Tools doesn't work with new versions.
*[http://www.nexusmods.com/dragonage/mods/895/? Eshme Import/Export DAO Tools] - Script for 3s max
*Dragon Age Origins and Dragon Age Toolset - install it in the same folder as the game.
*Adobe Photoshop and Nvidia DDS Plugin for textures.
*[http://social.bioware.com/project/2637/ mesh lightmap fixes] - Install this project.
*Engine won't work with models bigger than 45 000 polygons and 30 000 vertexes. Even if it works still make sure your model isn't too complex - Lightmapping render can be failed.

'''Before we begin extract all DAO resources and keep it somewhere. You will need them.'''

You can use also the toolset to extract the model and textures, but fisrt you need to know the name of what you are looking for, in the tooset go File->Open file-> /packages/core/data/modelmeshdata.erf there you have some strings to help you find the models:

armours: arm_ +armour type; gloves: glv_; boots: boo_; clothes: cth_; robes: rob_; helmets:hlh_; weapons: w_+ weapon type; shield:w_shd; hair: har_; props:prp_;placeabes:plc_;
creature: c_; npc creatures: cn_; children: kn_;

for races and genders you have human/elf/dwarf/qunari followed by the gender female/male, so human male: hm_; dwarf female: df_; etc.

*'''in the modelmeshdata.erf you need extract the .msh files''' the _0 files are the model you see in game when using the armour/cloth, the _2 and _3 files are the low level of detail (LOD) models, when other NPCs are using them and they are far away from you.

*'''in the .../core/data/modelmeshhierarchy.erf you need extract the .mmh and .phy files.'''

*'''in the .../core/data/materialobjects.erf you need to extract the .mao file.'''

*'''in the files .../core/data/textures.erf (props, placeables) and/or .../core/textures/high/textures.erf (characters and armours) you need to extract the .dds files''', in those files the letter for the races in the file's name are changed to p, so human male, dwarf male, elf male, qunari male are all: pm_, because they all use the same texture.

== Script Settings ==

Watch where you install Eshme script - program files(x86) for 32 programs at 64 bit computers. Eshme script and the game have to be in one folder of program files.

Take Eshme Import/Export: Startup, YAGG and DAOTools -> put into C(your disc):/Program Files/Autodesk/3dsmax/Scripts -> scripts

If your installation is correct them when you first open 3d man you will see window with the settings

In Game Path HAVE to be folder of the game C:\Program Files (x86)\Dragon Age, in Export Path folder Override in folders C:\Program Files (x86)\Dragon Age\packages\core\override.

Next sctar of 3d max you can begin your work in 3 d Max -> Run Script.

== Textures ==
Size of the texture have to be :4 1024 -> 2048 -> 4096 -> 8192. You will need 3 type of them and you probably need to connect textures because DAO engine works only with one material at one model. Put them all in one file and make the same posistion for each part of every type:

[[File:Text1.png|border]]

1) Diffuse map. Has "_d" letter in the name. What your model will looks like. Create Alpha channel and make it white inless you have parts than need to have "holes" in it. Then it will looks like that:

[[File:Alpha1ex.png|border]]

2) Normal map. Has "_n" letter in the name. It is grey texture. Just save your Diffuse map with this settings:

[[File:Normalsave.png|border|50%]]

How it has to looks like:

[[File:Normalex.png|border]]

3) Spectacular map. Has "_s" letter in the name and '''necessary for the lightmapping'''. Just take duffise texture the modify it image-> adjustments ->brightness brightness:45, contrast: 95 and copy its blue channel to alpa. The texture is ready.

Save you textures. Normal map settings is listed above. Diffuse and Spectacular settings:

[[File:Therestsave.png|border|50%]]

4) All textures put into '''Documents\BioWare\Dragon Age\AddIns\your Module_ID\module\override''' in the same folders as models. Each model has to be organised and be in it's own folder. Make sure each model has all 3 types of textures and each type has it's letter. '''Example:''' prp_namemodel_'''0d''', prp_namemodel_'''0n''', prp_namemodel_'''0s'''.

== Materials ==
Select your model and on the panel above use '''Rendering-> Material editor-> Compact material editor''' Then click on '''Get Material''' and choose from the list '''Dragon Age Material'''.

[[File:Materialeditor.png|border]]
[[File:Materialwork.png|border]]

In '''Material Type''' choose '''Prop Default''', in '''Render Semantics''' – '''Default (Opaque Prop)\ Trasparent if you have any transparency'''. Select your texture in '''Texture Maps''' - diffuse, normal and specular. Select your model and click on '''Assign Material to Selection''' (1) and use '''Show Map in Viewport''' (2). Now give your material proper name without '''_0''' in the end. Example: if your model texture is named is prp_orl_bed_0d name the material prp_orl_bed.

[[File:LOP_material.png|border]]

== More than one texture ==
Necessary step if you connect more then one texture for a model. But even if your model has only one texture it is better to make sure evertything is correct.

Select your model and then open '''Modifiers-> UV Coordinates- > Unwrap UVW'''

You will see something like this:

[[File:Editingmaterials.png|border]]

Geen lines are coordinates of textures on the model. '''Dragon age: Oginins engine work with only one material and can "see" everything ONLY inside the bolder square form the picture.''' WChoose as background texture if your model and now move all green lines so it will cover it like is has to be. You can move materials one by one by choosing them in All ID's. You can change scale of coordinates, rotate them and do all manipulations you see necessary to make your coordinates fit to texture inside the square just like this:

[[File:Mated2.png|border]]

Save and close Unwrap UVW.

== 3d Max ==
After you finish working with the materials and the textures you can work with the model now. If your model looks rough change it by '''Right click -> convert to Editable Poly-> Vertex-> Select all (CTRL+ A)-> Weld'''. Before next step finish all fixes: '''Unwrap UVW, material and textures.''' If you move to next step without fixing you have to redo it from the beginning later.

[[File:LOP_Convertintomesh.jpg|border]]

1 - Right click on a model and select '''"Convert into editable poly"'''> In '''modifier list choose and add 2 Unwrap UVW''' to your model. In the second one you have to change '''map channel''' to 2 - this is the channel needed for lighmapping.

[[File:LOP_cuteditmaterials.jpg|border]]

2 - For the rest part you need to look for this video becaue I cannot describe how this part supposed to work but you have to follow my instructions while you working with the materials. [https://youtu.be/m8DFXmIGJZc Dragon Age Modding: Creating Props using 3ds max]

3 - While you using '''Runscript-> manage models''' -> look for your models and make sure they have those settings. Change collision Walkable\ Non walkable if this object lies on the floor.
Mesh:

[[File:LOP_deletealll.jpg|border]]

Collision:

[[File:LOP_deletepixel.jpg|border]]

4 - Run script-> export and name your files with '''_0''' in the end. '''EXAMPLE:''' prp_yourmodel_0. Since you use textures for the whole group you folders for each model has to be in one big folder for your group. Like this:

[[File:LOP_materialgroup.jpg|border]]

5 - After you port the model open MAO file with the Notepad and '''JUST''' after line '''<DefaultSemantic Name="Blend"></DefaultSemantic>''' add this line '''<Texture Name="mml_tLightmap" ResName="LM.dds" RequiresID="true"></Texture>'''. Now save the file.

== Models for scaling ==
You can test the collision by pressing button "Fade cutaway" and see which models disappear - those don't have collision. You can change it by set '''Override Cutaway: false''' if you use model without collision. Now press "Fade cutaway" - the model will be in level now. You don't have collision to cover your whole model- you need it cover only part on the ground so your character won't walk through the model.
=== Level ===
*"wallfull1_0" - '''Both'''. Wall with collision. Use it when you need wall.
*"wallfulldoor1_0" - '''Both'''. Door arch with collision. Use it when you need an arch without door.
*"support1_0" - '''Both'''. Two columns with collision. Use it when you need column- collision is cylindric form.
*tti_top01_01 - '''TTI ONLY.Celing without collision. '''Use it when you need an item on the ceiling without collision.

=== Props ===
*prp_painting_01_0 - painting on a wall with collision.
*prp_chestornat01_0 - chest with collision.
*prp_chair_01_0 - chair with collision.
*prp_table_01_0 - table with collision.
*prp_tevbookshelf1_0 - bookshelf with collision.
*prp_vase_01_0 - vase with collision.
*prp_bed01_0 - bed with collision.
*prp_cand04_0 - chandelier from above no collision.
*prp_dwfrug2_0 - rug on the floor.
*fca_floor01_0 - floor with collision.

== Export==

Save your '''.LVL''' files in Documents\BioWare\Dragon Age\AddIns\your Module_ID\core\env. Make sure '''.ERF''' and '''.ERF.BACK''' are here too after you press "Do All Local post".

1) '''NOTE:ALWAYS port your custom levels from SINGLE PLAYER!''' Manage modules-> Single Player-> open your '''LVL''' there.

2) Add minimap. Right click, then select Minimap > Minimap Selection Tool. The default green box appears. Right click on the area again, Minimap > Post Minimap to Local. It's possible to handcraft or refine the minimap, as detailed under [[Custom minimaps]].

3) Press Button '''"Render lightmaps"'''.

4) Press button '''"Set Start point"''' for Pathfinding -> Press button '''"Generate pathfinding"'''. '''NOTE: Pathfinding is not possible for two overlapping height levels. Also generation fails if you put the start point in collision (non-walkable part) so watch carefully where do you put it.'''

5) Press button '''"Do All Local post"''' - this will export your level and you can use it in your area. Files will be ported into Documents\BioWare\Dragon Age\Toolset. Or use Search for each location name in Documents.

6) All files have to be in folder in '''Documents\BioWare\Dragon Age\addins\your Module_ID\packages\core\override'''. Each model has to be organised and be in it's own folder. Your Custom model and texture files has to be in the same folder as your ported Levels.

Make sure that your folder has all type of files also with folders Textures and trees.

'''NOTE: When you will make Builder to Player packed you will be asked to delete some of files NEVER DO THAT! Instead before creeating create different folder with the same name toolsetexport and keep there all you level files and custom level models. Keep also all your custom model armor and items in new folder override. After that create Builder to Player withou these files and look for next step'''

7) [https://datoolsetblog.wordpress.com/ Dr. dummie addition]

It is well known issue with B2P exporter when your file have more then two dots in name. Usually it is with *.gpu.rim files so here is simple how-to to pack your areas into dazip.

So you go ahead and create your dazip file without your areas. I’m not gonna explain here how to create dazip file, I assume you already know how to do that. Now when you have your file ready, open it with 7-zip (you can also do the same with any app which can open zip files – note that dazip is just a renamed zip file).

'''SO WHEN YOU HAVE OPENED YOUR DAZIP FILE WITH 7 ZIP:'''

* Navigate into “contents” -> “packages” – > “core” folder.

* There should already be a “data” folder. If there is already folder named “override” you are ready to go. If not -> Right click onto view and select “Create folder” and name it “override” (without quotes of course). Here I usually create another folder into override named “env_short_name_of_my_mod” like “env_yad” to keep things grouped, but it’s not needed.

* Drag your areas into that folder. They will be automatically added to dazip file. Exported areas are usually grouped into folder named by your exported level name which you have set up in your level editor.

'''SOME NOTES:'''

Be aware that anything you put in packages/core/override folder can override all other resources from game if they have same name.

When dazip is installed with damodder, it will unpack your areas into packages/core/override on target system.

'''ON TARGET SYSTEM:'''

Your areas (levels) will be unpacked into ../packages/core/override/env_your_mod_short_name/..

If user wants to uninstall mod, he must also manually delete “env_your_mod_short_name” folder from “../packages/core/override/..” folders in their documents folder after mod uninstall with damodder.

If not, your areas and items will be, or can be, used by game further on (other modders can use your areas, and items will continue to override other same named resources in main game).

You can use similar procedure for almost any resource from the game. You just need to follow exact same folder structure as in your mod, remember, mod is working on your PC with your files without any erf files or similar.

8- Done. You module is ready to play.

== Useful links ==
*[[Installing the toolset]] - very important for program troubleshooting. NVIDIA_PhysX section- if you have pathfinding generation problems.
*[[Bug: Water plane missing in-game]] - how to fix this bug and make your water appear in the game.
*[[Bug: New level doesn't work correctly]] - how to fix it if your level doesnt work.
*[[Bug: Bulder to Player with new level issue]] - description of the bug.
*[[Lighting Tutorial]] - Lightmapping troubleshooting.
*[[Level Editor Tutorial]] and [[Level tutorial]] - General advises.
*[[Adding custom armor tutorial]] - How to add your own armor.
*[[Adding custom shield tutorial]] - How to add your own shield.
*The .lvl files from DAO [http://social.bioware.com/project/1331/#files the Single player and core resource source files] project, if you wish to modify the layouts in the [[level editor]].
*[http://www.greentoken.de/onlineconv/ 3D converter]

[[Category:Tutorials]]

Adding a custom model to the toolset tutorial

2022-02-01T15:36:13Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

This tutorial describes how to add a custom model to your Toolset. It is assumed that the reader is familiar with the Toolset.

__TOC__

==Needed Files==
Download tazpn's Command Line Tools [http://social.bioware.com/project/218/#files]

or alternatively use

Allstar's GUI interface for Tazpn's Command Line Tools [http://social.bioware.com/project/1060/]

==Convert your model to DA:O compatible files==

It is assumed that the model is finished and textured.

Export your model as a *.fbx file.

Use tapzn`s Tool to convert the *.fbx file to a *.mmh.xml file (fbxcmd convert name.fbx name.mmh.xml).
You will get 3 files out of this:

• *.[[mmh]].xml

• *.[[msh]].xml

• *.[[mao]]

Since the *.mao file is not well named in some cases, you have to manually rename it. If you do this, don't forget to change the reference in the *.mmh.xml file!

== Create *.mmh ==

Just drag and drop your *.mmh.xml on the "\Dragon Age\tools\ResourceBuild\Processors\MMH\GraphicsProcessorMMH.exe"

== Create *.msh ==

Copy the *.msh.xml file to "\Dragon Age\tools\ResourceBuild\Processors\MSH"
Then do "GraphicsProcessorMSH -platform pc mmdtogff (filename).msh.xml" using your Shell / cmd

== Adding it to your Toolset ==

Copy all the files (*.msh, *.mmh, *.phy, *.dds, *.mao) to "\Dragon Age\packages\core\override\".
Optionally you can pack it into an *.[[erf]] file. The [[builder to player]] packaging process can package up these files into an erf for you in the process of creating a [[dazip]] installable file.

== Using it in the Toolkit ==

To use it in the toolkit you have to specify which item variation your item is. Edit the fitting *.gda in the 2da.erf to do so. See [[ItemVariations.xls]].

If you did nothing wrong up till now, you should be able to use it in the Toolset by now.
[[Category:Tutorials]]

3rd party extensions

2022-02-01T15:34:07Z

Ashhawk: BSN link flagged for maintenance - using AWB

{{BSN link}}

List 3rd party extensions and applications here!
__NOTOC__
== Third party applications ==

=== Models ===

* [http://social.bioware.com/project/218/ Tazpn's command line tools] - This packages includes an command line application for converting Dragon Age models from the native format to something that can be manipulated or used a reference for non-derivative works.
* [http://social.bioware.com/project/1060/ GUI for tazpn's Command Line Tools] - This is an easy-to-use program to convert Dragon Age Models utilizing tazpn's Command Line Tools & the Dragon Age Toolset Command Line Tools.
*[http://social.bioware.com/project/41/ DATool: DA model manipulator] - This is a tool for viewing, retexturing and resizing DA models. DATool allows you to easily browse the available DA models and make certain modifications to them.
*[http://social.bioware.com/project/563/ DA:O Toolset Model Exporter] - 3DS max and GMax. Can export static and animatable models. Also Collision,Materials,Animation. Current Version: 1.5.0
*[http://social.bioware.com/project/899/ Blender Import-Export Script] - A set of tools to import-export meshes and extract resources from erf or rim files, all working into Blender.
*[http://social.bioware.com/project/2246/ LightWave import-export plugin] - a plugin for [http://www.newtek.com/lightwave/ NewTek LightWave 3D]. Currently allows to import .msh files into LightWave and export 3d data from Modeler module to .msh.xml format.
*[http://social.bioware.com/project/1511/ Lightmap Post Processor] - Remove black artifacts from lightmaps.
*[http://social.bioware.com/project/2336/ GMax/3DSMax DA:O Model and Animation Import Export] - Importing and Exporting of Models and Animation. Model Creation Tools. Supports the free GMax as well as 3dsmax4 to 2011. Latest Version5.30 (08/23/2010)

=== Animation ===

*[http://social.bioware.com/project/563/ DA:O Toolset Model Exporter] - 3DS max and GMax. Exports Animation. Also Models/Materials/Collision.
*[http://social.bioware.com/project/2336/ GMax/3DSMax DA:O Model and Animation Import Export] - Importing and Exporting of Models and Animation. Makes Animations for use in Cutscenes or in Animation Blend Tree for use on Characters. Supports the free tool GMax as well as 3dsmax4 to 2010.

=== Game data ===

*[http://social.bioware.com/project/755/ GDApp] - GDApp is a simple editor that natively creates or modifies Dragon Age: Origins GD2A spreadsheet files (*.gda), without the need of Excel files.

Template:BSN link

2022-02-01T12:11:23Z

Ashhawk: Created page with "<div style="background:#f6f6f6; border: 1px solid #d0a5a5; padding:4px; margin-left:20%; margin-right:20%;"> This article contains links to the BioWare Social Network (B..."

<div style="background:#f6f6f6; border: 1px solid #d0a5a5; padding:4px; margin-left:20%; margin-right:20%;">
This article contains links to the BioWare Social Network (BSN), which is now closed.
These links should be replaced with working links where possible, and tutorials edited to remove reliance on BSN.
</div><includeonly>[[Category:Articles containing BioWare Social Network links]]</includeonly><noinclude>
[[Category:Maintenance templates]]
</noinclude>

Dragon Age 2

2022-01-26T11:03:32Z

Ashhawk: Updated pyGFF and GDApp bsn links to nexus

No toolset has been announced for Dragon Age 2 at the time of writing.

Nevertheless, some of the information in this wiki will help DA2 modders, who may wish to share their knowledge here, too.

==Clarity==

Obviously, since this wiki was originally written for DAO, by default it refers to DAO, not DA2.

The same applies to the [http://social.bioware.com/forum/1/subindex/70 Toolset Forum] and [http://social.bioware.com/browse_bw_projects.php Projects], where DA2 modders are most welcome.

So, it would help everyone if DA2 projects, forum posts, wiki articles, sections and comments were clearly labelled as DA2, to avoid confusion.

Ideally, information which only applies to DAO should be labelled, too, but that isn't going to happen comprehensively, so make no assumptions!

==Overview : how DA2 differs from DAO==

This information is evolving. Early days!

* Since there is no toolset or source material for DA2, it is not possible to work with [[Design | design resources]].

* However, it is possible to make simple changes to the exported DA2 resources (areas, creatures, conversations etc) that ship with the game.

* It may also be possible to make new resources with the DAO toolset, export them, and package them for DA2.

* The official exported resource files are held in [[ERF]] containers. DA2 uses version 3.0 for both main game content and DLC, whereas DAO uses version 2.0 for main game and expansion resources and version 2.2 for DLC.

* The exported resource file format is [[GFF]]. DA2 uses versions 4.1 and 4.0, while DAO uses version 4.0. Both games also use version 3.2 for some content types.

* The DAO toolset does not support ERF 3.0 or GFF 4.1 (see next section for alternate tools). With an available version 2.0 erf file, courtesy of Thought Process, the DAO toolset can be used to compile scripts that can be used in DA2. Similar custom erf files could likely be made to enable using models from DA2 in the DAO toolset to create new creature templates, though these will likely require hand editing in a stand-alone gff editor for use in DA2. Since many DA2 file types are the same as their DAO counterparts (with perhaps minor differences), those files will likely work as exported from the DAO toolset; if not, there are ways to tweak them manually.

* [[List of file types|Resource formats]] are generally the same (or similar) for both DAO and DA2.

* One exception is that the DAO conversation format (.dlg) has been replaced by .cnv in DA2. However, they share the same basic node structure, and it may be possible to convert dlg files to cnv.

==Builder Resources==

Some of the basic tools are

* [https://www.nexusmods.com/dragonage/mods/4512 pyGFF] for working with GFF files
* [https://www.nexusmods.com/dragonage/mods/214 GDApp] for editing 2DA files and exporting them to Excel
* [http://social.bioware.com/project/4419/ ERFv3 Packer] for putting files into the new format ERF container

See also [http://code.google.com/p/dragon-age-open-house/wiki/BSN_DA2IndexBuilders Community Index].

== Followers ==

* gen00fl_bethany
* gen00fl_carver
* gen00fl_varric
* gen00fl_anders
* gen00fl_aveline
* gen00fl_isabela
* gen00fl_merrill
* gen00fl_fenris

Getting Started

2022-01-26T10:54:51Z

Ashhawk: Updated toolset download link from bsn to dragonagekeep

== Installing the Toolset ==

* [http://dragonage.bioware.com/ Install the game.] Ensure that Dragon Age is installed before dabbling in the toolset, as it relies on the game's resources and engine, and cannot function without them.
* [[Creating an account|Create an account.]] In order to contribute to pages on the DA Builder Wiki or participate on the BioWare Social Network, you will need to create an online user account.
* [http://social.bioware.com/user_bw_games_register.php Register the game.] In addition, you will need to register your copy of Dragon Age before gaining access to game-owner only content, including the toolset.
* [https://dragonagekeep.com/en_US/downloads Download the toolset.] The Dragon Age toolset contains the same functionality used by BioWare to craft the official campaign, and provides the power and flexibility to create your own custom content and adventures.
* [[Installing the toolset|Install the toolset.]] Refer to this page for general information and step-by-step instructions to installing the toolset.
* [[Installation troubleshooting|Troubleshooting.]] Refer to this page for specific information on how to resolve issues in the event that toolset installation goes awry.
* [[Known issues|Known issues.]] Refer to this page for a currently documented list of known issues and bugs in the current version of the toolset.

== Overview of the Toolset ==

*[[Overview of the toolset|Overview of the toolset:]] A quite good overview of interface layout and toolset resource management.

*[[Comparisons with other toolkits|Comparisons with other toolkits:]] A brief feature overview of the Dragon Age toolset for users familiar with similar software (e.g., the NWN Aurora Toolset).

== Starting the Toolset ==

{| align=right
|[[File:Titlebar components.png|thumb|300px|right|How to determine which module is currently open]]
|-
|{{Warnbox|Do not edit Single Player or Core Resources with custom content!|300px}}
|}
Before using the Toolset, it is important to take note of what [[Module|module]] the toolset has open. A module is a "container" in which game resources are stored in; you will only be able to see the resources for the currently open module (and any modules that it is marked as depending on). The default module when first starting the Toolset is the "Demo" module, which is a very small and simple module intended to show several common resource types in a basic pre-built adventure that you can experiment with safely.

The main Dragon Age: Origins campaign resources are stored in a module named "Single Player". If you're just starting out with the toolset, it can be dangerous to edit these, as you could inadvertently corrupt your main campaign. Take care when exploring not to edit any of those resources without knowing what you're doing.

The first basic steps in the Toolset shall be to create your own [[Module]]. The only possible type of Module is "Addin", but note that this name is somewhat misleading; it is possible to have "standalone addins" that are completely separate from any other module (such as the main campaign).

*See: [[Module]] - For a general overview of how a Module works, and what awaits you.

== Using the Toolset ==

As described in the overview linked to above, the game uses a wide variety of resource types. A "resource" is something that you can create, such as a script or a creature, and you will often need to combine many different resources together to accomplish a particular design goal. The toolset consists of many independent tools for working with these different types of resources. These tools can be well discussed separately.

The next best step for learning the toolset would be to look into the categories on the [[Main Page]], which link deeper into each topic and the tools involved with them. If you are having questions at a specific part of the toolset give this Wiki a search for it. This can be very specific, and always worth a try. You may also find the [http://social.bioware.com/forum/1/subindex/70 toolset forums] to be useful in solving specific problems the documentation here may not cover.

A list of certain Interest, and the 3 Resource types:
*[[Design]] - Talks mainly about Designer Resources, such as Items, Monsters, NPC's, Vendors, etc.
*[[Art]] - Talks mainly about Art Resources, such as Models, Textures, Facemorphs, etc.
*[[2DA]] - Talks about the 2DA Resourcetype, which is sets of Gamewide usable variables and references.

=== Tips and tricks ===
*[[Shortcuts]] - Assorted toolset shortcuts.
*[[Common Problems]] - Little things that most people will need to know but that are not necessarily obvious.

== Specials ==

It is currently not possible to delete a module by normal means.

If you run into a problem that the documentation doesn't cover and that you can't fix, contact toolsetsupport@bioware.com

== Removing Custom Content ==

This section describes how to remove all custom content from the game.

To be on the safe side, before you start, you might want to

* disable all the unofficial add-ins on the DLC screen in game
* play a recently saved game (using the Force Load option) to confirm that it works reasonably well without the add-ins
* back up your Documents > Bioware folder

Since you can't be certain that all authors have followed best practice, you'll need to clean out all the folders that can be customised.

In Documents > Bioware > Dragon Age,

* In the AddIns folder, delete all the folders except Demo, Single Player and anything starting with dao_prc (the official DLC).
* Delete any files In the AddIns > Single Player folder and sub-folders (you might get away with just deleting the Single Player folder, but caution never hurts).
* Delete any files from the modules and packages folders.

== Dragon Age 2 ==

See [[Dragon Age 2]] for more information.

{{Languages}}