Issue Type (Required):
Other
Issue Description (Required):
The Problem:
The AMD Adrenaline app doesn’t properly point to Darktide.exe sometimes. Most often when I check Darktide’s profile it points to Warhammer 40,000 DARKTIDE\shader_cache\darktide_shader_cache_builder.exe but I’ve also seen it point to Warhammer 40,000 DARKTIDE\launcher\CrashReporter.exe after the game crashes. Unless you manually add Darktide.exe, there’s no option to toggle FSR4 on. I’ve also seen a separate entry for GPUDetection.exe which has it’s own entry in the game list.
Usually adding darktide.exe changes it in the app but the shader cache step in the launch changes it back. This was a problem on my 7900XT and now is also a problem with my 9070XT (a card with a feature that needs this to be right to work easier). However my friend with a 6800XT has her AMD app properly point to Darktide.exe which points me to the solution.
What Fatshark probably needs to do:
Amd_ags_x64.dll, the AMD GPU services dll in the game files, is supposed to register the app in the driver and tell it what profile to use. However, the version included with the game is version 6.0.1 which only officially supports up to RDNA2 (6000 series).
Source: GitHub - GPUOpen-LibrariesAndSDKs/AGS_SDK: AMD GPU Services (AGS) library and samples
AGS 6.3 is out and adds official support for detecting RDNA4 cards. It’s only been out for a week which in most cases wouldn’t be a problem as games have been using FSR4 since the new GPUs came out 3 months ago but the way controlling the game bounces between the launcher, shader cache builder, and the main darktide.exe messes it up and Adrenaline just has to make a best guess based on what was used. Skipping the launcher apparently fixes this so this is the mostly likely case. It could also be that the other .exe files also need the same GPU profile as darktide.exe, and fair enough, but they all occupy the same entry in the AMD app.
Updating AGS manually doesn’t work like it does with the fidelityfx dll and just throws an error in the console logs: warning: [AMD_GPU_SERVICES] Failed to initialize AGS. Error code: 2. Make sure you have an up to date AMD driver. Falling back to running without AGS which means it’s up to the devs to integrate the newest version themselves (and keep it updated)
This line’s up with the documentation: AGS_SDK/ags_lib/inc/amd_ags.h at master · GPUOpen-LibrariesAndSDKs/AGS_SDK · GitHub
/// agsVersion must be specified as AGS_CURRENT_VERSION or the call will return \ref AGS_INVALID_ARGS.
My setup to make it work even when it doesn’t say it is:
Set your global gaming experience in the AMD app to default, then toggle on FSR 4 so the profile is now set as custom. I manually added Darktide.exe to make sure it showed FSR4 toggled on. If you’ve changed the setting for darktide specifically to toggle FSR4 on it’s no longer following the global profile. Now any time I boot the game, even if the AMD app points to the shader cache builder and the AMD popup in the corner on startup doesn’t list FSR4, it’s still working.
My guess based on why this works is based on AMDs GPUOpen page on app registration: AMD GPU Services (AGS): App Registration. (Devs: The AGS GPUOpen page hasn’t been updated for 6.3 yet but the Github page has)
I think what happens is: Launch game → AGS error of some kind → falls back to the last used profile or the closest match → Global profile says FSR4 on so Darktide follows that even if it doesn’t show you the option or tell you on start.
I’ll have screenshots of what my AMD app settings look like in the comments as well as examples of how you can tell it’s FSR4 or not.
Pictures included:
-The AMD app pointing to darktide.exe with the FSR4 option visible
-The AMD app pointing to the shader cache builder with no FSR4 option visible
-The AMD app entry for Darktide’s GPU detection being listed as its own game for some reason
-The AGS dll that comes with the game
[PC] Do You Use Mods? (Optional):
No, I don’t use mods
Reproduction Rate (Required):
Often (<75%)
Platform (Required):
PC - Steam
Darktide set to the global profile
You do not want this
