Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
18
Found in
2019.3
2019.3.0f5
2020.1
Issue ID
1212234
Regression
No
[HDRP] [XRSDK] Camera does not respect near/far clipping plane settings
How to reproduce:
1. Open attached project ("Repro-1212234.zip")
2. Open SampleScene scene
3. Enter Play mode
4. Select the Main Camera in Inspector window
5. Set Far Clipping plane value to anything bigger than 1170
6. Set Near Clipping plane to any value
Expected result: Near/Far Clipping plane settings are respected
Actual result: Near/Far Clippings plane settings aren't respected
Reproducible with: 2019.3.0f6 [HDRP 7.1.6] [XR Management 3.0.5], 2020.1.0a22 [HDRP 7.1.8] [XR Management preview.2 3.1.0]
Not tested with: 2019.2.21f1 and previous versions (XR SDK crashes HDRP, errors in code)
-
hgouveia
Jan 10, 2021 19:36
Fixed by itself , all packages are the same without modification in unity, so i guess was a WMR drivers update
-
hgouveia
Dec 20, 2020 15:30
Note from previous comment since it canĀ“t be edited tested on 2020.2.0f1, Windows XR Plugin 4.2.1, XR Interaction Toolkit 0.10.0-preview7
-
hgouveia
Dec 20, 2020 15:27
I still has this issue, with HP Reverb G2 and using the Windows Mixed Reality (WMR) loader, my hands constantly disappea when they are near, i've changed the Near of the camera to the minimum 0.01 but is not working, i need to put my arm all streach in order to show, but if i use OpenVR loader, this works perfectly, but i would like to use the native WMR
-
bmbmjmdm
Nov 08, 2020 21:20
We need a fix for 2019. Upgrading to 2020, especially with XR being completely redone, is unrealistic, and this is a critical bug
-
coolnehuel
May 05, 2020 16:09
YAY! I am working on a game for the VR game jam 2020. I had this issue and spent ~5 hours on it. Setting the camera to main camera worked for me! Thanks alot @Foonix!
-
renekuhn
Mar 31, 2020 10:50
Tested it in 2019.3.7f1 and 2020.1.0b3
Still the same behaviourDoes it work for anyone ?
-
icarus1564
Mar 11, 2020 17:04
I'm getting this issue even with a single camera tagged as MainCamera. I ported a non-HD VR app where the clipping worked as expected using the old-school Oculus two-camera setup. It seems that all other aspects of the camera work (at least for my use case) except the clipping planes.
-
abenyamina
Mar 09, 2020 16:19
@Foonix The issue is there even with the camera tagged as MainCamera on our project
-
foonix
Mar 09, 2020 12:56
It turns out that this was issue triggered for me by not having the VR camera tagged as MainCamera. If you have this problem, check that the camera (and only the VR camera) is tagged as MainCamera.
I'd still say this is a bug however. HDRP is calling XRDisplaySubsystem.GetCullingParameters() with the camera to use as a parameter. XRSDK should probably not be using something like Camera.main for this kind of call chain.
-
TandT
Mar 06, 2020 09:32
I can confirm this issue, seems like a very extreme bug.
I can't even imagine why it has so few votes. Is no one using HDRP and XR ?
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2020.2):
Fix for this issue is incoming