How to fix/disable shaders in games(DLL,guide and fixes).
149 / 167
[quote="mike_ar69"]Has anyone had issues in games with the DLL not saving presets? I seem to have this with the new Metal Gear Rising fix. I've tried a few DLLs and none of them save presets, and as far as I could tell with some of the release dlls the presets did not even work at all. This game does have some issues with the latest DLL as in it wouldn't dump pixel shaders, but otherwise it has been one of the most stable games with the debugger that I have worked on, so it's odd.[/quote]
Helix's Castlevania fix (with auto book convergence) also doesn't let me save presets. Saving any preset settings work only during my game session. After exit and relaunch they are lost/back to default. I had to manually put my convergence/depth settings in the ini with Notepad.
mike_ar69 said:Has anyone had issues in games with the DLL not saving presets? I seem to have this with the new Metal Gear Rising fix. I've tried a few DLLs and none of them save presets, and as far as I could tell with some of the release dlls the presets did not even work at all. This game does have some issues with the latest DLL as in it wouldn't dump pixel shaders, but otherwise it has been one of the most stable games with the debugger that I have worked on, so it's odd.
Helix's Castlevania fix (with auto book convergence) also doesn't let me save presets. Saving any preset settings work only during my game session. After exit and relaunch they are lost/back to default. I had to manually put my convergence/depth settings in the ini with Notepad.
[quote="bo3b"]For the preset keys- did you try moving the keys specified in the Helix DLL? If the game or other overlay wants that key binding, it might conflict and eat the key events. (just a thought)[/quote]
Thats a good idea, I'll try it.
bo3b said:For the preset keys- did you try moving the keys specified in the Helix DLL? If the game or other overlay wants that key binding, it might conflict and eat the key events. (just a thought)
[quote="enthralled"][quote="mike_ar69"]Has anyone had issues in games with the DLL not saving presets? I seem to have this with the new Metal Gear Rising fix. I've tried a few DLLs and none of them save presets, and as far as I could tell with some of the release dlls the presets did not even work at all. This game does have some issues with the latest DLL as in it wouldn't dump pixel shaders, but otherwise it has been one of the most stable games with the debugger that I have worked on, so it's odd.[/quote]
Helix's Castlevania fix (with auto book convergence) also doesn't let me save presets. Saving any preset settings work only during my game session. After exit and relaunch they are lost/back to default. I had to manually put my convergence/depth settings in the ini with Notepad.[/quote]
That's worth knowing, it might be an issue with the newest DLL...
mike_ar69 said:Has anyone had issues in games with the DLL not saving presets? I seem to have this with the new Metal Gear Rising fix. I've tried a few DLLs and none of them save presets, and as far as I could tell with some of the release dlls the presets did not even work at all. This game does have some issues with the latest DLL as in it wouldn't dump pixel shaders, but otherwise it has been one of the most stable games with the debugger that I have worked on, so it's odd.
Helix's Castlevania fix (with auto book convergence) also doesn't let me save presets. Saving any preset settings work only during my game session. After exit and relaunch they are lost/back to default. I had to manually put my convergence/depth settings in the ini with Notepad.
That's worth knowing, it might be an issue with the newest DLL...
Hi! I've been trying to get Helix to work with my Steam-installed copy of Assassin's Creed IV - Black Flag. The game itself will not display correctly in nVidia stereoscopic 3D - lots of shadows only show for one eye, which makes the experience very painful.
I tried putting the debug d3d9.dll in the steam\bin folder to find out which shaders cause the problem, but I have not been able to get the red text overlay to appear (though something seems to happen - stereoscopic 3D gets permanently turned off in some cases).
Can someone give me a hint on what I could do better/differently?
Hi! I've been trying to get Helix to work with my Steam-installed copy of Assassin's Creed IV - Black Flag. The game itself will not display correctly in nVidia stereoscopic 3D - lots of shadows only show for one eye, which makes the experience very painful.
I tried putting the debug d3d9.dll in the steam\bin folder to find out which shaders cause the problem, but I have not been able to get the red text overlay to appear (though something seems to happen - stereoscopic 3D gets permanently turned off in some cases).
Can someone give me a hint on what I could do better/differently?
[quote="Vasastan"]Thank you for that swift response. I saw some DX11 reference on the Helix website which made me think it could work, but apparently not, then.[/quote]
New beta drivers give black flag a rating "excellent". Its going to get download link any minute now. Deffo try those drivers first. http://forums.guru3d.com/showthread.php?t=386051
Vasastan said:Thank you for that swift response. I saw some DX11 reference on the Helix website which made me think it could work, but apparently not, then.
Hello,
First, please accept my apologies if this is the wrong place to post this, but this seemed the best. I am having an issue using the Call of Juarez Gunslinger fix by DHR posted on Helix Mod site in conjunction with the Helixmod launcher. I am trying to use it to allow Afterburner overlay without problem. I have used the Helximod launcher successfully on other fixes such as Far Cry 3, Blood Dragon, Mass Effect 2, etc. But, for CoJ Gunslinger the fixes do not work with the Helixmod launcher and helixmod.dll in place. If I use the d3d9.dll it works, but if I remove that and use the helixmod.dll with the launcher it does not.
I have added DefModuleName=CoJGunslinger.exe under the General section. I have the files in the same folder as the exe and I never left the d3d9.dll and the helixmod.dll in the folder at the same time. I have tried the most recent and the prior DLL release package to see if that made a difference. The second most recent package seemed to be the one DHR used in his fix based on file size and modified stamp.
I had some similar issues using it for Skyrim but finally got it to work by changing some of the DX9Settings.ini statements (presumably because some syntax has changed with newer dlls?) and finally got it to work.
Anyway, can anyone provide any suggestions as to what might be wrong? Also, is there any way to get any kind of log output to see if the dll is not properly parsing some statement and therefore not erroring out?
Any help will be greatly appreciated.
First, please accept my apologies if this is the wrong place to post this, but this seemed the best. I am having an issue using the Call of Juarez Gunslinger fix by DHR posted on Helix Mod site in conjunction with the Helixmod launcher. I am trying to use it to allow Afterburner overlay without problem. I have used the Helximod launcher successfully on other fixes such as Far Cry 3, Blood Dragon, Mass Effect 2, etc. But, for CoJ Gunslinger the fixes do not work with the Helixmod launcher and helixmod.dll in place. If I use the d3d9.dll it works, but if I remove that and use the helixmod.dll with the launcher it does not.
I have added DefModuleName=CoJGunslinger.exe under the General section. I have the files in the same folder as the exe and I never left the d3d9.dll and the helixmod.dll in the folder at the same time. I have tried the most recent and the prior DLL release package to see if that made a difference. The second most recent package seemed to be the one DHR used in his fix based on file size and modified stamp.
I had some similar issues using it for Skyrim but finally got it to work by changing some of the DX9Settings.ini statements (presumably because some syntax has changed with newer dlls?) and finally got it to work.
Anyway, can anyone provide any suggestions as to what might be wrong? Also, is there any way to get any kind of log output to see if the dll is not properly parsing some statement and therefore not erroring out?
Any help will be greatly appreciated.
CPU: i7 5930K, 4.5 (125x36) with Corsair H100i | MB: Asus Rampage V Extreme (1401 Bios) | GPU: NVIDIA RTX 2080 Ti | RAM: Corsair Vengeance 32 GB DDR4 2666MHz (4x8GB) | Storage: Crucial MX100 512 GB SSD (OS & Apps), 2 Seagate 1TB Serial ATA HD 7200/32MB/SATA-3G (Data - RAID 1) | PSU: Corsair HX1000W | Chassis: Cooler Master HAF X | OS: Win 10 Pro 1809
I don't know the answer but I'll offer a suggestion, try using this version of the launcher as it matches the version of the dll that's included with the fix. https://s3.amazonaws.com/Helixfix/DllsModPack.zip
I don't know the answer but I'll offer a suggestion, try using this version of the launcher as it matches the version of the dll that's included with the fix. https://s3.amazonaws.com/Helixfix/DllsModPack.zip
[quote="TsaebehT"]I don't know the answer but I'll offer a suggestion, try using this version of the launcher as it matches the version of the dll that's included with the fix. https://s3.amazonaws.com/Helixfix/DllsModPack.zip[/quote]
Hi, thanks. I have tried with that version and the newest version. Neither works. It is really strange as I have gotten it to work with other games. I wish there was some log option to turn on to get some information.
I can just disable Afterburner for the game, but I also prefer the helixmod.dll version because then when I game via either Shield or Steam Home Streaming, the custom dll is not used when not necessary since I am not gaming in 3D.
Is there any guide or documentation about the valid statements for the ini file?
TsaebehT said:I don't know the answer but I'll offer a suggestion, try using this version of the launcher as it matches the version of the dll that's included with the fix. https://s3.amazonaws.com/Helixfix/DllsModPack.zip
Hi, thanks. I have tried with that version and the newest version. Neither works. It is really strange as I have gotten it to work with other games. I wish there was some log option to turn on to get some information.
I can just disable Afterburner for the game, but I also prefer the helixmod.dll version because then when I game via either Shield or Steam Home Streaming, the custom dll is not used when not necessary since I am not gaming in 3D.
Is there any guide or documentation about the valid statements for the ini file?
CPU: i7 5930K, 4.5 (125x36) with Corsair H100i | MB: Asus Rampage V Extreme (1401 Bios) | GPU: NVIDIA RTX 2080 Ti | RAM: Corsair Vengeance 32 GB DDR4 2666MHz (4x8GB) | Storage: Crucial MX100 512 GB SSD (OS & Apps), 2 Seagate 1TB Serial ATA HD 7200/32MB/SATA-3G (Data - RAID 1) | PSU: Corsair HX1000W | Chassis: Cooler Master HAF X | OS: Win 10 Pro 1809
[quote="Jason20910"]Is there any guide or documentation about the valid statements for the ini file?[/quote]This might be a good time to point you to the most recent entry on Helixmod blog, where I summarize a lot of the links. There is no one spot for all the .ini settings, but that list of links will contain them all indirectly.
The other thing to note would be that you can run the Helix debug versions of the dll. That puts the red text up on screen, but more importantly it starts logging more information. You should try the debug version and see if the LOG.txt has anything for you. Use the same package as Tsaebeht linked above, but use the Debug variant.
Lastly, at the link below, there is a debugging log version (pretty old version nowadays), that has a more extensive logging:
[url]http://helixmod.blogspot.it/2012/03/dlls-update.html[/url]
Jason20910 said:Is there any guide or documentation about the valid statements for the ini file?
This might be a good time to point you to the most recent entry on Helixmod blog, where I summarize a lot of the links. There is no one spot for all the .ini settings, but that list of links will contain them all indirectly.
The other thing to note would be that you can run the Helix debug versions of the dll. That puts the red text up on screen, but more importantly it starts logging more information. You should try the debug version and see if the LOG.txt has anything for you. Use the same package as Tsaebeht linked above, but use the Debug variant.
Lastly, at the link below, there is a debugging log version (pretty old version nowadays), that has a more extensive logging:
[quote="bo3b"][quote="Jason20910"]Is there any guide or documentation about the valid statements for the ini file?[/quote]This might be a good time to point you to the most recent entry on Helixmod blog, where I summarize a lot of the links. There is no one spot for all the .ini settings, but that list of links will contain them all indirectly.
The other thing to note would be that you can run the Helix debug versions of the dll. That puts the red text up on screen, but more importantly it starts logging more information. You should try the debug version and see if the LOG.txt has anything for you. Use the same package as Tsaebeht linked above, but use the Debug variant.
Lastly, at the link below, there is a debugging log version (pretty old version nowadays), that has a more extensive logging:
[url]http://helixmod.blogspot.it/2012/03/dlls-update.html[/url][/quote]
Thanks for these pointers. I have reviewed that post. It is very useful but much went over my head. I tried the debug version of the injector but no red text displayed. I did not notice any log.txt but I will try it again. And, if no luck there I will try the regular debug to see if it tells me anything.
I would think the .ini file is valid since it works fine with the regular Helix d3d9.dll.
I will try this soon. Thanks for the pointers.
UPDATE: I just tried the debug helixmod.dll. I launched HelixLauncher.exe and then the game. It created log.txt and this is the entire file: "Start logging.. ". No red text displayed. Now, if I used the regular debug, the red text displays and there is a lot of log data, but no obvious error message. It seems that The helixmod.dll is not properly injecting when the game is loaded for some reason.
Jason20910 said:Is there any guide or documentation about the valid statements for the ini file?
This might be a good time to point you to the most recent entry on Helixmod blog, where I summarize a lot of the links. There is no one spot for all the .ini settings, but that list of links will contain them all indirectly.
The other thing to note would be that you can run the Helix debug versions of the dll. That puts the red text up on screen, but more importantly it starts logging more information. You should try the debug version and see if the LOG.txt has anything for you. Use the same package as Tsaebeht linked above, but use the Debug variant.
Lastly, at the link below, there is a debugging log version (pretty old version nowadays), that has a more extensive logging:
Thanks for these pointers. I have reviewed that post. It is very useful but much went over my head. I tried the debug version of the injector but no red text displayed. I did not notice any log.txt but I will try it again. And, if no luck there I will try the regular debug to see if it tells me anything.
I would think the .ini file is valid since it works fine with the regular Helix d3d9.dll.
I will try this soon. Thanks for the pointers.
UPDATE: I just tried the debug helixmod.dll. I launched HelixLauncher.exe and then the game. It created log.txt and this is the entire file: "Start logging.. ". No red text displayed. Now, if I used the regular debug, the red text displays and there is a lot of log data, but no obvious error message. It seems that The helixmod.dll is not properly injecting when the game is loaded for some reason.
CPU: i7 5930K, 4.5 (125x36) with Corsair H100i | MB: Asus Rampage V Extreme (1401 Bios) | GPU: NVIDIA RTX 2080 Ti | RAM: Corsair Vengeance 32 GB DDR4 2666MHz (4x8GB) | Storage: Crucial MX100 512 GB SSD (OS & Apps), 2 Seagate 1TB Serial ATA HD 7200/32MB/SATA-3G (Data - RAID 1) | PSU: Corsair HX1000W | Chassis: Cooler Master HAF X | OS: Win 10 Pro 1809
I was wondering if someone can clarify how to use Helix's XCOM script.
So after the part where I add PSscript.lua: I find the pixel shaders that are causing distortion, Note the names & add them to the skip list. Locate the pixel shader in "dumps/allshaders/pixelshaders/" and add file to "shaderoverride/pixelshaders/". Restart the game & repeat as necessary.
Is this procedure correct? Also, will this work with vertex shaders?
I was wondering if someone can clarify how to use Helix's XCOM script.
So after the part where I add PSscript.lua: I find the pixel shaders that are causing distortion, Note the names & add them to the skip list. Locate the pixel shader in "dumps/allshaders/pixelshaders/" and add file to "shaderoverride/pixelshaders/". Restart the game & repeat as necessary.
Is this procedure correct? Also, will this work with vertex shaders?
"Distortion"
Do you mean legitimately called distortion? [Just making sure because it could be vague in meaning]
Documents\My Games\XCOM - Enemy Unknown\XComGame\Config\XComEngine.ini
change
distortion = false
---------------------
Otherwise
[url]http://helixmod.blogspot.com/2012/04/how-to-guide-remove-effects-from-game.html[/url]
Helix's Castlevania fix (with auto book convergence) also doesn't let me save presets. Saving any preset settings work only during my game session. After exit and relaunch they are lost/back to default. I had to manually put my convergence/depth settings in the ini with Notepad.
Thats a good idea, I'll try it.
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
That's worth knowing, it might be an issue with the newest DLL...
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
I tried putting the debug d3d9.dll in the steam\bin folder to find out which shaders cause the problem, but I have not been able to get the red text overlay to appear (though something seems to happen - stereoscopic 3D gets permanently turned off in some cases).
Can someone give me a hint on what I could do better/differently?
New beta drivers give black flag a rating "excellent". Its going to get download link any minute now. Deffo try those drivers first. http://forums.guru3d.com/showthread.php?t=386051
First, please accept my apologies if this is the wrong place to post this, but this seemed the best. I am having an issue using the Call of Juarez Gunslinger fix by DHR posted on Helix Mod site in conjunction with the Helixmod launcher. I am trying to use it to allow Afterburner overlay without problem. I have used the Helximod launcher successfully on other fixes such as Far Cry 3, Blood Dragon, Mass Effect 2, etc. But, for CoJ Gunslinger the fixes do not work with the Helixmod launcher and helixmod.dll in place. If I use the d3d9.dll it works, but if I remove that and use the helixmod.dll with the launcher it does not.
I have added DefModuleName=CoJGunslinger.exe under the General section. I have the files in the same folder as the exe and I never left the d3d9.dll and the helixmod.dll in the folder at the same time. I have tried the most recent and the prior DLL release package to see if that made a difference. The second most recent package seemed to be the one DHR used in his fix based on file size and modified stamp.
I had some similar issues using it for Skyrim but finally got it to work by changing some of the DX9Settings.ini statements (presumably because some syntax has changed with newer dlls?) and finally got it to work.
Anyway, can anyone provide any suggestions as to what might be wrong? Also, is there any way to get any kind of log output to see if the dll is not properly parsing some statement and therefore not erroring out?
Any help will be greatly appreciated.
CPU: i7 5930K, 4.5 (125x36) with Corsair H100i | MB: Asus Rampage V Extreme (1401 Bios) | GPU: NVIDIA RTX 2080 Ti | RAM: Corsair Vengeance 32 GB DDR4 2666MHz (4x8GB) | Storage: Crucial MX100 512 GB SSD (OS & Apps), 2 Seagate 1TB Serial ATA HD 7200/32MB/SATA-3G (Data - RAID 1) | PSU: Corsair HX1000W | Chassis: Cooler Master HAF X | OS: Win 10 Pro 1809
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
[MonitorSizeOverride][Global/Base Profile Tweaks][Depth=IPD]
Hi, thanks. I have tried with that version and the newest version. Neither works. It is really strange as I have gotten it to work with other games. I wish there was some log option to turn on to get some information.
I can just disable Afterburner for the game, but I also prefer the helixmod.dll version because then when I game via either Shield or Steam Home Streaming, the custom dll is not used when not necessary since I am not gaming in 3D.
Is there any guide or documentation about the valid statements for the ini file?
CPU: i7 5930K, 4.5 (125x36) with Corsair H100i | MB: Asus Rampage V Extreme (1401 Bios) | GPU: NVIDIA RTX 2080 Ti | RAM: Corsair Vengeance 32 GB DDR4 2666MHz (4x8GB) | Storage: Crucial MX100 512 GB SSD (OS & Apps), 2 Seagate 1TB Serial ATA HD 7200/32MB/SATA-3G (Data - RAID 1) | PSU: Corsair HX1000W | Chassis: Cooler Master HAF X | OS: Win 10 Pro 1809
The other thing to note would be that you can run the Helix debug versions of the dll. That puts the red text up on screen, but more importantly it starts logging more information. You should try the debug version and see if the LOG.txt has anything for you. Use the same package as Tsaebeht linked above, but use the Debug variant.
Lastly, at the link below, there is a debugging log version (pretty old version nowadays), that has a more extensive logging:
http://helixmod.blogspot.it/2012/03/dlls-update.html
Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers
Thanks for these pointers. I have reviewed that post. It is very useful but much went over my head. I tried the debug version of the injector but no red text displayed. I did not notice any log.txt but I will try it again. And, if no luck there I will try the regular debug to see if it tells me anything.
I would think the .ini file is valid since it works fine with the regular Helix d3d9.dll.
I will try this soon. Thanks for the pointers.
UPDATE: I just tried the debug helixmod.dll. I launched HelixLauncher.exe and then the game. It created log.txt and this is the entire file: "Start logging.. ". No red text displayed. Now, if I used the regular debug, the red text displays and there is a lot of log data, but no obvious error message. It seems that The helixmod.dll is not properly injecting when the game is loaded for some reason.
CPU: i7 5930K, 4.5 (125x36) with Corsair H100i | MB: Asus Rampage V Extreme (1401 Bios) | GPU: NVIDIA RTX 2080 Ti | RAM: Corsair Vengeance 32 GB DDR4 2666MHz (4x8GB) | Storage: Crucial MX100 512 GB SSD (OS & Apps), 2 Seagate 1TB Serial ATA HD 7200/32MB/SATA-3G (Data - RAID 1) | PSU: Corsair HX1000W | Chassis: Cooler Master HAF X | OS: Win 10 Pro 1809
So after the part where I add PSscript.lua: I find the pixel shaders that are causing distortion, Note the names & add them to the skip list. Locate the pixel shader in "dumps/allshaders/pixelshaders/" and add file to "shaderoverride/pixelshaders/". Restart the game & repeat as necessary.
Is this procedure correct? Also, will this work with vertex shaders?
Dual boot Win 7 x64 & Win 10 (1809) | Geforce Drivers 417.35
Do you mean legitimately called distortion? [Just making sure because it could be vague in meaning]
Documents\My Games\XCOM - Enemy Unknown\XComGame\Config\XComEngine.ini
change
distortion = false
---------------------
Otherwise
http://helixmod.blogspot.com/2012/04/how-to-guide-remove-effects-from-game.html
Co-founder/Web host of helixmod.blog.com
Donations for web hosting @ paypal -eqzitara@yahoo.com
or
https://www.patreon.com/user?u=791918