Difference between revisions of "Bug: Tint Override dropdown reverts to default"
(Created page with '*'''Toolset verion:''' 1.0.1008.0 *'''Game version:''' 1.02a *'''Status:''' Open == Description == <!-- Describe the bug here including as many details as possible. What situat...') |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
*'''Toolset verion:''' 1.0.1008.0 | *'''Toolset verion:''' 1.0.1008.0 | ||
| − | *'''Game version:''' 1. | + | *'''Game version:''' 1.03 |
*'''Status:''' Open | *'''Status:''' Open | ||
| Line 12: | Line 12: | ||
It may be relevent that even when there is no M2DA, the default dropdown includes some mysterious labels (7) through (23) which are not defined in tints.xls. | It may be relevent that even when there is no M2DA, the default dropdown includes some mysterious labels (7) through (23) which are not defined in tints.xls. | ||
| + | |||
| + | The same issue can occur with a custom Rewards table (even if it overrides the 2DA completely). | ||
| + | |||
| + | UPDATE : a similar issue has been experienced when trying to use a custom var_module 2DA for the module variables. If the custom file has a different name, it is possible to select it in module properties, but after a while every save/export results in an error message that the custom file cannot be found. | ||
== Workarounds == | == Workarounds == | ||
Latest revision as of 16:31, 2 November 2010
- Toolset verion: 1.0.1008.0
- Game version: 1.03
- Status: Open
Description
When an item is opened in the Object Inspector, the Tint Override dropdown includes any additional entries defined in a tint_override M2DA as expected.
However, after working with the toolset for a while, the dropdown reverts to the default list. The custom list can only be restored by reopening the toolset.
Very often, the bug occurs as soon as any object is saved and exported. However, this cannot be reproduced on every occasion.
It may be relevent that even when there is no M2DA, the default dropdown includes some mysterious labels (7) through (23) which are not defined in tints.xls.
The same issue can occur with a custom Rewards table (even if it overrides the 2DA completely).
UPDATE : a similar issue has been experienced when trying to use a custom var_module 2DA for the module variables. If the custom file has a different name, it is possible to select it in module properties, but after a while every save/export results in an error message that the custom file cannot be found.
Workarounds
Open the toolset.
Create or open all the items you want to tint, but don't save or export anything.
Then tint all the items without saving or exporting.
Finally save and export all the items.
There is an unverified report that the bug goes away if the tint_override M2DA is placed in the packages override folder.
