Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2019.4
2020.1.3f1
2020.2
Issue ID
1272243
Regression
No
[V1 - V2 Regression] ScriptableObject loses reference to the built-in Sprite when imported for the first time
How to reproduce:
1. Open the user's attached "2020SpriteBug.zip" project
2. Go to Window -> Rewired -> Extras -> Control Mapper -> Install (Text Mesh Pro)
3. Select the "DefaultTheme" ScriptableObject in the Project window (Assets/Rewired/Extras/ControlMapper/Themes)
4. Expand the "Main Window Background" property in the Inspector
5. Observe the "Sprite" field reference
Expected result: "Background" built-in Sprite is referenced in the field
Actual result: No built-in Sprite is referenced in the field
Reproducible with: 2019.4.10f1, 2020.1.6f1, 2020.2.0b3 (V2)
Not reproducible with: 2019.4.10f1 (V1)
Could not test with: 2018.4.27f1 (Asset Pipeline V2 is not supported)
Note:
- The issue is not reproducible with the Asset Pipeline V1
- The built-in Sprite will be referenced if the Unity Editor is closed and re-opened
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment