Search Issue Tracker
Won't Fix
Votes
3
Found in
2020.3.38f1
2021.3.9f1
2022.1.15f1
2022.2.0b7
2023.1.0a10
2023.2.0a1
Issue ID
UUM-13299
Regression
No
Particle System is flickering when recovering deleted mesh file
Reproduction steps:
1. Open the user’s attached project
2. Open the “Assets/New Scene.unity“ scene
3. Backup “Assets/plane.fbx” outside the project folder
4. Click “Assets/plane.fbx” and press the “Delete” key
5. Enter and exit Play Mode
6. Copy and paste the “plane.fbx” back to the Assets folder
7. In the Hierarchy window, select Particle System
Expected result: “Particle System” GameObject is the same as before deleting
Actual result: “Particle System” GameObject is flickering
Reproducible with: 2020.3.38f1, 2021.3.9f1, 2022.1.15f1, 2022.2.0b7, 2023.1.0a10
Reproducible on: Windows 10 Pro 21H2
Note: 2020.3.38f1 reproduces inconsistently
Comments (1)
-
putlocker
Aug 31, 2022 19:40
//play.acast.com/s/630fb5bd0873810012bdfb48?
//play.acast.com/s/630fb68d6631380013b0f736?
//play.acast.com/s/630fb6d761dd90001237bca9?
//play.acast.com/s/630fb86b0873810012be0567?
//play.acast.com/s/630fb88c43400800124d47f7?
//play.acast.com/s/630fb901290e6d00127bf0e3?
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 with compiler errors when switching scripts GUIDs
- Many references for Animator elements redirect to missing pages
- User gets "EndLayoutGroup: BeginLayoutGroup must be called first." error during Xcode selection canceling
- "Unable to use a named GUIStyle without a current skin" error appears in the Console when entering the Play Mode in a project with specific layout
- [D3D12][XR] SRP Foveation foveated rendering on Windows platform not working when Graphics API is set to D3D12
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.