Bug: toolset export generates files with names that can't be packaged in builder to player

From Dragon Age Toolset Wiki
Jump to: navigation, search
  • Version found: 1.01
  • Status: Open


BioWare BWIcon rgb.png
 This issue has been recorded in BioWare's internal tracking system.

Reference number: 212197 -BryanDerksen

Description

Certain operations in the toolset will cause files to be exported that can't be packaged into ERFs by the builder to player process due to filename restrictions (ERF doesn't like filenames with two dots). Examples include:

  • .gpu.rim files, generated when posting level layouts
  • .mor.xml files, luckily they're not needed

See [1] for a forum thread where this bug is discussed.

Workarounds

The files that can't be packaged into ERFs can still be manually inserted into the DAZIP file using ordinary archive-manipulating programs, causing the installer to extract and place them in the correct locations when the DAZIP is installed.

To keep it simple, since the problem typically occurs with external levels, exclude the entire core override toolsetexport folder from the Builder-to-Player, rename to .zip, drag the missing toolsetexport folder to the core data folder in the .zip manually, then rename to .dazip.

Retrieved from "http://datoolset.net/mw/index.php?title=Bug:_toolset_export_generates_files_with_names_that_can%27t_be_packaged_in_builder_to_player&oldid=16078"