Search Issue Tracker
Fixed
Fixed in 6000.0.59f1, 6000.2.6f1, 6000.3.0a4
Votes
0
Found in
2022.3.60f1
6000.0.45f1
6000.1.0b13
6000.2.0a8
6000.3.0a1
Issue ID
UUM-102085
Regression
No
Particle System isn't playing in Play Mode when it's out of view in Scene view, Simulation Space is set to "World", and Culling mode is set to "Pause and Catch-up"
How to reproduce:
1. Open the attached “IN-98057_ParticleSystem Bug“ project
2. Open the “SampleScene“
3. Enter Play mode
4. In the Hierarchy window, select the “Particle System“ GameObject
5. In the Scene view, using the left mouse button, change the view so the “Particle System” GameObject is not visible
6. Under the Transform component, change the Position X value to “10“
7. Under the Transform component, change the Position X value back to “0“ (multiple value and Scene view visibility changes may be needed to reproduce the issue)
8. Observe the results in the Game view
Expected result: The Particle System effect is playing when the Position X value is set to “0“ (In the Camera’s field of view)
Actual result: The Particle System effect isn't playing when the Position X value is set to “0“ (In the Camera’s field of view)
Reproducible with: 2022.1.0a10, 2022.3.60f1, 6000.0.45f1, 6000.1.0b13, 6000.2.0a8
Reproducible on: MacOS 15.3 (M4)
Not reproducible on: No other environments tested
Note: This issue only occurs when the Particle System's “Simulation Space” is set to “World” and “Culling Mode” is set to “Pause and Catch-up“ (these settings can be found in the Inspector window, under the Particle System component)
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
Add comment