Search Issue Tracker
By Design
Votes
0
Found in
2022.3.52f1
6000.0.28f1
6000.1.0a5
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-87937
Regression
No
Water Surface renders rectangular shape when the Camera is relatively close to the surface
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “OutdoorScene” Scene
3. Observe the Game View
Expected result: Consistent water color is seen
Actual result: Rectangular shape is seen
Reproducible with: 2022.3.52f1, 6000.0.28f1, 6000.1.0a5
Couldn’t test with: 2021.3.45f1 - No support for Water System
Reproducible on: Windows 10, Windows 11 (user), Ubuntu 24.04 (Vulkan)
Not reproducible on: MacOS (M1, Metal)
Note:
- For the Unity 6 versions the rectangular shape does not appear, but a black color is seen
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
Resolution Note:
Two separate issues:
In Unity 6, the issue can be mitigated by increasing the camera’s near plane, which is currently intersecting with water ripples. This is an unfortunate side effect of the water line performance optimizations we've implemented before.
In Unity 2022.3, the visible square is expected due to Underwater Screen Space Refraction being always enabled. Rays near the screen edges fallback to the water color. In Unity 6, we introduced a dedicated toggle in the Underwater section to disable this behavior (and it is off by default).
Many thanks for reporting this! Closing as both behaviors are expected.