Search Issue Tracker
Feature Request
Votes
0
Found in
2021.3.28f1
2022.3.5f1
2023.1.3f1
2023.2.0a23
Issue ID
UUM-42530
Regression
No
The Sprite renders in incorrect size when it overlaps with the other Sprite and GPU Instancing is enabled on their shared Material
How to reproduce:
1. Open the user-attached project “SpriteRendererTest”
2. Open the “SampleScene” scene
3. Rotate or move the Camera in the Scene View
4. Observe the Sprites
Expected result: The Sprites are the same size at all angles
Actual result: The Sprites are rendered bigger at the certain angles
Reproducible with: 2021.3.28f1, 2022.3.5f1, 2023.1.3f1, 2023.2.0a23
Reproducible on: Windows 11 Pro
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
As resolved previously, GPU Instancing for Sliced Sprites is not supported. We will add this internally as a feature request, and may add support for it in the future. As a workaround, you can create different materials for different configurations of Sliced Sprites. Sliced Sprites with the same width and height should share the same material and will instance correctly.