Search Issue Tracker
By Design
Votes
1
Found in
5.1.1f1
Issue ID
714727
Regression
No
Windzone's turbulence and pulse parameters have no effect on wind animation
Steps to repro:
1. Open attached project and 't1' scene;
2. Enter Play mode;
3. Select WindZone gameobject in the Hierarchy;
4. Input some numbers into either Turbulense, Pulse Magnitude or Pulse Frequency field.
Expected result:
Tree's wind animation behavior alters with respect to corresponding field change.
Actual result:
Tree's wind animation behavior doesn't change with respect to corresponding field change. See attached video.
The issue has a big negative effect on users, since it greatly limits wind animation's customization to only toggling 'Main' field.
Notes:
- Reproducible on 2017.3.0a4, 2017.2.0b6, 2017.1.0p3;
- Reproducible on both Windows 10 and OSX 10.12.5.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UnityLinker causes crash when outputting snapshot data for very large projects
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
Add comment