Search Issue Tracker
Duplicate
Votes
0
Found in
2019.2.0b6
2019.2.0f1
2019.3.0a1
Issue ID
1174326
Regression
Yes
"Unapplied Import Settings" warning is Always thrown when Certain import Settings are Changed and Applied
How to reproduce:
1. Open the attached project named Case_1174326
2. Select one of the Sprites in the Project window
3. Change the compression setting
4. Click Apply in the Inspector window
5. Select the Scenes folder in the Project window
Expected result: The changes to the Sprite are saved and the folder is selected
Actual result: Unapplied Import Settings warning is displayed
Reproducible with: 2019.2.0b6, 2019.2.0f1, 2019.3.0a11
Not reproducible with: 2017.4.31f1, 2018.4.6f1, 2019.1.14f1, 2019.2.0b5
Notes:
1. Affected settings: Max Size, Resize Algorithm, Format, Compression, Use Crunch Compression
2. Trying to revert the changes when the warning pops up has no effect
Comments (1)
-
NKCy
Jan 07, 2020 03:54
Hi,
I have the "Unapplied import settings" warning keeps popping up issue as well.
In my case, it happens when I use AssetPostprocessor to set a float value which is very small.
Unity seem not able to apply the change, thus keeps popping up the popup.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
This is a duplicate of issue #1167983