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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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.