Search Issue Tracker
Fixed in 6000.0.36f1
Fixed in 6000.0.X, 6000.1.X, 6000.1.0b3
Votes
1
Found in
6000.0.27f1
6000.1.0a4
Issue ID
UUM-87614
Regression
Yes
SpeedTree does not move when using WindZone
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Enter the Play Mode
4. Observe the Game view
Expected result: SpeedTree moves
Actual result: SpeedTree does not move
Reproducible with: 2023.3.0b8, 6000.0.27f1, 6000.1.0a4
Not reproducible with: 2021.3.46f1, 2022.3.52f1, 2023.3.0b7
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Comments (1)
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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
JoMoschos
Feb 18, 2026 17:55
Hello,
This issue is marked as fixed in 6000.0.36f1 and related 6000.0/6000.1 streams.
However, I can confirm that the problem is still reproducible in Unity 6000.3.xx LTS.
When using Vulkan or OpenGLES3 as the active Graphics API, SpeedTree trees do not respond to WindZone and remain static. Wind animation only works when using DX-based backends.
Since 6000.3 is a later LTS branch, could you please clarify:
• Was this fix merged into the 6000.3 branch?
• If so, is this a regression?
Thank you for the clarification.