Search Issue Tracker
Fixed
Fixed in 6000.0.66f1, 6000.3.5f1, 6000.5.0a5
Under Consideration for 6000.4.X
Votes
0
Found in
6000.4.0b2
6000.5.0a5
Issue ID
UUM-130899
Regression
Yes
SpriteAtlas.GetSprite/GetSprites methods return incorrect position when processing the sprites
How to reproduce:
1. Open the attached project "IN-127684"
2. Select the "GetSprites" asset in the Project window
3. Click the "Process" button in the Inspector window
4. Observe the Console log
Actual result: The log shows the texture rect x,y for every sprite as (0.00, 0.00)
Expected result: The log shows the correct texture rect coordinates for each sprite (e.g., x:396.00, y:0.00)
Reproducible with: 6000.0.47f1, 6000.0.65f1, 6000.2.15f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Not reproducible with: 6000.0.46f1 (fb93bc360d3a)
Reproducible on: Windows 11 Enterprise, macOS (reporter)
Not reproducible on: No other environments tested
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
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Scale Snapping with Gizmos does not work in the Scene view when Snapping and Absolute Grid Snapping are toggled off
Resolution Note:
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.5.0a5):
Fixed in 6000.5.0a5
Resolution Note (fix version 6000.3.5f1):
Fixed in 6000.3.5f1
Resolution Note (fix version 6000.0.66f1):
Fixed in 6000.0.66f1