Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2021.1
2021.2
2021.2.0f1
2022.1
Issue ID
1377646
Regression
No
ParticleSystem.main.startSizeMultiplier doesn't scale ParticleSystem.main.startSize
How to reproduce:
1. Open project "case_1377646.zip"
2. Enter "SampleScene" Scene
3. Select GameObject "Particle System" from the Hierarchy
4. In the Inspector observe the "Start Size" value under the "Particle System" component
5. Observe the "Size Multiplier" value under the "New Behaviour Script" component
6. Enter Play Mode
7. In the Inspector observe the "Start Size" value under the "Particle System" component
Expected result: The "Start Size" value gets multiplied by the "Start Size" value
Actual result: The "Start Size" value is set to the "Start Size" value
Reproducible with: 2019.4.0f1, 2019.4.32f1, 2020.3.23f1, 2021.1.28f1, 2021.2.2f1, 2022.1.0a15
Note:
-When "Start Size" is set to "Random Between Two Constants" only the second value is affected by the "Start Multiplier"
-When "3D Start Size" is toggled only X value gets affected
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
I agree this isn't very clear (including in the docs) but it's the same value, not a separate one.
The main purpose of it is to let you scale the curve mode without assigning the entire curve.
When you are just using a constant, it's the same value.