Search Issue Tracker
Fixed in 5.2.0
Votes
0
Found in
5.1.0f3
Issue ID
703083
Regression
Yes
[SpriteEditor] Slices clamp to image size when the Max Size of the image is smaller than the actual size
How to reproduce:
1. Open any (new) project
2. Import any image
3. Make sure it is imported as a sprite
4. Set the sprite mode to Multiple
5. Set the image Max Size to be smaller than the actual image size
6. Apply Import Settings
7. Open Sprite Editor
8. Slice the sprite in a grid using a larger number than the Max Size of the image
- Notice the slice size is set to the Max Size of the image
- Actually slicing it does not create one slice of the image, but multiple slices because the slicing pixels appear to be counted as the actual pixels of the image
- Can be worked around by simply having Max Size be larger than the image size
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Add comment