Sildur's Enhanced WAR Shaders v6.0: DX11, DX12, OpenGL, Vulkan (January 31, 2023)

[Kalt]

Hello .

I'm actually using telperien method with reshade 3.1 and 64 bits exe.

I assume the old warhammer sildur profile 1.0 don't work in this condition ?

What i have to do , should i delete the old files ?
If yes , wich files i have to delete ?

Another question is it possible to keep reshade 3.1 and simply use the new sildur profile on nvidia inspector ?

[Telperien]

That's great update Sildurs. Some ppl here had problems with toggling reshade3. That's perfect solution for them. Does it mean now are available modifications via enb ini file?

[Sildur]

Hello .

I'm actually using telperien method with reshade 3.1 and 64 bits exe.

I assume the old warhammer sildur profile 1.0 don't work in this condition ?

What i have to do , should i delete the old files ?
If yes , wich files i have to delete ?

Another question is it possible to keep reshade 3.1 and simply use the new sildur profile on nvidia inspector ?

You can just import the new nvidia profile and it will work with the 64bit exe. No need to update reshade unless you want to.

That's great update Sildurs. Some ppl here had problems with toggling reshade3. That's perfect solution for them. Does it mean now are available modifications via enb ini file?

I don't use the full enb suite, just it's generic injector, so nothing to mess with on the enb side. If you want to add more shaders to reshade just place them in reshade\shaders and reshade\textures and edit the profile ingame with shift+f2.

[Sildur]

Reuploaded the reshade pack, apparently there was an issue with the path to the config files and shaders. Should load correctly now.

[Kalt]

A quick question.
After using the profile on nvidia inspector , the anti aliasing/ anisotropic filtering/ ambient occlusion work great.
But i have sometimes like a grilling on my screen.
Is this normal ?
Any way to solve this issue ?
Thanks in advance.

[Kalt]

Ok , so after changing the settings for ambiant occlusion compatibility from Demigods to Diablo 3 , the problem is solved.

[Sildur]

Ok , so after changing the settings for ambiant occlusion compatibility from Demigods to Diablo 3 , the problem is solved.

Nice find, the diablo 3 flag even seems to work a little better.

[saupreusse]

Ok , so after changing the settings for ambiant occlusion compatibility from Demigods to Diablo 3 , the problem is solved.

Nice find, the diablo 3 flag even seems to work a little better.

I always asked myself if it was possible to have a max distance for ao. Kinda annoying that it goes so far into distance

[Sildur]

Some of you might noticed that enbinjector sometimes fails to hook the game correctly. So another update time!
I'm now hooking reshade through a modified dinput8.dll file, which is used by warhammer but not present in the game folder, so the launcher won't patch it.

Delete enbinjector.exe, enbinjector.ini, enb_reshade.dll, enb_reshade.ini and the reshade folder before applying.

Code: Select all

Sildur's Enhanced Warhammer v1.0.2:
- Removed enbinjector, because it sometimes fails to hook the game correctly.
- Added modified dinput8.dll, this file is used by warhammer but not present in the game's folder by default. 
  So the launcher won't patch it. It's now used to hook reshade.

[Abubu76]

Thanks, working like a charm