[SOLVED] Issues running SweetFX with pcsx2

Hi all. Using both the last stable build (1.4) and the most recent (1.5.0-20160728222500) with SweetFX 1.4, 1.51 and 2.0, I can't get it to run. The game itself launches fine, but won't run the shader. It will run with the included one fine.

I have Graphics set to DX11 (hardware), I've enabled external shaders and pointed to the correct dxgi.fx shader (the one the readme specifies for dx10/11) and the correct config file. I've also tried using dxgi.dll just in case.

Whenever I launch the game (FFXII), the shader doesn't take effect, even using the toggle (scroll lock). Checking the log file each time I get this error:

"error X3501: 'ps_main': entrypoint not found

GSdx: failed to compile external post-processing shader."

It then shuts everything down and runs the game without any shaders.

Trying to run it pointing to the .dll gives me:
"\Games\PCSX2\dxgi.dll(267,1-2): error X3000: unrecognized identifier 'MZ'
\Games\PCSX2\dxgi.dll(269,323): error X1005: string continues past end of line
\Games\PCSX2\dxgi.dll(270,65): error X1005: string continues past end of line"

And the then same thing happens. Appreciate any help. I've been trying to sort through this forever now.

You do realize this forum is about ReShade and you aren't using ReShade but InjectSMAA there ...

Sorry, but I could have sworn that the 2.0 version of SweetFX uses your ReShade? 2.0.3.1120. The file description for dxgi.dll states "crosire's ReShade post-processing injector for 32-bit". When running this version specifically, the errors in the log are slightly different:

"Sweet.fx(42,10-16): warning X3568: 'reshade' : unknown pragma ignored
Sweet.fx(46,10-16): warning X3568: 'reshade' : unknown pragma ignored
\Games\PCSX2\dxgi.dll(3,1-2): error X3000: unrecognized identifier 'MZ'

GSdx: failed to compile external post-processing shader."

If I'm still way off base here then I apologize.

It does. But the errors you posted do not come from SweetFX running on ReShade. Those are from SweetFX 1.4/5 which runs on InjectSMAA. Make sure you fully delete those before installing SweetFX 2.0 ( reshade.me/sweetfx ). There is no dxgi.fx in SweetFX 2.0 for instance. Also, you can't replace the fx files with a DLL, those are different types of files ...

Following your advice, I completely removed everything in the PCSX2 folder including the PCSX2 files. Reinstalled that program, reinstalled SweetFX 2.0 from the link you posted, and configured the program to use external shaders, pointing at Sweet.fx as the shader, and SweetFX_settings.txt as the external shader config.

I receive essentially the same error:
"\Games\PCSX2\Sweet.fx(448,10-16): warning X3568: 'reshade' : unknown pragma ignored
\Games\PCSX2\Sweet.fx(452,10-16): warning X3568: 'reshade' : unknown pragma ignored
error X3501: 'ps_main': entrypoint not found

GSdx: failed to compile external post-processing shader."

Edit: Also, the reason I tried using the DLL was I thought maybe I had the program pointing at the wrong file to read from as the shader. Figured it was worth a shot since nothing else was working...

I'm sorry, but these errors still come from InjectSMAA. ReShade creates a .log file with the same name as the DLL (e.g. dxgi.log if ReShade was installed as dxgi.dll). It also shows a text overlay in-game so you know it is starting up.

You may want to read the README.txt accompanying the download for installation instructions again.

I'm not sure how that would be possible given how I wiped the entire program folder, including separate directories PCSX2 created in outside folders before reinstalling everything from scratch and using the download link you provided.

The log file I am using is the one generated from PCSX2. ReShade has yet to create it's own .log file which I can look at. I'm assuming because it never gets the chance to initialize due to the errors posted. I also haven't seen the in-game text overlay as PCSX2 decides not to run external shaders due to the error before it starts emulating the chosen game.

I've looked through the readme several times, and installed using both the automatic and manual methods with the same results.

The only time I have seen ReShade create it's log file is when I placed it in the Plugins folder of PCSX2 (I was trying any configuration I could) and had PCSX2 try to read it as a graphics plugin just like GSdx (it detected it obviously wasn't, so I couldn't choose it as a graphics plugin option). This is the log it generated:

29/07/2016 22:02:56:228 [06856] | INFO | Initializing crosire's ReShade version '2.0.3.1120' built on '2016-04-03 19:20:33' loaded from "\Games\PCSX2\plugins\dxgi.dll" to "\Games\PCSX2\pcsx2.exe" ...
29/07/2016 22:02:56:264 [06856] | INFO | Registering hooks for "C:\Windows\system32\d3d8.dll" ...
29/07/2016 22:02:56:264 [06856] | INFO | > Delayed.
29/07/2016 22:02:56:264 [06856] | INFO | Registering hooks for "C:\Windows\system32\d3d9.dll" ...
29/07/2016 22:02:56:264 [06856] | INFO | > Libraries loaded.
29/07/2016 22:02:56:264 [06856] | INFO | > Found 9 match(es). Installing ...
29/07/2016 22:02:56:340 [06856] | INFO | > Installed 9 hook(s).
29/07/2016 22:02:56:340 [06856] | INFO | Registering hooks for "C:\Windows\system32\d3d10.dll" ...
29/07/2016 22:02:56:402 [06856] | INFO | > Delayed.
29/07/2016 22:02:56:402 [06856] | INFO | Registering hooks for "C:\Windows\system32\d3d10_1.dll" ...
29/07/2016 22:02:56:403 [06856] | INFO | > Delayed.
29/07/2016 22:02:56:403 [06856] | INFO | Registering hooks for "C:\Windows\system32\d3d11.dll" ...
29/07/2016 22:02:56:403 [06856] | INFO | > Libraries loaded.
29/07/2016 22:02:56:403 [06856] | INFO | > Found 2 match(es). Installing ...
29/07/2016 22:02:56:420 [06856] | INFO | > Installed 2 hook(s).
29/07/2016 22:02:56:420 [06856] | INFO | Registering hooks for "C:\Windows\system32\d3d12.dll" ...
29/07/2016 22:02:56:420 [06856] | INFO | > Delayed.
29/07/2016 22:02:56:420 [06856] | INFO | Registering hooks for "C:\Windows\system32\dxgi.dll" ...
29/07/2016 22:02:56:420 [06856] | INFO | > Delayed.
29/07/2016 22:02:56:420 [06856] | INFO | Registering hooks for "C:\Windows\system32\opengl32.dll" ...
29/07/2016 22:02:56:421 [06856] | INFO | > Delayed.
29/07/2016 22:02:56:421 [06856] | INFO | Registering hooks for "C:\Windows\system32\user32.dll" ...
29/07/2016 22:02:56:421 [06856] | INFO | > Libraries loaded.
29/07/2016 22:02:56:421 [06856] | INFO | > Found 5 match(es). Installing ...
29/07/2016 22:02:56:464 [06856] | INFO | > Installed 5 hook(s).
29/07/2016 22:02:56:464 [06856] | INFO | Registering hooks for "C:\Windows\system32\ws2_32.dll" ...
29/07/2016 22:02:56:464 [06856] | INFO | > Libraries loaded.
29/07/2016 22:02:56:465 [06856] | INFO | > Found 8 match(es). Installing ...
29/07/2016 22:02:56:532 [06856] | INFO | > Installed 8 hook(s).
29/07/2016 22:02:56:532 [06856] | INFO | Initialized.
29/07/2016 22:02:56:532 [06856] | INFO | Exiting ...
29/07/2016 22:02:56:532 [06856] | INFO | Uninstalling 28 hook(s) ...
29/07/2016 22:02:56:758 [06856] | INFO | Exited.

I've never had it generate a log while trying to actually run the emulator, even running with SweetFX and ReShader installed using the Plugin folder as the base directory. The plugins folder is also the only one that has other DLLs in it.

Also, is the ReShade.fx file only supposed to say "#include "Sweet.fx""? Because that's all mine says. Granted, I know nothing about programming, but after looking through what the two .fx files say, neither seem to be pointing towards the ReShader DLL, which is why it's not opening and/or generating a log file?

Use enbinjector and Reshade works fine with PCSX2. Also, I would set the PCSX2 setting back to default to undo all the changes you made trying to get it to work.

enbdev.com/download_injector_generic.htm

enbinjector.ini change to look like this:

[LIBRARY]
LibraryName=ReShade32.dll

[TARGETPROCESS]
ProcessName0=pcsx2.exe
ProcessName1=
ProcessName2=
ProcessName3=
ProcessName4=
ProcessName5=
ProcessName6=
ProcessName7=
ProcessName8=
ProcessName9=
ProcessName10=
ProcessName11=
ProcessName12=
ProcessName13=
ProcessName14=
ProcessName15=


Lastly, PCSX2 has shader injector preloaded into the latest builds. More than likely this is what you see in the PCSX2 log files and why Crosire is saying that ain't Reshade. I don't recommend using both the PCSX2 injector and Reshade at same time. You can use both no problem but I wouldn't.

This is the shader injector that comes preloaded into the latest builds of PCSX2. You can and I would disable it in GSDX plugin settings. forums.pcsx2.net/Thread-Custom-Shaders-f...pid=288516#pid288516

Thank you so much! I figured PCSX2 wasn't running the DLL, but had no idea how to get it to do so besides pointing to it with the GSDX external shader option. I also assumed I had to get PCSX2 to point to the SweetFX/ReShade files to run, which I now know is incorrect. I turned everything off that had to do with external shaders.

I finally got the "start script" to show once the program was running and initially had 3 errors which caused it to fail:
\Games\PCSX2\SweetFX/Shaders/Main.h(62, 11): preprocessor error: redefinition of 'USE_SHARED'
\Games\PCSX2\SweetFX/Shaders/Main.h(67, 11): preprocessor error: redefinition of 'USE_SHARED'
\Games\PCSX2\SweetFX/Shaders/Main.h(72, 11): preprocessor error: redefinition of 'USE_SHARED'

Doing some searching, I saw previous posts on how basically some specific shaders do something incorrectly with the new ReShade version. It ended up being Tonemap, Vibrance, and Curves. I turned those back to 0 and booted up and finally...success! I really look forward to being able to utilize SweetFX and ReShade now with PCSX2.

Edit: Followed crosire's instructions on how to fix those errors and have it run properly from the other thread. You do this to the SweetFX>Shaders>Main.h file.
"SweetFX is missing a "#undef USE_SHARED" before the "#define USE_SHARED ..." line there. It unfortunately worked with the older binaries due to a bug that has now been fixed."

I'd like to ask: why is this an issue with only a few of the shaders and not all of them since they're all written without the "#undef USE_SHARED"?

It's only an issue if the effect is enabled. I fixed this in the download. Sorry for the inconvenience.

No worries, that part was easy enough to figure out with your previous posts. What I meant was, I have other effects enabled that run with no issues without those lines inserted. HDR, Bloom, etc.

Also I'm really enjoying this so far, and it's definitely keeping my GPU busy while emulating now!

Should have clarified that. Not all effects run in a shared pass and it only affected those. Some effects run independently from each other, one at a time, but some are put into a single calculation step to improve performance.