Difference between revisions of "Bug: toolset export generates files with names that can't be packaged in builder to player"
BryanDerksen (Talk | contribs) m (small clarification) |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
*'''Version found:''' 1.01 <!-- put the version number of your toolset here --> | *'''Version found:''' 1.01 <!-- put the version number of your toolset here --> | ||
*'''Status:''' Open | *'''Status:''' Open | ||
| + | |||
| + | {{EV|212197|[[User:BryanDerksen|BryanDerksen]]}} | ||
== Description == | == Description == | ||
<!-- Describe the bug here including as many details as possible. What situations trigger it and what effects it causes are the most important. --> | <!-- Describe the bug here including as many details as possible. What situations trigger it and what effects it causes are the most important. --> | ||
| − | Certain operations in the toolset will cause files to be exported that can't be packaged into [[ERF]]s due to filename restrictions (ERF doesn't like filenames with two dots). Examples include: | + | Certain operations in the toolset will cause files to be exported that can't be packaged into [[ERF]]s 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 | *.gpu.rim files, generated when posting level layouts | ||
| Line 16: | Line 18: | ||
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. | 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. | ||
| + | |||
| + | |||
[[Category:Toolset bugs]] | [[Category:Toolset bugs]] | ||
Latest revision as of 18:46, 18 April 2011
- Version found: 1.01
- Status: Open
 |
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.
