Difference between revisions of "Known issues"

From Dragon Age Toolset Wiki
Jump to: navigation, search
(more cleanup)
m (→‎Toolset Issues: add a newly reported bug to the list)
Line 10: Line 10:
 
===Toolset Issues===
 
===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: 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: 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.

Revision as of 21:27, 15 January 2010

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. This page will remain as a high-level summary of current known issues.

Build 1.0.1008.0 (Installer Version 1.01)

Installer Issues

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

Build 1.0.982.19 (Installer Version 1.00)

Installation Issues

Error: "Cannot open file for writing C:\Program Files\BioWare\..."

This is because the folder C:\Program Files\BioWare\ does not exist (for example: you installed Dragon Age from Steam.) Simply create the directory C:\Program Files\BioWare\ then hit retry.

Note: On some machines this path may appear differently. C:\Program Files\Common Files\BioWare\... for example.

Note: On Vista 64, the folder was C:\Program Files (x86)\Common Files\Bioware creating that one worked.

This will not work for everyone! If you're still having problems, please wait for an update.

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

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

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.

This is fixed in version 1.01 of the toolset. The underlying problem was identified and fixed, and a new set of core resources has been put into the database that does not give this problem anymore.

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.
Retrieved from "http://datoolset.net/mw/index.php?title=Known_issues&oldid=9670"