Hello, great preset. I have an issue. I'm playing in DX11 btw - the issue is that when I start the game, Reshade loads normally and so do all the effects, except Display Depth. It fails to compile and gives and x3004 error, something along the lines of "depth input X pixel offset undefined" I used both the latest version of Reshade and the 4.5.4 version, same problem
I'm not much of an expert on the technical aspects of ReShade, but from a quick google search it seems that it could be possibly be that the code has changed in later renditions of the Display Depth shader. If you can download an older version of DisplayDepth.fx (should be up on the github, or ReShade should have an option for legacy shaders in its install), I'd do that, but it's likely a better question for whoever created the shader if that doesn't work.
literally the best preset for fc 3. also, thanks for the mod merge tutorial on the bottom.
btw, ppfx bloom doesn't do anything for me. not sure what it do on this preset? also, fc 3 has a terrible color banding despite it's a direct x 11 game.
I'd turn the deband shader to maximum with 3 times iteration to fix them (it's still present but less noticeable). but the fps cost is like 10 frames (went from 144 in 1600p to 134 so maybe it's not worth it, I do noticed the input lag going from 144 to 134 but from someone who usually play bad optimized ubisoft game at 60 fps(looking at you breakpoint and wildlands) it still feels fantastic).
if you follow my suggestion, make sure to turn off antialiasing, and use the smaa from the author (cuz it messed up the deband depth shader to target only sky, pretty sure depth buffer is required for the bloom shader as well but I'm not sure maybe not) and also using the well configured cinematic dof as well, to make the aliasing less noticeable (cuz the aliasing is really bad unless you use msaa which is very expensive, i got only 90 fps for 4x with this preset).
I appreciate the kind words. I'm not sure why the bloom shader isn't working for you, it may have something to do with DX11 as I've primarily used DX9. It also shouldn't rely on the depth buffer, if I remember correctly it just checks the screen for bright spots and bumps them up. That all being said, it's been a couple of years since I've actually looked at this preset so it could be error on my part
Simply does not work for me (and I have plenty of experience with ReShade).
Installing 4.5.4, using DX9, everything seems to go fine. The problem is that no effects are checked when your preset loads; when I try to enable individual effects, I get a red message saying "Unable to save current preset. Make sure you have write permissions..."
I have write permissions to the folder, so what's going on?
EDIT- Fixed. The problem is caused by installing ReShade 4.5.4 via the reshade repository. Installing the latest reshade (4.8.2 as of this comment) worked fine.
A few remaining issues also fixed. ReShade defaults to the Home key as the menu key; even overwriting with your reshade.ini file doesn't change this, so the home key is both the menu and effect toggle. This is easily changed just by swapping 36,0,0,0 with 35,0,0,0.
Nightvision and HDR are also set to the same shortcut key (N), which toggles both simultaneously. The menu issue is just a problem with the reshade install, but this one is a mistake on your part. Your preset file shows KeyHDR=78,0,0,0 KeyNightvision=78,0,0,0
The HDR was intended to brighten the screen, as the Night-Vision effect alone is non-functioning and purely cosmetic. So, in essence, when you hit the "N" key, it enables both effects at once, one to add the Night-Vision effect, and the other to brighten the screen to give the illusion of functional night-vision. That being said, I gave up on that concept because the nights are bright enough and outside of screenshots, pressing a key to make nights darker is a little silly.
Thanks for the update about the repository downloads and the default key issue, I'll put a disclaimer in the description, as well as updating the file.
Are you sure you're hitting the right key? It should be "-", right next to your 0 button. If that isn't working, open up ReShade and right click the gamma shader, and see which button it is attached to. If it's still not working, I'm working on a new version that should be up in a week or so
Give Feedback
22 comments
I used both the latest version of Reshade and the 4.5.4 version, same problem
btw, ppfx bloom doesn't do anything for me. not sure what it do on this preset? also, fc 3 has a terrible color banding despite it's a direct x 11 game.
I'd turn the deband shader to maximum with 3 times iteration to fix them (it's still present but less noticeable). but the fps cost is like 10 frames (went from 144 in 1600p to 134 so maybe it's not worth it, I do noticed the input lag going from 144 to 134 but from someone who usually play bad optimized ubisoft game at 60 fps(looking at you breakpoint and wildlands) it still feels fantastic).
if you follow my suggestion, make sure to turn off antialiasing, and use the smaa from the author (cuz it messed up the deband depth shader to target only sky, pretty sure depth buffer is required for the bloom shader as well but I'm not sure maybe not) and also using the well configured cinematic dof as well, to make the aliasing less noticeable (cuz the aliasing is really bad unless you use msaa which is very expensive, i got only 90 fps for 4x with this preset).
Installing 4.5.4, using DX9, everything seems to go fine. The problem is that no effects are checked when your preset loads; when I try to enable individual effects, I get a red message saying "Unable to save current preset. Make sure you have write permissions..."
I have write permissions to the folder, so what's going on?
EDIT- Fixed. The problem is caused by installing ReShade 4.5.4 via the reshade repository. Installing the latest reshade (4.8.2 as of this comment) worked fine.
A few remaining issues also fixed. ReShade defaults to the Home key as the menu key; even overwriting with your reshade.ini file doesn't change this, so the home key is both the menu and effect toggle. This is easily changed just by swapping 36,0,0,0 with 35,0,0,0.
Nightvision and HDR are also set to the same shortcut key (N), which toggles both simultaneously. The menu issue is just a problem with the reshade install, but this one is a mistake on your part.
Your preset file shows
KeyHDR=78,0,0,0
KeyNightvision=78,0,0,0
78,0,0,0 is the N key.
Thanks for the update about the repository downloads and the default key issue, I'll put a disclaimer in the description, as well as updating the file.