Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.2.X, 2017.3.X
Votes
8
Found in
2017.2.0b11
Issue ID
953360
Regression
Yes
GrabPass grabs only one eye with Single Pass Rendering Method
To reproduce:
1. Open the attached project;
2. Open "test" scene;
3. Make sure Stereo Rendering Method is set to Single Pass (Edit > Project Settings > Player > XR Settings);
4. Enter Play Mode.
Expected result: GrabPass grabs both eyes when Stereo Rendering Method is set to Single Pass.
Actual result: GrabPass renders only one eye with Single Pass Rendering Method
Reproduced on versions: 2017.2.0b4, 2017.2.0f2, 2017.3.0b2.
Not reproduced on versions: 2017.1.1p4, 2017.2.0b3.
Regression introduced on: 2017.2.0b4.
Tested and reproduced with HTC Vive.
Comments (8)
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
- Volumetric Clouds close to the horizon flicker when "Ghosting Reduction" is enabled
- Temporary dark areas appear when quickly dragging Editor window splitters while using "Direct3D 12" graphics API and "Light" Editor theme
- Focus changes from the IDE to the Unity Editor when compiling code in the IDE
- A glare from the Light Placement Tool is visible when the Main Camera is set to "Perspective"
- List item is re-selected when moving the mouse after ClearSelection function
jeromeWork
Sep 13, 2019 12:47
Still a problem. Left eye grey using PostProcessing on 2018.4.1f1 building for Quest
Mandelboxed
Jun 19, 2019 22:13
This is still broken on Oculus Go, Unity 2019.1.5f1.
swanickj
May 30, 2019 18:10
I am still having this issue in 2018.3.10f1 on the Oculus Quest/ Android
Adam-Sowinski
Jan 10, 2018 15:30
What Unity version has this been fixed?
SuppleTeets
Oct 24, 2017 01:43
Sweet, thanks!
r3dthrawn
Oct 24, 2017 00:29
We have a fix on the way to trunk
SuppleTeets
Oct 23, 2017 23:18
We need to upgrade from 2017.1.2f1 for Native XR haptics support and this bug is preventing us from upgrading... sad face.
Tenebris_Lab
Oct 19, 2017 18:14
Same issue, was working great in 2017.1.1p4.