Search Issue Tracker
By Design
Votes
0
Found in
2019.2.0a6
2019.3.0a4
Issue ID
1158217
Regression
Yes
[TextureImporter] Texture Importer applies settings before they are Applied in the Inspector
How to reproduce:
1. Open the attached project
2. Select "level4" texture and make sure it has "Read/Write Enabled" setting disabled and applied
3. Find menu item "TextureCheck/IsSettingApplied" and press it
- You should get "isReadable = False" in Console as Asset importer returns False on importer.isReadable
4. Select "level4" texture again and enable "Read/Write Enabled" setting, but don't apply
5. Find menu item "TextureCheck/IsSettingApplied" and press it
Result: You will get "isReadable = True" even when this setting wasn't applied on texture. Might be the same with all texture importer settings
Reproducible: 2019.3.0a4, 2019.2.0a12, 2019.2.0a6
Not reproducible: 2019.1.1f1, 2019.2.0a4
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
This behavior is caused by an AssetImporter refactor done in 2019.2. Note that although the property values of the Importer instance changes, the meta file still won't be modified until the user press Apply so the asset won't change on the fly as the user modify the properties. It's just that now, the Instance of the Importer will reflect what's from the UI.