Dragon Age Toolset Wiki - User contributions [en]

User:Allan Smith/sandbox

2010-03-05T21:09:43Z

Allan Smith: cleaning out the sand

Bug: DAUpdater needs to be run from the bin ship folder

2010-02-25T17:49:46Z

Allan Smith: updated to reflect change in patch 1.03

*'''Toolset verion:''' (n/a)
*'''Game version:''' 1.02a 
*'''Status:''' Fixed in patch 1.03

{{EV|198331|[[User:BryanDerksen|BryanDerksen]]}}

{{Dashedborder|Update: This problem is solved with game patch 1.03 (unreleased)
-[[User:Allan Smith|Allan Smith]] 17:49, 25 February 2010 (UTC)}}

== Description ==

While not a toolset issue per se, it's an issue that affects builders, so seems just as important to me. After packaging a mod into a DAZIP, the player can't simply install it by double-clicking the file that's already associated with DAUpdater. Instead, DAUpdater errors out with ''Cannot find "DAUpdater.xml" file. Please contact tech support''. Here's the reference thread [http://social.bioware.com/forum/1/topic/8/index/567852].

== Workarounds ==


* Run DAUpdater from $GameInstallDir/bin_ship

Or

* Supply a copy of DAUpdater.XML relative to the DAZIP file: $CWD/../data/DAUpdater.XML. The game will complain afterwards about the content requiring a later version of Dragon Age than what's installed, but it will install it. This might not work with the Korean version though... I think there's a Korean-language version at least.

[[Category:Toolset bugs]]

Bug: ConfigureToolset application fails to set a registry key

2010-01-15T22:06:54Z

Allan Smith: added tracking number

*'''Version found:''' 1.0.1008.0 
*'''Status:''' Open

== Description ==


The ConfigureToolset application currently (as of 1.01) doesn't set a registry entry that the toolset also needs in order to find the database properly.

== Workarounds ==


If you need to use ConfigureToolset to change your database settings, you'll need to set this key manually. The key you'll need to update is:

<pre>
HKEY_LOCAL_MACHINE\SOFTWARE\BioWare\Dragon Age\Toolset\Environment
</pre>

Change it to match the database line produced by the configuration tool in the previous step. For example, the value in a default installation of the toolset is:

<pre>
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_dragonage_content;Data Source=.\\BWDATOOLSET
</pre>

{{EV|203026}}

[[Category:Toolset bugs]]

Bug: Water plane missing in-game

2010-01-15T21:52:39Z

Allan Smith: added tracking number

*'''Version found:''' 1.0.982.19 
*'''Status:''' Open

== Description ==


If you create a level with a water plane in it the water is appearing properly in the toolset but is non-existent in the game. This problem has been identified. It is not lightmapper related; it turns out that "single player" is hard-coded into a part of the resource processing pipeline.

== Workarounds ==


A proper fix may take some time, but there's a fairly simple workaround for it; switch to the "single player" module before posting the level and then copy the files this produces from the single player override directory to your addin's override directory.

{{EV|203997}}
[[Category:Toolset bugs]]

Template:EV

2010-01-15T19:05:24Z

Allan Smith: added a space

<noinclude>
== Usage ==
Used by BioWare Employees to tag a bug or feature request on the wiki with the internal tracking number, and records the wiki user name
{{EV|Reference number}}
</noinclude>
This issue has been recorded in BioWare's internal tracking system.
Reference number: {{{1}}} -[[User:Allan Smith|Allan Smith]]

Feature request: Deleting a module

2010-01-15T19:04:36Z

Allan Smith: added reference number

The current toolset does not allow for the deletion of a module that has been created.
Users typically initially create a bunch of test modules that cannot be removed, and forever after clutter up the list of modules.

There is a hacky workaround of deleting the module name manually from the database, but it just orphans all the modules resources without removing them from the database.

{{EV|210854}}
[[Category:Feature requests]]

Template:EV

2010-01-15T19:03:26Z

Allan Smith: Create template

Requesting a new feature

2010-01-15T17:23:05Z

Allan Smith: Adding a more explicit link to page listing all feature requests

Instructions on how to request a new toolset feature. Stay tuned for more information

If you wish to report a bug, see [[Reporting a bug]]

Use this if you want to let BioWare and other community members know about some feature that you wish the toolset had. By doing so, you are helping to create a wish list. Wishes may be granted by Bioware or by clever community members. Some may not be granted at all. We can't guarantee anything.

You can view a current list of requested features [[:Category:Feature requests|here]].

== Category ==

Feature request pages will be in the category [[:Category:Feature requests]]. Include the following text in your feature request page to put it in this category:

<pre>[[Category:Feature requests]]</pre>

== Creating a new feature request page ==

A feature request page should have a title that serves as a brief description of the feature being requested.

The body of the page should contain as detailed a description of the feature as you think is appropriate. Some of the points it would be valuable to cover are:

* What exactly you would like this feature to do
* Why it cannot be done (or can't easily be done) with existing capabilities
* Specific examples of situations where the feature would be useful

== Editing an existing feature request page ==

Feature requests are by their nature often a lot more nebulous than a bug report. There is likely to be disagreement or uncertainty about what a feature request actually entails - both in scope and value. If you find a feature request that's very similar to something you'd like, you should feel free to add to the page rather than creating a possibly redundant feature request. Likewise, if a feature request turns out to have several independent parts to it, they may be split into separate pages or at least implemented as separate features.

Some feature requests may be simply impossible. In these cases a BioWare admin will likely add a note explaining that they are unfulfillable and move the feature request into some other category. For example, a request for an XBox 360 version of the toolset simply cannot be fulfilled for reasons outside BioWare's control. Again, we can't promise anything.

Some feature requests are good ideas that we here at BioWare don't have the resources to fulfil, but that we're confident could be handled by other community members in some way or another. We'll move these to the category [[:Category:Community feature suggestions]]. See also [[Community support ideas]].

Reporting a bug

2010-01-15T17:16:11Z

Allan Smith:

As a public-facing semi-formal bug tracking system we're going to use a set of categories on this wiki organize bug report pages, with one page per issue. You can still report a bug via other means (such as the toolset support email address) but ideally this set of pages and categories will serve as a one-stop destination for dealing with bugs and other toolset-related issues.

Bugs will be in the category [[:Category:Toolset bugs]], with [[:Category:closed bugs]] for those that no longer apply to the current version of the toolset.

You can view a current list of reported bugs [[:Category:Toolset bugs|here]].

== Creating a new bug page ==

Bug pages should have a title that serves as a brief description of the problem that the bug causes. You can create a new page a number of different ways in MediaWiki.

One of the easiest is to type the intended page title into the search field and then when the failed search page appears click on the red link to that page title.

[[File:How to create a new bug page.png|800px|thumb|center|The red link for the searched-for page is directly below the "Search results" title]]

In the new blank page that this brings you to, copy and paste the following template:

<pre>
*'''Version found:''' 
*'''Status:''' Open

== Description ==


== Workarounds ==


[[Category:Toolset bugs]]
</pre>

As BioWare developers and members of the community work on the issue the bug's description will be expanded and its status updated, you don't need to worry too much about getting every detail filled in immediately. Just knowing the bug exists is an important first step.

== Editing an existing bug page ==

If there's already a page describing the bug you'd like to report and you have new details you'd like to add to it, feel free to edit the page to include them. You can also add comments on the bug's associated talk page if you want to discuss certain aspects - for example if you're not certain whether the problem you've encountered is really the same bug, or if you've got questions about a suggested workaround.

Feature request: Context sensitive help

2010-01-15T17:04:54Z

Allan Smith: Create page

Would be nice to have context sensitive help in the toolset that linked the toolset directly to the toolset wiki.
If you are struggling with some properties on a particular editor, it would be nice to have the toolset take you directly to the related wiki help page.

{{dashedborder|This feature is currently in the process of being implemented. [[User:Allan Smith|Allan Smith]] 17:04, 15 January 2010 (UTC)}}

Feature request: Deleting a module

2010-01-15T16:55:55Z

Allan Smith: Create page

2009-12-11T21:18:11Z

Allan Smith:

File:Toolset setup screen.png

2009-12-11T21:17:39Z

Allan Smith: Screenshot of settings to use to install the toolset without installing SQL Server 2005 or restoring the Database.

Screenshot of settings to use to install the toolset without installing SQL Server 2005 or restoring the Database.

2009-12-10T22:37:40Z

Allan Smith: /* Lightmapper Issues */

This page is somewhat redundant as it duplicates things from pages such as [[Installation troubleshooting]]. However, it is gathering place for issues related to specific builds, along with plans to fix them.
==Build 1.0.982.19==
===Installation Issues===
====Problems Installing on Windows XP Service Pack 2====
For some, but not all users using SP2, the installation of SQL Server 2005 Express (part of the install process) can cause an infinite reboot situation on the computer. It does not happen on all systems running SP2, but it is a potential very unpleasant hazard. See [[Installation troubleshooting]] or http://social.bioware.com/forum/1/topic/8/index/113400/1 for more details.
{{Dashedborder|Version 1.01 of the toolset installer will detect SP2 and warn users about the potential craziness they are about to unleash}}

====Problems Installing to a long path====
SQL Server 2005 Express will not install to a path longer than 58 characters. The default install path for Steam, is longer than this, so this issue appears regularly for Steam installs, but could happen to anyone depending on how long their install path is. See [[Installation with Steam]] for more details
{{Dashedborder|Version 1.01 of the toolset installer will install the SQL instance to a shorter path to avoid this issue}}

====Unable to connect to the database error on Startup of toolset====
This error is accurrate, the toolset is unable to connect to the database. This indicates that there was some kind of problem when SQL Server Express 2005 was installed. Unfortunately, this is common, but unpredictable. The toolset itself cannot diagnose what the problem is. It can range from the long file path issue (above) to interference from UAC, to permissions issues, to a conflict with an existing installation of SQL Server, to registry entries, to the location of the installation file on your computer. The list is long.

See [[Installation troubleshooting]] for the current list of things that people have found that have worked. The list is regularly updated and tweaked. Sometimes [[Manual database installation]] seems to work. the installer is being adjusted to deal with what we can, but most of this process is beyond our control, as it is a third party installer, and a complex piece of software that seems to interact differently with each machine it is installed on.

====Problems with the Installer hanging at "Execute:regsvr32.exe"====
For unknown reasons, the installer will sometimes stop at this line. It seems to be waiting for a response from regsvr32 to indicate that it is finished the task it was given to do. See [[Installation troubleshooting]] for current workaround.
{{Dashedborder|Version 1.01 of the toolset installer is calling this in a different way to attempt to avoid the problem}}

===Toolset Issues===
====Exporting resources can cause the main campaign to fail====
An incompatibility has been discovered between the core resources in the database released with the toolset and the core resources used by the existing main campaign. This can cause the main campaign to stop working correctly after any resources are exported from the toolset. See [[Plot GUID bug]], or http://social.bioware.com/forum/1/topic/8/index/114380 for more details, and for information on how to clean up after this error strikes.

{{Dashedborder|This will be fixed in version 1.01 of the toolset. The underlying problem has been identified and fixed, and a new set of core resources has been put into the database that will not give this problem anymore.}}

====Installing the toolset can corrupt savegames made after the toolset is installed====
This is the same problem as above (Exporting resources can cause the main campaign to fail), Just another manifestation of it.

====ERF and GFF Editors====
Attempting to run the ERF and GFF Editors as stand alone applications from the Dragon Age\tools\ directory (as opposed to within the toolset) will result in a "Keyfile not found" error. This is a remnant of the security that was in place for our Beta Testers.
The next version of the toolset will allow you to run these executables without a keyfile
====FaceFX not appearing in Menus====
FaceFx is not appearing in consistently in some menus. Workaround can be found here: http://social.bioware.com/forum/1/topic/8/index/139865
{{Dashedborder|The next version of the toolset will fix this problem.}}

====Lightmapper Issues====
There are various issues with the lightmapper creating odd shadows, and black artifacts, particularly along chunk boundaries.
{{dashedborder|The latest version of the lightmapper is available now at [http://social.bioware.com/project/717/ the Lightmapper project]. It seems to solve many of the previous issues. It can be downloaded and installed over top of your existing lightmapper files

The latest lightmapper files are included with version 1.01 of the toolset installer as well.}}

====Water Plane Missing in Game====
If you create a level with a water plane in it, the water is appearing properly in the toolset, but is non-existent in the game. This problem has been identified. It is not lightmapper related. A proper fix may take some time, but there's a fairly simple workaround for it; switch to the "single player" module before posting the level and then copy the files this produces from the single player override directory to your addin's override directory. See [[water]] for more detail.

==== Toolset freezes while exporting or compiling ====

Issue: The toolset freezes when exporting modules, compiling scripts, or saving scripts. Typically the freeze happens when the log reaches the effect_death_h.nss log entry.

Solution: This problem seems to be related to one of the language settings in windows. In the language control panel of Windows, the "Language for Non-Unicode programs" option must be set to English (United States). So far this fix seems to remove the freeze problem.

== Older known issues (Beta issues, needs cleanup) ==

=== Build 925 issues ===

When working on a multiple-monitor system, it is possible that rearranging the monitors will cause the previously-recorded default location of popup windows such as "manage modules" to be off the edge of the display area where it can't be seen or manipulated. This can lock up the toolset, since the toolset won't respond until the popup is dismissed. To reset the position of the popup windows, delete the file "My Documents\BioWare\Dragon Age\Toolset\Layouts3.xml". It will be recreated the next time the toolset is run using default values.

=== Build 888 issues ===

Build 888 and subsequent builds has some built-in assumptions that it will be installed in "Program Files\Dragon Age". If it's installed elsewhere, the resource processor (used during certain resource exports, the generation of VO, FaceFX, and other activities) will become confused and fail with log messages such as "Unable to load C:\Programme\Dragon Age\tools\ResourceBuild/Settings/ResourceBuilder.xml" or "Failed to copy template 'C:\Program Files\Dragon Age\tools\ResourceBuild\Processors\VO_template_project.fdp' to 'C:\DOCUME~1\Owner\LOCALS~1\Temp\DragonAgePlaceholderVO\VO_template_project.fdp'" To correct this, go to the Tools -> Options -> Environment -> Resource Build Path setting and correct the path listed there to point to the resource builder's actual location.

This appears to have been resolved in 1.0.982.0

=== Build 773 issues ===

*When creating a new crust VFX in the [[VFX editor]], by default a model named "default_player" will be added as the model to apply the crust to. default_player doesn't exist in the current database and won't exist in any new modules that are created, so an error message is generated. To resolve this simply change the broken model's appearance to one of the existing ones.
*The "preview line" command available under the "tools" menu of the conversation editor doesn't work and can make future previews troublesome (the VO isn't always generated afterward). To preview a line, first generate the VO with the "Generate VO" command, then generate the FaceFX with the "Generate FaceFX" command, and then select the "preview line without generating VO/FaceFX" command.
*If you use resource history to view past revisions of a large conversation and then try to diff two of them, the toolset will crash. You can diff small conversations correctly. It's not known exactly what the cutoff between "large" and "small" conversations are as far as this bug is concerned.

*Under Vista, the default install of MSSQL doesn't support multiple different user accounts on the same machine. Attempting to start the toolset from the wrong user account will pop up an error advising that you use the configuration tool to correct the database settings, but the database settings are not in error - it's the database server itself that's refusing to cooperate. One possible solution is to use SQL Server Management Studio Express to set up MSSQL properly.

* When loading a saved game file, areas and objects contained therein are loaded from the save rather than the game resource. This means that if you save your game inside an area, make changes to the area and export them using the toolset, and then reload your game, none of the changes will appear. The changes will only appear if you start a new game. This affects objects such as waypoints, creatures, placeables, and so on.

[[Category:Toolset installation]]