Search Issue Tracker
Duplicate
Votes
0
Found in
5.4.0b1
Issue ID
755330
Regression
No
Particles GetCollisionEvents returns larger than actual number of events
1. What happened
ParticlePhysicsExtensions.GetCollisionEvents returns larger than actual number of events. Issue is relevant for Editor only and only if particle burst occurs at the beginning of PS life. And if more than 1 collider exists.
Overall the issue is more complex and not always reproducible with the above conditions. Originally attached project with other recent fixes now works OK.
2. How we can reproduce it using the example you attached
Use project '4b9wq6ut.9qo With Spaces.zip' attached to one of the comments to this case.
- Open scene '000-startup'
- Run
---> Observe console output - (it'll print 'current particles count' every frame to show that actual number of particles is OK) and then will output final 'Test Result' message that prints smth like '...at line 71 expected: 50 was: 208...'
Reproducible also in 5.2.3, 5.3.0.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
This is a duplicate of issue #762690