4.0

Myashi wrote: Hey guys,
long time no see I want to ask if it's just me or ReShade 4.2 doesn't work with Sunset Overdrive (steam version).
I can see the greeting message, when I launch the game but as soon i press shift +F2, the gui doesn't show up.

crosire wrote: The default keyboard shortcut for opening the in-game overlay has changed to the "Home" ("Pos 1" on some keyboards) button.

lowenz wrote:

Groovex wrote: How do I move the Reshade settings menu that appears in the game? It's locked on the left side of the screen!

It's intended.

No it isn't. As having it locked to the left side makes things rather useless to use, you can move it, but it's cumbersome at the moment (see a page or so back). There are several things that can be done tho, as I've suggested earlier, but no idea if these are going to be picked up or if anything will be done to make this easier.

crosire wrote: Bison was used for the initial revision of the compiler. It wasn't flexible enough for my needs and actually slower than a hand-written recursive decscent parser. So I ditched it pretty fast and wrote the thing myself.

Flex/Bison are getting old and there are better options now. I only listed those because they're the most well-known examples. Modern tools generate code at least as fast as hand-written versions ( re2c example studies ). Some tools like Coco/R actually generate top-down descent parsers that are very similar to your code, so integration would be seamless. If you're planning additional changes I would recommend using them at least for the lexer.

Viper_Joe wrote:

Myashi wrote: Hey guys,
long time no see I want to ask if it's just me or ReShade 4.2 doesn't work with Sunset Overdrive (steam version).
I can see the greeting message, when I launch the game but as soon i press shift +F2, the gui doesn't show up.

crosire wrote: The default keyboard shortcut for opening the in-game overlay has changed to the "Home" ("Pos 1" on some keyboards) button.

I've missed that comment, thanks mate.

Also, someone knows why some shaders are changed? For example, lumasharpen has a dropdown menù but I can't find any way to edit like in the past.

Great update, on the old version, so many of the shaders were broken on Sven Coop now all of them works great!

But the "FXAA" doesn't work anymore, also "PerfectPerspective".

CHOPPER wrote: Great update, on the old version, so many of the shaders were broken on Sven Coop now all of them works great!

But the "FXAA" doesn't work anymore, also "PerfectPerspective".

Both of these are working for me with 4.02.

What errors are you getting?

CHOPPER wrote: Great update, on the old version, so many of the shaders were broken on Sven Coop now all of them works great!

But the "FXAA" doesn't work anymore, also "PerfectPerspective".

Did you update the shader package?

Since the update, I can't edit any settings or do anything

prntscr.com/ln3baf Its pretty much locked

BlueVantra wrote: Since the update, I can't edit any settings or do anything

prntscr.com/ln3baf Its pretty much locked

Disable performance mode

klotim wrote:

BlueVantra wrote: Since the update, I can't edit any settings or do anything

prntscr.com/ln3baf Its pretty much locked

Disable performance mode

How would I do that when I'm unable to click or move it?

Myashi wrote: Also, someone knows why some shaders are changed? For example, lumasharpen has a dropdown menù but I can't find any way to edit like in the past.

UP. Until a month ago, everything was ok. Now a clean install of any Reshade, come up with these new filters/shaders (whatever is the correct way to call them).
LumaSharpen can't no longer be tweaked, it has just 4 preset I believe they are the old "sample pattern". But what if I want to tweak even the strenght and the limit, like in the second screenshots? I've noticed that even Fake Hdr is changed (now is just an ON/OFF filter). So I'm assuming since October, all the filters are changed?

Current LumaSharpen:



Old LumaSharpen:

Myashi wrote:

Myashi wrote: Also, someone knows why some shaders are changed? For example, lumasharpen has a dropdown menù but I can't find any way to edit like in the past.

UP. Until a month ago, everything was ok. Now a clean install of any Reshade, come up with these new filters/shaders (whatever is the correct way to call them).
LumaSharpen can't no longer be tweaked, it has just 4 preset I believe they are the old "sample pattern". But what if I want to tweak even the strenght and the limit, like in the second screenshots? I've noticed that even Fake Hdr is changed (now is just an ON/OFF filter). So I'm assuming since October, all the filters are changed?

Current LumaSharpen:

Old LumaSharpen:

Is it because you're using shaders meant for 4.x with a 3.x version of ReShade?

If I understand it correctly, 4.x uses a different method of sliders to change values, so 3.x ReShade is looking for the old method, which is no longer present in the shaders currently distributed for 4.x.

That's what I'm surmising having read this thread. I'm still using 3.4.1 with its original shaders, so I can't comment from personal experience here.

Are old versions of shaders available via github? It seems like it would be a good idea to keep old versions so people who want to continue using 3.x can use the shaders appropriate to that version. The ReShade repository only has the binaries.

Lumasharpen still has the controls you have in the bottom shot, see: github.com/crosire/reshade-shaders/blob/...s/LumaSharpen.fx#L13

So why they don't turn up now in 3.4.1 for you, no idea, but try to check whether you're indeed using the latest shaders or some old stuff instead?

(edit) Ah, missed the change from drag to slider for some shaders (well, a lot of them, except e.g. cinematic dof), which is the reason it doesn't work in v3. It should work in v4, but in v3 you need the old version. you can get the old version from github: browse the repo from this commit: github.com/crosire/reshade-shaders/tree/...340a66495ac1ac059c85

Thanks for new reshade but I have very bad performance with adaptive sharpen in Arcane Dimensions (quake 1 mod on quakespasm source port/OpenGL). With 3.4.1 I do not have any problems and game runs 100+ FPS but with reshade 4.0.2 I have FPS under 60. (Win7, GTX 1070, i7 4770)

weird, getting trojan detection for 4.0.2 but not for 4.0 .

also virustotal reports 4 trojans: www.virustotal.com/en/file/1ec2bf65e4ecc...analysis/1543272018/

pretty sure false positive, but why 4.0.2 and not 4.0?

OtisInf wrote: (edit) Ah, missed the change from drag to slider for some shaders (well, a lot of them, except e.g. cinematic dof), which is the reason it doesn't work in v3. It should work in v4, but in v3 you need the old version. you can get the old version from github: browse the repo from this commit: github.com/crosire/reshade-shaders/tree/...340a66495ac1ac059c85

amoebae wrote: If I understand it correctly, 4.x uses a different method of sliders to change values, so 3.x ReShade is looking for the old method, which is no longer present in the shaders currently distributed for 4.x.

Thank you guys, you made me realize where was the mistake. I wasn't aware of the changes, so I kept using reshade like i was used to. Everything works fine.
I'm not sure if, the ctrl + left click feature is disabled or not. I noticed the values can be changed with a slider, but I'd like the old way. Is still possible?

Would require the old shader code, or manually change 'slider' into 'drag' at the top of the file in a text editor. Use the link I gave above to browse to the old shader version which has 'drag' instead of 'slider' in the variable /control definitions at the top of the file.

so either copy/paste this: raw.githubusercontent.com/crosire/reshad...aders/LumaSharpen.fx

or change 'slider' into 'drag' here: github.com/crosire/reshade-shaders/blob/...s/LumaSharpen.fx#L14 in the file you have on disk (and the other slider definitions of course ;))

OtisInf wrote: Would require the old shader code, or manually change 'slider' into 'drag' at the top of the file in a text editor. Use the link I gave above to browse to the old shader version which has 'drag' instead of 'slider' in the variable /control definitions at the top of the file.

so either copy/paste this: raw.githubusercontent.com/crosire/reshad...aders/LumaSharpen.fx

or change 'slider' into 'drag' here: github.com/crosire/reshade-shaders/blob/...s/LumaSharpen.fx#L14 in the file you have on disk (and the other slider definitions of course ;))

Thanks mate! I'll do as you suggest

OtisInf wrote: Would require the old shader code, or manually change 'slider' into 'drag' at the top of the file in a text editor. Use the link I gave above to browse to the old shader version which has 'drag' instead of 'slider' in the variable /control definitions at the top of the file.

so either copy/paste this: raw.githubusercontent.com/crosire/reshad...aders/LumaSharpen.fx

or change 'slider' into 'drag' here: github.com/crosire/reshade-shaders/blob/...s/LumaSharpen.fx#L14 in the file you have on disk (and the other slider definitions of course ;))

Thanks for the info. So just changing slider to drag for every ui element will make it look and act like it used to? Will the click-to-input function still be there, or was that controlled by something else?

Also, as someone who isn't familiar at all with github, I find navigating it an almost entirely opaque process. Is there a way for someone (a group effort, perhaps) to make it easy to access old versions of shaders all grouped together as they would be if downloading the current versions? Similar to how we have the repository for old binaries?

As users and preset authors, there are a ton of presets out there that were made with specific versions of ReShade, and that are tied to the shaders that were released at that time. It's easy to download the relevant binary, but near impossible to get hold of the relevant shaders. As it stands, it's not a particularly user-friendly process.

Even better would be if somehow the installer recognised the version number and downloaded the shaders appropriate to that version automatically.

Perhaps we can get permission to share shaders from previous versions if they're not easily available anymore?