Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0b1
Issue ID
960246
Regression
Yes
Particles emission values are set to zero after upgrading project to 2017.2.0b1
To reproduce:
1. Open the QA's supplied project "particlesBeforeUpgrade" with any version after 2017.2.0b1, including that one
2. Open scene "particles"
3. Observe that particle prefabs have emission set to 0
Expected result: Particle emission stays unchanged after project upgrade
Actual result: Particle emission is zeroed after the upgrade
Reproducible with: 2017.2.0b1, 2017.2.0f3, 2017.3.0b5, 2018.1.0a1
Not reproducible with: 5.6.4f1, 2017.1.2p1, 2017.2.0a4
Regression since: 2017.2.0b1
Note: When opening the upgraded project with older versions than 2017.2.0b1, the emission values are back to previous ones
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Adaptive Probe Volume “No Adaptive Probe Volume in Scene” warning is shown only on the first time and is never shown again when baking the Adaptive Probe Volumes with all the Adaptive Probe Volume components disabled
- “NullReferenceException” thrown in Console when changing Profile field to ‘DefaultLookDevProfile’ in Lighting window after deleting Directional Light
- "GardenDraft_LightingSettings" Asset is included in the URP Sample Template
- “Releasing render texture that is set as Camera.targetTexture!” Error thrown in the Console when undoing/redoing Camera addition in Graphics Compositor window > Render Schedule list
- The cursor moves into wrong place when renaming folder/asset
Add comment