I have no active overlays running except for UPlay of course which I need to run to launch the game. But if Uplay was the problem then no one should be able to enable sweetFX with Blacklist, right!? (since Uplay is mandatory to run the game). Or am I getting something wrong here?
I have no active overlays running except for UPlay of course which I need to run to launch the game. But if Uplay was the problem then no one should be able to enable sweetFX with Blacklist, right!? (since Uplay is mandatory to run the game). Or am I getting something wrong here?
Please paste in the line of your DX9settings.ini where you specify the proxy dll.
As for uPlay, you can disable the actual overlay 9but not the launcher). Run the game, exit, and you should be able to change settings in the launcher. It's unlikely to be the cause, but it could be.
Please paste in the line of your DX9settings.ini where you specify the proxy dll.
As for uPlay, you can disable the actual overlay 9but not the launcher). Run the game, exit, and you should be able to change settings in the launcher. It's unlikely to be the cause, but it could be.
@pirate
This is the proxy-line I added directly under the [General] tab in the DX9Settings.ini:
[General]
ProxyLib = D:\Ubisoft Games\Splinter Cell Blacklist\src\SYSTEM\d3d9_fx.dll
This is the exact path where the sweetfx-d3d9 is located. As you can see I renamed the sweetfx d3d9.dll into d3d9_fx.dll to make the file different from the 3d-fix d3d9.dll
I didn't set up any sweetfx config by myself but took one from a well known sweetfx database. Judging from the comments there These Settings should work.
Any idea?
This is the exact path where the sweetfx-d3d9 is located. As you can see I renamed the sweetfx d3d9.dll into d3d9_fx.dll to make the file different from the 3d-fix d3d9.dll
I didn't set up any sweetfx config by myself but took one from a well known sweetfx database. Judging from the comments there These Settings should work.
Have you used sweetfx before?
Just to make sure you've set it up correctly, you should copy the text from the txt file you downloaded, and paste it into the SweetFX_settings.txt file in the game directory. You could also rename the file you downloaded to SweetFX_settings.txt and have it replace the old file, either way. If you've left it with the filename it downloaded as, it won't work.
Just to make sure you've set it up correctly, you should copy the text from the txt file you downloaded, and paste it into the SweetFX_settings.txt file in the game directory. You could also rename the file you downloaded to SweetFX_settings.txt and have it replace the old file, either way. If you've left it with the filename it downloaded as, it won't work.
I am using sweetfx in every single game that I play since a year now but this time I am really stuck. Yes, I always do the "rename the txt-file to SweetFX_settings.txt"-procedure but this time it just doesn't work.
I am using sweetfx in every single game that I play since a year now but this time I am really stuck. Yes, I always do the "rename the txt-file to SweetFX_settings.txt"-procedure but this time it just doesn't work.
Problem solved! Same solution for me as Devil may cry last year. Beside the ...src\ System-folder where the .exe for DX9 and DX11 is located (all installation guides are saying that the sweetfx files need to be put here just as mike's 3D fix-files) there is another Blacklist-exe located 2 levels above (where the folder src is located) which is named something like SplinterCell_Blacklist_Launcher.exe. When I launched the game today I noticed a shortly visible pop-up window which told me that the application is running this launcher.exe to start the game. So I put mike's files as well as the whole sweetfx stuff into that folder where the launcher.exe is located. Now not only mike's fix is kicking in when launching the game but sweetfx as well!
Problem solved! Same solution for me as Devil may cry last year. Beside the ...src\ System-folder where the .exe for DX9 and DX11 is located (all installation guides are saying that the sweetfx files need to be put here just as mike's 3D fix-files) there is another Blacklist-exe located 2 levels above (where the folder src is located) which is named something like SplinterCell_Blacklist_Launcher.exe. When I launched the game today I noticed a shortly visible pop-up window which told me that the application is running this launcher.exe to start the game. So I put mike's files as well as the whole sweetfx stuff into that folder where the launcher.exe is located. Now not only mike's fix is kicking in when launching the game but sweetfx as well!
As it seems I declared the problem solved a little bit too early. Things are getting really weird now. The day after I succesfully tested mike's fix in conjunction with sweetfx it was broken again.....although I didn't change anything. After the succesful test on Wednesday I instantly switched off the PC. When I tried to launch the game on Thursday sweetfx AGAIN didn't kick in.
Right now I have all the files for mike's 3D fix as well as all sweetfx files in Blacklist's system folder. The sweetfx-d3d9.dll is renamed d3d9_sfx.dll. I added the ProxyLib-line with the exact path and name for the renamed sweetfx-d3d9.dll.
And now comes the crazy part:
I tried mike's fix and sweetfx isolated and both work. So if I only use mike's fix I get the glorious 3D. If I only use sweetFX it also kicks in. When I try to use both simultaneously I only get the glorious 3D (mike's fix). That led me to the conclusion that something with my ProxyLib line must be faulty. Out of desparation I just launched the DX11.exe of the game which is located in the same folder (remember both mike's fix AND sweetfx being installed in Blacklist'S system folder at that moment meaning that the sweet-fx d3d9.dll was renamed as mentioned above with the only reference being my ProxyLib-line in mike-fixes DX9Settings.ini. And now it gets even more weird. Just as expected the 3D was broken know in DX11 respectively the crappy Nvidia fake 3D kicked in but SWEETFX WORKED! Maybe I am getting it totally wrong but isn't it that the application somehow must have accessed the DX9Settings.ini where the reference for the renamed sweetfx d3d9.dll was?
So the question remains: Why am I not able to run Blacklist with mike's fix AND sweetfx although a) both work like a charme when being used separately and b) I can be pretty sure that my ProxyLib line is correct?
As it seems I declared the problem solved a little bit too early. Things are getting really weird now. The day after I succesfully tested mike's fix in conjunction with sweetfx it was broken again.....although I didn't change anything. After the succesful test on Wednesday I instantly switched off the PC. When I tried to launch the game on Thursday sweetfx AGAIN didn't kick in.
Right now I have all the files for mike's 3D fix as well as all sweetfx files in Blacklist's system folder. The sweetfx-d3d9.dll is renamed d3d9_sfx.dll. I added the ProxyLib-line with the exact path and name for the renamed sweetfx-d3d9.dll.
And now comes the crazy part:
I tried mike's fix and sweetfx isolated and both work. So if I only use mike's fix I get the glorious 3D. If I only use sweetFX it also kicks in. When I try to use both simultaneously I only get the glorious 3D (mike's fix). That led me to the conclusion that something with my ProxyLib line must be faulty. Out of desparation I just launched the DX11.exe of the game which is located in the same folder (remember both mike's fix AND sweetfx being installed in Blacklist'S system folder at that moment meaning that the sweet-fx d3d9.dll was renamed as mentioned above with the only reference being my ProxyLib-line in mike-fixes DX9Settings.ini. And now it gets even more weird. Just as expected the 3D was broken know in DX11 respectively the crappy Nvidia fake 3D kicked in but SWEETFX WORKED! Maybe I am getting it totally wrong but isn't it that the application somehow must have accessed the DX9Settings.ini where the reference for the renamed sweetfx d3d9.dll was?
So the question remains: Why am I not able to run Blacklist with mike's fix AND sweetfx although a) both work like a charme when being used separately and b) I can be pretty sure that my ProxyLib line is correct?
What do you mean by both locations? Currently all mikes as well as all sfx files are located in Blacklist's system folder (where every exe of the game is located too...except for the launcher.exe). I took the sfx files out of the folder where this Blacklist_launcher.exe is located because after my unsuccesful try on Thursday putting the sfx files there no longer seemed the solution.
Should I leave the sfx files in the system folder and copy them into the launchet.exe folder as well? Which location should the proxylib line in mike fixes ini refer to then (the launcher.exe location or the system folder location)?
What do you mean by both locations? Currently all mikes as well as all sfx files are located in Blacklist's system folder (where every exe of the game is located too...except for the launcher.exe). I took the sfx files out of the folder where this Blacklist_launcher.exe is located because after my unsuccesful try on Thursday putting the sfx files there no longer seemed the solution.
Should I leave the sfx files in the system folder and copy them into the launchet.exe folder as well? Which location should the proxylib line in mike fixes ini refer to then (the launcher.exe location or the system folder location)?
Can't hurt to try having them in both locations, and experiment with where you point the proxy lines.
To be clear, I don't actually know how to fix this problem. I'm just providing suggestions in the hope something sticks :)
Got it! I found out that sweetFX is always creating a log.log file in the folder where sweetfx is installed (btw this should be the system folder for Blacklist. My suggestion it should be the folder where that Blacklist_Launcher.exe is located was wrong) where you can see which error caused it to crash. In that file I found this:
SweetFX_settings.txt(1,1): error X3000: Illegal character in shader file
Judging from other's experiences this seems to be a common issue for some while others seem to have no problem at all with the same sweetfx settings. Since I couldn't find out which the illegal character was in the sweetfx_settings.txt and all the others who were facing the same problem didn't come up with a solution in the forums where they stated their problem I just tried another good preset. Now Mike's 3D fix AND SweetFX work flawlessly.
Thanks again to Mike and Pirate for their invaluable help!
Got it! I found out that sweetFX is always creating a log.log file in the folder where sweetfx is installed (btw this should be the system folder for Blacklist. My suggestion it should be the folder where that Blacklist_Launcher.exe is located was wrong) where you can see which error caused it to crash. In that file I found this:
SweetFX_settings.txt(1,1): error X3000: Illegal character in shader file
Judging from other's experiences this seems to be a common issue for some while others seem to have no problem at all with the same sweetfx settings. Since I couldn't find out which the illegal character was in the sweetfx_settings.txt and all the others who were facing the same problem didn't come up with a solution in the forums where they stated their problem I just tried another good preset. Now Mike's 3D fix AND SweetFX work flawlessly.
Thanks again to Mike and Pirate for their invaluable help!
As for uPlay, you can disable the actual overlay 9but not the launcher). Run the game, exit, and you should be able to change settings in the launcher. It's unlikely to be the cause, but it could be.
This is the proxy-line I added directly under the [General] tab in the DX9Settings.ini:
[General]
ProxyLib = D:\Ubisoft Games\Splinter Cell Blacklist\src\SYSTEM\d3d9_fx.dll
This is the exact path where the sweetfx-d3d9 is located. As you can see I renamed the sweetfx d3d9.dll into d3d9_fx.dll to make the file different from the 3d-fix d3d9.dll
I didn't set up any sweetfx config by myself but took one from a well known sweetfx database. Judging from the comments there These Settings should work.
Any idea?
Just to make sure you've set it up correctly, you should copy the text from the txt file you downloaded, and paste it into the SweetFX_settings.txt file in the game directory. You could also rename the file you downloaded to SweetFX_settings.txt and have it replace the old file, either way. If you've left it with the filename it downloaded as, it won't work.
Right now I have all the files for mike's 3D fix as well as all sweetfx files in Blacklist's system folder. The sweetfx-d3d9.dll is renamed d3d9_sfx.dll. I added the ProxyLib-line with the exact path and name for the renamed sweetfx-d3d9.dll.
And now comes the crazy part:
I tried mike's fix and sweetfx isolated and both work. So if I only use mike's fix I get the glorious 3D. If I only use sweetFX it also kicks in. When I try to use both simultaneously I only get the glorious 3D (mike's fix). That led me to the conclusion that something with my ProxyLib line must be faulty. Out of desparation I just launched the DX11.exe of the game which is located in the same folder (remember both mike's fix AND sweetfx being installed in Blacklist'S system folder at that moment meaning that the sweet-fx d3d9.dll was renamed as mentioned above with the only reference being my ProxyLib-line in mike-fixes DX9Settings.ini. And now it gets even more weird. Just as expected the 3D was broken know in DX11 respectively the crappy Nvidia fake 3D kicked in but SWEETFX WORKED! Maybe I am getting it totally wrong but isn't it that the application somehow must have accessed the DX9Settings.ini where the reference for the renamed sweetfx d3d9.dll was?
So the question remains: Why am I not able to run Blacklist with mike's fix AND sweetfx although a) both work like a charme when being used separately and b) I can be pretty sure that my ProxyLib line is correct?
Should I leave the sfx files in the system folder and copy them into the launchet.exe folder as well? Which location should the proxylib line in mike fixes ini refer to then (the launcher.exe location or the system folder location)?
To be clear, I don't actually know how to fix this problem. I'm just providing suggestions in the hope something sticks :)
SweetFX_settings.txt(1,1): error X3000: Illegal character in shader file
Judging from other's experiences this seems to be a common issue for some while others seem to have no problem at all with the same sweetfx settings. Since I couldn't find out which the illegal character was in the sweetfx_settings.txt and all the others who were facing the same problem didn't come up with a solution in the forums where they stated their problem I just tried another good preset. Now Mike's 3D fix AND SweetFX work flawlessly.
Thanks again to Mike and Pirate for their invaluable help!