Search Issue Tracker
Fixed in 3.2.1
Votes
7
Found in [Package]
3.2.0
Issue ID
1389160
Regression
Yes
Compilation errors are thrown after Post Processing is installed when Built-in VR package is disabled
Reproduction steps:
1. Create a new project
2. Disable VR Built-in package
3. Install Post Processing package
4. Observe the Console output
Expected result: Console doesn't throw any errors
Actual result: Errors are thrown:
Library\PackageCache\com.unity.postprocessing@3.2.0\PostProcessing\Runtime\PostProcessLayer.cs(722,33): error CS0103: The name 'XRSettings' does not exist in the current context
Library\PackageCache\com.unity.postprocessing@3.2.0\PostProcessing\Runtime\PostProcessLayer.cs(722,67): error CS0103: The name 'XRSettings' does not exist in the current context
Reproducible with: PostProcessing 3.2.0 (2019.4.34f1, 2020.3.25f1. 2021.2.7f1,2022.1.0b2)
Not reproducible with: PostProcessing 3.1.1 (2019.4.34f1, 2020.3.25f1)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment