Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
5.3.1
Issue ID
1126850
Regression
No
[XR][Android][URP] Water System is not rendered if VR is enabled
How to reproduce:
1. Open attached project "WaterRepro"
2. Build to Android, notice that VR app opens and water is not rendered
3. Disable VR support in project
4. Build again, notice that water is rendered
Reproducible with - 2019.2.0a5, 2019.1.0b3, 2019.1.0a13
Reproduced with LWRP 5.3.1, 5.2.0 package versions and LWRP Water System 1.2.0
DUT:
Reproducible with:
VLNQA00118, Google Pixel 2 XL (Pixel 2 XL), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540 (reproduced on Daydream, Cardboard)
VLNQA00219, Samsung Galaxy Note9 (SM-N960U), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630 (reproduced on Daydream, Cardboard, GearVR)
VLNQA00136, Samsung Galaxy S9+ (SM-G965F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72 (GearVR only, no repro on Daydream, Cardboard)
VLNQA00134, Samsung Galaxy S8 (SM-G950F), Android 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71 (GearVR only, no repro on Daydream, Cardboard)
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
- [Build Profile] [VisionOS/iOS/tvOS] - Build Player Library button is getting displayed depending on the selected build target
- EnsureRunningOnMainThread error in TessellationJob.ApplyInset
- MultiColumnListView causes a memory leak when repeatedly shown and hidden
- Position Node with Object Space has a wrong value when there are multiple active GameObjects with the same shader
- [URP][RG] Fullscreen blit is not working when Render Graph is enabled
Resolution Note:
Unity's support for Cardboard, Daydream, and GearVR has been deprecated in our 2019.3 release and will be removed in a future release. As such, we're deprioritizing our support for those XR platforms, and won't be actively fixing issues related to the platform.
This issue is being marked as Won't Fix. If that resolution isn't appropriate, please reopen the issue and let us know the issue's impact for you.