Search Issue Tracker
Fixed
Fixed in 6000.3.7f1, 6000.4.0b7, 6000.5.0a6
Votes
4
Found in
6000.0.65f1
6000.3.0a2
6000.4.0a1
6000.5.0a6
Issue ID
UUM-121090
Regression
Yes
[HDRP] Water surface water height sampling returns false height when distant wind speed is high
Steps to reproduce:
- Open any HDRP project
- Download the water sample from HDRP package manager sample tab
- Open island scene
- Enable Water in Project Settings > HDRP > Rendering > Water
- Observe the seagulls, and make sure that they follow the water surface
- Now select the ocean and increase distant wind speed
Actual results: The seagulls stops following the ocean water surface
Expected results: Seagulls should still float properly
!image-2025-10-04-17-34-23-256.png!
Reproducible with versions: 6000.0.10f1, 6000.4.0a1
Not reproducible with versions: 6000.0.9f1
Notes:
- Cf forum post : [https://discussions.unity.com/t/water-level-in-water-system/1688088/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
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- Module installation fails with "Download failed: Validation Failed" errors when using beta.2 Hub version
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
- Shader Graph Category dropdown cannot be expanded/collapsed when clicking on the text
- Different text alignment in the column header in Entities "System" window
Resolution Note:
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.5.0a6):
Fixed in 6000.5.0a6
Resolution Note (fix version 6000.4.0b7):
Fixed in 6000.4.0b7
Resolution Note (fix version 6000.3.7f1):
Fixed in 6000.3.7f1
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.