Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.14f1
2023.2.0f1
2023.3.0a14
Issue ID
UUM-56602
Regression
Yes
The Particle System and Sprite Renderer components render behind the CanvasRenderer even if placed in front of the Canvas Plane Distance (Position Z 100 or less)
Steps to reproduce:
1. Open the attached user's project "CanvasTestUnity2021.zip"
2. Select the ParticleSystem in the Hierarchy to play it in the Scene/Game View
3. Observe the rendering order of the components
4. Move the ParticleSystem in Scene View behind and in front of the CanvasRenderer and observe the changes
Expected Result: The ParticleSystem and SpriteRenderer components render in front of the CanvasRenderer when placed in front of the CanvasRenderer
Actual Result: The ParticleSystem and SpriteRenderer components render behind the CanvasRenderer even if placed in front of the CanvasRenderer
Reproducible with: 2022.2.0a9, 2022.3.14f1, 2023.2.0f1, 2023.3.0a14
Not reproducible on: 2021.3.32f1, 2022.2.0a8
Testing Environment: Windows 10
Not reproducible on: No other environment tested
Notes:
-Workaround: Setting the Canvas Order In Layer to -1 partially resolves the issue. However, the Particle System remains visible even when positioned behind the canvas
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:
After discussion with the client and explanations about how the Z values shouldn't be used like they were in the given project example. A few workarounds exist that support the use case and therefore no action will be taken at this time.