Search Issue Tracker
By Design
Votes
0
Found in
2019.1.0a4
2019.2.0a1
2019.2.17f1
2019.3.0a1
2020.1.0a1
Issue ID
1206714
Regression
Yes
[VR] Shader is broken after entering Play mode
How to reproduce:
1. Open attached project ("outline_shader_bug_repro.zip")
2. Open Repro scene
3. Enter Play mode in VR
4. Open Game window
Expected result: Shader is displayed the same as before entering Play mode in VR
Actual result: Shader is different than it is before entering Play mode in VR
Reproducible with: 2019.1.0a4, 2019.1.14f1, 2019.2.18f1, 2019.3.0f4, 2020.1.0a18
Not reproducible with: 2017.4.36f1, 2018.4.15f1, 2019.1.0a3
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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Resolution Note:
When rendering outline like this, make sure to set "Cull Off" in your shader so that your logic will work in all cases (some code path use inverted projection matrix and can affect the backface culling).