Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.2.X, 2017.3.X
Votes
0
Found in
5.3.7f1
Issue ID
956329
Regression
Yes
[Emission] Min/max bursts don't upgrade properly to random between two constants
Repro steps:
1. Open Scene1 from the attached project in 2017.2 or later.
2. Observe the burst emission settings (comparison image attached below).
Expected result: the min/max values to upgrade to the random between two constants.
Actual result: in 2017.2 the original 10, 17 values upgrade to 0,0, in 2017.3 they appear as 0, 238.
Notes:
- Regression when upgrading from 2017.1 to 2017.2
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment