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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.