Known issues

From Dragon Age Toolset Wiki
Revision as of 23:14, 28 June 2009 by BryanDerksen (Talk | contribs) (imported from extranet)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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.

Older known issues (needs to be cleaned)

  • 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.
  • In build 648 there was no proper way to add your own recorded voice over to a conversation. The toolset tried to find the recorded voice over files in a Perforce repository (which isn't present for the end user toolset) and then when that failed it auto-generated placeholder VO. This has been fixed in the current build; see the relevant section in [Conversation].

You can manually generate the correct FMOD files and put them in the override directory like so:

File:Temporary vo workaround.png

Note that if you click on the "Generate VO" command after you've done this, your recorded VO will be overwritten with new placeholder VO. You'll want to keep backups of the FMOD files to make fixing this easier.

Under Vista the directory is C:\Users\__username__\AppData\Local\Temp\DragonAgePlaceholderVO\en-us\.

  • 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. It will be fixed in a later update to the Toolset.