Performance should be fine, though reloading shaders with F10 might take longer. If there's that many though I would seriously consider trying to force them to render in mono instead (unless doing so looks bad)
Performance should be fine, though reloading shaders with F10 might take longer. If there's that many though I would seriously consider trying to force them to render in mono instead (unless doing so looks bad)
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
First of all I want to apologize that I didn't contribute to game fixes the last months - I had not much time for playing and the games I have played had much content to offer (MMORPGs, FF XIII). So I didn't have a look at new games (and fixes).
But now the kickstarter project Woolfe was released and after making a fix for the demo (https://forums.geforce.com/default/topic/787005/3d-vision/woolfe-beautiful-2-5d-platformer-with-promising-s3d-potential/) I would like to offer a fix for the release version. I want to include a fix for dynamic shadows and hope that You can give me some hints how to do that. The game uses the UR3 engine and there are several fixes for dynamic shadows in UR3 games. So I hope that it is quite simple to find a solution. If there is already a tutorial how to fix shadows please tell me where I can find it. I have already tried to use the PSscript.lua (e.g. from Zeno Clash 2) and ShaderH3dFixer.jar (from Mind Path to Thalamus). It changed the PS for the shadow but didn't fix it.
This is the original PS (I hope that I hunted the correct one):
This is the pattern I've been using to fix shadows in UE3 games - I wasn't aware of ShaderH3dFixer.jar, but I did study Mind to find this:
https://github.com/DarkStarSword/3d-fixes/commit/b3654fabe988589ee660a3c02da3fa5e67569c5a
I'd bet the only reason the script didn't work is because it was looking for UE3's usual stereo correction to find where to insert the correction for v0, but for whatever reason that shader is missing it. I reckon if you add that correction near the top of the shader (between the dcl's and the rcp) it will probably do the trick (you will still need the uncorrection before ScreenToShadowMatrix that the script already added for you).
I'd bet the only reason the script didn't work is because it was looking for UE3's usual stereo correction to find where to insert the correction for v0, but for whatever reason that shader is missing it. I reckon if you add that correction near the top of the shader (between the dcl's and the rcp) it will probably do the trick (you will still need the uncorrection before ScreenToShadowMatrix that the script already added for you).
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
// approximately 150 instruction slots used (43 texture, 107 arithmetic)
Unfortunately it didn't fix the shadows but made it worse (outlines moved away from the character). I also wasn't sure about line 78 if I should replace v0 with r30 after the unstereoisation. Anyway it didn't work either with v0 nor r30 in line 78.
Can You see a mistake in my code or is the shader too different from the shadow shaders used in other UR3 games?
My original display name is 3d4dd - for some reason Nvidia changed it..?!
I was working on another UE3 game tonight (Viscera Cleanup Detail), so I decided to add the UE3 shadow fix to my shadertool.py - you can run it from the windows command prompt with something like this:
c:\Python34\python.exe c:\...\shadertool.py --install --auto-fix-unreal-shadows --auto-fix-unreal-light-shafts --only-autofixed Dumps\AllShaders\PixelShader\*
As usual you can grab the latest version from my 3d-fixes repository on github. The pattern it uses to fix the shadows does not depend on the Unreal stereo correction (in fact, if it exists it will actively disable it), so there's a good chance it will work for the shadows in Woolfe.
[s]Edit: If that pattern didn't work by hand then this script probably won't do any better.[/s]
I was working on another UE3 game tonight (Viscera Cleanup Detail), so I decided to add the UE3 shadow fix to my shadertool.py - you can run it from the windows command prompt with something like this:
As usual you can grab the latest version from my 3d-fixes repository on github. The pattern it uses to fix the shadows does not depend on the Unreal stereo correction (in fact, if it exists it will actively disable it), so there's a good chance it will work for the shadows in Woolfe.
Edit: If that pattern didn't work by hand then this script probably won't do any better.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
I see the problem:
[quote="3d4dd"][code]...
// ScreenToShadowMatrix c14 4
...
mul r2, r0.z, c15
// Unstereoise before ScreenToShadowMatrix
add r31.w, r0.x, -r31.y
mad r0.y, -r31.w, r31.x, r0.y
mad r2, c14, r0.y, r2
mad r2, c16, r0.w, r2
add r2, r2, c17
...[/code][/quote]
The problem here is that the x, y and w components don't quite match up with the example I posted - you need to look at what it is using in the matrix multiply to work this out - since ScreenToShadowMatrix starts in c14, then you look at the line with that in it to find what it is using for X. Then add 2 to c14 to get c16 to and look at where that is used to find W.
So here you will need to use r0.w as w (you're using r0.x), and r0.y as x.
My shadertool.py script does this automatically - if you use it, please let me know if it worked for you :)
The problem here is that the x, y and w components don't quite match up with the example I posted - you need to look at what it is using in the matrix multiply to work this out - since ScreenToShadowMatrix starts in c14, then you look at the line with that in it to find what it is using for X. Then add 2 to c14 to get c16 to and look at where that is used to find W.
So here you will need to use r0.w as w (you're using r0.x), and r0.y as x.
My shadertool.py script does this automatically - if you use it, please let me know if it worked for you :)
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
This script sounds very interesting!!!
Unfortunately it didn't work for me - but the reason is most likely that I didn't use it correctly ;)
I have downloaded and installed Python 3.4.3 (https://www.python.org/downloads/) in C:\Python34. I copied the content from https://raw.githubusercontent.com/DarkStarSword/3d-fixes/master/shadertool.py to notepad++ and saved it as shadertool.py. Than I have made a folder C:\shaderfix and placed shadertool.py there. I have also made a folder C:\shaderfix\PixelShader and placed PixelShader_33_CRC32_952E819A.txt inside this folder. In the comand line I wrote c:\Python34\python.exe c:\shaderfix\shadertool.py --install --auto-fix-unreal-shadows --auto-fix-unreal-light-shafts --only-autofixed PixelShader\*
After getting this error message
[code]Traceback (most recent call last):
File "c:\shaderfix\shadertool.py", line 5, in <module>
import shaderutil
ImportError: No module named 'shaderutil'[/code]
I also placed shaderutil.py (from https://raw.githubusercontent.com/DarkStarSword/3d-fixes/master/shaderutil.py) in c:\shaderfix\
When I entered the command line again I got no (error) message but the shader was unchanged and I only could find shaderutil.cpython-34.pyc in C:\shaderfix\__pycache__
Edit: I have manually replaced r0.x with r0.w in the shader and the shadows are perfect now :) But it would be great to be able to use Your shadertool for other games!
This script sounds very interesting!!!
Unfortunately it didn't work for me - but the reason is most likely that I didn't use it correctly ;)
I have downloaded and installed Python 3.4.3 (https://www.python.org/downloads/) in C:\Python34. I copied the content from https://raw.githubusercontent.com/DarkStarSword/3d-fixes/master/shadertool.py to notepad++ and saved it as shadertool.py. Than I have made a folder C:\shaderfix and placed shadertool.py there. I have also made a folder C:\shaderfix\PixelShader and placed PixelShader_33_CRC32_952E819A.txt inside this folder. In the comand line I wrote c:\Python34\python.exe c:\shaderfix\shadertool.py --install --auto-fix-unreal-shadows --auto-fix-unreal-light-shafts --only-autofixed PixelShader\*
After getting this error message
Traceback (most recent call last):
File "c:\shaderfix\shadertool.py", line 5, in <module>
import shaderutil
ImportError: No module named 'shaderutil'
Edit: I have manually replaced r0.x with r0.w in the shader and the shadows are perfect now :) But it would be great to be able to use Your shadertool for other games!
My original display name is 3d4dd - for some reason Nvidia changed it..?!
Oh yeah, I forgot to mention that it won't overwrite a shader that is already in the ShaderOverride folder unless you specify both --install and --force (to make sure it won't accidentally overwrite a manual fix).
I used to make it print out a message saying that it needed --force to overwrite a shader, but I removed it for Life Is Strange where the act of printing out that message 3,000 times was starting to take a significant amount of time. It will still print it if you specify --verbose, but I think I'll bring it back as the default and add a --quiet to suppress it instead.
You can also use --in-place to fix a shader without copying it anywhere (say, to fix something already in ShaderOverride), but my intention is that the script would usually be run on the original shaders in Dumps and copied to ShaderOverride with --install (it may not always do what you expect if you run it on a shader that already has the stereo sampler or other fix applied). If you run the script with --help it will tell you all the other options it supports.
Oh yeah, I forgot to mention that it won't overwrite a shader that is already in the ShaderOverride folder unless you specify both --install and --force (to make sure it won't accidentally overwrite a manual fix).
I used to make it print out a message saying that it needed --force to overwrite a shader, but I removed it for Life Is Strange where the act of printing out that message 3,000 times was starting to take a significant amount of time. It will still print it if you specify --verbose, but I think I'll bring it back as the default and add a --quiet to suppress it instead.
You can also use --in-place to fix a shader without copying it anywhere (say, to fix something already in ShaderOverride), but my intention is that the script would usually be run on the original shaders in Dumps and copied to ShaderOverride with --install (it may not always do what you expect if you run it on a shader that already has the stereo sampler or other fix applied). If you run the script with --help it will tell you all the other options it supports.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
[quote="DarkStarSword"]I think I'll bring it back as the default and add a --quiet to suppress it instead.[/quote]This is done. It will now also print out an error if you don't pass it any arguments to tell it what to do with the result (like if you forget --install)
DarkStarSword said:I think I'll bring it back as the default and add a --quiet to suppress it instead.
This is done. It will now also print out an error if you don't pass it any arguments to tell it what to do with the result (like if you forget --install)
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
I need help.
I'm trying to disable the hud in a game using the Helix mod. I want to toggle the hud on/off with a key press.
I've been through bo3b's shaderhacker tutorial, but I have a problem.
I copy the shader into the Shaderoverride/vertexshaders folder and rename it correctly. When I run the game, the effect is automatically disabled before I've edited anything in the shader. Why is that happening? I need to be able to turn it on and off.
Guts of the shader:
[code]//
vs_2_0
dcl_position v0
dcl_color v1
dcl_color1 v2
dp4 oPos.x, v0, c0
dp4 oPos.y, v0, c1
dp4 oT0.x, v0, c2
dp4 oT0.y, v0, c3
mov oPos.zw, v0
mov oD0, v1.zyxw
mov oD1, v2.zyxw
// approximately 7 instruction slots used[/code]
I'm trying to disable the hud in a game using the Helix mod. I want to toggle the hud on/off with a key press.
I've been through bo3b's shaderhacker tutorial, but I have a problem.
I copy the shader into the Shaderoverride/vertexshaders folder and rename it correctly. When I run the game, the effect is automatically disabled before I've edited anything in the shader. Why is that happening? I need to be able to turn it on and off.
@ hudfreegamer
The shader needs to be converted to VS_3_0
[code] vs_3_0
dcl_position o10
dcl_texcoord o0.xy
dcl_color o8
dcl_color1 o9
dcl_position v0
dcl_color v1
dcl_color1 v2
dp4 o10.x, v0, c0
dp4 o10.y, v0, c1
dp4 o0.x, v0, c2
dp4 o0.y, v0, c3
mov o10.zw, v0
mov o8, v1.zyxw
mov o9, v2.zyxw[/code]
DarkStarSword has a good tool to convert VS 2.0 to 3.0: [url]https://github.com/DarkStarSword/3d-fixes#shadertoolpy[/url]
Also, TsaebehT has a program for this (ShaderConverter), but I can't locate the link for it at the moment.
How do I use that python shader converter? I get syntax errors. I just want a straight conversion from v2_0 to v_3_0.
This is what I tried (I entered the first line, the rest was generated by the program):
[code]>>> python shadertool.py 0B3F4AB7.txt
File "<stdin>", line 1
python shadertool.py 0B3F4AB7.txt
^
SyntaxError: invalid syntax
[/code]
I tried different combinations of brackets and quote marks, but I keep getting the same error.
@hudfreegamer: I guess You have to enter the path for python.exe, the path for shadertool.py, different arguments (like --install --auto-fix-unreal-shadows etc., see --help) and the path where the pixel shaders are stored (I had to enter the complete path to get the tool to work e.g. C:\test\ShaderOverride\PixelShaders\*). So it should look like this:
c:\Python34\python.exe c:\shaderfix\shadertool.py --install --auto-fix-unreal-shadows --auto-fix-unreal-light-shafts --only-autofixed C:\test\Dumps\AllShaders\PixelShader\*
@4everAwake,DarkStarSword: Thanks to Your hints PS 952E819A is fixed now (using the tool or doing it manually). Now I have stumbled across another PS which is responsible for dynamic shadows in a sunset scenario. It is very similar to PS 952E819A but in this case using the tool didn't fix the shader.
This is the original code for PS 1341BDFB:
// approximately 134 instruction slots used (43 texture, 91 arithmetic)
Any idea why it worked for PS 952E819A but not for PS 1341BDFB? Both look very similar to me. And disabling PS 1341BDFB removed the broken shadows so I think that I hunted the right shader...
My original display name is 3d4dd - for some reason Nvidia changed it..?!
4everAwake showed me how to toggle shaders here: [url]https://forums.geforce.com/default/topic/513190/3d-vision/how-to-fix-disable-shaders-in-games-dll-guide-and-fixes-/post/4491727/#4491727[/url]
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
But now the kickstarter project Woolfe was released and after making a fix for the demo (https://forums.geforce.com/default/topic/787005/3d-vision/woolfe-beautiful-2-5d-platformer-with-promising-s3d-potential/) I would like to offer a fix for the release version. I want to include a fix for dynamic shadows and hope that You can give me some hints how to do that. The game uses the UR3 engine and there are several fixes for dynamic shadows in UR3 games. So I hope that it is quite simple to find a solution. If there is already a tutorial how to fix shadows please tell me where I can find it. I have already tried to use the PSscript.lua (e.g. from Zeno Clash 2) and ShaderH3dFixer.jar (from Mind Path to Thalamus). It changed the PS for the shadow but didn't fix it.
This is the original PS (I hope that I hunted the correct one):
This is the changed shader by ShaderH3dFixer.jar (that didn't work):
The depth of the shadow seems to be correct if You look at the square You get when hunting the PS: http://photos.3dvisionlive.com/3d4dd/image/550b2406e7e564b43a00020c/ Only the outlines are wrong and also suffer from halo like issues: http://photos.3dvisionlive.com/3d4dd/image/550b243ee7e564894f00008b/
Do You have a suggestion how to fix the shader...?
My original display name is 3d4dd - for some reason Nvidia changed it..?!
https://github.com/DarkStarSword/3d-fixes/commit/b3654fabe988589ee660a3c02da3fa5e67569c5a
I'd bet the only reason the script didn't work is because it was looking for UE3's usual stereo correction to find where to insert the correction for v0, but for whatever reason that shader is missing it. I reckon if you add that correction near the top of the shader (between the dcl's and the rcp) it will probably do the trick (you will still need the uncorrection before ScreenToShadowMatrix that the script already added for you).
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
Unfortunately it didn't fix the shadows but made it worse (outlines moved away from the character). I also wasn't sure about line 78 if I should replace v0 with r30 after the unstereoisation. Anyway it didn't work either with v0 nor r30 in line 78.
Can You see a mistake in my code or is the shader too different from the shadow shaders used in other UR3 games?
My original display name is 3d4dd - for some reason Nvidia changed it..?!
c:\Python34\python.exe c:\...\shadertool.py --install --auto-fix-unreal-shadows --auto-fix-unreal-light-shafts --only-autofixed Dumps\AllShaders\PixelShader\*
As usual you can grab the latest version from my 3d-fixes repository on github. The pattern it uses to fix the shadows does not depend on the Unreal stereo correction (in fact, if it exists it will actively disable it), so there's a good chance it will work for the shadows in Woolfe.
Edit: If that pattern didn't work by hand then this script probably won't do any better.2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
The problem here is that the x, y and w components don't quite match up with the example I posted - you need to look at what it is using in the matrix multiply to work this out - since ScreenToShadowMatrix starts in c14, then you look at the line with that in it to find what it is using for X. Then add 2 to c14 to get c16 to and look at where that is used to find W.
So here you will need to use r0.w as w (you're using r0.x), and r0.y as x.
My shadertool.py script does this automatically - if you use it, please let me know if it worked for you :)
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
Unfortunately it didn't work for me - but the reason is most likely that I didn't use it correctly ;)
I have downloaded and installed Python 3.4.3 (https://www.python.org/downloads/) in C:\Python34. I copied the content from https://raw.githubusercontent.com/DarkStarSword/3d-fixes/master/shadertool.py to notepad++ and saved it as shadertool.py. Than I have made a folder C:\shaderfix and placed shadertool.py there. I have also made a folder C:\shaderfix\PixelShader and placed PixelShader_33_CRC32_952E819A.txt inside this folder. In the comand line I wrote c:\Python34\python.exe c:\shaderfix\shadertool.py --install --auto-fix-unreal-shadows --auto-fix-unreal-light-shafts --only-autofixed PixelShader\*
After getting this error message
I also placed shaderutil.py (from https://raw.githubusercontent.com/DarkStarSword/3d-fixes/master/shaderutil.py) in c:\shaderfix\
When I entered the command line again I got no (error) message but the shader was unchanged and I only could find shaderutil.cpython-34.pyc in C:\shaderfix\__pycache__
Edit: I have manually replaced r0.x with r0.w in the shader and the shadows are perfect now :) But it would be great to be able to use Your shadertool for other games!
My original display name is 3d4dd - for some reason Nvidia changed it..?!
I used to make it print out a message saying that it needed --force to overwrite a shader, but I removed it for Life Is Strange where the act of printing out that message 3,000 times was starting to take a significant amount of time. It will still print it if you specify --verbose, but I think I'll bring it back as the default and add a --quiet to suppress it instead.
You can also use --in-place to fix a shader without copying it anywhere (say, to fix something already in ShaderOverride), but my intention is that the script would usually be run on the original shaders in Dumps and copied to ShaderOverride with --install (it may not always do what you expect if you run it on a shader that already has the stereo sampler or other fix applied). If you run the script with --help it will tell you all the other options it supports.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
VS 952E819A
Dual boot Win 7 x64 & Win 10 (1809) | Geforce Drivers 417.35
I'm trying to disable the hud in a game using the Helix mod. I want to toggle the hud on/off with a key press.
I've been through bo3b's shaderhacker tutorial, but I have a problem.
I copy the shader into the Shaderoverride/vertexshaders folder and rename it correctly. When I run the game, the effect is automatically disabled before I've edited anything in the shader. Why is that happening? I need to be able to turn it on and off.
Guts of the shader:
The shader needs to be converted to VS_3_0
DarkStarSword has a good tool to convert VS 2.0 to 3.0: https://github.com/DarkStarSword/3d-fixes#shadertoolpy
Also, TsaebehT has a program for this (ShaderConverter), but I can't locate the link for it at the moment.
Dual boot Win 7 x64 & Win 10 (1809) | Geforce Drivers 417.35
This is what I tried (I entered the first line, the rest was generated by the program):
I tried different combinations of brackets and quote marks, but I keep getting the same error.
c:\Python34\python.exe c:\shaderfix\shadertool.py --install --auto-fix-unreal-shadows --auto-fix-unreal-light-shafts --only-autofixed C:\test\Dumps\AllShaders\PixelShader\*
@4everAwake,DarkStarSword: Thanks to Your hints PS 952E819A is fixed now (using the tool or doing it manually). Now I have stumbled across another PS which is responsible for dynamic shadows in a sunset scenario. It is very similar to PS 952E819A but in this case using the tool didn't fix the shader.
This is the original code for PS 1341BDFB:
This is the fixed code by the tool (shadows still broken):
Any idea why it worked for PS 952E819A but not for PS 1341BDFB? Both look very similar to me. And disabling PS 1341BDFB removed the broken shadows so I think that I hunted the right shader...
My original display name is 3d4dd - for some reason Nvidia changed it..?!