Sometimes a UI display created using setObjectTexture will become inaccessible / trying to retrieve the display using findDisplay and the related identifier strings returns a displayNull.
Description
Description
Details
Details
- Severity
- Minor
- Resolution
- Open
- Reproducibility
- Sometimes
- Operating System
- Windows 10 x64
- Operating System Version
- 19045.4529
- Category
- Scripting
Steps To Reproduce
- Create a pair of UI display elements in description.ext, one with a RscStructuredText control and a RscProgress control, and another with just a RscStructuredText control.
- Use setObjectTexture on two different selections of an object using a uiEx texture to create a unique identifier for instances of the two UI elements
- Attempt to find the displays and change parts of their display sequentially using the string argument version of findDisplay
- Note that at some point, some displays will stop returning displays, and instead return a displayNull.
Attached is a specific example mission
Additional Information
This seems to be not 100% reproducible on a per mission basis, but rather a cumulative effect once in the game (usually within the first few times a display is initialized). I've also noticed Superflush / flush will sometimes fix parts of it, but not always.