Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
1
Found in
2017.4
2018.4
2018.4.5f1
2019.2
2019.3
2020.1
Issue ID
1197056
Regression
No
Imported Object's Settings properties are not saved in the Inspector Debug Mode
How to reproduce:
1. Open the attached '1197056-imported-object-settings.zip' project
2. Select the 'Mario' image in Project Browser
3. Change Imported Object -> Texture Settings -> Mip Bias to 5 in the Inspector Debug Mode
4. Click 'Assets' folder in Project Browser
Expected result: Apply Settings window pops up when Imported Object Settings properties are changed
Actual result: Imported Object's Settings changed properties are not saved
Reproducible with: 2017.4.34f1, 2018.4.13f1, 2019.2.12f1, 2019.3.0b10, 2020.1.0a13
Notes:
- TextureImporterInspector.OnInspectorGUI must call ApplyRevertGUI to avoid unexpected behavior error is thrown
- Not reproducible with other Import Settings properties
- Functionality is also affected, settings are not applied to the texture
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
- [macOS] There is no way to tell if you are running under Rosetta
- [AssetImport] Changing Graphics APIs in Android platform reimports most of the assets (textures, fonts, ...)
- Stack frames are missing from Console window when in Full Stack trace mode
- An error is returned and no package is listed if an invalid package is hosted on a scoped registry
- Crash with ComputeTileMeshJob when generating Navmesh
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a3
Resolution Note (fix version 2019.4):
Fixed in 2019.4.4f1