DAZIP - Revision history

BryanDerksen: how to generate and use dazips

2009-11-10T20:37:51Z

how to generate and use dazips

BryanDerksen: This bug was resolved before the toolset launched.

2009-11-10T20:36:18Z

This bug was resolved before the toolset launched.

BryanDerksen at 22:48, 16 September 2009

2009-09-16T22:48:01Z

BryanDerksen: Category:File types

2009-08-21T21:22:52Z

Category:File types

BryanDerksen: Created page with 'DAZIP files are packages of exported resources ready to be installed and loaded into the Dragon Age game. The format is actually just a renamed ZIP file, and can be opened by...'

2009-07-29T22:10:42Z

Created page with 'DAZIP files are packages of exported resources ready to be installed and loaded into the Dragon Age game. The format is actually just a renamed ZIP file, and can be opened by...'

New page

DAZIP files are packages of [[export]]ed resources ready to be installed and loaded into the Dragon Age game. The format is actually just a renamed ZIP file, and can be opened by any zip editor to manually extract or manipulate the contents.

Inside are the exported binary resources for a module, packaged into ERFs and arranged in a directory tree corresponding to where they will be placed when installed. Also included is a manifest XML file that contains information about the module, such as title, release date, version number, and so forth.

← Older revision		Revision as of 20:37, 10 November 2009
Line 2:		Line 2:

	Inside are the exported binary resources for a module, packaged into [[ERF]]s and arranged in a directory tree corresponding to where they will be placed when installed. Also included is a manifest XML file that contains information about the module, such as title, release date, version number, and so forth.		Inside are the exported binary resources for a module, packaged into [[ERF]]s and arranged in a directory tree corresponding to where they will be placed when installed. Also included is a manifest XML file that contains information about the module, such as title, release date, version number, and so forth.
		+
		+	See [[builder to player]] for information on how to generate a DAZIP from the toolset.
		+
		+	To install a DAZIP so that your game can use it, either double-click on it (if the file type has been associated with the DAUpdater program) or go to the bin_ship directory where your game executable is and run DAUpdater.exe manually.

	[[Category:File types]]		[[Category:File types]]

← Older revision		Revision as of 20:36, 10 November 2009
Line 2:		Line 2:

	Inside are the exported binary resources for a module, packaged into [[ERF]]s and arranged in a directory tree corresponding to where they will be placed when installed. Also included is a manifest XML file that contains information about the module, such as title, release date, version number, and so forth.		Inside are the exported binary resources for a module, packaged into [[ERF]]s and arranged in a directory tree corresponding to where they will be placed when installed. Also included is a manifest XML file that contains information about the module, such as title, release date, version number, and so forth.
−
−	~~== Known issues ==~~
−
−	Certain types of file are not packaged into ERFs and may be omitted from the DAZIP file by the current builder-to-player packaging process. Known examples include TGA files and BIK files. If you're using these sorts of resources you can manually insert them into the DAZIP file using any standard ZIP-editing program.

	[[Category:File types]]		[[Category:File types]]

@@ Line 1: / Line 1: @@
 DAZIP files are packages of [[export]]ed resources ready to be installed and loaded into the Dragon Age game. The format is actually just a renamed ZIP file, and can be opened by any zip editor to manually extract or manipulate the contents.
-Inside are the exported binary resources for a module, packaged into ERFs and arranged in a directory tree corresponding to where they will be placed when installed. Also included is a manifest XML file that contains information about the module, such as title, release date, version number, and so forth.
+Inside are the exported binary resources for a module, packaged into [[ERF]]s and arranged in a directory tree corresponding to where they will be placed when installed. Also included is a manifest XML file that contains information about the module, such as title, release date, version number, and so forth.
 [[Category:File types]]

← Older revision		Revision as of 21:22, 21 August 2009
Line 2:		Line 2:

	Inside are the exported binary resources for a module, packaged into ERFs and arranged in a directory tree corresponding to where they will be placed when installed. Also included is a manifest XML file that contains information about the module, such as title, release date, version number, and so forth.		Inside are the exported binary resources for a module, packaged into ERFs and arranged in a directory tree corresponding to where they will be placed when installed. Also included is a manifest XML file that contains information about the module, such as title, release date, version number, and so forth.
		+
		+	[[Category:File types]]