#开源 适用于 Windows 的预构建 Mesa3D 驱动程序

Table of Contents

• Downloads

• Known issues

• Differences between MSVC and MinGW packages

• Mingw and MSVC Package contents
• OpenGL and OpenGL ES common shared libraries
• Microsoft CLonD3D12 and GLonD3D12 ICDs common dependency
• Desktop OpenGL drivers
• OpenGL off-screen rendering driver
• OpenGL ES drivers and EGL library
• Vulkan drivers
• OpenCL drivers, compilers and backends
• Direct3D drivers, libraries and tools
• Testing library and tools
• Development packages
• Debug packages

• Build Mesa3D yourself

• Installation and usage
• Usage notes

• Uninstall Messa3D

• Legacy software compatibility

• OpenGL context configuration override

• How to set environment variables

Downloads

Known issues

• libgallium_wgl.dll missing error with Mesa3D OpenGL ES and desktop OpenGL drivers

• libEGL.dll missing error with Mesa3D OpenGL ES

• libvulkan-1.dll missing error with Mesa3D opengl32.dll from MinGW release package

• 64-bit binaries in both MSVC and MinGW packages require a CPU with AVX even though they shouldn't

• Mesa opengl32.dll from MinGW package depends on Vulkan runtime since 21.0.0

• Programs can behave like there is no OpenGL support when using Mesa opengl32.dll since 21.0.0

• Important notes about errors related to missing libglapi.dll

Differences between MSVC and MinGW packages

• MinGW package requires a CPU with SSSE3 with benefit of providing 3-5% performance boost with software rendering drivers;

• d3d10sw introduced in 21.2.0 is only available in MSVC package;

• MinGW package uses ZSTD for certain compression tasks since 20.1.8;

• OpenCL support which began appearing piece by piece since 21.3.0 is only available for MSVC package until this issue is resolved.

Mingw and MSVC Package contents

OpenGL and OpenGL ES common shared libraries

• GLAPI shared library. File name: libglapi.dll. Its presence is required when providing both OpenGL and OpenGL ES support. Mesa3D off-screen renderer and all Mesa3D OpenGL and OpenGL ES drivers depend on it when present. Since 20.0.2 it's available in both MSVC and MSYS2 Mingw-w64 packages.

• Gallium OpenGL megadriver. File name: libgallium_wgl.dll. When present it contains all Mesa3D desktop OpenGL drivers instead of opengl32.dll. It debuted in 21.3.0. Mesa3D EGL library and OpenGL ES drivers depend on it when present.

• Mesa3D WGL runtime. File name: opengl32.dll. This used to contain all Mesa3D desktop OpenGL drivers and OpenGL ES depended on it, but since 21.3.0 it was reduced to only being a loader for gallium OpenGL megadriver, so only programs using Mesa3D desktop OpenGL drivers via per-application deployment depend on it now.

Microsoft CLonD3D12 and GLonD3D12 ICDs common dependency

• DirectX IL for redistribution. File name: dxil.dll. This Windows SDK binary is installable via deployment tools as necessary.

Desktop OpenGL drivers

• llvmpipe. llvmpipe is a Desktop OpenGL software renderer intended as fallback when hardware acceleration is not possible. It can only handle very light gaming with good performance. This is the default Mesa3D desktop OpenGL driver when GLonD3D12 is either unavailable or fails to load. It's available for both x86 and x64 as part of Mesa3D Desktop OpenGL bundle opengl32.dll or libgallium_wgl.dll if the latter is available. When it's not the default driver select it by setting environment variable GALLIUM_DRIVER=llvmpipe.

• softpipe is a reference implementation of a Desktop OpenGL software renderer with no focus towards gaming performance. It's available for both x86 and x64 as part of Mesa3D Desktop OpenGL bundle opengl32.dll or libgallium_wgl.dll if the latter is available. Select it by setting environment variable GALLIUM_DRIVER=softpipe.

• GLonD3D12. It's available for both x86 and x64 as part of Mesa3D Desktop OpenGL bundle opengl32.dll or libgallium_wgl.dll if the latter is available and standalone as openglon12.dll and it's available in MSVC package and since 22.2.0 in MinGW package as well. In addition to officially requiring Windows 10 v10.0.19041.488 or newer, it also depends on DirectX IL for redistribution - dxil.dll to load, which can be installed via deployment tools. When available and if it can load, this is the default Mesa3D desktop OpenGL driver on D3D12 GPU accelerated systems. This driver introduced in 21.0.0 is operating as wrapper returning D3D12 API calls. Due to this nature it can use GPU accelleration. If it's not selected by default you can test it with Direct3D WARP software renderer built into Windows by setting GALLIUM_DRIVER=d3d12 and LIBGL_ALWAYS_SOFTWARE=1 environment variables. The standalone copy doesn't need GALLIUM_DRIVER=d3d12 being set and it can only be installed via system-wide deployment tool. The standalone GLonD3D12 and Mesa3D Desktop OpenGL bundle replace each other when using system-wide deployment tool but you can reverse it any time.

• zink. This driver introduced in MinGW package in 21.0.0 and MSVC package in 21.2.0 it's available for both x86 and x64 as part of Mesa3D Desktop OpenGL bundle opengl32.dll or libgallium_wgl.dll if the latter is available. Siimilarly to GLonD3D12, it operates as wrapper returning Vulkan API calls. Due to this nature it uses GPU accelleration by default but it supports software rendering too. Select it via GALLIUM_DRIVER=zink environment variable, but note that it requires at least 1 Vulkan device and Vulkan loader/runtime to initialize. zink ignored Vulkan CPU type devices by default until 22.1.0. Nowdays it uses a priority system that automatically selects a Vulkan CPU type device if no higher priority Vulkan type device exists. You can test zink with Vulkan CPU type devices only by setting LIBGL_ALWAYS_SOFTWARE=1 (Mesa 22.1.0 and newer) or ZINK_USE_LAVAPIPE=true (deprecated in Mesa 22.1.0).

• swr. This driver is no longer available in Mesa 22.0 and newer. File names: swrAVX.dll, swrAVX2.dll, swrSKX.dll, swrKNL.dll. Even though it resides outside of Mesa3D Desktop OpenGL bundle opengl32.dll or libgallium_wgl.dll if the latter is available, it still depends on it. This alternative desktop OpenGL software rendering driver developed by Intel is optimized for visualization software. It's available in MSVC package and since 20.1.7 in MinGW package as well. It only supports x64, x86 is officially unsupported. There are currently 4 DLLs, only one being loaded based on what the user CPU can do. You can switch to swr by setting GALLIUM_DRIVER environment variable value to swr.

OpenGL off-screen rendering driver

• osmesa. File name: osmesa.dll. Available for both x86 and x64. This driver is used in special cases by software that is designed to use Mesa code to render without any kind of window system or operating system dependency. Since 21.0.0 only osmesa gallium remained. It supports OpenGL 3.x and newer. Since 20.0.2 osmesa integration with standalone GLLES drivers is available in both MSVC and MSYS2 Mingw-w64 packages requiring libglapi.dll in the process.

OpenGL ES drivers and EGL library

• EGL library. File name: libEGL.dll. Mesa3D EGL library used by OpenGL ES drivers. This debuted in 21.3.0 and it's available for 32-bit and 64-bit applications in both MSVC and MSYS2 packages. It depends on desktop OpenGL bundle opengl32.dll or libgallium_wgl.dll if the latter is available.

• OpenGL ES standalone drivers. File names: libGLESv1_CM.dll and libGLESv2.dll. OpenGL ES 1.x, 2.x and 3.x standalone drivers available for 32-bit and 64-bit applications. Since 20.0.2 they are available in both MSVC and MSYS2 Mingw-w64 packages. They depend on Mesa3D EGL library if available and desktop OpenGL bundle opengl32.dll or libgallium_wgl.dll if the latter is available.

Vulkan drivers

• lavapipe Vulkan CPU driver is available in both MSVC and MinGW packages since 21.1.0. File names: lvp_icd.x86_64.json, lvp_icd.x86.json, vulkan_lvp.dll. Note that some programs may ignore Vulkan CPU type devices on purpose. For information on how to deploy see usage notes.

• Microsoft dozen Vulkan driver is available since 22.1.0 in MSVC package and since 22.2.0 in MinGW package as well. This driver relies on D3D12 API to function and it can use GPU acceleration on supported systems. File names: dzn_icd.x86_64.json, dzn_icd.x86.json, vulkan_dzn.dll. For information on how to deploy see usage notes.

• Vulkan driver for AMD graphics (radv) is no longer available since 22.1.0 per @zmike suggestion as it won't work anytime soon. RADV was available in both MSVC and MinGW packages since 21.2.0. 32-bit binary of it was available since Mesa 22.0. File names: radeon_icd.x86_64.json, radeon_icd.x86.json, libvulkan_radeon.dll and vulkan_radeon.dll. For information on how to deploy see usage notes.

OpenCL drivers, compilers and backends

• Microsoft OpenCL stack. File names: clon12compiler.dll (compiler), openclon12.dll (ICD) and WinPixEventRuntime.dll (x64 only dependency). These components introduced in 21.0.0 are finally provided by mesa-dist-win since 21.3.0 (compiler only) and 21.3.6-2 respectively. ClonD3D12 driver is available as an OpenCL ICD. For information on how to deploy see usage notes. CLonD3D12 officially requires Windows 10 v10.0.19041.488 or newer and it depends on DirectX IL for redistribution - dxil.dll to load, which can be installed via deployment tools. CLonD3D12 is operating as wrapper returning D3D12 API calls. Due to this nature it can use D3D12 GPU accelleration if available otherwise Windows built-in WARP software rendering is used. Even when using WARP CLonD3D12 advertises CL_DEVICE_TYPE_GPU, but this can change anytime to CL_DEVICE_TYPE_CPU. Some programs ignore drivers with CL_DEVICE_TYPE_CPU set on purpose.

• clover OpenCL stack has been removed from release package in 22.1.1 until Windows support is finalized as it's currently unusable. File names: MesaOpenCL.dll (ICD), OpenCL.dll (standalone runtime), and pipe_swrast.dll (pipe loader). The runtime can be deployed with per app deployment tool since 21.3.7 or on older versions via copy-paste along with all available pipe loaders which it depends on. While deployed, the runtime hides all other OpenCL ICDs present on the system and only lets software use Mesa3D clover as the only OpenCL driver. For information on how to deploy the ICD see usage notes.

Direct3D drivers, libraries and tools

• D3D10 software renderer is available in MSVC package since 21.2.0. File name: d3d10sw.dll. This is a drop in replacement for Microsoft WARP and unfortunately there is no clean way of deploying it.

• SPIR-V to DXIL tool and library are available in MSVC package since 21.0.0 and since 22.2.0 in MinGW package as well. File names: libspirv_to_dxil.dll, spirv_to_dxil.dll and spirv2dxil.exe.

Testing library and tools

• Gallium raw interface. File names: graw.dll, graw_null.dll. This is a dummy gallium driver without any graphics API mainly used for testing. Available for both x86 and x64 and in full (with window system support) and headless (no window) versions. Since 20.0.2 both windowed and windowless versions are available in both MSVC and MSYS2 Mingw-w64 packages. This deprecated component has been removed in Mesa3D 22.3.0-devel.

• test suite. Many executable unit tests.

Development packages

Debug packages

Build Mesa3D yourself

Installation and usage

• A system-wide deployment tool. While intended for systems lacking hardware accelerated OpenGL support like virtual machines in cloud environments, it can also be used on any Windows system to replace the inbox software rendering OpenGL 1.1 driver extending OpenGL support for use cases where hardware accelerated OpenGL is not available like RDP connections. Due to potential issues with Virtualbox VMs running Windows it is recommended to disable 3D acceleration in such VMs if Mesa3D desktop OpenGL driver is installed inside them using the system-wide deployment tool, see #9.

• A per-application deployment tool, used to deploy Mesa3D for a single program regardless of hardware accelerated OpenGL support being present or not. Per-app deployment utility changes are persistent and are being kept across upgrades and re-installations. Per-app deployment utility helps you save storage and makes things easier as you won't have to manually copy DLLs from Mesa installation directory as it creates symbolic links to whatever Mesa drivers you opt-in to use. This behavior ensures all programs that use Mesa use the same up-to-date version. Per-app deployment utility asks for path to directory containing application executable, application executable filename (optional, it can remain blank but if specified can force some programs to use Mesa3D when they won't otherwise), if the app is 64-bit or 32-bit and the drivers you need. 32-bit applications have their names marked in Task Manager while running. Most applications will use Mesa regardless of GPU capabilities, but some applications may be smart enough to load OpenGL from system directory only. By providing the application filename, a .local file is generated in an attempt to force the application to use Mesa3D when it doesn't want to. Also, Federico Dossena's Mesainjector can be used to workaround this issue as well. Build instructions for Mesainjector.

Usage notes

• Old applications from early 200x and older may need MESA_EXTENSION_MAX_YEAR environment variable set, see legacy software compatibility section.

• Applications requiring OpenGL 3.2 or newer may need OpenGL context configuration override.

• The official Mesa3D documentation is available here.

• OpenCL ICDs deployment is done through registration of ICD file with system OpenCL runtime (e.g. opencl.dll from Windows\system32). If you don't have system OpenCL runtime you can get it by installing Intel OpenCL CPU runtime. It works for AMD CPUs as well.

• Deployment for Vulkan drivers is done through Vulkan runtime using ICD discovery method. Note that Vulkan runtime commes bundled with graphics drivers supporting Vulkan so manually installing it may not be necessary.

Uninstall Messa3D

1. Run system wide deployment and perform uninstall operation if available, then exit;

2. Download and run Everything tool (any flavor should work);

3. Run per application deployment tool and leave it running;

4. In Everything tool, in text field under menu enter libgallium_wgl.dll attrib:L and keep Everything tool running;

5. For each search result in Everything tool:

• open its location in Windows Explorer via Open Path or Open File location context menu option;

• find *.local files and remove them, but only if you are certain you specified a filename during deployment to that location;

• copy location from address bar and feed it to per application deployment tool;

• send no to all deployments until you are asked to do more deployments, send yes there.

1. Repeat steps 4 and 5 using osmesa.dll and graw.dll filenames respectively the same way was done for libgallium_wgl.dll;

2. Close per application deployment and Everything tools;

3. Revert any registry changes and any environment variables that configure Vulkan runtime to use any of Mesa3D Vulkan drivers;

4. Repeat stepp 8, but for OpenCL.

Legacy software compatibility

OpenGL context configuration override

• MESA_GL_VERSION_OVERRIDE

• MESA_GLSL_VERSION_OVERRIDE

How to set environment variables

• for every application requiring higher OpenGL and GLSL versions than what is exposed by selected Mesa3D driver by default;

• if you want to select a non-default driver for desktop OpenGL;

• if you need to trim extensions list for old programs compatibility.