Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.51f1
2022.3.62f1
6000.0.49f1
6000.1.3f1
6000.2.0b1
6000.3.0a1
6000.4.0a1
Issue ID
UUM-105168
Regression
No
Particle Effect window buttons overlap with other UI elements when opened in Editor
Steps to reproduce:
- Create a new Unity project using Universal 3D template
- Create a new Particle system (GameObject > Effects > Particle System)
- Select the newly created Particle System in the Hierarchy window
- Click the "Open Editor..." button in the Inspector window
- Resize the window to be smaller or dock the window and resize
- Observe the "Optimize" and "Remove" buttons
Actual results: The "Optimize" and "Remove" buttons overlap with other UI elements
Expected results: No UI elements overlap
Reproducible with versions: 2021.3.51f1, 2022.3.62f1, 6000.0.49f1, 6000.1.3f1, 6000.2.0b1
Tested on (OS): macOS Silicon Sequoia 15.3
Notes:
- This is very noticeable when there are more Particle Systems and the Particle System slider is all the way to the right
- Very noticeable when the window is docked and smaller than the minimum width for undocked window
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
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.
Resolution Note:
Forward-ports for this version need to be handled at a later time.