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
- Points Lights are getting culled prematurely when using Forward+ and Deferred+ rendering paths
- Search's Indexing settings in the Preferences window are not searchable
- Crash on block_locate_free when opening a specific project
- "Project connected" pop opens again after closing it
- Cloud Code Authoring logs "JsAssetHandler:OpenAsset (int,int) does not match any of [OnOpenAssetAttribute] expected signatures" when opening or switching scenes and having the Deployment Package Installed
Add comment