Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.2.0f1
2019.3.0a1
Issue ID
1175229
Regression
No
#if ENABLE_VR is always set to true even if there is no VR support enabled on the project
How to reproduce:
1. Open the "case1175229_ReproProject" Project
2. Observe the console
Expected result: Error message does not get printed in the console
Actual result: ENABLE_VR is set to true and prints an error in the console
Reproducible with 2017.4.31f1, 2018.4.6f1, 2019.1.14f1, 2019.2.1f1, 2019.3.0a12
Comments (3)
-
Tymianek
Feb 25, 2021 17:05
This bug is also present in 2019.4.10f1
-
MartinCoatsink
Jul 30, 2020 11:25
This is a very confusing issue, since the Visual Studio seems to be unaware that the ENABLE_VR flag is set (code relying on it is grayed out).
What am I supposed to do to make my project compile again?
-
AnomalusUndrdog
May 23, 2020 12:43
The mentioned link https://github.com/Unity-Technologies/ScriptableRenderPipeline/pull/4313 is doesn't exist. The ScriptableRenderPipeline repo in https://github.com/Unity-Technologies/ doesn't exist anymore.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
ENABLE_VR is set from the C++ engine per platform and cannot be changed unless you edit and recompile source code.
See https://github.com/Unity-Technologies/ScriptableRenderPipeline/pull/4313 for an alternative solution.