Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.29f1
2022.3.8f1
2023.1.10f1
2023.2.0b6
Issue ID
UUM-47652
Regression
No
Modifying the Particle System component makes the Editor freeze temporarily when another Particle System is attached as a Sub Emitter
Reproduction steps:
1. Open the attached project “EmitterLagSpike”
2. Open Scene “Assets/Scenes/SampleScene.unity”
3. Select the “Particle System” GameObject
4. Make sure that the Particle System is playing or paused
5. In the Inspector enable the “Velocity over Lifetime” module
6. Observe the Editor
Expected result: The module is enabled without interruption
Actual result: The Editor freezes for some time
Reproducible with: 2021.3.29f1, 2022.3.8f1, 2023.1.10f1, 2023.2.0b6
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- In step 5 any kind of modification can be made to the Particle System component to make the Editor freeze
- The longer the Playback Time is, the longer the freeze lasts
- If the Sub Emitter module is disabled, the Editor will no longer freeze after any modifications
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
- Errors "InvalidOperationException: Trying to use a texture (_InternalGradingLut)..." and “Render Graph Execution error” shown and Scene turns black when 16 or more Render Objects are used
- GameObjects in the Game View are rendered differently than in the Scene View when the Rendering Path is set to "Deferred" and Screen Space Shadows Renderer Feature is added
- Errors “InvalidOperationException: Trying to use a texture (_CameraDepthTexture)...” and “Render Graph Execution error” shown when selecting GameObjects with Mesh Renderer from the Hierarchy
- macOS stutters in a minimal project
- [Usability] HDRP Wizard calls for VR fixes when opening the HDRP Wizard a second time after they have already been applied and the Wizard has finished checking
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug. Currently, we're focusing our resources on fixing more critical issues that affect a larger portion of our user base.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.