Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.1.0a8
2019.2
2019.2.17f1
2019.3
2020.1
Issue ID
1207764
Regression
Yes
ParticleSystem.LimitVelocityOverLifetimeModule.limit value is not the same as the Speed value, when not using one curve per axis
How to reproduce:
1. Open the project "case_1207764-particleSystem"
2. Open the scene "SampleScene"
3. Select the GameObject "Particle System" in the Hierarchy window
4. Select Limit Velocity over Lifetime Module in the Particle System component in the Inspector window
5. Press the Play button
6. Observe what is the value of the Speed in the "Limit Velocity over Lifetime" Module in the Particle System component in the Inspector window
Expected results: the Speed value is set to the value of ParticleSystem.LimitVelocityOverLifetimeModule.limit
Actual results: the Speed value does not change
Reproducible with: 2019.1.0a8, 2019.1.14f1, 2019.2.17f1, 2019.3.0f4, 2020.1.0a18
Not reproducible with: 2017.4.35f1, 2018.4.14f1, 2019.1.0a7
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a24
Resolution Note (fix version 2019.3):
Fixed in 2019.3.7f1