Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.42f1
2021.3.14f1
2022.1.23f1
2022.2.0f1
2023.1.0a20
2023.2.0a1
2023.3.0a3
Issue ID
UUM-20051
Regression
No
Texture2D.GenerateAtlas returns true with a list of returned rectangles with a size of 0 when it should return false or return true and downscale the sizes provided in the parameters to fit the atlas size
Reproduction steps:
# Open the attached project “GenerateAtlas-unity.zip”
# Open the “/Assets/Scenes/SampleScene.unity” Scene
# Enter the Play Mode
# Observe the Console window
Expected result: Texture2D.GenerateAtlas returns false, thus no outputs with “[GenerateAtlas]” are present or the sizes of the rectangles are not equal to 0, but downscaled to fit the atlas size
Actual result: Texture2D.GenerateAtlas returns true, but all of the Rects in the result List<Rect> are returned with a size of 0
Reproducible with: 2020.3.42f1, 2021.3.14f1, 2022.1.23f1, 2022.2.0f1, 2023.1.0a20
Reproducible on: Windows 10 (21H2)
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
- [URP][Lighting] The skybox doesn't render after changing the settings of the Material when using the URP Render Pipeline
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.