Search Issue Tracker
Won't Fix
Votes
1
Found in
6000.2.8f1
6000.3.0b7
6000.4.0a3
6000.5.0a1
Issue ID
UUM-122696
Regression
Yes
Underwater effect height detection is inaccurate when the Distant Wind Speed has a high value in HDRP Water
Reproduction steps:
1. Open the attached “IN-121118.zip” project
2. Open the “Island” scene
3. From the Hierarchy, select the “Ocean” GameObject
4. In the Inspector, make sure “Distant Wind Speed” is set to around 250
5. Place the Scene view camera at the waterline (so that waves cover and uncover the camera)
6. Observe the Scene view
Expected result: Camera correctly reflects underwater effect when it is either under or above the waterline
Actual result: Camera mismatches and may show the underwater effect above water or fail to show it below water
Reproducible with: 6000.2.1f1, 6000.2.8f1, 6000.3.0b7, 6000.4.0a3
Not reproducible with: 6000.0.60f1, 6000.2.0f1 (eed1c594c913)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- The reproduction can be inconsistent and might take a few tries to reproduce
- Also affects the Camera output in the Game view
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
- Radio Button is squished or selection indicator is off center in Play mode when it's scaled down
- Particle System Renderer icon is missing in Animation window > Add Property context menu
- [Android] Legacy, TMP and UI Toolkit Input Field language toggle to some non-latin alphabet languages does not work with external keyboard
- Crash on keywords::LocalKeywordState::operator when calling ShaderUtil.GetPasskeywords with ShaderType.RayTracing set as the third parameter
- Inconsistent “Remove property” behavior when removing child properties in Animator window
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.