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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
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.