Search Issue Tracker
Fixed
Fixed in 2022.3.42f1, 6000.0.1f1, 7000.0.0a1
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.36f1
2022.3.22f1
2023.2.16f1
6000.0.0b13
7000.0.0a1
Issue ID
UUM-67831
Regression
No
"Sprites can not be generated from textures with NPOT scaling" warning is displayed when importing a texture via Texture Importer Preset feature
Steps to reproduce:
1. Open the attached user's project "1804792_Preset_2022322f1.zip"
2. Import the attached "NPOT Texture.png" into the project
3. Select the imported texture and observe the warning in the Console Window
Expected results: no warnings are generated when when importing the texture via Texture Importer Preset feature
Actual result: "Sprites can not be generated from textures with NPOT scaling" warning is displayed when importing the texture via Texture Importer Preset feature
Reproducible on: 2021.3.36f1, 2022.3.22f1, 2023.2.16f1, 6000.0.0b13
Testing Environment: Windows 11
Not reproducible on: No other environment tested
Notes:
-Warning message:
Sprites can not be generated from textures with NPOT scaling.
(Filename: C:\build\output\unity\unity\Editor\Src\AssetPipeline\TextureImporting\TextureImporter.cpp Line: 643)
-If Non-Power of 2 property is not excluded, the warning will not be displayed and the Sprite will be properly generated
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
- Inconsistent behaviour when interacting with different dropdown types with pointer events on parent Visual Element
- Hidden GameObjects won't re-enable when they have call "DontDestroyOnLoad" function
- Overlay Canvas are rendered on each split-screen camera when HDR is enabled
- [Android] The Player loses focus when using UnityEngine.Handheld.StartActivityIndicator() with Facebook SDK
- Build fails with "Building Library/Bee/artifacts/MacStandalonePlayerBuildProgram/gahcy/hj9mx3z/951.0 failed with output:..." errors when Scripting Backend is set to IL2CPP
Resolution Note (2021.3.X):
Fixing this bug properly requires us, on upgrade, to force a full re-import of all textures, regardless of whether the project is affected by this issue or not.
In the case of the 2021 LTS, we believe that a backport is thus likely to create more pain than it would remove: as such, we are opting to close this port as "Won't Fix".