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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment