Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.4.X, 2019.1.X, 2019.2.X
Votes
4
Found in
2017.3.0a1
2017.3.0f3
Issue ID
986355
Regression
Yes
Camera.Render() is incorrectly rendering to a RenderTexture when VR is enabled
To reproduce:
1. Open attached project ("Bug Report");
2. Open "scene" scene;
3. Make sure VR is enabled (Edit > Project Settings > Player > XR Settings);
4. Enter Play mode;
5. Exit Play mode;
6. Disable VR;
7. Enter Play mode - notice that the view is different.
Expected result: the view is rendered correctly with Camera.Render() when VR is enabled and Allow HDR disabled.
Actual result: Camera.Render() incorrectly renders to the Render Texture when VR is enabled.
Workaround: check "Allow HDR" on Plane's child object camera.
Tested and reproduced on Oculus Rift DK2.
Reproduced on versions: 2017.3.0a1, 2017.3.0p2, 2018.1.0b2.
Not reproduced on version: 2017.2.1p1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Source Image property gets set to 'None' when using a specific Sprite and Play mode is entered
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
Add comment