Search Issue Tracker
Won't Fix
Won't Fix in 6000.5.X
Votes
0
Found in
6000.0.19f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-79816
Regression
No
The order of activation for Water Deformers and Foam Generators will cause water artefacts in the Player
How to reproduce:
1. Open the “WaterDeformerIssueRepro“ project
2. Open the “Island“ scene
3. Spam toggle on and off the “Decals/Caustics“ GameObject for a bit (More information about this in the comments)
4. Build the project
5. Open the Build and observe the Player by moving like in the Scene view (with WASD and mouse)
Expected result: No water artefacts
Actual result: Several water artefacts
Reproducible with: 6000.0.19f1
Could not test with: 2021.3.43f1 (Physical water shader not introduced yet), 2022.3.46f1 (Could not fix the “Water“ shader not showing up)
Reproducible on: macOS 14.6.1 (Intel), Windows 10 Pro (22H2), Windows 11 (Reporters)
Not reproducible on: No other environments tested
Notes:
- Not reproducible in the Editor both Edit Mode and Play Mode
- More information in the comments
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
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.
Resolution Note (6000.5.X):
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.