Reshade not working anymore on DOOM Eternal (Vulkan)

Doom Eternal recently received a big update that introduced official mod support - it now has a dedicated launcher (idTechLauncher) that either launches de default game or another separate executable located in a separate sandbox folder.  To access the latest version with the official mod support you have to opt in to a beta branch on Steam - this is explained at the min FAQ section in this page:  slayersclub.bethesda.net/en-US/article/d...ernal-pc-mod-preview

Reshade used to work perfectly up to this point (since 2020 when Eternal was launched).  I verified the paths and executable names in the reshade config file for the Vulkan layers, I have installed the latest Reshade version (6.2.0) and still nothing. 

Reshade still works without issue for other Vulkan apps (DOOM 2016, the Ironwail Quake 1 engine, etc). 
It seems that the Reshade Vulkan layer is disabled by the Doom Eternal application itself and I don't know how to force it back on. There also seems to be a new CVAR r_allowBlackListedLayers which by default is set to "0" and can only be set by using it as a launch parameter. However even if set to "1" the Reshade VK layer is still disabled. 

 It's kind of driving me nuts, any suggestions ? 

Thank you !
 

Also tried the manual method described in the last post of this topic: 

reshade.me/forum/troubleshooting/6153-reshade-and-vulkan

Still no luck. Rolling back (opting out of the beta that comes with the new launcher and official mod support) Doom Eternal makes Reshade work instantly. 

So it's not related to my Reshade install, they're actively blocking additional VK layers in this new / beta branch. This seems to be the future and I can't figure out how to disable this mechanism. 

Not sure why r_allowBlackListedLayers isn't hooked up properly, the game still explicitly disables the ReShade layer with it active by setting the environment variable "DISABLE_VK_LAYER_reshade_1". You can however simply change which environment variable should disable the layer, by going to C:\ProgramData\ReShade\ReShade64.json and renaming the "DISABLE_VK_LAYER_reshade_1" entry to something else, e.g. "DISABLE_VK_LAYER_reshade_2". ReShade will load successfully in DOOM afterwards, since the game still tries to disable it by setting "DISABLE_VK_LAYER_reshade_1".

First of all thank you very much ! Your solution works perfectly.
It's strange that the r_allwowBlackListedLayers isn't hooked up properly.
In the non-beta branch of the latest game version v6.66Rev3 (which has the old idTechLauncher.exe binary) the CVAR does work and setting it will disable that annoying pop-up asking to disable unsupported VK layers (namely Reshade). Only in the beta branch that has the new idTechLauncher the CVAR doesn't seem to function properly. I suspect it's a bug in the beta branch.
May I ask how you figured this out ? Where do I even start looking if I'm facing something similar in the future ? I've spent some time on this and made zero progress.
Thank you again very much for your help.
Would it be ok to post your solution also on the Steam forums ? There's a thread in the Doom Eternal Steam forums where people were asking why Reshade has stopped working.

Sure, feel free.
Regarding how I debugged it: I had first checked if the ReShade layer is recognized by the Vulkan loader in the game at all (one can set the environment variable "VK_LOADER_DEBUG" to e.g. "error,warn,info" for it to print log messages to the debug output (see github.com/KhronosGroup/Vulkan-Loader/bl...enable-layer-logging , which can e.g. be monitored with DebugView [ learn.microsoft.com/en-us/sysinternals/downloads/debugview ]). That showed that the implicit ReShade layer was in fact enumerated. And there were no errors, so the only way it could still not get loaded is when explicitly being disabled via the corresponding environment variable (every implicit Vulkan layer is required to define an environment variable that can be used to disable it). So I checked which environment variables the game sets (using Process Explorer [ learn.microsoft.com/en-us/sysinternals/d...ads/process-explorer ], by right clicking on the DOOM process > Properties > Environment) and sure enough that included "DISABLE_VK_LAYER_reshade_1", regardless of whether the CVAR was set or not. So next test was to rename that environment variable (hoping that the game doesn't query it from the layer config, but rather just has it hardcoded) and that worked.

Thank you again for taking the time to explain! I really learned a lot. I also posted the solution in the Steam thread. I will also start supporting Reshade on Patreon as of today. It's the very least I can do.   

Hi, I wanted to add a quick update as it seems that following your workaround makes DE crash and freezes the window (which doesn't allow you to alt+tab). I was wondering if this was due to the API version or the new patch rev 3.1 breaking something.

PM: This seems to happen ONLY in the mod portal preview. If not opted for the beta, the game runs both reshade and gshade normally, sadly with overly impacting performance regression, but works out of the box.

Sorry, but this no longer seems to work, either.

I've renamed the line in the json file and Reshade does load during the Bethesda logos and such but when the actual game menu loads up Reshade disappears and pressing the Home button doesn't bring it up.

Am I missing something?