Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.3
2019.3.13f1
2020.1
2020.2
Issue ID
1248028
Regression
No
ParticleSystem prefab is marked dirty when setting ParticleSystem.useAutoRandomSeed to the same value
How to reproduce:
1. Open the attached 'project-1248028.zip' project and load 'SampleScene'
2. Enter Play mode
3. In the Project window select 'ParticleSystemPrefab'
4. Observe the Console window
Expected result: last logged message is 'IsDirty::::False'
Actual result: last logged message is 'IsDirty::::True'
Reproducible with: 2019.3.14f1, 2020.1.0b9, 2020.2.0a12
Could not test with: 2018.4.22f1 (EditorUtility.IsDirty() method not available)
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
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
- Articulation Bodies spawn at the same point on a Spline when entering the Play mode
- [HDRP] Mip Map Debugging View turns White if there are Directional Lights in the Scene
- RenderDoc Capture Frame can't be completed after Particle System is simulated
Resolution Note:
Most of the time we dont check if values are the same before setting things dirty in Unity. Nearly all the properties in the Particle System are set dirty even if the value is the same. If we were to fix this then we would need to fix all the properties to be consistent which adds unnecessary complexity and overhead. It is also possible to just perform the check in a script before setting the value.