Search Issue Tracker
By Design
Votes
0
Found in
5.4.0f3
Issue ID
826283
Regression
No
SystemInfo.supportsComputeShaders returns true on Windows when launched with -force-glcore41
Steps to reproduce:
1. open User's attached project
2. attach script "supportsCompute" to one of the game objects
3. check Console
Expected behavior: SystemInfo.supportsComputeShaders is: False
Actual result: SystemInfo.supportsComputeShaders is: True
Reproduced with: 5.5.0a6, 5.4.0p3, 5.3.6p2, 5.2.5f1
Note:
-OpenGL 4.1 does not support ComputeShaders
-SystemInfo.copyTextureSupport returns a list of full support, which according to the Unity manual is also incorrect
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