SweetFX Settings DB
Latest forum threads
18 hours, 10 minutes ago
2 days, 5 hours ago
2 days, 13 hours ago
3 days, 16 hours ago
Posted 2 years, 6 months ago
Hey guys, i'm using win 10 and try to start AC black flag with fx but always d3d11.dll error pop up, i try to remove dxgi.dll it was start to opening but sweetfx setting cant work still there is no change as i can see. i' m using Abstergo 1.1 preset from list. can any1 have any idea?
Posted 2 years, 6 months ago
I only use Reshade 3.0+, but for me, most games CTD with any version of Reshade or SeeetFX unless I set them to borderless window or windowed mode, no fullscreen. Also, for Ghost Recon Wildlands, I was forced to chouse the DirectX 8/9 version, even though 10+ would seem like the right choice, or else instant CTD all day. Hope hope this helps.
Posted 2 years, 5 months ago
@AssassinsDecree and webhammerksk Make sure you have every driver installed and not just the ones that come with games Runtime and some others are not enough. I had both you're problems many years back but with myself using a lot of different modding software a part from Reshade i had to install a lot of additional window drivers and now i never have problems with modding software including reshade.
Posted 2 years, 5 months ago
@QTmodz, Really? OK very interesting, I'll habe to check and see if I have all the window drivers. Any suggestions on where to start checking? Thanks!
Posted 2 years, 5 months ago
@QTmodz All drivers are updated already. I'm sure of it. Saw same problems on other forums like me, and cant figure out still. Win 10 making difficult to modding especially Reshade.
Posted 4 weeks, 1 day ago
I just had that problem too after installing NFS U2 again and adding SweetFX (v1.5.1) to it. After a bit of research the solution for me was to rename/delete the dxgi.dll and dxgi.fx files. They're for DX11 and not needed therefore in my situation anyway. What about games using DX11? Don't know if and don't think this is a solution when those games actually throw that error message too.. I don't remember having that problem years ago, it's either due to some Win 10 update or Nvidia driver update. Some info about my System: Windows 10 Home 64bit (build #1809) Nvidia Driver v411.70 Just wanted to post this as an answer, to actually have one possible solution here for people searching for that on this forum.
New post

Please log in to post an answer