Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
5.3.0f1
Issue ID
744083
Regression
No
ParticleSystem.EmitParams.ResetAngularVelocity doesn't revert angularVelocity
ParticleSystem.EmitParams.ResetAngularVelocity() doesn't revert EmitParams.angularVelocity and angularVelocity3D settings.
2. How we can reproduce it using the example you attached
a. Open scene 1 and Run it
b. Press 'Emit(params,count)' and 'Emit(count)' btns to confirm that angularVelocity is applied
c. Press 'Reset to original' btn
d. Press again 'Emit(params,count)' and 'Emit(params,count)' btns
Expected: Particles emitted from these 2 calls should look identical.
Actual: Particles from Emit(params,count) still have angularVelocity initial setting applied.
Note: this project demoes only angularVelocity issue. But same principle applied to angularVelocity3D.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment