Difference between revisions of "Bug: Builder to Builder Load may not reproduce resource detail correctly"
(Created page with '*'''Version found:''' 1.0.1008.0 (Installer Version 1.01) *'''Status:''' Open == Description == A Builder-to-Builder Load may result in resources that have missing detail. For ...') |
|||
| Line 5: | Line 5: | ||
A Builder-to-Builder Load may result in resources that have missing detail. | A Builder-to-Builder Load may result in resources that have missing detail. | ||
| − | For | + | For instance, |
* A female NPC may load as a male with the default head and no inventory. | * A female NPC may load as a male with the default head and no inventory. | ||
* All lines may disappear from a conversation. | * All lines may disappear from a conversation. | ||
* All flags may vanish from a plot. | * All flags may vanish from a plot. | ||
| + | * A cutscene may load without its dependent resources - consequently, it does nothing when viewed. | ||
| − | + | These are just examples - evidently, all sorts of omissions can occur, depending on the resource type. | |
| + | |||
| + | Other symptoms include alarming messages about core resources being loaded when none have been selected, and changes to the check in/out status of core resources. To date, there's no evidence that this has harmed anything, but at the very least it's bad for builder confidence. | ||
== Workarounds == | == Workarounds == | ||
| Line 20: | Line 23: | ||
* Create New (strings) | * Create New (strings) | ||
* Do not select any resources which already exist (default) | * Do not select any resources which already exist (default) | ||
| + | * Ensure all new resources are selected | ||
If the target data base already contains a resource named X within module A, don't attempt to load X to module B. If A is not a parent of B, depending on the resource type, the toolset may report an error or attempt to work around the name duplication by creating a resource X_1. This can make the above-mentioned bug even worse (though it is not the sole cause). | If the target data base already contains a resource named X within module A, don't attempt to load X to module B. If A is not a parent of B, depending on the resource type, the toolset may report an error or attempt to work around the name duplication by creating a resource X_1. This can make the above-mentioned bug even worse (though it is not the sole cause). | ||
[[Category:Toolset bugs]] | [[Category:Toolset bugs]] | ||
Revision as of 17:17, 17 February 2010
- Version found: 1.0.1008.0 (Installer Version 1.01)
- Status: Open
Description
A Builder-to-Builder Load may result in resources that have missing detail.
For instance,
- A female NPC may load as a male with the default head and no inventory.
- All lines may disappear from a conversation.
- All flags may vanish from a plot.
- A cutscene may load without its dependent resources - consequently, it does nothing when viewed.
These are just examples - evidently, all sorts of omissions can occur, depending on the resource type.
Other symptoms include alarming messages about core resources being loaded when none have been selected, and changes to the check in/out status of core resources. To date, there's no evidence that this has harmed anything, but at the very least it's bad for builder confidence.
Workarounds
This doesn't seem to happen if you choose the following options:
- Show Dependents (which is not the default)
- Create New (strings)
- Do not select any resources which already exist (default)
- Ensure all new resources are selected
If the target data base already contains a resource named X within module A, don't attempt to load X to module B. If A is not a parent of B, depending on the resource type, the toolset may report an error or attempt to work around the name duplication by creating a resource X_1. This can make the above-mentioned bug even worse (though it is not the sole cause).
