Page MenuHome

Fill limited and unuspported GPUs list
Open, NormalPublic


After D5955: GPU: Platform Support Level we have a mechanism to show one-time warnings for some GPUs on startup.

However we still need to fill in this list. T61936: EOL GPU problems tracking report provides a starting point, along with other reported bugs. It may be most reliable to test for the driver version when possible, since often the bugs are in the driver, and old cards don't work with new drivers.

We will need to parse the driver version which can get tricky, need to look at a lot of OpenGL strings to figure out the patterns.

  • Intel Windows
  • Intel Linux (no known issues with OpenGL 3.3 drivers I believe)
  • AMD Windows
    • Latest GCN 1st gen drivers: 19.Q3.1 (pro), Adrenalin 2019 Edition 19.9.3
    • Latest Terascale 3 drivers: 15.201.2401.1010 (pro), 16.2.1, 15.7.1
    • Warn for driver version 16 and older. Or 18 and older?
  • AMD Linux
    • No obvious way to distinguish between Terascale and GCN. Maybe just don't warn as drivers are still being maintained for both.
  • NVIDIA: official driver
    • Latest driver for GTX 2xx: 342.01
    • Latest driver for NVIDIA Quadro Tesla: R340 U14 (342.00)
    • Warn for 341 and lower.
  • NVIDIA: nouveau driver unsupported
    • Always warn.
  • macOS
    • Test if operating system is 10.12 or newer.

Event Timeline

Brecht Van Lommel (brecht) lowered the priority of this task from Needs Triage by Developer to Normal.Fri, Oct 4, 3:47 PM
Brecht Van Lommel (brecht) created this task.
Brecht Van Lommel (brecht) changed Type from Bug to To Do.

I would like to bring to the attention of you devs and managers @Ton Roosendaal (ton) an issue that I believe is best made evident.

These dated GPUs, I think it's much better to debug them and give them some love, as much as possible (the vast majority of problems have been solved, so it's just a minimum of maintenance, especially on legacy drivers on windows, on linux there the open source Mesa drivers devs are thinking about solving the problems, and now that blender 2.80 has started working properly and that people are familiarizing themselves with it, everything is becoming easier to find solutions.)

Why do I insist on this? the answer is very simple and obvious if you think about it, these gpus, especially the old radeons, the old nvidia and the most widely used intel cpu with integrated gpu of the entry level pc are all lowcost, so the schools mostly have this kind of technology (believe me, I've seen things you humans can't imagine, hehehe) computer classrooms with 20-30 pc dated.

Now, someone manages to make good use of these PCs, installing linux and keeping them reasonably in step with the times, but many remain with windows, and at most they update the drivers.
I think that keeping a working blender on these slow GPUs as long as possible is a long-term investment. For every boy who learns to use blender, to overcome the first threshold of difficulty, it will excite and use blender also at home and in a few years will become potentially a supporter.

Greetings Masters

nobody is advocating dropping support for older gpu's, this ticket is merely here to index the 'bad driver versions' and notify the users on how to rectify the situation, rather than just having blender crash on their system.

@LazyDodo (LazyDodo)
I know, I have seen the efforts that devs have been made with the workarounds to maintain maximum compatibility in this long span of development of blenders 2.80 and 2.81 .
Mine was just a reasonable intuition, which I wanted to make explicit now that the opportunity to do so has opened up.

The policy regarding supported GPUs was decided a while ago, and we have no plans to change this.

If you want to discuss that, please use devtalk, development planning tasks are not the place:

Things have changed quickly, especially on linux the improvements are quickly becoming evident on these GPUs. And they will continue to come from the open source community. In the legacy windows drivers marginal problems remain. (of osx I know little that world)

but I will do as you say, I will open a discussion on devtalk, you are right, is something to discuss.

@Brecht Van Lommel (brecht) I would say we can start with limited support for most cases. I would use unsupported only when system can actually crash. That said that means that the current AMD Windows test record needs to be set to limited as I haven't seen any crashes, only incorrect viewport renderings.

Reverted that initial AMD test in rB4707f1982ddb: Fix T70568, T70570: wrong AMD driver warning dialog. Not sure if there is something wrong in that specification or the testing mechanism, we'll have to check next week.

Agee we should use limited support for this case. We may not have any unsupported cases besides the OpenGL 3.3 warning in practice, only limited.

Brecht Van Lommel (brecht) updated the task description. (Show Details)
Brecht Van Lommel (brecht) updated the task description. (Show Details)

I enabled the warnings now for the most common problem, which is old Intel drivers. That's the case I consider most important for 2.81.

In general we should be pretty conservative with this since such warnings are annoying. We should show this mainly for cases where there are known serious problems, or cases where we know newer graphics drivers are actually available.