Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
5.0.0
Issue ID
1098245
Regression
Yes
[XR][GearVR][URP] Sprites with Sprites-Default material are rendered close to camera when using Oculus and URP package
How to reproduce:
1. Open attached "XR-Rat" project
2. Build and run on some Samsung device supporting GearVR (if you get the errors related to package, comment those script lines in PackageCache)
3. Move camera right(sprites will not be visible if using LWRP, if you don't move camera)
Expected result: Sprites should be rendered in scene and they should be far away from camera
Actual result: Sprites are rendered, but they are rendered very near to the camera
Reproducible with - 2019.1.0a10 + LWRP 5.0.0
Not reproducible with - 2018.3.0b10 + LWRP 4.1.0
Notes:
1. Reproducible with Oculus SDK (GearVR), not reproduced when using Cardboard/Daydream SDK's
2. OpenGLES3 tested only, Vulkan is not supported with VR currently
DUT:
VLNQA00121, Samsung Galaxy S9 (SM-G960F), 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00142, Samsung Galaxy S9+ (SM-G965U1), 8.0.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00005, Samsung Galaxy S7 (SM-G930V), 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
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
- Sprite artefacts appear when Sprite Packer is enabled
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
Resolution Note:
Unity's support for GearVR has been deprecated in our 2019.3 release and will be removed in a future release. As such, we're deprioritizing our support of GearVR, 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.