Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0f3
Issue ID
1111738
Regression
No
Particle System startSizeMultiplier and startSize overrides each other when changing parameters via script
To reproduce:
1. Open user's attached project
2. Enter Play mode
3. Observe Console window and Inspector window
Expected: startSizeMultiplier and startSize have different values assigned
Actual: startSizeMultiplier and startSize have same value assigned, depending which one was assigned last to any of them
Reproduced in: 2017.4.18f1, 2018.2.20f1, 2018.3.1f1, 2019.1.0a13
Note: reproduces on both Windows and Mac
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
- Duplicate External Textures start appearing when a Texture created with "CreateExternalTexture" is modified causing Memory Usage spikes on VisionOS
- Silent crash when using a "Blend Shape" in a "Skinned Mesh Renderer" to move vertices to Vector3.positiveInfinity, and "Occlusion Culling" is baked
- Some Prefab Source and Override content bounds are misaligned
- The Package Manager's "install packages by..." panels break when Domain Reload is triggered, and the panel is open
- Crash with multiple stack traces when leaving a docked VFX Graph open
Resolution Note:
They are 2 properties for controlling the same thing.
startSize gives access to the whole MinMaxCurve.
startSizeMultiplier only modifies the multiplier within the MinMaxCurve.