Search Issue Tracker
By Design
Votes
0
Found in
2021.3.48f1
2022.3.58f1
6000.0.38f1
6000.1.0b6
6000.2.0a3
Issue ID
UUM-97358
Regression
No
Trees painted on a Terrain are not affected by any Wind Zone when those trees are part of an LOD Group
Reproduction steps:
1. Open the attached “IN-93597 LOD Tree Terrain Wind Bug (2).zip“ project (link in the internal comments)
2. Open the “SampleScene”
3. Enter Play mode
4. Observe the tree movement in the Game view
Expected result: All 4 trees are moving
Actual result: 3 left-most trees are moving but the right-most tree is not
Reproducible with: 2021.3.48f1, 2022.3.58f1, 6000.0.38f1, 6000.1.0b6, 6000.2.0a3
Reproduced on: Windows 11 Pro (23H2), MacOS (M1)
Not reproduced on: No other environment tested
Notes:
- Any tree, that is painted directly on the Terrain with the Paint Trees tool and has the LOD Group Component on its parent GameObject, is not affected by the wind
- No matter if the Wind Zone is attached to the Terrain or placed in the scene as a separate GameObject, the actual result is the same (see the attached reproduction video in the internal comments)
- Reproducible in a new project
- Reproducible in the Player
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
- Different text alignment in the column header in Entities "System" window
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
Resolution Note:
Wind on terrain scattered Tree Creator trees with LODs has never been supported, so I am closing this bug. However, as it does seem like this is something we should support, I have added it to the list of potential improvements for us to work on.