Search Issue Tracker
Fixed
Fixed in 6000.0.38f1, 6000.1.0b6, 6000.2.0a2
Votes
1
Found in
6000.0.33f1
6000.1.0b1
6000.2.0a1
Issue ID
UUM-91921
Regression
Yes
Particle System only collides with one Terrain Collider at a time when Collision Type is set to 'World'
Reproduction steps:
1. Open the attached “TerrainCollider.zip” project
2. Open the “SampleScene”
3. Select the “Particle System” GameObject from the Hierarchy
4. Observe the Particle movement against both Terrain GameObjects
Expected result: Particles bounce off/collide with both Terrains
Actual result: Particles collide with only one of the Terrain and fully go through the other Terrain
Reproducible with: 2023.3.0b2, 6000.0.33f1, 6000.1.0b1
Not reproducible with: 2021.3.47f1, 2022.3.55f1, 2023.3.0b1
Reproducible on: Windows 10, Windows 11
Not reproducible on: No other environment tested
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Resolution Note:
Forward-ports for this version need to be handled at a later time.