Search Issue Tracker
Fixed
Fixed in 6000.0.42f1, 6000.1.0b10, 6000.2.0a7, 7000.0.0a23
Votes
0
Found in
6000.0.39f1
6000.1.0b7
6000.2.0a4
Issue ID
UUM-97977
Regression
Yes
ParticleCollisionEvent.intersection generates extremely high values when particles collide while in Play Mode
Reproduction steps:
1. Open the attached “repro_IN-90208“ project
2. Open the “Assets/Scenes/TestScene.unity“ Scene
3. Enter the Play Mode
4. Observe the Console
Expected result: No errors are thrown
Actual result: Debugging errors are thrown, notifying that ParticleCollisionEvent.intersection is generating high values
Reproducible with: 6000.0.39f1, 6000.1.0b7, 6000.2.0a4
Not reproducible with: 2022.3.58f1
Reproducible on: Windows 10 (22H2)
Not reproducible on: No other environments tested
Note:
- Repro is inconsistent - please try entering the Play Mode repeatedly, reopening the project, downgrading and upgrading the Editor version, regenerating the Library folder and/or restarting the computer if you’re not able to reproduce the errors on the first attempt
- Will not look for the FAV as the reproduction is inconsistent
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment