Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2018.4.13f1
Issue ID
1200893
Regression
No
[2018.4] Switching between GPUs on Device to Use setting will not render the editor correctly until resized or restarted
The Editor will simply render red once the GPU is changed in the general settings to Automatic or AMD, on Intel it will simply render black. Currently I can briefly work around it by resizing the window or restarting the Unity editor.
How to reproduce:
1. Open a new empty project
2. Select Unity > Preferences in the menu
3. Choose General
4. Change the GPU under "Device to Use" to AMD (or change it to Intel)
Expected Result: Unity switches devices and renders correctly without any artefacts
Actual Result: When set to AMD the editor turns red or black when set to Intel
Reproducible with: 2018.4.13f1, 2019.3.0a8
Not reproducible with: 2019.3.0b4
Could not test with 2017.4.34f1 (No Device to Use feature)
Switching to OpenGL will not show the option anymore.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2021.1.X):
This isn't an issue anymore on 2019.4 onwards. We display a warning "Changing this effect requires a restart to take place" now when we change the device. Also rendering is unaffected when running the project without restarting. On 2018.4 as there is a workaround to restart Unity (which is not actually a workaround but a requirement when switching devices) and this doesn't seem like a frequent thing to do, resolving this as Won't Fix.