Search Issue Tracker
Fixed in 3.2.1
Votes
0
Found in [Package]
3.1.1
Issue ID
1368370
Regression
No
Screen space refelctions not working when the graphics API is set to OpenGLCore
How to reproduce:
1. Open the user attached project (reflectionSample.zip) and make sure the "SampleScene" is open
2. In the Scene view observe the tree reflections on the ground
3. Go the Player Settings by going to the menu bar "Edit > Project Settings..." then selecting the "Player" section
4. Under "Other Settings" switch up the "OpenGLCore" graphics API's location to be at the bottom, below all the other API's for your current platform
5. Restart the Editor when prompted
6. Observe and compare the tree reflections on the ground to the ones seen previously
Expected results: The reflections look identical before and after switching the graphics APIs
Actual results: When OpenGLCore is the main graphics API the reflections don't work as they do on other graphics APIs
Reproducible with: 2019.4.31f1, 2020.3.20f1, 2021.1.22f1, 2021.2.0b12, 2022.1.0a11
Notes:
1. Reproducible on Ubuntu 20.04 and Windows 10
2. The issue is also present on project builds with OpenGLCore as the active graphics API on both Ubuntu 20.04 and Windows 10
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note (fix version 3.2.1):
Fixed in "Post Processing" version 3.2.1