Error Compiling effects

Ever since the upgrade to 5.9.1 (I think, it's been a while, and don't usually look at reshade when I turn on the game, so I don't usually remember untill I try to find new shaders) I've had errors compiling certain effects for the shaders. Noone arround me has this errors, and I know for a fact we use the same effect files. All the log says about the error is that there is an unrecognized property in each file, giving the parameters 'AdressU', 'Width', 'Height' and 'MinFilter'. I've not tampered with those files at all and I found no solution googling it.

Yukimura wrote:

I know for a fact we use the same effect files.
 

You aren't, you are using outdated effect files that have since been fixed, so just need to update those.

Ignore this, I'm not used to posting in forums and such.

You aren't, you are using outdated effect files that have since been fixed, so just need to update those.

How do I find these updated effect files then? I took them from Gshade as the exodus happened. Do I have to go back to Gshade to update them or does Reshade have effect files that work with Gshade presets too?

Most of those were originally copied from the repositories of the actual authors (which is where the ReShade setup tool sources shaders from). But if you want the convenient route, can just download and replace the full GShade collection manually from github.com/Mortalitas/GShade/tree/master again to update (Code > Download ZIP).

I've finally got time to re-download them but there is still an effect file that is not working. Just a singular one, [qUNIT_ssr.fx], again for unrecognized property 'AdressU'

github.com/martymcmodding/qUINT/blob/mas...Shaders/qUINT_ssr.fx

how do i download them and put them to my files.

Ensure that your Reshade version is up-to-date and matches your friends'. Additionally, check the shader files for any unintended modifications.

I have the exact same issue. I've tried manually downloading every fx file that doesn't compile directly from Mortalitas' repository, but it hasn't fixed the problem. Has anyone found a different solution?