Intel graphics for Haswell and newer are supported and generally working well. But for good performance GCN is still required. On Linux, drivers do continue to be updated and Blender tends to work better. No Terascale OpenGL drivers have been released for Windows in the last 3 years. Unfortunately, this does mean some GPUs released in the last 10 years are not officially supported. See the list of AMD GPUs to check which architecture your card has. Terascale architecture cards are not working reliably, mainly on Windows. GCN 1 st gen and newer architectures are supported on both Windows and Linux. This covers the NVIDIA GPUs released in the last 10 years. GeForce 200 series, Quadro with Tesla architecture and newer are supported on both Windows and Linux. Older macOS versions have bugs in the OpenGL drivers that cause problems for Eevee, and the only way to upgrade the drivers is to upgrade the operating system as a whole. MacOS 10.12 or newer is supported, and Mac hardware from the last 10 years appear to be working. External developers may contribute patches to improve hardware support if said patches are not too cumbersome. While Blender does not officially support such older hardware, we do not prevent Blender from running on it. All these are cases where the OpenGL driver was last updated 3 years ago or more. Unfortunately, there are still some GPUs where Blender does not run reliably, and we won’t be able to officially support them for the 2.80 release. Blender now works on the large majority GPUs that our users have. We have found workarounds for dozens of those bugs, which has been very time-consuming. However, we have found that there are many graphic cards that support OpenGL 3.3 in hardware, but have critical bugs in the OpenGL drivers. Cleaner than #ifdefs around large blocks of inline code.The original plan for Blender 2.80 was to work on all GPUs that have OpenGL 3.3 drivers and were released in the last 10 years. Nice thing is that presumably it works with the preprocessor so you can do conditional includes and such to speed up compilation time without having to use an external preprocessor or write your own. Not something you have to use if you don’t like it. So the driver does the strcat’ing instead of you. IIRC, you load the include files and give the content strings and the “filenames” to the driver, and it just uses that as a dictionary to resolve #includes. The driver doesn’t “hit the disk” or anything.
> Edit: whoops, the non-core include-extension is not available yet ^^".Īnd this is maybe for the best… I’m really not sure about this extension.Įh, it’s really not bad. That’s the kind of news that make you think that the best of nVidia is the developers support!ĭefinitely! And that’s GTX 480 comin’ up next Friday.
0 kommentar(er)
