Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.50f1
2022.3.60f1
6000.0.44f1
6000.1.0b12
6000.2.0a7
Issue ID
UUM-101106
Regression
No
Left side cog menu button is obstructed by the maximum Y value of the graph when editing a curve in the Particle System Curves
Steps to reproduce:
- Create a new Unity project
- Create a new Particle System (GameObject > Effects > Particle System)
- Select the newly created Particle System in the Hierarchy window
- Change the "Start Lifetime" property to a curve in the Inspector window
- Click on the "Start Lifetime" property curve to edit the curve
- Observe the Particle System Curves
Actual results: Half of the left side cog menu button is obstructed by the maximum Y value of the graph
Expected results: Left side cog menu button is fully visible
Reproducible with versions: 2021.3.50f1, 2022.3.60f1, 6000.0.44f1, 6000.1.0b12, 6000.2.0a7
Tested on (OS): macOS Silicon Sequoia 15.3
Notes:
- This also makes it difficult to change the maximum Y value of the graph because clicking on it opens up the cog menu
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
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
- EnterPlayModeOptions doesn't take effect if user manually modifies m_EnterPlayModeOptionsEnabled to 0
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. Currently, we're focusing our resources on fixing more critical issues that affect a larger portion of our user base.
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.