Art Resources - Revision history

Ashhawk: BSN link flagged for maintenance - using AWB

2022-02-01T15:43:01Z

BSN link flagged for maintenance - using AWB

Sunjammer: Fixing links, formatting and typos

2011-06-11T12:33:47Z

Fixing links, formatting and typos

BloodsongVengeance: bloodsong adds another link to the layout list.

2010-12-28T20:35:59Z

bloodsong adds another link to the layout list.

Eshme: /* Modding and Creating */ added links

2010-01-30T00:36:18Z

‎Modding and Creating: added links

Eshme: /* Overview */ added links

2010-01-30T00:34:27Z

‎Overview: added links

Eshme: /* Overview */

2010-01-30T00:30:28Z

‎Overview

Eshme: /* Resourcetypes */

2010-01-27T18:17:06Z

‎Resourcetypes

Eshme: /* Visual effects */ cleaning

2010-01-27T18:15:14Z

‎Visual effects: cleaning

Eshme: /* Level/Area layouts */

2010-01-26T21:58:22Z

‎Level/Area layouts

Eshme: /* Animations */

2010-01-26T21:56:52Z

‎Animations

← Older revision		Revision as of 15:43, 1 February 2022
Line 1:		Line 1:
		+	{{BSN link}}
		+
	{{MarkedForReview}}		{{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.		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.

@@ Line 1: / Line 1: @@
-Art Resources are all Art created and stored into the Dragon Age Filesystem. Creators of Worldmaps will need Art Resources to shape them with Models, while creators of Facemorphs need Models of Faces. With that ,they are also creating Art Resources.
+{{MarkedForReview}}
 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 properies tell which [[Model]] it uses.
+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 Filesystems [[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]].
+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 Filename 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.
+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.
-=== Filestructure ===
+=== File Structure ===
-[[ERF]] Files for Dragon Age are stored in the Folder and Subfolders:
+[[ERF]] files for Dragon Age are stored in the folder and sub-folders:
-<pre>(Dragon Age Install Dir)\packages\core\</pre>
+<pre>[Dragon Age Install Directory]\packages\core\</pre>
-*Browsing the Filestructure, see Article: [[ERF]]
+* Browsing the [[ERF]] files supplied with the toolset
-*List of Filestypes: [[File types]]
+* [[List of file types]]
 == Modding and Creating ==
-When talking Art Resources, its creation requires mostly knowing only about the Resourcetype in question. Anything about creation, exporting, formats is explained for each on their own.
+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 mimicing the Filename 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 Filesystem. This is normally an Override Folder of some sort, and those Resources are initially stored as single Files.
+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 wouldnt 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|"DAZIP"]] [[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 Filesystem.
+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.
+Only the [[Builder to player]] functionality packs those Resources into [[ERF|ERF Files]] again.
 :''See also: [[Tutorials]]''
-== Resourcetypes ==
+== Resource Types ==
 === Models ===
-See Main Article: [[Model]]
+: ''See Main Article: [[Model]]''
 === Materials / Textures / Tints ===
-See Main Article: [[Material editor]]
+: ''See Main Article: [[Material editor]]''
 In closer relation to Models see Article: [[Model]]
@@ Line 46: / Line 47: @@
 === Animations ===
-See Main Article: [[Animation blend tree editor]]
+: ''See Main Article: [[Animation blend tree editor]]''
 === Morphs ===
-Facemorphs, are generated with the face-morphing tool.
+: ''See Main Article: [[Morph]]''
-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 ===
 Handles facial expressions and lip-synching.
 === Visual effects ===
-See Main Article : [[VFX editor]]
+: ''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]
@@ Line 70: / Line 71: @@
 === Audio ===
-See Main Article : [[Sound and music]]
+: ''See Main Article : [[Sound and music]]''
 === Level/Area layouts  ===
-''(Note that this is distinct from the Area editor)''
+: ''See Main Article: [[Level editor]]''
-−
 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]
-See also [[Area layouts used in the single player module]] for a listing of what each one is.
+Note that [[level]]s and [[area layout]]s are are distinct from [[area]]s created in the [[Area editor]]
 [[Category:Art resources]]

← Older revision		Revision as of 20:35, 28 December 2010
Line 79:		Line 79:

	You can download the source files for all the level layouts in the main campaign from here: [http://social.bioware.com/project/1331/#files]		You can download the source files for all the level layouts in the main campaign from here: [http://social.bioware.com/project/1331/#files]
		+
		+	See also [[Area layouts used in the single player module]] for a listing of what each one is.

	[[Category:Art resources]]		[[Category:Art resources]]

@@ Line 24: / Line 24: @@
 When talking Art Resources, its creation requires mostly knowing only about the Resourcetype 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 mimicing the Filename of the original, so that the Designer Resource ,or anything that previously read that File, will now pick the modded one. Art Resources, along with 2DA Resources, need to be manually arranged into the Filesystem. This is normally an Override Folder of some sort, and Resources are initially stored as single Files.
+A common activity in modding is overriding existing Art Resources. This is the process of recreating a special type and mimicing the Filename 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 Filesystem. 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 wouldnt matter. However when the Art Resource should be integrated into a custom Module, it should be placed alongside the override folder of that Module. The reason is that the Toolset creates [[DAZIP|"DAZIP"]] [[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 Filesystem.
+Generally, the Game and the Toolset reads multiple override Folders [[Source directory priorities|after a list of priorities]], so it wouldnt 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|"DAZIP"]] [[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 Filesystem.
-Only the [[Builder to player]] Functionality packs those Resources into ERF Files again.
+Only the [[Builder to player]] Functionality packs those Resources into [[ERF|ERF Files]] again.
 :''See also: [[Tutorials]]''

@@ Line 4: / Line 4: @@
 == 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 Resource. A sword, which is a Designer Resource, for example has attack properties, and another of these properies tell which Model it uses.
+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 properies 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.
+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 Filesystems [[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]]s.
+Any Resource is stored in the Dragon Age Filesystems [[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 Filename 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.

← Older revision		Revision as of 18:17, 27 January 2010
Line 57:		Line 57:

	You can download the source files for all the visual effects in the main campaign from here: [http://social.bioware.com/project/1331/#files]		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 ===		=== Level/Area layouts ===

← Older revision		Revision as of 18:15, 27 January 2010
Line 55:		Line 55:

	See Main Article : [[VFX editor]]		See Main Article : [[VFX editor]]
−	*[[VFX list]] lists visual effects in Dragon Age's library.

	You can download the source files for all the visual effects in the main campaign from here: [http://social.bioware.com/project/1331/#files]		You can download the source files for all the visual effects in the main campaign from here: [http://social.bioware.com/project/1331/#files]

← Older revision		Revision as of 21:56, 26 January 2010
Line 37:		Line 37:

	See Main Article: [[Animation blend tree editor]]		See Main Article: [[Animation blend tree editor]]
−	*[[ANI]]
−	*[[Animation list]]

	=== Morphs ===		=== Morphs ===