Search Issue Tracker
Fixed in 5.4.0
Votes
0
Found in
Issue ID
786263
Regression
No
PlayerSettings.useDirect3D11 obsolete - console warning message is not precise
To reproduce issue follow the steps:
1. Create new project
2. Open new scene
3. Create the script with following code and attach to any GameObject in the scene
void Start () {
bool p = PlayerSettings.useDirect3D11;
}
4. Run the scene
5. Console throws this warning
Assets/NewBehaviourScript.cs(8,41): warning CS0618: `UnityEditor.PlayerSettings.useDirect3D11' is obsolete: `Use SetGraphicsAPIs/GetGraphicsAPIs instead'
More precise behavior would be:
warning CS0618: `UnityEditor.PlayerSettings.useDirect3D11' is obsolete: `Use UnityEditor.PlayerSettings.SetGraphicsAPIs/GetGraphicsAPIs instead'
Reproduced in 5.4.0b13
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