Search Issue Tracker
Won't Fix
Votes
5
Found in
5.6.1p1
Issue ID
922123
Regression
No
Terrain grass is not affected by the Wind Zone
To reproduce:
1. Download Unity project "GrassWindIssues.zip" from the link provided by the user
2. Open "Main" scene
3. Go into Play Mode
4. Observe the grass
Expected result: Grass, just like trees, should be affected by the Wind Zone
Actual result: Grass moves in one direction and is not affected by the Wind Zone at all
Reproduced on: 5.5.4p1, 5.6.2f1, 2017.1.0b10, 2017.2.0a4
-
shubhamswaraj2021
Aug 19, 2020 13:31
good one <a href="https://www.lyricsauto.com">lyricsauto</a>
-
DiGiaCom-Tech
Jan 13, 2019 21:16
Thank you for this information ... is there some place where I can track the development of the "GPU rendering details system" and, more specifically, the implementation these wind/detail overrides?
-
DiGiaCom-Tech
Nov 22, 2018 18:24
As for the resolution proposed ... how long do you think it's going to be before we see this in an update? Your best rough guesstimate will suffice ... this has been an issue for a long time now.
-
DiGiaCom-Tech
Jul 12, 2017 00:30
The bending of the grass over a large terrain area produces a wave pattern that moves across the grass in a single direction only. There is currently no way to get the wave to move in a specific direction (i.e. with the wind) and/or link it directly to a WindZone. One could argue that each grass prototype should have it's own rotation setting, just like trees do, giving the developer infinite control over each prototype vs. simply linking a single WindZone to the terrain that controls every grass therein.
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
- [Particle System] Editor freezes when assigning a nested Particle System in the Sub Emitter Module
- Unable to switch to different material when selecting another material from Asset selector window on Particle System Material
- [UI] Float type parameter in the Animator Controller displays 0.0 after being changed to a value <0.05
- Inspector displaying wrong characters when using ANSI encoding and non latin characters in a Shader property
- Error in console when using the progress bar API along with Texture compression
Resolution Note:
We are focusing our efforts on the instanced GPU rendering details system; I will add local wind overrides to the requirements there.