Search Issue Tracker
Won't Fix
Won't Fix in 6000.2.X
Votes
0
Found in
2022.3.50f1
6000.0.23f1
6000.2.0a1
Issue ID
UUM-84204
Regression
No
Particle System flickers in the Player
Steps to reproduce:
1. Open “Repro” project
2. Build And Run
3. Press “Next” button until “8/19 HybridEntitiesConversion” text is shown in the Player
4. Observe the Particle System
Actual results: Particles are flickering
Expected results: Nothing of note happens
Reproducible with versions: 2022.3.50f1, 6000.0.23f1
Can’t test with versions: 2021.3.44f1 (due to Entities Graphics not being supported in the stream)
Tested on (OS): macOS Sonoma 14.5 (Intel)
Notes:
- Not reproducible in the Editor
- Not reproducible on Windows 11 Pro
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
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
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. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
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.
Resolution Note (6000.2.X):
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. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
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.