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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment