Difference between revisions of "Builder to player"
From Dragon Age Toolset Wiki
| Line 1: | Line 1: | ||
| + | {{Infobox module}} | ||
"Builder to player" packaging is a system for packaging up the playable binary files you've exported from your toolset into a form that is easily installed and played on another system. It can be found under the "Tools -> Builder" menu. | "Builder to player" packaging is a system for packaging up the playable binary files you've exported from your toolset into a form that is easily installed and played on another system. It can be found under the "Tools -> Builder" menu. | ||
The toolset will list all the binary files you've exported, including both art and designer resources, and give you the opportunity to select which ones to include in the package (you usually won't need to include core resources, for example). It will then package them into [[ERF]]s, which will be bundled together into a [[DAZIP]] file along with a manifest file used by the program DAUpdater when installing the package on the end user's machine. | The toolset will list all the binary files you've exported, including both art and designer resources, and give you the opportunity to select which ones to include in the package (you usually won't need to include core resources, for example). It will then package them into [[ERF]]s, which will be bundled together into a [[DAZIP]] file along with a manifest file used by the program DAUpdater when installing the package on the end user's machine. | ||
[[category:database]] | [[category:database]] | ||
Revision as of 20:33, 29 January 2010
| Module topics |
|---|
|
"Builder to player" packaging is a system for packaging up the playable binary files you've exported from your toolset into a form that is easily installed and played on another system. It can be found under the "Tools -> Builder" menu.
The toolset will list all the binary files you've exported, including both art and designer resources, and give you the opportunity to select which ones to include in the package (you usually won't need to include core resources, for example). It will then package them into ERFs, which will be bundled together into a DAZIP file along with a manifest file used by the program DAUpdater when installing the package on the end user's machine.
