AMD Open Source Driver for Vulkan®
The AMD Open Source Driver for Vulkan® is an open-source Vulkan driver for Radeon™ graphics adapters on Linux®. It is built on top of AMD’s Platform Abstraction Library (PAL), a shared component that is designed to encapsulate certain hardware and OS-specific programming details for many of AMD’s 3D and compute drivers. Leveraging PAL can help provide a consistent experience across platforms, including support for recently released GPUs and compatibility with AMD developer tools.
Shaders that compose a particular VkPipeline
object are compiled as a single entity using the LLVM-Based Pipeline Compiler (LLPC) library. LLPC builds on LLVM’s existing shader compilation infrastructure for AMD GPUs to generate code objects compatible with PAL’s pipeline ABI. Notably, AMD’s closed-source Vulkan driver currently uses a different pipeline compiler, which is the major difference between AMD’s open-source and closed-source Vulkan drivers.
Product Support
The AMD Open Source Driver for Vulkan is designed to support the following AMD GPUs:
- Radeon™ RX 9070 Series
- Radeon™ RX 7900/7800/7700/7600 Series
- Radeon™ RX 6900/6800/6700/6600/6500 Series
- Radeon™ RX 5700/5600/5500 Series
- Radeon™ Pro W5700/W5500 Series
Note
For Pre-GFX10 GPUs, please use v-2023.Q3.3 or older release.
Operating System Support
The AMD Open Source Driver for Vulkan is designed to support following distros and versions on both the AMDGPU upstream driver stack and the AMDGPU Pro driver stack:
- Ubuntu 22.04 (amd64 version)
- Ubuntu 24.04 (amd64 version)
- RedHat 9.0 (x86-64 version)
- RedHat 10.0 (x86-64 version)
The driver has not been well tested on other distros and versions. You may try it out on other distros and versions of your choice.
Note
To run the Vulkan driver with AMDGPU upstream driver stack on SI and CI generation GPUs, amdgpu.si_support and amdgpu.cik_support need to be enabled in kernel
Feature Support and Performance
The AMD Open Source Driver for Vulkan is designed to support the following features:
- Vulkan 1.4
- More than 180 extensions
- Radeon™ GPUProfiler tracing
- Built-in debug and profiling tools
- Mid-command buffer preemption and SR-IOV virtualization
The following features and improvements are planned in future releases (Please refer to Release Notes for update of each release):
- Upcoming versions of the Vulkan API
- Hardware performance counter collection through RenderDoc
- LLPC optimizations to improve GPU-limited performance and compile time
- Optimizations to improve CPU-limited performance
Known Issues
- If you are using upstream stack, you may need to upgrade the kernel to 5.3 or later version and firmware (under /lib/firmware/amdgpu/) to the right version from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu, and then update ramfs (sudo update-initramfs -u -k `uname -r`)
- Timeline semaphore is not fully supported in Linux kernel until version 5.5. You can install Vulkan timeline semaphore layer to enable the extension if you are using earlier version of Linux kernel
How to Contribute
You are welcome to submit contributions of code to the AMD Open Source Driver for Vulkan.
The driver is built from source code in five repositories: LLVM, XGL, LLPC, GPURT and PAL.
For changes to LLVM, you should submit contribution to the LLVM trunk. Commits there will be evaluated to merge into the amd-gfx-gpuopen-master branch periodically.
For changes to XGL, LLPC, GPURT and PAL, please create a pull request against the dev branch. After your change is reviewed and if it is accepted, it will be evaluated to merge into the master branch in a subsequent regular promotion.
IMPORTANT: By creating a pull request, you agree to allow your contribution to be licensed by the project owners under the terms of the MIT License.
When contributing to XGL, LLPC, GPURT and PAL, your code should:
- Match the style of nearby existing code. Your code may be edited to comply with our coding standards when it is merged into the master branch.
- Avoid adding new dependencies, including dependencies on STL.
Please make each contribution reasonably small. If you would like to make a big contribution, like a new feature or extension, please raise an issue first to allow planning to evaluate and review your work.
Note
Since PAL is a shared component that must support other APIs, other operating systems, and pre-production hardware, you might be asked to revise your PAL change for reasons that may not be obvious from a pure Linux Vulkan driver perspective.
Build Instructions
System Requirements
It is recommended to install at least 16GB RAM in your build system.
Build System
- CMake 3.21 or newer is required. Download and install proper one if the cmake is older than 3.21.
- C++ 20 support is required. Like gcc9, clang11.
- Ninja is required.
Install Dev and Tools Packages
Ubuntu
sudo apt-get install build-essential cmake curl g++-multilib gcc-multilib git ninja-build pkg-config python3 python3-jinja2 python3-ruamel.yaml
64-bit
sudo apt-get install libssl-dev libx11-dev libxcb1-dev x11proto-dri2-dev libxcb-dri3-dev libxcb-dri2-0-dev libxcb-present-dev libxshmfence-dev libxrandr-dev libwayland-dev
32-bit
dpkg --add-architecture i386
sudo apt-get install libssl-dev:i386 libx11-dev:i386 libxcb1-dev:i386 libxcb-dri3-dev:i386 libxcb-dri2-0-dev:i386 libxcb-present-dev:i386 libxshmfence-dev:i386 libwayland-dev libwayland-dev:i386 libxrandr-dev:i386
RedHat
64-bit
sudo yum -y install openssl-devel gcc-c++ python3 python3-pip curl glibc-devel libstdc++-devel libxcb-devel libX11-devel libxshmfence-devel libXrandr-devel wayland-devel
pip3 install jinja2 ruamel.yaml
32-bit
sudo yum -y install openssl-devel.i686 gcc-c++ python3 python3-pip curl glibc-devel.i686 libstdc++-devel.i686 libxcb-devel.i686 libX11-devel.i686 libxshmfence-devel.i686 libXrandr-devel.i686 wayland-devel.i686
pip3 install jinja2 ruamel.yaml
Install shader compiler tools
Shader compiler tools such as DirectXShaderCompiler and glslang need to be installed to build raytracing support.
Ubuntu 22.04
It is recommended to install them from VulkanSDK 1.3.290 or higher.
Ubuntu 22.04 (Jammy)
wget -qO- https://packages.lunarg.com/lunarg-signing-key-pub.asc | sudo tee /etc/apt/trusted.gpg.d/lunarg.asc
sudo wget -qO /etc/apt/sources.list.d/lunarg-vulkan-1.3.290-jammy.list https://packages.lunarg.com/vulkan/1.3.290/lunarg-vulkan-1.3.290-jammy.list
sudo apt update
sudo apt install vulkan-sdk
Others
Get DirectXShaderCompiler and glslang source code and build tools on local.
#!/bin/bash
if [ ! -d DirectXShaderCompiler ]; then
git clone --depth=1 -b release-1.8.2403 https://github.com/microsoft/DirectXShaderCompiler.git
fi
if [ ! -d glslang ]; then
git clone --depth=1 -b vulkan-sdk-1.3.290.0 https://github.com/KhronosGroup/glslang.git
fi
cd DirectXShaderCompiler
git submodule init
git submodule update
cmake -H. -Bbuilds -GNinja -DCMAKE_BUILD_TYPE=Release -C ./cmake/caches/PredefinedParams.cmake
cmake --build builds
cd ..
cd glslang
cmake -H. -Bbuilds -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX='builds/install'
cd builds
make -j8 install
cd ../../
Set env PATH and LD_LIBRARY_PATH before amdvlk driver build.
export PATH=<DirectXShaderCompiler>/builds/bin:<glslang>/install/bin:$PATH
export LD_LIBRARY_PATH=<DirectXShaderCompiler>/builds/lib:$LD_LIBRARY_PATH
Get Repo Tools
mkdir ~/bin
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
export PATH=~/bin:"$PATH"
Get Source Code
mkdir vulkandriver
cd vulkandriver
repo init -u https://github.com/GPUOpen-Drivers/AMDVLK.git -b master
repo sync
Note
Source code in dev branch can be gotten by using «-b dev» in the «repo init» command.
Build Driver and Generate JSON Files
cmake -G Ninja -S xgl -B builds/Release64
cmake --build builds/Release64
cmake -G Ninja -S xgl -B builds/Release32 -DCMAKE_C_FLAGS=-m32 -DCMAKE_CXX_FLAGS=-m32
cmake --build builds/Release32
Note
- For debug build, use
-DCMAKE_BUILD_TYPE=Debug -DLLVM_PARALLEL_LINK_JOBS=2
(Linking a debug build of llvm is very memory intensive, so we use only two parallel jobs).- If you want to build tools (such as amdllpc) together with driver, add
-m build_with_tools.xml
in repo init and add the build option-DVKI_BUILD_TOOLS=ON
.
Installation Instructions
Install Vulkan SDK
You can download and install the SDK package here.
Install dependencies
Ubuntu
RedHat
sudo yum install openssl-libs
Install Driver and JSON Files
sudo cmake --install builds/Release64 --component icd
sudo cmake --install builds/Release32 --component icd
If you want to install driver to customized directory, you can add «-DCMAKE_INSTALL_PREFIX={installation directory}» in the cmake build command. JSON files will be installed to /etc/vulkan/icd.d while other files will be installed to the installation directory you specified.
If RADV is also installed in the system, AMDVLK driver will be enabled by default after installation. You can switch the driver between AMDVLK and RADV by environment variable AMD_VULKAN_ICD = AMDVLK or RADV.
Note: The remaining steps are only required when running the AMDGPU upstream driver stack.
Turn on DRI3 and disable modesetting X driver
Add following lines in /usr/share/X11/xorg.conf.d/10-amdgpu.conf:
Section "Device"
Identifier "AMDgpu"
Option "DRI" "3"
EndSection
And make sure following line is NOT included in the section:
Required Settings
On the AMDGPU upstream driver stack with libdrm version lower than 2.4.92, the max number of IB per submission MUST be limited to 4 (the default setting in AMD Open Source driver for Vulkan is 16). This can be accomplished via the Runtime Settings mechanism by adding the following line to amdPalSettings.cfg:
MaxNumCmdStreamsPerSubmit,4
CommandBufferCombineDePreambles,1
Install with pre-built driver
You could generate the installation package with below command while building driver:
Ubuntu
cmake -G Ninja -S xgl -B builds/Release64 [-DPACKAGE_VERSION=package version]
cmake --build builds/Release64 --target makePackage
RedHat
cmake -G Ninja -S xgl -B builds/Release64 [-DPACKAGE_VERSION=package version]
cmake --build builds/Release64 --target makePackage
You could also download pre-built package from https://github.com/GPUOpen-Drivers/AMDVLK/releases for each code promotion in master branch.
Below is the installation instruction:
Ubuntu
sudo dpkg -r amdvlk # If old version is installed on the machine, remove it first
sudo dpkg -i amdvlk_x.x.x_amd64.deb
sudo apt-get -f install
RedHat
sudo rpm -e amdvlk # If old version is installed on the machine, remove it first
sudo rpm -i amdvlk-x.x.x.x86_64.rpm
For Ubuntu, you could also install the latest driver build from https://repo.radeon.com:
sudo wget -qO - http://repo.radeon.com/amdvlk/apt/debian/amdvlk.gpg.key | sudo apt-key add -
sudo sh -c 'echo deb [arch=amd64,i386] http://repo.radeon.com/amdvlk/apt/debian/ bionic main > /etc/apt/sources.list.d/amdvlk.list'
sudo apt-get remove amdvlk # If old version is installed on the machine, remove it first
sudo apt update
sudo apt-get install amdvlk
Runtime Settings
The driver exposes many settings that can customize the driver’s behavior and facilitate debugging. You can add/edit settings in amdVulkanSettings.cfg or amdPalSettings.cfg file under one of below paths, formatted with one name,value
pair per line:
- /etc/amd
- $AMD_CONFIG_DIR
Some example settings are listed below:
Setting Name | Valid Values | Comment |
---|---|---|
AllowVkPipelineCachingToDisk |
0: disallow 1: default |
1 is default value which enables Pal’s archive-file based caching. The archive-file is stored under ~/.cache/AMD/VkCache. |
ShaderCacheMode |
0: disable cache 1: runtime cache 2: cache to disk |
Runtime cache is the default mode. For «cache to disk», the cache file is generated under $AMD_SHADER_DISK_CACHE_PATH/AMD/LlpcCache or $XDG_CACHE_HOME/AMD/LlpcCache or $HOME/.cache/AMD/LlpcCache |
IFH |
0: default 1: drop all submits |
Infinitely Fast Hardware. Submit calls are dropped before being sent to hardware. Useful for measuring CPU-limited performance. |
EnableVmAlwaysValid |
0: disable 1: default 2: force enable |
1 is the default setting which enables the VM-always-valid feature for kernel 4.16 and above. The feature can reduce command buffer submission overhead related to virtual memory management. |
IdleAfterSubmitGpuMask |
Bitmask of GPUs (i.e., bit 0 is GPU0, etc.) | Forces the CPU to immediately wait for each GPU submission to complete on the specified set of GPUs. |
All available settings can be determined by examining below source files that define them.
- …/xgl/icd/settings/settings_xgl.json (API layer settings)
- …/pal/src/core/settings_core.json (PAL hardware-independent settings)
- …/pal/src/core/hw/gfxip/gfx9/settings_gfx9.json (PAL GFX9+ settings)
- …/pal/src/core/hw/gfxip/gfx12/settings_gfx12.json (PAL GFX12 settings)
Runtime settings are only read at device initialization, and cannot be changed without restarting the application. If running on a system with multiple GPUs, the same settings will apply to all of them. Lines in the settings file that start with ;
will be treated as comments.
Enable extensions under development
The extensions under development are not enabled by default in driver. You can enable them through environment variable:
export AMDVLK_ENABLE_DEVELOPING_EXT="<extension1-name> [<extension2-name>...]"
or
export AMDVLK_ENABLE_DEVELOPING_EXT="all"
The extension name is case-insensitive.
PAL GpuProfiler Layer
The GpuProfiler is an optional layer that is designed to intercept the PAL interface to provide basic GPU profiling support. Currently, this layer is controlled exclusively through runtime settings and outputs its results to file.
You can use the following Runtime Settings to generate .csv files with GPU timings of work performed during the designated frames of an application (one file for each frame):
Setting Name | Value | Comment |
---|---|---|
GpuProfilerMode |
0: disable 1: enable with sqtt off 2: enable with sqtt for thread trace 3: enable with sqtt for RGP |
Enables and sets the SQTT mode for the GPU performance profiler layer. Actual capture of performance data must be specified via frame number with GpuProfilerConfig_StartFrame or by pressing shift-F11. |
GpuProfilerConfig.LogDirectory |
<directory-path> | The directory path is relative to $AMD_DEBUG_DIR or $TMPDIR or /var/tmp/, default value is «amdpal/». Your application must have write permissions to the directory. The profiling logs are output to a subdirectory that is named in the format like <AppName><yyyy-MM-dd><HH:mm:ss>. |
GpuProfilerConfig.Granularity |
0: per-draw 1: per-cmdbuf |
Defines what is measured/profiled. Per-draw times individual commands (such as draw, dispatch, etc.) inside command buffers, while per-cmdbuf only profiles entire command buffers in aggregate. |
GpuProfilerConfig.StartFrame |
Positive integer | First frame to capture data for. If StartFrame and FrameCount are not set, all frames will be profiled. |
GpuProfilerConfig.FrameCount |
Positive integer | Number of frames to capture data for. |
GpuProfilerConfig.RecordPipelineStats |
0, 1 | Gathers pipeline statistic query data per entry if enabled. |
You can use the script timingReport.py to analyze the profiling log:
python timingReport.py <profiling_log_subdirectory>
Dump Pipelines and Shaders
The output of timeReport.py includes the information of top pipelines like below:
Top Pipelines (>= 1%)
Compiler Hash | Type | Avg. Call Count | Avg. GPU Time [us] | Avg. Frame %
1. 0xd91d15e42d62dcbb | VsPs | 43 | 11,203.15 | 10.20 %
2. 0x724e9af55f2adf1b | Cs | 1 | 9,347.50 | 8.51 %
3. 0x396e5ad6f7a789f7 | VsHsDsPs | 468 | 8,401.35 | 7.65 %
You can add the following settings to amdPalSettings.cfg to dump the information of each pipeline:
EnablePipelineDump,1
PipelineDumpDir,<dump_dir_path>
PipelineDumpDir is a sub-path relative to $AMD_DEBUG_DIR or $TMPDIR or /var/tmp/, default value is «spvPipeline/». The pipeline dump file is named in the format like Pipeline<Type>_<Compiler_Hash>.pipe. For example, the above top 1 pipeline is dumped to PipelineVsFs_0xD91D15E42D62DCBB.pipe. The shaders referenced by each pipeline are also dumped to .spv files.
PAL Debug Overlay
PAL’s debug overlay can be enabled to display real time statistics and information on top of a running application. This includes a rolling FPS average, CPU and GPU frame times, and a ledger tracking how much video memory has been allocated from each available heap. Benchmarking (i.e., «Benchmark (F11)») is currently unsupported.
Setting Name | Value | Comment |
---|---|---|
DebugOverlayEnabled |
0, 1 | Enables the debug overlay. |
DebugOverlayConfig.DebugOverlayLocation |
0: top-left 1: top-right 2: bottom-left 3: bottom-right |
Determines where the overlay text should be displayed. Can be used to avoid collision with important rendering by the application. |
DebugOverlayConfig.PrintFrameNumber |
0, 1 | Reports the current frame number. Useful when determining a good frame range for profiling with the GpuProfiler layer. |
DebugOverlayConfig.TimeGraphEnable |
0, 1 | Enables rendering of a graph of recent CPU and GPU frame times. |
Third Party Software
The AMD Open Source Driver for Vulkan contains code written by third parties.
- LLVM is distributed under the Apache License v2.0 with LLVM Exceptions. See LICENSE.TXT file in the top directory of the LLVM repository.
- MetroHash is distributed under the terms of Apache License 2.0. See LICENSE file in the top directory of the MetroHash repository.
- CWPack is distributed under the terms of MITLicense. See LICENSE file in the top directory of the CWPack repository.
- Please see the README.md file in the PAL, LLPC, GPURT and XGL repositories for information on third party software used by those libraries.
DISCLAIMER
The information contained herein is for informational purposes only, and is subject to change without notice. This document may contain technical inaccuracies, omissions and typographical errors, and AMD is under no obligation to update or otherwise correct this information. Advanced Micro Devices, Inc. makes no representations or warranties with respect to the accuracy or completeness of the contents of this document, and assumes no liability of any kind, including the implied warranties of noninfringement, merchantability or fitness for particular purposes, with respect to the operation or use of AMD hardware, software or other products described herein. No license, including implied or arising by estoppel, to any intellectual property rights is granted by this document. Terms and limitations applicable to the purchase or use of AMD’s products are as set forth in a signed agreement between the parties or in AMD’s Standard Terms and Conditions of Sale.
AMD, the AMD Arrow logo, Radeon, FirePro, and combinations thereof are trademarks of Advanced Micro Devices, Inc. Other product names used in this publication are for identification purposes only and may be trademarks of their respective companies.
Vega is a codename for AMD architecture, and is not a product name.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Vulkan and the Vulkan logo are registered trademarks of the Khronos Group, Inc.
Сегодня AMD выложила новый драйвер AMD Vulkan, AMDVLK v-2022.Q4.3, который предлагает несколько последних улучшений производительности в нескольких играх, а также некоторые графические исправления в некоторых играх.
Ниже приведена информация о новом обновлении драйвера AMD Vulkan, размещенная на Github GPUOpen-Drivers компании AMD.
Новые возможности и улучшения
- Обновление Khronos Vulkan Headers до версии 1.3.235
- Настройка производительности для WolfYB, Three Kingdoms и т.д.
- Расширение NonBlockCompressedView для поддержки view3dAs2dArray
Исправленные проблемы
- Цветное мерцание в GTA IV
- Замыкание в Doom Eternal
- Dota2 не запускается с AMDVLK, когда установлен RADV
- [Проблемы с PAL # 91] Драйвер AMDVLK использует DRM_NODE_PRIMARY, даже если VK_KHR_display не включен
AMD Open Source Driver for Vulkan, AMDVLK, — это официальный графический драйвер Radeon с открытым исходным кодом, специально разработанный для платформы Linux.
Новое обновление корректирует производительность для Wolfenstein Youngblood и Total War: Three Kingdoms. Компания не уточняет другие игры, производительность которых повышена в этом новом обновлении.
Новый драйвер также устраняет мерцание цветов при запуске Grand Theft Auto IV и графические заикания при игре в DOOM Eternal. Наконец, DOTA 2 теперь запускается, если в системе установлен Radeon Vulkan ray-tracing.
Майкл Ларабель с сайта Phoronix также отмечает, что оптимизация ускорения была сделана для игр под Windows, запускаемых Linux в экосистеме Steam Play компанией Valve при помощи DXVK и VKD3D-Proton.
Драйвер AMDVLK совместим со следующими сериями видеокарт AMD:
- Radeon RX 6900/6800/6700/6600/6500 Series
- Radeon RX 5700/5600/5500 Series
- Radeon RX Vega Series
- Radeon RX 400/500 Series
- Radeon Pro WX 9100, x200 Series
- Radeon Pro W5700/W5500 Series
Драйвер AMD Vulkan совместим с дистрибутивами Ubuntu и Redhat, но не был официально протестирован на других версиях. Компания предупреждает пользователей, что они могут свободно использовать драйвер на других дистрибутивах, но результаты могут отличаться.
Чтобы загрузить новейший AMDVLK v-2022.Q4.3 от AMD, вы можете найти инструкции и файл загрузки здесь, на странице GitHub компании.
AMD has published few days ago a graphics driver for Radeon-based graphics cards on Windows 10 and Windows 11. Adrenalin 22.2.1 is the first public driver with Vulkan 1.3 support. This driver brings the following changes:
Support For
– Dying Light 2
– Lost Ark
– Vulkan 1.3 and Vulkan Roadmap 2022. Click here for more information.Fixed Issues
– On some AMD Graphics Products such as Radeon RX 6700 XT Graphics, some users may observe flashing colored lights around their character when playing Fortnite using DirectX 12.
Update: Adrenalin 22.2.2
Support For
– Total War: Warhammer III
– AMD Smart Access Memory optimizations for AMD Ryzen processors with integrated graphics paired with discrete Radeon graphics can be found below:
. Up to 24% increase in performance in Assassin’s Creed Valhalla @ 1080p Ultra High settings, using Radeon Software Adrenalin 22.2.2 on the Ryzen 9 5900HX and Radeon RX 6800M, versus the previous software driver version 22.2.1.
. Up to 23% increase in performance in Battlefield 5 @ 1080p Ultra settings, using Radeon Software Adrenalin 22.2.2 on the Ryzen 7 5800H and Radeon RX 6600M, versus the previous software driver version 22.2.1.
. Up to 18% increase in performance in Borderlands 3 @ 1080p Badass settings, using Radeon™ Software Adrenalin 22.2.2 on the Ryzen 9 5900HX and Radeon RX 6800M, versus the previous software driver version 22.2.1.
. Up to 17% increase in performance in F1 2021 @ 1080p Ultra High settings, using Radeon™ Software Adrenalin 22.2.2 on the Ryzen 7 5800H and Radeon RX 6600M, versus the previous software driver version 22.2.1.
. Up to 12% increase in performance in Gears 5 @ 1080p High settings, using Radeon™ Software Adrenalin 22.2.2 on the Ryzen 7 5800H and Radeon RX 6600M, versus the previous software driver version 22.2.1.
. Up to 11% increase in performance in Fortnite @ 1080p Ultra settings, using Radeon™ Software Adrenalin 22.2.2 on the Ryzen 7 5800H and Radeon RX 6600M, versus the previous software driver version 22.2.1.
. Up to 10% increase in performance in Cyberpunk 2077 @ 1080p Ultra settings, using Radeon™ Software Adrenalin 22.2.2 on the Ryzen 9 5900HX and Radeon RX 6800M, versus the previous software driver version 22.2.1.
Radeon Software Adrenalin Downloads
- latest version for win10/win11 64-bit @ Geeks3D
- v22.2.2 downloads + release notes @ AMD
- v22.2.1 downloads + release notes @ AMD
Quick driver information
Adrenalin 22.2.1
Adrenalin 22.2.2
OpenGL support
Adrenalin 22.2.1
Adrenalin 22.2.1 exposes OpenGL 4.6 and 330 extensions for a Radeon RX 6800 XT. This support is similar to Adrenalin 21.5.2.
- GL_VENDOR: ATI Technologies Inc. - GL_RENDERER: AMD Radeon RX 6800 XT - GL_VERSION: 4.6.14802 Compatibility Profile/Debug Context 22.2.1 30.0.14023.7007 - GL_SHADING_LANGUAGE_VERSION: 4.60 - OpenGL Extensions: 330 extensions (GL=305 and WGL=25)
Adrenalin 22.2.2
Adrenalin 22.2.2 exposes OpenGL 4.6 and 330 extensions for a Radeon RX 6800 XT. This support is similar to Adrenalin 21.5.2.
- GL_VENDOR: ATI Technologies Inc. - GL_RENDERER: AMD Radeon RX 6800 XT - GL_VERSION: 4.6.14802 Compatibility Profile/Debug Context 22.2.2 30.0.14029.1011 - GL_SHADING_LANGUAGE_VERSION: 4.60 - OpenGL Extensions: 330 extensions (GL=305 and WGL=25)
Vulkan support
Adrenalin 22.2.1
Adrenalin 22.2.1 exposes Vulkan 1.3.203 API for a Radeon RX 6800 XT on Windows 10/11. The following new device extensions have been added:
– VK_KHR_global_priority
– VK_KHR_maintenance4
– VK_EXT_depth_clip_control
– VK_EXT_global_priority_query
– VK_EXT_provoking_vertex
- [ device 0 ] - name: AMD Radeon RX 6800 XT - deviceID: 1002-73BF (4098-29631) - API version (raw): 4206795 - API version: 1.3.203 - # of extensions: 141 VK_KHR_16bit_storage VK_KHR_8bit_storage VK_KHR_acceleration_structure VK_KHR_bind_memory2 VK_KHR_buffer_device_address VK_KHR_copy_commands2 VK_KHR_create_renderpass2 VK_KHR_dedicated_allocation VK_KHR_deferred_host_operations VK_KHR_depth_stencil_resolve VK_KHR_descriptor_update_template VK_KHR_device_group VK_KHR_draw_indirect_count VK_KHR_driver_properties VK_KHR_dynamic_rendering VK_KHR_external_fence VK_KHR_external_fence_win32 VK_KHR_external_memory VK_KHR_external_memory_win32 VK_KHR_external_semaphore VK_KHR_external_semaphore_win32 VK_KHR_format_feature_flags2 VK_KHR_fragment_shading_rate VK_KHR_get_memory_requirements2 VK_KHR_global_priority VK_KHR_imageless_framebuffer VK_KHR_image_format_list VK_KHR_maintenance1 VK_KHR_maintenance2 VK_KHR_maintenance3 VK_KHR_maintenance4 VK_KHR_multiview VK_KHR_pipeline_executable_properties VK_KHR_pipeline_library VK_KHR_ray_query VK_KHR_ray_tracing_pipeline VK_KHR_relaxed_block_layout VK_KHR_sampler_mirror_clamp_to_edge VK_KHR_sampler_ycbcr_conversion VK_KHR_separate_depth_stencil_layouts VK_KHR_shader_atomic_int64 VK_KHR_shader_clock VK_KHR_shader_draw_parameters VK_KHR_shader_float16_int8 VK_KHR_shader_float_controls VK_KHR_shader_integer_dot_product VK_KHR_shader_non_semantic_info VK_KHR_shader_subgroup_extended_types VK_KHR_shader_subgroup_uniform_control_flow VK_KHR_shader_terminate_invocation VK_KHR_spirv_1_4 VK_KHR_storage_buffer_storage_class VK_KHR_swapchain VK_KHR_swapchain_mutable_format VK_KHR_synchronization2 VK_KHR_timeline_semaphore VK_KHR_uniform_buffer_standard_layout VK_KHR_variable_pointers VK_KHR_vulkan_memory_model VK_KHR_win32_keyed_mutex VK_KHR_zero_initialize_workgroup_memory VK_EXT_4444_formats VK_EXT_border_color_swizzle VK_EXT_calibrated_timestamps VK_EXT_color_write_enable VK_EXT_conditional_rendering VK_EXT_conservative_rasterization VK_EXT_custom_border_color VK_EXT_depth_clip_control VK_EXT_depth_clip_enable VK_EXT_depth_range_unrestricted VK_EXT_descriptor_indexing VK_EXT_extended_dynamic_state VK_EXT_extended_dynamic_state2 VK_EXT_external_memory_host VK_EXT_full_screen_exclusive VK_EXT_global_priority VK_EXT_global_priority_query VK_EXT_hdr_metadata VK_EXT_host_query_reset VK_EXT_image_robustness VK_EXT_image_view_min_lod VK_EXT_index_type_uint8 VK_EXT_inline_uniform_block VK_EXT_line_rasterization VK_EXT_load_store_op_none VK_EXT_memory_budget VK_EXT_memory_priority VK_EXT_pageable_device_local_memory VK_EXT_pipeline_creation_cache_control VK_EXT_pipeline_creation_feedback VK_EXT_post_depth_coverage VK_EXT_primitive_topology_list_restart VK_EXT_private_data VK_EXT_provoking_vertex VK_EXT_queue_family_foreign VK_EXT_robustness2 VK_EXT_sampler_filter_minmax VK_EXT_sample_locations VK_EXT_scalar_block_layout VK_EXT_separate_stencil_usage VK_EXT_shader_atomic_float VK_EXT_shader_atomic_float2 VK_EXT_shader_demote_to_helper_invocation VK_EXT_shader_image_atomic_int64 VK_EXT_shader_stencil_export VK_EXT_shader_subgroup_ballot VK_EXT_shader_subgroup_vote VK_EXT_shader_viewport_index_layer VK_EXT_subgroup_size_control VK_EXT_texel_buffer_alignment VK_EXT_tooling_info VK_EXT_transform_feedback VK_EXT_vertex_attribute_divisor VK_EXT_ycbcr_image_arrays VK_AMD_buffer_marker VK_AMD_calibrated_timestamps VK_AMD_device_coherent_memory VK_AMD_display_native_hdr VK_AMD_draw_indirect_count VK_AMD_gcn_shader VK_AMD_gpa_interface VK_AMD_gpu_shader_half_float VK_AMD_gpu_shader_int16 VK_AMD_memory_overallocation_behavior VK_AMD_mixed_attachment_samples VK_AMD_negative_viewport_height VK_AMD_pipeline_compiler_control VK_AMD_shader_ballot VK_AMD_shader_core_properties VK_AMD_shader_core_properties2 VK_AMD_shader_explicit_vertex_parameter VK_AMD_shader_fragment_mask VK_AMD_shader_image_load_store_lod VK_AMD_shader_info VK_AMD_shader_trinary_minmax VK_AMD_texture_gather_bias_lod VK_AMD_wave_limits VK_GOOGLE_decorate_string VK_GOOGLE_hlsl_functionality1 VK_GOOGLE_user_type - memory heaps: 3 - heap 1: 16112 kB - heap 2: 7908 kB - heap 3: 256 kB - Features (55) -> robustBufferAccess: 1 -> fullDrawIndexUint32: 1 -> imageCubeArray: 1 -> independentBlend: 1 -> geometryShader: 1 -> tessellationShader: 1 -> sampleRateShading: 1 -> dualSrcBlend: 1 -> logicOp: 1 -> multiDrawIndirect: 1 -> drawIndirectFirstInstance: 1 -> depthClamp: 1 -> depthBiasClamp: 1 -> fillModeNonSolid: 1 -> depthBounds: 1 -> wideLines: 1 -> largePoints: 1 -> alphaToOne: 0 -> multiViewport: 1 -> samplerAnisotropy: 1 -> textureCompressionETC2: 0 -> textureCompressionASTC_LDR: 0 -> textureCompressionBC: 1 -> occlusionQueryPrecise: 1 -> pipelineStatisticsQuery: 1 -> vertexPipelineStoresAndAtomics: 1 -> fragmentStoresAndAtomics: 1 -> shaderTessellationAndGeometryPointSize: 1 -> shaderImageGatherExtended: 1 -> shaderStorageImageExtendedFormats: 1 -> shaderStorageImageMultisample: 1 -> shaderStorageImageReadWithoutFormat: 1 -> shaderStorageImageWriteWithoutFormat: 1 -> shaderUniformBufferArrayDynamicIndexing: 1 -> shaderSampledImageArrayDynamicIndexing: 1 -> shaderStorageBufferArrayDynamicIndexing: 1 -> shaderStorageImageArrayDynamicIndexing: 1 -> shaderClipDistance: 1 -> shaderCullDistance: 1 -> shaderFloat64: 1 -> shaderInt64: 1 -> shaderInt16: 1 -> shaderResourceResidency: 1 -> shaderResourceMinLod: 1 -> sparseBinding: 1 -> sparseResidencyBuffer: 1 -> sparseResidencyImage2D: 1 -> sparseResidencyImage3D: 1 -> sparseResidency2Samples: 0 -> sparseResidency4Samples: 0 -> sparseResidency8Samples: 0 -> sparseResidency16Samples: 0 -> sparseResidencyAliased: 1 -> variableMultisampleRate: 1 -> inheritedQueries: 1 - Limits (106) -> maxImageDimension1D: 16384 -> maxImageDimension2D: 16384 -> maxImageDimension3D: 8192 -> maxImageDimensionCube: 16384 -> maxImageArrayLayers: 8192 -> maxTexelBufferElements: 4294967295 -> maxUniformBufferRange: 4294967295 -> maxStorageBufferRange: 4294967295 -> maxPushConstantsSize: 128 -> maxMemoryAllocationCount: 4096 -> maxSamplerAllocationCount: 1048576 -> bufferImageGranularity: 1 -> sparseAddressSpaceSize: 17562121273344 -> maxBoundDescriptorSets: 32 -> maxPerStageDescriptorSamplers: 4294967295 -> maxSamplerAllocationCount: 4294967295 -> maxPerStageDescriptorStorageBuffers: 4294967295 -> maxPerStageDescriptorSampledImages: 4294967295 -> maxPerStageDescriptorStorageImages: 4294967295 -> maxPerStageDescriptorInputAttachments: 4294967295 -> maxPerStageResources: 4294967295 -> maxDescriptorSetSamplers: 4294967295 -> maxDescriptorSetUniformBuffers: 4294967295 -> maxDescriptorSetUniformBuffersDynamic: 8 -> maxDescriptorSetStorageBuffers: 4294967295 -> maxDescriptorSetStorageBuffersDynamic: 8 -> maxDescriptorSetSampledImages: 4294967295 -> maxDescriptorSetStorageImages: 4294967295 -> maxDescriptorSetInputAttachments: 4294967295 -> maxVertexInputAttributes: 64 -> maxVertexInputBindings: 32 -> maxVertexInputAttributeOffset: 4294967295 -> maxVertexInputBindingStride: 16383 -> maxVertexOutputComponents: 128 -> maxTessellationGenerationLevel: 64 -> maxTessellationPatchSize: 32 -> maxTessellationControlPerVertexInputComponents: 128 -> maxTessellationControlPerVertexOutputComponents: 128 -> maxTessellationControlPerPatchOutputComponents: 120 -> maxTessellationControlTotalOutputComponents: 4096 -> maxTessellationEvaluationInputComponents: 128 -> maxTessellationEvaluationOutputComponents: 128 -> maxGeometryShaderInvocations: 127 -> maxGeometryInputComponents: 128 -> maxGeometryOutputComponents: 128 -> maxGeometryOutputVertices: 1023 -> maxGeometryTotalOutputComponents: 4095 -> maxFragmentInputComponents: 128 -> maxFragmentOutputAttachments: 8 -> maxFragmentDualSrcAttachments: 1 -> maxFragmentCombinedOutputResources: 4294967295 -> maxComputeSharedMemorySize: 65536 -> maxComputeSharedMemorySize: [65535 ; 65535 ; 65535] -> maxComputeWorkGroupInvocations: 1024 -> maxComputeWorkGroupSize: [1024 ; 1024 ; 1024] -> subPixelPrecisionBits: 8 -> subTexelPrecisionBits: 8 -> mipmapPrecisionBits: 8 -> maxDrawIndexedIndexValue: 4294967295 -> maxDrawIndirectCount: 4294967295 -> maxSamplerLodBias: 15.996094 -> maxSamplerAnisotropy: 16.000000 -> maxViewports: 16 -> maxViewportDimensions: [16384 ; 16384] -> viewportBoundsRange: [-32768.000000 ; 32767.000000] -> viewportSubPixelBits: 8 -> minMemoryMapAlignment: 64 -> minTexelBufferOffsetAlignment: 4 -> minUniformBufferOffsetAlignment: 16 -> minStorageBufferOffsetAlignment: 4 -> minTexelOffset: -64 -> maxTexelOffset: 63 -> minTexelGatherOffset: -32 -> maxTexelGatherOffset: 31 -> minInterpolationOffset: -2.000000 -> maxInterpolationOffset: 1.000000 -> subPixelInterpolationOffsetBits: 8 -> maxFramebufferWidth: 16384 -> maxFramebufferHeight: 16384 -> maxFramebufferLayers: 8192 -> framebufferColorSampleCounts: 15 -> framebufferDepthSampleCounts: 15 -> framebufferStencilSampleCounts: 15 -> framebufferNoAttachmentsSampleCounts: 15 -> maxColorAttachments: 8 -> sampledImageColorSampleCounts: 15 -> sampledImageIntegerSampleCounts: 15 -> sampledImageDepthSampleCounts: 15 -> sampledImageStencilSampleCounts: 15 -> storageImageSampleCounts: 15 -> maxSampleMaskWords: 1 -> timestampComputeAndGraphics: 1 -> timestampPeriod: 10.000000 -> maxClipDistances: 8 -> maxCullDistances: 8 -> maxCombinedClipAndCullDistances: 8 -> discreteQueuePriorities: 2 -> pointSizeRange: [0.000000 ; 8191.875000] -> lineWidthRange: [0.000000 ; 8191.875000] -> pointSizeGranularity: 0.125000 -> lineWidthGranularity: 0.125000 -> strictLines: 0 -> standardSampleLocations: 1 -> optimalBufferCopyOffsetAlignment: 1 -> optimalBufferCopyRowPitchAlignment: 1 -> nonCoherentAtomSize: 128 - VK_KHR_driver_properties -> driverName: AMD proprietary driver -> driverID: VK_DRIVER_ID_AMD_PROPRIETARY_KHR -> driverInfo: 22.2.1 -> conformanceVersion: 1.3.0.0 - VK_AMD_shader_core_properties -> shaderEngineCount: 4 -> shaderArraysPerEngineCount: 2 -> computeUnitsPerShaderArray: 10 -> simdPerComputeUnit: 2 -> wavefrontsPerSimd: 16 -> sgprsPerSimd: 2048 -> minSgprAllocation: 128 -> maxSgprAllocation: 104 -> sgprAllocationGranularity: 128 -> vgprsPerSimd: 1024 -> minVgprAllocation: 16 -> maxVgprAllocation: 256 -> vgprAllocationGranularity: 16
Adrenalin 22.2.2
Adrenalin 22.2.2 exposes Vulkan 1.3.203 API for a Radeon RX 6800 XT on Windows 10/11. Same support than Adrenalin 22.2.1.
- name: AMD Radeon RX 6800 XT - deviceID: 1002-73BF (4098-29631) - API version (raw): 4206795 - API version: 1.3.203 - # of extensions: 141
—
via (v22.2.1)
via (v22.2.2)
Posted at May 13, 2025 by PCI-DB Team
Install Driver Automatically
Device Name | AMD Radeon Graphics Vulkan Driver 16.15.2401.1001 Beta |
---|---|
Category | Graphics Board |
Manufacturer | AMD |
File Size | 221.3 MB |
Supported OS | Windows 7 ,Windows 8.1 ,Windows 10 |
AMD Radeon Graphics Vulkan Driver 16.15.2401.1001 Beta Description
Highlights:
— PowerXpress Systems — Added Vulkan Support
— The Talos Principle — Potential version compatibility issues addressed
— Hologram — No longer crashes on launch
Important Notes:
— Product is conformant with Vulkan 1.0 Specification.
— This product is based on a published Khronos specification but has not yet passed the Khronos Conformance Test Process. A fully conformant implementation of the Vulkan API will be included in a forthcoming Radeon Software release.
— This driver is intended as beta level support for use solely with Vulkan applications and as such some Radeon Software functionality has been removed. This is including and not limited to support for other Graphics APIs, Radeon Settings and other Radeon Software driver features.
What is Vulkan?
— As a complement to OpenGL, descended from AMD’s Mantle, and forged by the industry, Vulkan is a powerful low-overhead graphics API that gives software developers deep control over the performance, efficiency, and capabilities of Radeon GPUs and multi-core CPUs.
NOTE:
— This driver is not intended for use on AMD products running in Apple Boot Camp platforms. Users of these platforms should contact their system manufacturer for driver support.
— When installing the AMD Radeon Software Beta for Vulkan on the Windows operating system, the user must be logged on as Administrator, or have Administrator rights to complete the installation of the AMD Radeon Software Beta for Vulkan.
— The AMD Radeon Software Beta for Vulkan requires Windows 7 Service Pack 1 to be installed.
AMD Desktop Product Family Compatibility:
— AMD Radeon R9 Fury Series Graphics
— AMD Radeon R9 Nano Series Graphics
— AMD Radeon R9 300 Series Graphics
— AMD Radeon R9 200 Series Graphics
— AMD Radeon R7 300 Series Graphics
— AMD Radeon R7 200 Series Graphics
— AMD Radeon HD 8500 — HD 8900 Series Graphics
— AMD Radeon HD 7700 — HD 7900 Series Graphics
AMD APU Product Family Compatibility:
AMD APU series codenamed «Kaveri», «Godavari» and «Carrizo» are only supported by AMD Radeon Software Beta for Vulkan on Windows 7 (32 & 64-bit), Windows 8.1 (64-bit) and Windows 10 (64-bit).AMD APU Product Family Compatibility
Desktop:
— AMD A-Series APUs with Radeon R4, R5, R6, or R7 Graphics
— AMD Pro A-Series APUs with Radeon R5 or R7 Graphics
— AMD Athlon Series APUs with Radeon R3 Graphics
— AMD Sempron Series APUs with Radeon R3 Graphics
— AMD A-Series APUs with Radeon R3, R4, R5, R6, R7, or R8 Graphics
Mobile:
— AMD Pro A-Series APUs with Radeon R5, R6, or R7 Graphics
— AMD FX-Series APUs with Radeon R7 Graphics
— AMD E-Series APUs with Radeon R2 Graphics
— AMD Radeon HD 8180 — HD 8400 Series Graphics
AMD Mobility Radeon Family Compatibility:
— AMD Radeon R9 M300 Series Graphics
— AMD Radeon R7 M300 Series Graphics
— AMD Radeon R5 M300 Series Graphics
— AMD Radeon R9 M200 Series Graphics
— AMD Radeon R7 M200 Series Graphics
— AMD Radeon R5 M200 Series Graphics
— AMD Radeon HD 8500M — HD 8900M Series Graphics
— AMD Radeon HD 7700M — HD 7900M Series Graphics
Known Issues:
— Some AMD PowerXpress systems may experience instability
— Windows re-sizing in some applications may cause an application crash
— HDMI and DP to DVI adapters on Windows 7 may intermittently cause display issues
AMD Issue Reporting Form:
— This driver release incorporates suggestions received through the AMD Issue Reporting Form. To provide us with your feedback, visit the AMD Issue Reporting Form.
How-To Uninstall AMD Radeon Software:
— Start by opening the Control Panel
— For Windows 10/8.1, right-click on the Windows button and select Control Panel from the Context Menu
— For Windows 7, click on the Windows button and select Control Panel from the Start Menu
— In the Control Panel select Programs and Features
— Select AMD Install Manager and then click Uninstall/Change
— Check all items, and then click the Uninstall button.
— Note: If you had others versions of AMD drivers installed previously, you should get an additional prompt providing the options to remove All Versions or Current Version.
— Select All Versions to remove all AMD drivers and application components (recommended).
— Select Current Version will uninstall only the latest version of the drivers and its related components.
— The uninstall process will begin removing drivers and software components.
— Select Restart Now to complete the uninstallation process.
— To verify that the AMD Radeon Software has been removed from the system, return to the Program and Features list, and check that there are no AMD entries. If AMD specific entries are still listed, remove them using the above process.
How-To Install AMD Radeon Software:
— Ensure that any existing versions of AMD Radeon Software on the system have been uninstalled before proceeding with installing a new driver.
— Close all opened applications including anti-virus, firewall, remote-access, or webcam software before attempting the install process.
— Double-click the downloaded file and select Install to begin file extraction process.
— Note: It is recommended to use the default destination folder for installation.
— Select the desired components or keep default selection (recommended) and click Install.
— The drivers and software components will begin installing.
— Note: The screen will flicker whilst the AMD Radeon Software is being installed. If you have multiple displays, some of them may turn black for a few seconds.
— Once the drivers and software have been successfully installed, choose Restart Now
— Note: A system restart is required to complete the installation process.
About Graphics Drivers:
While installing the graphics driver allows the system to properly recognize the chipset and the card manufacturer, updating the video driver can bring about various changes.
It can improve the overall graphics experience and performance in either games or various engineering software applications, include support for newly developed technologies, add compatibility with newer GPU chipsets, or resolve different problems that might have been encountered.
When it comes to applying this release, the installation steps should be a breeze, as each manufacturer tries to make them as easy as possible so that each user can update the GPU on their own and with minimum risks (however, check to see if this download supports your graphics chipset).
Therefore, get the package (extract it if necessary), run the setup, follow the on-screen instructions for a complete and successful installation, and make sure you reboot the system so that the changes take effect.
That being said, download the driver, apply it on your system, and enjoy your newly updated graphics card. Moreover, check with our website as often as possible in order to stay up to speed with the latest releases.
It is highly recommended to always use the most recent driver version available.
Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.
Related AMD Drivers
-
MerolaC
Ancient Guru- Messages:
- 4,667
- Likes Received:
- 1,361
- GPU:
https://www.amd.com/en/support/kb/release-notes/rn-rad-win-23-10-01-41-vlk-extn
Highlights
Support for additional Vulkan® extensions- VK_KHR_cooperative_matrix for Radeon™ RX 7000 series
- VK_KHR_ray_tracing_position_fetch for Radeon™ RX 6000 and newer series
- VK_KHR_video_decode_h264
- VK_KHR_video_decode_h265
- VK_KHR_video_decode_queue
- VK_KHR_video_queue
- VK_EXT_device_address_binding_report
- VK_VALVE_mutable_descriptor_type
- VK_EXT_mutable_descriptor_type
- VK_EXT_dynamic_rendering_unused_attachments
Fixed issues
- Certain virtual reality games or applications may encounter suboptimal performance or occasional stuttering on Radeon™ RX 7000 series GPUs.
- Application crash or driver timeout may be observed during playback of AV1 video content using DaVinci Resolve™ Studio.
- Improvements to high idle power when using select high-resolution and high refresh rate displays on Radeon™ RX 7000 series GPUs.
Known issues
- Application crash may be intermittently observed while playing RuneScape™ on some AMD Graphics Products, such as the Radeon™ RX 5700 XT.
- Intermittent corruption may be observed after switching windows while play Nioh 2™ on some AMD Graphics Products, such as the Radeon™ RX 6800 XT.
Thanks to @buzarini for the heads up.
-
buzarini
Active Member- Messages:
- 92
- Likes Received:
- 68
- GPU:
I have a problem with this driver. In chromium-like browsers, micro freezes of the system occur. This issue occurred with driver 31.0.22000.11008.
Disabling hardware acceleration helped. The firefox browser does not have this problem. Version 23.5.2 does not have this problem.I found a post on the microsoft site. This person describes the same problem.
Microsoft Edge造成系统异常卡顿 — Microsoft Community -
Finally a useful 7900 driver!
Driver Version — 23.10.01.41-230614a-392850E-KB-AMD-Software-Adrenalin-Edition
AMD Windows Driver Version — 31.0.21001.41000
Direct3D API Version — 12.2
Vulkan™ API Version — 1.3.250
OpenCL™ API Version — 2.0
OpenGL® API Version — 4.6
Direct3D® Driver Version — 9.14.10.01526
Vulkan™ Driver Version — 2.0.270
OpenCL® Driver Version — 31.0.21001.14018
OpenGL® Driver Version — 23.06.230411_6f40c97
2D Driver Version — 8.1.1.1634
UI Version — 2023.0614.1528.1980
AMD Audio Driver Version — 10.0.1.27It has the new OpenGL driver with 323 extensions as the Adrenalin 23.5.1 for 7600 cards. At the same time, it has the newest Vulkan module.
This driver has ReLive functionality which was missing in the previous Adrenalin Edition 23.10.01.14 for DirectX®12 Agility SDK — GPU Work Graphs.The driver has the same new UMD modules as the 7600 driver:
AMD DX12 UMD Version:8.18.10.0474
AMD DX10/DX11 UMD Version:8.17.10.0050
AMD DX9 UMD Version:8.14.10.0244OpenCL 2.1 AMD-APP (3570.0) — the same as UWP.
The MFT module is 1.4.30 (only UWP has 1.4.31)
The metrics overlay works fine.
No HAGS support as we expected. Maybe 23.6.1?
As a bonus — this driver has DirectML optimization for Stable Diffusion 1.5 from 23.5.2.
Last edited: Jun 27, 2023
-
Macer
Maha Guru- Messages:
- 1,108
- Likes Received:
- 1,177
- GPU:
If you prefer HAGS feature, you can choose NVIDIA.
The AMD driver has no feature requirements for HAGS. Maybe when FSR 3.0 is officially launched we will see HAGS available. -
Also contains the RAM consumption fix for TLOU shader compile, so I guess this is probably 23.10 branch with all fixes + other improvements for everyone (or so I hope).
Vsync on with Vulkan is still garbage at certain fps under full GPU load vs. vsync off:
I guess they’ll never fix that. Somehow it’s beyond AMD’s Vulkan driver team’s comprehension how correct vsync with fps below refresh rate works. This is btw. with VRR, so even if the game screwed up backbuffer config, frame time graph should always be a flat line (as it is with Nvidia)…
Maybe post this on Reddit? Reported it months ago, of course nothing happened.
Last edited: Jun 27, 2023
-
Cp0
Ancient Guru- Messages:
- 1,639
- Likes Received:
- 339
- GPU:
If nagged for months until they acknowledged issue with valheim and it was easily avoidable issue like running the game in directx instead which took 1 and half year from the day they recognized the existance of the issue, they simply copy pasted my bug report and work around and then fixed it early this year, i would not have any hope of them reading bug reports if been reporting sons of the forest issue for few months already.
Maybe if could get like 100 people to do the same bug report at same time it popups on their radar as they probably skiping over bug reports right now or automaticly ignoring old reports that have less reports.
With the market share AMD has they will simply just ignore all bug reports until people complain on reddit.
-
good11
Member- Messages:
- 27
- Likes Received:
- 27
- GPU:
I already tested with RX 7900 XTX with Mi 34 Monitor at 144 Hz,
It still has problems with high idle power from the spike of the VRAM clock. (80W+)
But the VRAM clock now more often decreases lower than 909 MHz resulting in 10-30W idle power consumption from 50W+ with 144 Hz. -
Driver also contains HW RT support for HIP in Blender 3.6, it’s 2:57min vs. 3:25min for barbershop demo on 6700 XT. I guess difference would be a bit bigger when not including fixed preparation period.
-
I have no problem with power consumption in IDLE. With this driver, it’s just 6W (10 with modified UWP). The monitor is 75Hz. Recently I had a TV (60Hz) connected as a second monitor and I had no problems as well.
But 7900 XT cards are not so greedy as XTX’s.
-
shm0
Master Guru- Messages:
- 249
- Likes Received:
- 54
- GPU:
lav filters, 16-235 to 0-255 conversion seem broken with these.
-
That’d be weird, is this likely is some most simple shader, or something like that.
Makes me wonder why you even use it, as it usually is just a workaround. -
shm0
Master Guru- Messages:
- 249
- Likes Received:
- 54
- GPU:
Most videos are limited color range but my display is running full rgb.
Without it, colors look washed out.
Well, mpc-hc has a build in shader to convert the colors range.
I will use this for the time being. -
Every video renderer by default converts limited range video to full range RGB without manual intervention if your output is full range (and I guess also otherwise), something apparently isn’t configured right at your end.
-
shm0
Master Guru- Messages:
- 249
- Likes Received:
- 54
- GPU:
Well yes and it was working correctly before.
//edit
the «normal» evr renderer in mpc-hc doesn’t seem to have this problem.
but the custom evr and also madvr output the wrong levels now.
weird. -
The normal EVR Render is already outdated. The new «normal» D3D11 renderer works fine with limited color range videos.
With PotPlayer this option of LAV Video filter doesn’t work. At least doesn’t change the colors at all. I have no idea if, with the older driver, the situation is the same.
But the similar option in PotPlayer works fine:
Last edited: Jun 27, 2023
-
LCA
Active Member- Messages:
- 92
- Likes Received:
- 51
- GPU:
I installed these drivers on my i9-13900/Z790 with Sapphire Nitro+ RX 7900 XTX PC after wiping out the UWP drivers\software with DDU.
I frankly found them underwhelming performance wise. Running the Aida64 Extreme GPGPU benchmark the raw numbers weren’t great. In Superposition the benchmark score was down on UWP and 23.5.2 scores. In 3Dmark Timespy the score was half of what it should have been.
So I’ve gone back to the UWP’s available via Windows Update (Windows 11 Release Preview Channel build 22621.1928).
-
Forgive my ignorance, but is this a beta/preview driver? Confused by the version numbering since it doesn’t follow typical Yr.Mo.DriverRelease#.
-
MerolaC
Ancient Guru- Messages:
- 4,667
- Likes Received:
- 1,361
- GPU:
Yes, something like that.
Don’t really know how to categorize it.
You can say it’s a in between normal release and preview.
The Vulkan extensions should, luckily, be included in the next driver. -
Macer
Maha Guru- Messages:
- 1,108
- Likes Received:
- 1,177
- GPU:
June 27, 2023—KB5027303 (OS Build 22621.1928) added *This update addresses an issue that might affect your computer when you are playing a game. Timeout Detection and Recovery (TDR) errors might occur.
June 27, 2023—KB5027303 (OS Build 22621.1928) Preview — Microsoft Support
I since update to KB5027303, The RDR2 does not have CTD.
My card id RX7600, AMD Driver 23.10.01.41
EDK-Rise and MerolaC like this.
-
WHQL and this will be the thing
Share This Page