Difference between revisions of "Bug: toolset export generates files with names that can't be packaged in builder to player"
From Dragon Age Toolset Wiki
BryanDerksen (Talk | contribs) (Created page with '*'''Version found:''' 1.01 <!-- put the version number of your toolset here --> *'''Status:''' Open == Description == <!-- Describe the bug here including as many details as pos...') |
BryanDerksen (Talk | contribs) m (small clarification) |
||
| Line 5: | Line 5: | ||
<!-- 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. Examples include: | + | 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: |
*.gpu.rim files, generated when posting level layouts | *.gpu.rim files, generated when posting level layouts | ||
Revision as of 00:45, 22 January 2010
- Version found: 1.01
- Status: Open
Description
Certain operations in the toolset will cause files to be exported that can't be packaged into ERFs 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.
