Search Issue Tracker
Fixed in 13.x
Votes
0
Found in [Package]
13.1.2
Issue ID
1384634
Regression
No
[HDRP] Project becomes unusable after trying to switch Graphics API to OpenGLCore and back
Reproduction steps:
1. Create a new HDRP Template project
2. Go Edit -> Project Settings -> Player
3. Disable Auto Graphics API for Windows
4. Switch to OpenGLCore and restart the Editor when prompted
5. You will get errors in Console and Play Mode indicating that OpenGLCore is not supported for HDRP (this is expected)
6. Switch back to Vulkan or DX and restart the Editor when prompted
Expected result: the Graphics API is changed and the project returns to normal state
Actual result: the Graphics API does not change even if the settings indicate that OpenGLCore is not selected. The same errors are still in the console. There is no way to switch the Graphics API back to Vulkan or DX. Scene view is gray, and Game view is black
Reproducible with: 7.7.1 (2019.4.33f1), 10.7.0 (2020.3.24f1), 12.1.2 (2021.2.5f1), 13.1.2 (2022.1.0b1)
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (fix version 13.x):
Fixed in 2022.2.0a8.1216