Source directory priorities - Revision history

Proleric1: /* Overriding base campaign resources */

2010-03-06T18:58:22Z

‎Overriding base campaign resources

Adaram at 20:07, 12 November 2009

2009-11-12T20:07:51Z

BryanDerksen at 22:51, 1 October 2009

2009-10-01T22:51:36Z

BryanDerksen at 22:36, 1 October 2009

2009-10-01T22:36:52Z

BryanDerksen: A note on overriding engine resources

2009-10-01T20:34:11Z

A note on overriding engine resources

BryanDerksen: add textures to the addinss

2009-07-30T20:26:44Z

add textures to the addinss

BryanDerksen: I believe these are some of the corresponding directories

2009-07-30T20:23:20Z

I believe these are some of the corresponding directories

BryanDerksen: dump some internal documentation in here. Needs to be fixed up

2009-07-30T20:19:00Z

dump some internal documentation in here. Needs to be fixed up

New page

The Dragon Age toolset exports resources to a set of directories that varies depending on the module's settings, and the game reads these resources from various directories with a certain order of priority. Resources with the same name can override each other by being placed in directories with greater priority, and may or may not be loaded depending on which module the game is currently playing.

This list is the order from top priority to bottom:

*My Documents Core Override
*Core Override

*Addin Override
*Addin Patch
*Addin Locale
*Addin Audio\VO
*Addin Audio\Sound
*Addin Env
*Addin Data

'''Note:''' There is currently a bug in the game preventing it from reading resources in the "My Documents Module" locations. This is a bug which has been WNF'ed for initial release. The toolset does read from here, however, so there is some possibility for confusion if you're working on resources that are located here.
*My Documents Module Override
*My Documents Module Patch
*My Doucments Module Locale
*My Documents Module Data
*My Documents Module Toolset
*My Documents Module Patch
*My Documents Module Local
*My Documents Module Data

*Module Override
*Module Textures\Patch_<Med/High>
*Module Patch
*Module Locale
*Module Data
*Module Toolset
*Module Audio\VO
*Module Audio\Sound
*Module Root

*Core Patch
*Core Locale
*Core Env
*Core Textures\<Med/High>
*Core Data
*Core Audio\VO
*ENV_LAYOUT??? - Doesn't seem to be used
*ENV_CHUNK??? - Uses for env rims somehow
*Core Audio\Sound
*RESMETRICS??? - Doesn't seem to be used

'''Note:''' end-users will not be able to create functioning offers, this is a feature used by official BioWare-produced post-release content.
*Offer Textures\Patch_<Med/High>
*Offer Override
*Offer Patch
*Offer Locale
*Offer Audio\VO
*Offer Audio\Sound
*Offer Env
*Offer Data

@@ Line 61: / Line 61: @@
 created in the same database as that module. Since the database that comes with the toolset has a set of core resources and the base campaign already in it, this makes overriding base campaign resources tricky.
-One possible approach to overriding a core resource would be to open a local copy (not checked out), make your edits to it, then export it.
+One possible approach to overriding a core resource would be to open a local copy (not checked out), make your edits to it, then export it. This has not yet been tested and may or may not work. Experiments remain to be done.
-Another possible approach could be to create a new resource with a similar name, and then after exporting it (but before doing a builder to player packaging) go into the toolset export directory where it's been exported and renaming it to match the resource you wish to override.
+Another possible approach is to create a new resource with a similar name, and then after exporting it (but before doing a builder to player packaging) go into the toolset export directory where it's been exported and renaming it to match the resource you wish to override. This does work, but there's almost invariably an easier way, such as changing the 2DA that identifies the name of the resource to load.
-−
-These approaches have not yet been tested and may or may not work. Experiments remain to be done.
 == Overriding engine resources ==
 Note that it is possible to override resources that are used by the game engine. For example, the "fade" framebuffer effect uses the material object "fade.mao"; if you were to create your own material object with this name and put it in override the game would use that instead. This can cause unexpected effects and should be done with care.

@@ Line 15: / Line 15: @@
 *My Documents\BioWare\Dragon Age\AddIns\<module UID>\core\data
-'''Note:''' There is currently a bug in the game preventing it from reading resources in the "My Documents Module" locations.  This is a bug which has been WNF'ed for initial release. The toolset does read from here, however, so there is some possibility for confusion if you're working on resources that are located here. Until the patch correcting this comes out, users are advised to create modules as "addin" type even when they're stand-alone.
+'''Note:''' There is currently a bug in the game preventing it from reading resources in the "My Documents Module" locations.  This is a bug which has been WNF'ed for initial release. The toolset does read from here, however, so there is some possibility for confusion if you're working on resources that are located here. Until the patch correcting this comes out, users are advised to [[creating a module|create modules]] as "addin" type even when they're stand-alone.
 *My Documents Module Override
 *My Documents Module Patch

@@ Line 60: / Line 60: @@
 Currently resources with the same name and type as an existing resource in another module can't be
 created in the same database as that module. Since the database that comes with the toolset has a set of core resources and the base campaign already in it, this makes overriding base campaign resources tricky.
 == Overriding engine resources ==
 Note that it is possible to override resources that are used by the game engine. For example, the "fade" framebuffer effect uses the material object "fade.mao"; if you were to create your own material object with this name and put it in override the game would use that instead. This can cause unexpected effects and should be done with care.

@@ Line 55: / Line 55: @@
 *Offer Env
 *Offer Data
 == Overriding engine resources ==
 Note that it is possible to override resources that are used by the game engine. For example, the "fade" framebuffer effect uses the material object "fade.mao"; if you were to create your own material object with this name and put it in override the game would use that instead. This can cause unexpected effects and should be done with care.

← Older revision		Revision as of 20:34, 1 October 2009
Line 55:		Line 55:
	*Offer Env		*Offer Env
	*Offer Data		*Offer Data
		+
		+	== Overriding engine resources ==
		+
		+	Note that it is possible to override resources that are used by the game engine. For example, the "fade" framebuffer effect uses the material object "fade.mao"; if you were to create your own material object with this name and put it in override the game would use that instead. This can cause unexpected effects and should be done with care.

@@ Line 9: / Line 9: @@
 *My Documents\BioWare\Dragon Age\AddIns\<module UID>\core\patch
 *My Documents\BioWare\Dragon Age\AddIns\<module UID>\core\locale
 *My Documents\BioWare\Dragon Age\AddIns\<module UID>\core\audio\VO
 *My Documents\BioWare\Dragon Age\AddIns\<module UID>\core\audio\Sound

@@ Line 3: / Line 3: @@
 This list is the order from top priority to bottom:
-*My Documents Core Override
+*My Documents\BioWare\Dragon Age\packages\core\override
-*Core Override
+*Program Files\Dragon Age\packages\core\override
-*Addin Override
+*My Documents\BioWare\Dragon Age\AddIns\<module UID>\core\override
-*Addin Patch
+*My Documents\BioWare\Dragon Age\AddIns\<module UID>\core\patch
-*Addin Locale
+*My Documents\BioWare\Dragon Age\AddIns\<module UID>\core\locale
-*Addin Audio\VO
+*My Documents\BioWare\Dragon Age\AddIns\<module UID>\core\audio\VO
-*Addin Audio\Sound
+*My Documents\BioWare\Dragon Age\AddIns\<module UID>\core\audio\Sound
-*Addin Env
+*My Documents\BioWare\Dragon Age\AddIns\<module UID>\core\env
-*Addin Data
+*My Documents\BioWare\Dragon Age\AddIns\<module UID>\core\data
-'''Note:''' There is currently a bug in the game preventing it from reading resources in the "My Documents Module" locations.  This is a bug which has been WNF'ed for initial release.  The toolset does read from here, however, so there is some possibility for confusion if you're working on resources that are located here.
+'''Note:''' There is currently a bug in the game preventing it from reading resources in the "My Documents Module" locations.  This is a bug which has been WNF'ed for initial release. The toolset does read from here, however, so there is some possibility for confusion if you're working on resources that are located here. Until the patch correcting this comes out, users are advised to create modules as "addin" type even when they're stand-alone.
 *My Documents Module Override
 *My Documents Module Patch
@@ Line 34: / Line 34: @@
 *Module Root
-*Core Patch
+*Program Files\Dragon Age\packages\core\Patch
 *Core Locale
 *Core Env