Minimal package missing pre-build DLLs and sample?

[beeradmoore]

SDK v2.0.0 has a minimal package that comes in at ~125MB.
SDK v1.1.4 has a minimal package that comes in at ~450MB.

Both versions say

We offer a single minimal packaged download for this release of the FidelityFX SDK, which contains the pre-built, signed DLLs and sample library:

In the v1.1.4 SDK there is pre-built samples in the bin/ folder. Howver with v2.0.0 there is no bin/ folder, nor does there seem to be any pre-built samples. The only pre-built DLLs were amd_fidelityfx_upscaler_dx12.dll, amd_fidelityfx_framegeneration_dx12.dll, and amd_fidelityfx_loader_dx12.dll. None of these are for Vulkan, and it doesn't seem to be any amd_fidelityfx_dx12.dll and amd_fidelityfx_vk.dll for FSR 3.1.5.

Are the pre-built samples and FSR 3.1.5 no longer part of the SDK release or was this a mistake?

[sKepTiCal404]

As far as I know, FSR 4 doesn’t support the Vulkan API. That’s why even OptiScaler wasn’t able to add FSR 4 to Doom. Also, I’m not 100% sure, but maybe that DLL file contains both FSR 4 and FSR 3.1.5, so that cards which don’t support FSR 4 will fall back to FSR 3.1.5.

[beeradmoore]

The existing DLLs support FSR 3.1.X and 2.4.Y, so maybe now they contain 3 variants inside them. I'll be able to test after work.

[yuheho7749]

From https://gpuopen.com/manuals/fidelityfx_sdk2/whats-new/ documentation

Updated Components

Starting with AMD FidelityFX™ SDK 2.0.0 the effects, previously combined in amd_fidelityfx_dx12.dll, are split into multiple DLLs based on effect type. Please see Introduction to FidelityFX API for details.

PDBs are provided for the effects DLLs.

The Introduction to FidelityFX API embedded link is broken (404) but you can go to that page using the link on the left tab.

The API doc says (here is the link btw: https://gpuopen.com/manuals/fidelityfx_sdk2/getting-started/ffx-api/)

Applications previously loading amd_fidelityfx_dx12.dll (or linking with amd_fidelityfx_dx12.lib) need to load amd_fidelityfx_loader_dx12.dll (or link to amd_fidelityfx_loader_dx12.lib) instead.

Edit: Small testing update. If the game is using a dll, you can just rename the loader to amd_fidelityfx_dx12.dll.

[beeradmoore]

Thanks for the doc links. I can load amd_fidelityfx_upscaler.dll in my own tester application and query it and see it has FSR 3.1.5 and FSR 2.3.4 in it.

Edit: Small testing update. If the game is using a dll, you can just rename the loader to amd_fidelityfx_dx12.dll.

Do you mean with also adding amd_fidelityfx_upscaler.dll into the same directory where amd_fidelityfx_dx12.dll (renamed from amd_fidelityfx_loader_dx12.dll) is? I'll have some testing with it tonight after work.

EDIT: And based on that, does that also now inject FSR 4 when used with compatible hardware into FSR 3.1 supported titles or do the developers need to enable that by adding the new SDK?

[yuheho7749]

To preface, I'm running Linux, so it probably does not translate 100% to Windows.

But yes, I think I got 3.1.5 to work. Not 100% confirmed with visual quality comparisons or anything but the game Horizon Zero Dawn and Monter Hunter Wilds (benchmark) reports it as 3.1.5. File structure is replacing the old amd_fidelityfx_dx12.dll with amd_fidelityfx_loader_dx12.dll and drag and drop in amd_fidelityfx_upscaler_dx12.dll and amd_fidelityfx_framegeneration_dx12.dll alongside it.

FSR4 injection/override no longer works. I'm testing on Linux so probably Wine dll loader name is wrong or some version override problem (I'm not too familiar with how it's actually handled by Wine). Might have better luck on Windows on day 1.

Edit: Removed inaccurate info due to my poor testing.