Difference between revisions of "Known issues"

Latest revision as of 17:19, 1 February 2022

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.

We're now moving detailed bug reports to individual pages, grouped in the category Toolset bugs. See Reporting a bug for instructions on how to submit bugs. This page will remain as a high-level summary of current known issues.

Final Build

Toolset Issues

• Bug: Out of memory message
• Bug: New level doesn't work correctly
• Bug: Bulder to Player with new level issue

Build 1.0.1008.0 (Installer Version 1.01)

Installer Issues

• Bug: Cannot open file for writing C:\Program Files\BioWare\...

Unable to connect to the database

Unfortunately this will always be a potential issue, as it is an issue with connecting to SQL Server 2005 Express, which can fail in as many ways as there are users. The latest help can be found here.

Toolset Issues

• Bug: SpeedTree rendering distance - it has been reported that in at least one case a user can't set his tree rendering distance above 20m.
• Bug: ConfigureToolset application fails to set a registry key . This bug requires a workaround if you need to use ConfigureToolset to change your database settings.
• Bug: Computer names with non-English characters can cause checkout problems. This can cause checked-out resources to be recognized as checked out to the wrong user, making them impossible to edit.
• Bug: Unable to save a new module. This can occur for users with long usernames.
• Bug: Water plane missing in-game. Level art that's posted when not in the single player module is missing its water planes.

Build 1.0.982.19 (Installer Version 1.00)

Installation Issues

• Bug: Endless reboot cycles after install under Windows XP SP 2
• Installation into a directory with a long path name (this arose with Steam installations in particular)
• Bug: Installer hangs at the stage of Execute:regsvr32.exe /s "C:\Dragon Age\tools\Engine.dll"
• Bug: Cannot open file for writing C:\Program Files\BioWare\...

Unable to connect to the database

Unfortunately this will always be a potential issue, as it is an issue with connecting to SQL Server 2005 Express, which can fail in as many ways as there are users. The latest help can be found here.

Toolset Issues

• Bug: GFF and ERF editors require a keyfile
• Bug: FaceFX not appearing in menus
• Bug: Lightmapper causes shading artifacts along chunk boundaries
• Bug: 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.
• Bug: Toolset freezes when exporting or compiling

Exporting resources can cause the main campaign to fail, and can corrupt savegames made after installation

• 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.

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.

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

• 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.