Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.6.0p4
Issue ID
914333
Regression
Yes
Particle bounds are not being calculated correctly when "Force over Lifetime" is "Random Between Two Constants"
To reproduce:
1. Create new project.
2. Create Particle System.
3. Enable "Force over Lifetime" module.
4. Set "Force over Lifetime" to "Random Between Two Constants", where first constant is (0,0,-3) and another (0,0,-5).
5. Check "Bounds" to make particle bounds visible.
6. Open Scene window, with Particle System selected so it's Simulating.
Expected result: Bounds are drawn around particles.
Actual result: Bounds are in the wrong position.
Reproducible:5.6.1p1, 2017.1.0b8, 2017.2.0a1
Not reproducible: 5.6.0p3 (all particles are inside bounds (good), but bounds are too big).
Workaround:
Enable one of these modules: Limit Velocity over Lifetime, Rotation by Speed, External Forces, Noise, Collision, Triggers, Sub Emitters, Trails
Comments (2)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
bfoddy
Jul 25, 2018 22:52
STill the case in 2018.1.1f
Ryan-Gatts
Jul 25, 2018 17:53
I can confirm this is still the case in 2018.1.61f.