Known issues - Revision history

Ashhawk: BSN link flagged for maintenance - using AWB

2022-02-01T16:19:41Z

BSN link flagged for maintenance - using AWB

Ladyofpayne1: /* Toolset Issues */

2018-01-06T14:35:32Z

‎Toolset Issues

Ladyofpayne: /* Toolset Issues */

2017-07-04T13:21:31Z

‎Toolset Issues

Ladyofpayne at 09:54, 27 June 2017

2017-06-27T09:54:40Z

Kelamor: Add languages bar

2011-02-17T03:12:43Z

Add languages bar

BryanDerksen: split another issue out into a separate bug page

2010-01-25T17:23:53Z

split another issue out into a separate bug page

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

2010-01-23T16:30:47Z

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

BryanDerksen: /* Build 773 issues */ delete two issues that were resolved long ago.

2010-01-15T22:52:15Z

‎Build 773 issues: delete two issues that were resolved long ago.

BryanDerksen at 20:30, 15 January 2010

2010-01-15T20:30:05Z

BryanDerksen: /* Toolset Issues */ add a newly reported bug to the list

2010-01-15T20:27:44Z

‎Toolset Issues: add a newly reported bug to the list

← Older revision		Revision as of 16:19, 1 February 2022
Line 1:		Line 1:
		+	{{BSN link}}
		+
	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.		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.

@@ Line 7: / Line 7: @@
 *[[Bug: Out of memory message]]
 *[[Bug: New level doesn't work correctly]]
 ==Build 1.0.1008.0 (Installer Version 1.01)==

@@ Line 6: / Line 6: @@
 ===Toolset Issues===
 *[[Bug: Out of memory message]]
 ==Build 1.0.1008.0 (Installer Version 1.01)==

← Older revision		Revision as of 09:54, 27 June 2017
Line 2:		Line 2:

	We're now moving detailed bug reports to individual pages, grouped in the category [[:Category:Toolset bugs\|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.		We're now moving detailed bug reports to individual pages, grouped in the category [[:Category:Toolset bugs\|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]]

	==Build 1.0.1008.0 (Installer Version 1.01)==		==Build 1.0.1008.0 (Installer Version 1.01)==

← Older revision		Revision as of 03:12, 17 February 2011
Line 64:		Line 64:
	* 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.		* 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.

		+	{{languages}}
	[[Category:Toolset installation]]		[[Category:Toolset installation]]

@@ Line 5: / Line 5: @@
 ==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 [[Unable to connect to the database|here]].
@@ Line 21: / Line 24: @@
 *[[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\...]]
-==== Error: <code>"Cannot open file for writing C:\Program Files\BioWare\..."</code> ====
-−
-This is because the folder <code>C:\Program Files\BioWare\</code> does not exist (for example: you installed Dragon Age from Steam.)
-Simply create the directory <code>C:\Program Files\BioWare\</code> then hit retry.
-−
-Note: On some machines this path may appear differently. <code>C:\Program Files\Common Files\BioWare\...</code> 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.
-−
-'''Note: This error is still present in 1.01.'''
 ====[[Unable to connect to the database]]====

← Older revision		Revision as of 16:30, 23 January 2010
Line 32:		Line 32:

	This will not work for everyone! If you're still having problems, please wait for an update.		This will not work for everyone! If you're still having problems, please wait for an update.
		+
		+	'''Note: This error is still present in 1.01.'''

	====[[Unable to connect to the database]]====		====[[Unable to connect to the database]]====

← Older revision		Revision as of 22:52, 15 January 2010
Line 65:		Line 65:
	=== Build 773 issues ===		=== 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.		*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.

@@ Line 1: / Line 1: @@
 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 [[:Category:Toolset bugs|Toolset bugs]]. This page will remain as a high-level summary of current known issues.
+We're now moving detailed bug reports to individual pages, grouped in the category [[:Category:Toolset bugs|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.
 ==Build 1.0.1008.0 (Installer Version 1.01)==

@@ Line 10: / Line 10: @@
 ===Toolset Issues===
 *[[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.