Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.64f1
6000.0.53f1
6000.1.11f1
6000.2.0b9
6000.3.0a1
6000.4.0a1
Issue ID
UUM-111545
Regression
No
UI Elements/Layout inconsistencies in the Particle System component
Steps to reproduce:
- Create a new Unity project using the Universal 3D template
- Create a new Particle System GameObject (GameObject > Effects > Particle System)
- Select the new Particle System GameObject in the Hierarchy window
- Scroll down and expand "Renderer" in the Inspector window
- Observe the "Sorting Layer ID" and "Order in Layer" property labels
- Observe the "Sorting Layer ID" dropdown
Actual results: "Sorting Layer ID" and "Order in Layer" property labels are too close together comparing with other labels, and the "Sorting Layer ID" dropdown is pushed some pixels to the right/misaligned compared to other fields
Expected results: "Sorting Layer ID" and "Order in Layer" property labels have a gap between them that is the same with the other property labels, and the "Sorting Layer ID" dropdown/field is aligned with other dropdowns/fields
Reproducible with versions: 2021.3.51f1, 2022.3.64f1, 6000.0.53f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a1
Tested on (OS): Windows 11, macOS Silicon Sequoia 15.5
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
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.