Difference between revisions of "Installing the toolset"

From Dragon Age Toolset Wiki
Jump to: navigation, search
(import from extranet)
 
(Physix and Phyton version added)
(44 intermediate revisions by 18 users not shown)
Line 4: Line 4:
 
* Visual C Runtime Library
 
* Visual C Runtime Library
 
* Microsoft SQL Server Express 2005 Edition
 
* Microsoft SQL Server Express 2005 Edition
* Nvidia PhysX drivers
+
* 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.
 
These components will be installed along with the toolset by the toolset's installer.
Line 10: Line 11:
 
== Location ==
 
== Location ==
  
The first screen you'll get to after starting the installer and passing the title page is the install location selector. The default is to install the program into a subdirectory of Program Files\Dragon Age. The install will require about 4.2 GB of disk space.
+
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.<sup>[http://support.microsoft.com/kb/935371]</sup>
 +
 
 +
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 ==
 
== Components ==
Line 20: Line 25:
 
== Manual database selection ==
 
== 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>.\SQLEXPRESS</code> and the default database name is <code>bw_dragonage_content</code>.
+
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 ==
 
== Installation ==
Line 32: Line 37:
 
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.
 
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.
  
== Configuration ==
+
=== Lightmapper ===
  
The external configuration utility is used to configure the toolset's database connection. 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 [[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:
  
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 ([[ellipsis.png]]) to open the data link properties window.
+
# 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 <BR> '''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] <BR> '''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).
  
Note that the configuration utility will first ask where the game build is. The game executable is not currently available for distribution but it is not necessary for the toolset to run so there's no need to be concerned about this.
+
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.
  
== Uninstallation ==
+
* 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.
  
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.
+
* 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.
  
* Core Resources - uninstalled by default, this is the toolset itself.
+
* Do not install both ActivePython and Python.org.  This will most likely cause you to get an Error Code 1 when rendering lightmaps.
* 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.  
+
* 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.
  
== Troubleshooting ==
+
* 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.
*If you have never installed MSSQLServer Express, check for updates available for it through Windows Update after installing the toolset.
+
  
*"unable to connect to the database"
+
=== NVIDIA PhysX ===
** On some systems you may encounter a problem running the toolset if you copy the uninstalled files off of the DVD first before installing them. By default SQLServer doesn't necessarily have permission to read from all of the directories that the user may have put the installation files, so if you install from such a directory it may be unable to import resources into the database. To correct this either change the administrative privileges for the directory you're installing the toolset from or install it directly from DVD.
+
**If you already have MSSQLServer Express installed as part of a different program, the toolset may not get the correct configuration to use it. Run the toolset configuration, select "Programmer" as user type, and then click "next" through the configuration wizard until you get to the "Content Database" field. It should read: "<code>Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_da_content_euts;Data Source=MSSQLDEV</code>"
+
**On Vista systems the toolset may need administrator privileges to read the database where it's installed but fail to prompt you for them. Try right-clicking the toolset's shortcut and selecting "Run as Administrator" from the dropdown menu.
+
**Some users report that the installer fails to create the SQL database (e.g. your <code>Dragon Age\toolssql\data</code> folder is empty). You can enter the following command to try restoring the database manually.  Change the paths to <code>bw_dragonage_content.bak</code> and your Dragon Age folder as appropriate): <code>"C:\Program Files\Microsoft SQL Server\90\Tools\Binn\"sqlcmd -S .\BWDATOOLSET -E -Q "RESTORE DATABASE bw_dragonage_content FROM DISK = 'C:\EUTS_Install\data\bw_dragonage_content.bak' WITH MOVE 'bw_da_content_euts_Data' TO 'C:\Program Files\Dragon Age\toolssql\Data\bw_dragonage_content.mdf', MOVE 'bw_da_content_euts_Log' TO 'C:\Program Files\Dragon Age\toolssql\Data\bw_dragonage_content.ldf'"</code>
+
**Some users have been successful simply installing from a more direct path (ie extract rars to a new folder C:\DAInstall and then run the exe file from that location rather than from a MSFT created My Documents path).
+
  
*If the SQL install fails with a crash it is possible that it is conflicting with MSXML6. If you have MSXML6 installed, uninstall it and try reinstalling the toolset.
+
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 the toolset cannot find DLLs you may need to run the configuration tool after installation to tell the toolset where to find the Dragon Age build. This can happen if you uninstall the toolset and then reinstall it again in a different location.
+
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].
  
*During the SQL Server Express installation when the installation script attempts to start the database, a message box with the "The SQL Server service failed to start..." error message and options to Retry or Cancel may pop up.
+
== Configuration ==
**Don't hit cancel as it rolls back the installation and you never get the BWDATOOLSET database!
+
**Instead navigate to C:\Documents and Settings\NetworkService\Application Data\Microsoft\ and right click on the Protect folder and open the Properties window. On the Security tab add NETWORK SERVICE to the list of Groups and User names and grant it Full Permissions.
+
**If you don't have a Security tab then close the Properties window and select Tools | Folder Options from Explorer's menu bar. In the Folder Options window click on the View tab, scroll to the last option and uncheck Use simple file sharing (Recommended) option. Now you should be able to do complete the previous step.
+
**Finally return to the "The SQL Server service failed to start..." error message and click on the Retry option.
+
  
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.  
+
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.
  
== Authentication ==
+
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.
  
In its current pre-release version, the end user toolset requires that the user have a valid keyfile and be logged in to a telemetry recording system while using it. This is intended both to limit the distribution of this version (it's not yet even to beta status) and to allow usage telemetry to be gathered so that the toolset's features can be improved.
+
==== Moving the database files from the default location ====
  
Your keyfile will be named "<code>dragon.age</code>" and must be put into the "toolset" directory of the end user toolset after it's been installed (the same directory the main executable file is in). Your keyfile is personalized to your specific account, if you have not received a keyfile contact us to have one sent to you.
+
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.
  
== Firewall issues ==
+
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.
  
In its current pre-release state, the toolset requires constant internet access in order to deliver telemetry. If you use a router or firewall you will need to ensure that the toolset can connect properly with the outside world. If the internet connection is lost the toolset will pop up the authentication window again.
+
If you have customized your database during installation, replace the bw_dragonage_content with your database name.
  
== Features included and features not included ==
+
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
  
The toolset as it currently stands is in a pre-release state. It does not include every component needed to make a full-blown adventure module from scratch.
+
This [http://support.microsoft.com/kb/224071 Microsoft KB article] has more details, if required.
  
The toolset also doesn't come with a large selection of pre-created resources since most of these would contain spoilers and other confidential information about Dragon Age's single player campaign. A small set of basic, generic resources have been included to make experimentation possible in the meantime.
+
== 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 ==
Line 92: Line 121:
  
 
http://social.bioware.com/wiki/datoolset/
 
http://social.bioware.com/wiki/datoolset/
 +
 +
{{Languages}}
 +
[[Category:Toolset installation]]

Revision as of 16:36, 31 January 2018

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.[1]

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 .\BWDATOOLSET and the default database name is bw_dragonage_content.

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 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:

  1. Install Python 2.5.4
  2. Install the win32 extensions for Python 2.5
    OR
  3. Install 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 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 "Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_dragonage_content;Data Source=.\SQLEXPRESS". For advanced configuration, click on the ellipsis button (Ellipsis.png) 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 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 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 My Documents\BioWare\Dragon Age\Toolset\logs. 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/


Language: English  • русский