Radeon-ID Community Driver: Hybrid - Release Nebula 23.11.1 WHQL

I have kinda the same problem with yobawo's as my Vega 3 is read as Vega 6.
But funny enough, the Vulkan engine is still correctly read as Vega 3 per Chrome report:

Code:

<Integrated GPU> Vulkan backend - AMD Radeon(TM) Vega 3 Graphics
[Default Toggle Names]
lazy_clear_resource_on_first_use: https://crbug.com/dawn/145: Clears resource to zero on first usage. This initializes the resource so that no dirty bits from recycled memory is present in the new resource.
use_temporary_buffer_in_texture_to_texture_copy: https://crbug.com/dawn/42: Split texture-to-texture copy into two copies: copy from source texture into a temporary buffer, and copy from the temporary buffer into the destination texture when copying between compressed textures that don't have block-aligned sizes. This workaround is enabled by default on all Vulkan drivers to solve an issue in the Vulkan SPEC about the texture-to-texture copies with compressed formats. See #1005 (https://github.com/KhronosGroup/Vulkan-Docs/issues/1005) for more details.
vulkan_use_d32s8: https://crbug.com/dawn/286: Vulkan mandates support of either D32_FLOAT_S8 or D24_UNORM_S8. When available the backend will use D32S8 (toggle to on) but setting the toggle to off will make it use the D24S8 format when possible.
disallow_unsafe_apis: http://crbug.com/1138528: Produces validation errors on API entry points or parameter combinations that aren't considered secure yet.
[WebGPU Forced Toggles - enabled]
disallow_spirv: https://crbug.com/1214923: Disallow usage of SPIR-V completely so that only WGSL is used for shader modules.This is useful to prevent a Chromium renderer process from successfully sendingSPIR-V code to be compiled in the GPU process.
[Supported Features]
texture-compression-bc
pipeline-statistics-query
timestamp-query
depth-clamping
depth32float-stencil8
dawn-internal-usages
dawn-native

But D3D11 reading is incorrect:

Code:

<Integrated GPU> D3D12 backend - AMD Radeon RX Vega 6 Graphics
[Default Toggle Names]
lazy_clear_resource_on_first_use: https://crbug.com/dawn/145: Clears resource to zero on first usage. This initializes the resource so that no dirty bits from recycled memory is present in the new resource.
use_d3d12_resource_heap_tier2: https://crbug.com/dawn/27: Enable support for resource heap tier 2. Resource heap tier 2 allows mixing of texture and buffers in the same heap. This allows better heap re-use and reduces fragmentation.
use_d3d12_render_pass: https://crbug.com/dawn/36: Use the D3D12 render pass API introduced in Windows build 1809 by default. On versions of Windows prior to build 1809, or when this toggle is turned off, Dawn will emulate a render pass.
use_d3d12_residency_management: https://crbug.com/dawn/193: Enable residency management. This allows page-in and page-out of resource heaps in GPU memory. This component improves overcommitted performance by keeping the most recently used resources local to the GPU. Turning this component off can cause allocation failures when application memory exceeds physical device memory.
disallow_unsafe_apis: http://crbug.com/1138528: Produces validation errors on API entry points or parameter combinations that aren't considered secure yet.
[WebGPU Forced Toggles - enabled]
disallow_spirv: https://crbug.com/1214923: Disallow usage of SPIR-V completely so that only WGSL is used for shader modules.This is useful to prevent a Chromium renderer process from successfully sendingSPIR-V code to be compiled in the GPU process.
[Supported Features]
texture-compression-bc
pipeline-statistics-query
timestamp-query
depth24unorm-stencil8
depth32float-stencil8
dawn-internal-usages
multiplanar-formats
dawn-native

Registery key that you suggested to remove is not available to me so idk

 

Okay so that registry key made me get Gaming Drivers but it introduced something else.



I can only go for +1 and -1% on the power Limit and UV doesn't work in Afterburner

 

GPU Names doesn't matter if the game can be launched.

This Gaming Mode switch that caused missing features on Radeon Tuning too. Have to try extended overclocking mode in MSI

 

Well today I tested it again like i said, reinstalling the previous drivers and I come to the conclusion that in the past I was overriding the tessellation to x8 in amd sett and that's why I reach those max FPS... so I go back to the older drivers and run the bench with the default amd sett. but I don't know how I manage to get the score of 1460 and now I'm like 3 points below to an average of 1138

Nimez Mod v21.8.2-RSA = Direct3D11 (1119)

Nimez Mod v22.2.2-DCH = Direct3D11 (1119)

Nimez Mod v22.3.2-DCH = Direct3D11 (1138)

Nimez Mod v22.3.2-DCH = Direct3D11 (1195) With Radeon software Tessellation at x8

 

Can you provide registry screenshot like what I mean?

Because deleting these two registries can fix that problem

 

Will there be added support for amd rsr for series 500?

 

I tried to enabled and disabled but still showing 1.1 instead of 3.0
Am I doing something wrong?

 

Decima Engine is very sensitive for PCIe performance. Im playing Death Stranding Director's Cut right know and i found out Resizeable BAR Flag actually do something for PCIe in my RIG, 5th gen Intel. I tested 3DMark PCIe Test and Death Stranding. 3DMark gave me best and full stable results with enabled RBAR, but Death Stranding run very, very unstable, constant stuttering etc. After disabling RBAR results in benchmark is much worse, with major drops during test, but Death Stranding itself runs better than ever.

I recommend disable RBAR for older hardware.

 

here:

 

Tried to uninstall and reinstall V5 Dependencies?

 

Might just do a DDU install whenever 22.4.1 arrives

 

I disabled pcie idle & get that 1.1
.
After one pointed that i have to enable idle , after enable idle it gets back to 3.0 .
Check 2/3 pages back, you will find it.

 

got error missing:
api-ms-win-core-winrt-string-l1-1-0.dll missing
rx 5500 xt 4gb, ryzen 3100, windows 7 ultimate esu, wufuc.
tried anything wit ddu/reinstall etc.
googled a lot, any solution ?

LE: since min req is win10 and I am on 7 which one is latest for win7?

 

I have a laptop with an Intel i5 2450M CPU and a Radeon HD 6370M dedicated GPU. I identified that my GPU lies in the Terrascale DX11 category and downloaded the corresponding drivers.

However, I am torn between options 1 and 3. I thought my GPU fits the 3rd option (Switchable Graphics), but when installing that, I noticed it was installing a GCN GPU and a Terrascale APU, which is definitely not what I have.

I suppose this 3rd category is designed for laptops having an AMD APU + AMD dedicated GPU, but if my CPU is Intel, am I supposed to go for the first option?

 

Windows 7 isn't supported, use Windows 10 with minimum build 1903

 

Yep, the 3rd option is only for AMD APU + AMD dGPU

 

But should I be using the first one for my hardware (Intel CPU + AMD dGPU)? Or is it not supported?

 

Yes, the first choice is compatible for Intel + AMD or AMD + NVIDIA

 

Thank you very much .

 

@zingzs If I may also ask, do you think it would work well to install nIGHTmAYOR's custom Intel HD2000/3000 drivers along these? They might not be designed for switchable graphics.

https://www.tenforums.com/graphic-c...00-extreme-plus-nighmayor-12.html#post2406322