Search Issue Tracker
Won't Fix
Won't Fix in 2021.3.X
Votes
0
Found in
2021.3.30f1
Issue ID
UUM-49346
Regression
No
Particle System External Forces Multiplier cannot be set to a negative value
How to reproduce:
1. Download the attached "Loaded8s-Refactored" project
2. In the Hierarchy window, select "Canvas" > "BlingSplosion_Purple"
3. In the Inspector window, select "External Forces"
4. Try to set a negative Multiplier value
Expected outcome: You are able to set a negative Multiplier value
Actual outcome: You are unable to set a negative multiplier value
Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.13f1, 2023.2.0b10, 2023.3.0a5
Reproduced on: macOS Ventura 13.4
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
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- Long Sprite names are not truncated in the Inspector window name label and the preview labels when a Sprite with a long name is selected
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
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.
Resolution Note (2021.3.X):
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.