How to fix/disable shaders in games(DLL,guide and fixes).
106 / 167
@eqzitara Thanks for the advice. With Divinity 2 I did identify that both vertex shaders and pixel shaders can be disabled to remove shadows, so I was working on the assumption that both would need fixing to correct the shadows. I also looked at Mana84's UT3 fix and he has a VS shader fix for shadows as well. I suppose that just means the job is a whole lot more than I was hoping for ;-)
I seem to remember someone recommended a book on shader programming in this thread, but can't seem to find it - anyone know what it is? I would love to be able to contribute more to this endeavour, but the whole thing about having a wife, kids, and a job keeps getting in the way... Not forgetting actually [i]playing[/i] games of course.
@eqzitara Thanks for the advice. With Divinity 2 I did identify that both vertex shaders and pixel shaders can be disabled to remove shadows, so I was working on the assumption that both would need fixing to correct the shadows. I also looked at Mana84's UT3 fix and he has a VS shader fix for shadows as well. I suppose that just means the job is a whole lot more than I was hoping for ;-)
I seem to remember someone recommended a book on shader programming in this thread, but can't seem to find it - anyone know what it is? I would love to be able to contribute more to this endeavour, but the whole thing about having a wife, kids, and a job keeps getting in the way... Not forgetting actually playing games of course.
Ok, this is the deal: if someone could fix bioshock 2 in dx9 I would pay 200 Euro's blindly for it because it's my favorite game ever. To be able to go Rapture in 6000X1080 in 3D is priceless to me.[b][u]REALLY[/u][/b]![/quote]
Ok, this is the deal: if someone could fix bioshock 2 in dx9 I would pay 200 Euro's blindly for it because it's my favorite game ever. To be able to go Rapture in 6000X1080 in 3D is priceless to me.REALLY!
[quote="Schmeltzer"]Ok, this is the deal: if someone could fix bioshock 2 in dx9 I would pay 200 Euro's blindly for it because it's my favorite game ever. To be able to go Rapture in 6000X1080 in 3D is priceless to me. [b][u]REALLY[/u][/b]![/quote]
Schmeltzer said:Ok, this is the deal: if someone could fix bioshock 2 in dx9 I would pay 200 Euro's blindly for it because it's my favorite game ever. To be able to go Rapture in 6000X1080 in 3D is priceless to me. REALLY!
@Schmeltzer
I have managed to get Bioshock to look pretty good in 3D by disabling one Vertex Shader and turning off "Shadow Maps", "High Detail Post Processing", "Distortion" and "Directx 10 Feature" in graphic settings. There are much fewer issues once the Vertex Shader is removed.
2D19FD90 - Disabling this VS shader made a world of difference. Removed the ambient effects that messed up the 3D. Keep in mind that is by no means a fix. The contents of 2D19FD90.txt is
vs_3_0
dcl_position v0
dcl_position o0
This has worked for me using Helix Debug DLL (just F11 to turn off red text at top) before playing. I can adjust depth and convergence by quite a bit to get my desired look.
See this URL for clarity on how to disable an effect
http://helixmod.blogspot.ca/2012/04/how-to-guide-remove-effects-from-game.html
I'm not sure if creating the same txt file that I have in the ShaderOverride/VertexShaders folder will work for you...if it doesn't you can always use the above link to learn how to cycle through the shaders and disable those that affect your game...disabling is very easy to do....sorry that this is not an actual fix, but might be of use for you and get you by until there is a legitimate fix.....I have enjoyed Bioshock 1 in 3D after disabling that one VS and above mentioned graphic settings. I have enjoyed the games immersion in 3D
Hope this helps...
I have managed to get Bioshock to look pretty good in 3D by disabling one Vertex Shader and turning off "Shadow Maps", "High Detail Post Processing", "Distortion" and "Directx 10 Feature" in graphic settings. There are much fewer issues once the Vertex Shader is removed.
2D19FD90 - Disabling this VS shader made a world of difference. Removed the ambient effects that messed up the 3D. Keep in mind that is by no means a fix. The contents of 2D19FD90.txt is
vs_3_0
dcl_position v0
dcl_position o0
This has worked for me using Helix Debug DLL (just F11 to turn off red text at top) before playing. I can adjust depth and convergence by quite a bit to get my desired look.
I'm not sure if creating the same txt file that I have in the ShaderOverride/VertexShaders folder will work for you...if it doesn't you can always use the above link to learn how to cycle through the shaders and disable those that affect your game...disabling is very easy to do....sorry that this is not an actual fix, but might be of use for you and get you by until there is a legitimate fix.....I have enjoyed Bioshock 1 in 3D after disabling that one VS and above mentioned graphic settings. I have enjoyed the games immersion in 3D
@eqzitara: Thanks for your guess regarding this skyrim's shader and by the way many thanks for what you've done already to improve 3D gaming experience (with fabulous Helix tools and fixes)! That's cool to share.
Unfortunately this modifications are not working yet: the sky remains at screen depth. So I searched for the sovngarde's sky shader again and found another one.
So I tried to figure out the lines you edited previously to 'inject' (and adapt) them in this new shader. I found these modifications you made:
5. def c200, 750.0, 0, -100, 0 // I know this is for setting new depth to 750. why c200? why -100?
...
10. dcl_2d s0 // shader 2d mode?
...
44. dp4 r10.w, c183, r3 // no idea what it does
...
80. mov r10.xyz, r0 // no idea what is this for
81. mul r10.xyzw, r10, c200.x
82. mov o0, r10
I hope that is not asking too much, just trying to go further somehow...
[quote="Schmeltzer"]I think having a tutorial "fixing games for dummies" would help me (and others) a great deal.[/quote] Definitely. ;)
Cheers!
@eqzitara: Thanks for your guess regarding this skyrim's shader and by the way many thanks for what you've done already to improve 3D gaming experience (with fabulous Helix tools and fixes)! That's cool to share.
Unfortunately this modifications are not working yet: the sky remains at screen depth. So I searched for the sovngarde's sky shader again and found another one.
So I tried to figure out the lines you edited previously to 'inject' (and adapt) them in this new shader. I found these modifications you made:
5. def c200, 750.0, 0, -100, 0 // I know this is for setting new depth to 750. why c200? why -100?
...
10. dcl_2d s0 // shader 2d mode?
...
44. dp4 r10.w, c183, r3 // no idea what it does
...
80. mov r10.xyz, r0 // no idea what is this for
81. mul r10.xyzw, r10, c200.x
82. mov o0, r10
I hope that is not asking too much, just trying to go further somehow...
Schmeltzer said:I think having a tutorial "fixing games for dummies" would help me (and others) a great deal.
Hi, I've juste registered, so I can maybe spare some guys to search:
I used Helix Debug file to remove Player shadows in PES2013, the only annoying thing left ist vertex shader 66373B07, which I couldn't remove nor set back.
Maybe someone could give advise...
Thank All of You, especially Helix for his tool!!!!!
[url]https://dl.dropbox.com/u/2878489/PES2013NoPlayerShadows.zip[/url]
[url]https://dl.dropbox.com/u/2878489/66373B07.txt[/url]
Maybe someone could provide the files elsewhere, they are on dropbox now...
Cheers,
Mzsk
Hi, I've juste registered, so I can maybe spare some guys to search:
I used Helix Debug file to remove Player shadows in PES2013, the only annoying thing left ist vertex shader 66373B07, which I couldn't remove nor set back.
Maybe someone could give advise...
Thank All of You, especially Helix for his tool!!!!!
Probably not everyone's cup of tea, but I got the demo for a new game on Steam called "Euro Truck Simulator 2", and it looks pretty great in stereo 3D. The only problem I have seen so far (and I have only trundled around Grimsby in England, during the day, so far) is that cloud cover is too low. I found the shader for this, and had my first successful fix (!) pushing the depth right back. Unfortunately it also makes some of the foreground 'ground areas' like parts of the road etc also have high depth (which makes cars look like they are floating on parts of the road, which is worse than having clouds at the wrong depth).
The demo can be found here: http://www.eurotrucksimulator2.com/download.php
The shader is pretty simple, here is the before and after:
BEFORE
vs_3_0
dcl_position v0
dcl_normal v1
dcl_color v2
dcl_texcoord v3
dcl_texcoord1 v4
dcl_position o0
dcl_color o1
dcl_texcoord o2.xyz
dcl_texcoord1 o3.xyz
dcl_texcoord2 o4
dp4 o0.x, v0, c0
dp4 o0.y, v0, c1
dp4 o0.z, v0, c2
dp4 o0.w, v0, c3
dp4 o2.x, v0, c4
dp4 o2.y, v0, c5
dp4 o2.z, v0, c6
dp3 o3.x, v1, c4
dp3 o3.y, v1, c5
dp3 o3.z, v1, c6
mov o1, v2
mov o4.xy, v3
mov o4.zw, v4.xyxy
AFTER
vs_3_0
def c220, 10000, 0, 0, 0
dcl_position v0
dcl_normal v1
dcl_color v2
dcl_texcoord v3
dcl_texcoord1 v4
dcl_position o0
dcl_color o1
dcl_texcoord o2.xyz
dcl_texcoord1 o3.xyz
dcl_texcoord2 o4
dp4 r10.x, v0, c0
dp4 r10.y, v0, c1
dp4 r10.z, v0, c2
dp4 r10.w, v0, c3
mul r10, r10, c220.x
mov o0, r10
dp4 o2.x, v0, c4
dp4 o2.y, v0, c5
dp4 o2.z, v0, c6
dp3 o3.x, v1, c4
dp3 o3.y, v1, c5
dp3 o3.z, v1, c6
mov o1, v2
mov o4.xy, v3
mov o4.zw, v4.xyxy
I attach a before and after jps screenshot as well as one with the shader removed so you can see how different bits are affected.
https://www.dropbox.com/sh/dggascskoqn4prv/KtZQmazN1N
Any ideas on if this can be fixed?
Probably not everyone's cup of tea, but I got the demo for a new game on Steam called "Euro Truck Simulator 2", and it looks pretty great in stereo 3D. The only problem I have seen so far (and I have only trundled around Grimsby in England, during the day, so far) is that cloud cover is too low. I found the shader for this, and had my first successful fix (!) pushing the depth right back. Unfortunately it also makes some of the foreground 'ground areas' like parts of the road etc also have high depth (which makes cars look like they are floating on parts of the road, which is worse than having clouds at the wrong depth).
The demo can be found here: http://www.eurotrucksimulator2.com/download.php
[quote="Stryker_66"]@Schmeltzer
I have managed to get Bioshock to look pretty good in 3D by disabling one Vertex Shader and turning off "Shadow Maps", "High Detail Post Processing", "Distortion" and "Directx 10 Feature" in graphic settings. There are much fewer issues once the Vertex Shader is removed.
2D19FD90 - Disabling this VS shader made a world of difference. Removed the ambient effects that messed up the 3D. Keep in mind that is by no means a fix. The contents of 2D19FD90.txt is
vs_3_0
dcl_position v0
dcl_position o0
This has worked for me using Helix Debug DLL (just F11 to turn off red text at top) before playing. I can adjust depth and convergence by quite a bit to get my desired look.
See this URL for clarity on how to disable an effect
http://helixmod.blogspot.ca/2012/04/how-to-guide-remove-effects-from-game.html
I'm not sure if creating the same txt file that I have in the ShaderOverride/VertexShaders folder will work for you...if it doesn't you can always use the above link to learn how to cycle through the shaders and disable those that affect your game...disabling is very easy to do....sorry that this is not an actual fix, but might be of use for you and get you by until there is a legitimate fix.....I have enjoyed Bioshock 1 in 3D after disabling that one VS and above mentioned graphic settings. I have enjoyed the games immersion in 3D
Hope this helps...[/quote]
I tried adding that shader txt to the override folder but it didn't do anything to fix the game as I saw it, so could you pls upload it somewhere?
And I would add $10 to the bioshock pot mentioned before, not much but im poor sorry.
I have managed to get Bioshock to look pretty good in 3D by disabling one Vertex Shader and turning off "Shadow Maps", "High Detail Post Processing", "Distortion" and "Directx 10 Feature" in graphic settings. There are much fewer issues once the Vertex Shader is removed.
2D19FD90 - Disabling this VS shader made a world of difference. Removed the ambient effects that messed up the 3D. Keep in mind that is by no means a fix. The contents of 2D19FD90.txt is
vs_3_0
dcl_position v0
dcl_position o0
This has worked for me using Helix Debug DLL (just F11 to turn off red text at top) before playing. I can adjust depth and convergence by quite a bit to get my desired look.
See this URL for clarity on how to disable an effect
I'm not sure if creating the same txt file that I have in the ShaderOverride/VertexShaders folder will work for you...if it doesn't you can always use the above link to learn how to cycle through the shaders and disable those that affect your game...disabling is very easy to do....sorry that this is not an actual fix, but might be of use for you and get you by until there is a legitimate fix.....I have enjoyed Bioshock 1 in 3D after disabling that one VS and above mentioned graphic settings. I have enjoyed the games immersion in 3D
Hope this helps...
I tried adding that shader txt to the override folder but it didn't do anything to fix the game as I saw it, so could you pls upload it somewhere?
And I would add $10 to the bioshock pot mentioned before, not much but im poor sorry.
All hail 3d modders DHR, MasterOtaku, Losti, Necropants, Helifax, bo3b, mike_ar69, Flugan, DarkStarSword, 4everAwake, 3d4dd and so many more helping to keep the 3d dream alive, find their 3d fixes at http://helixmod.blogspot.com/ Also check my site for spanish VR and mobile gaming news: www.gamermovil.com
Hi,
I am trying to get lefuneste's Rise of flight working on the latest exe (1.129). I am running the debug exe and have been able to fix the shader for labels (VSED87B35) by using lefuneste's original shaderfix code but changing filename for new CRC. However, I can't find the shader for icons etc.
I am trying to dump existing shaders and whilst I get the dump directories created on startup, when pressing the NUMLOCK6 to dump currently disabled vs shader, i get no message on the debug hud, nor do I get any shader code dumped. I can't seem to get any shader code dumped/written using the debug dll. Other default keys seem to work fine, just cant dump shaders.
Any help would be greatly appreciated.
I am trying to get lefuneste's Rise of flight working on the latest exe (1.129). I am running the debug exe and have been able to fix the shader for labels (VSED87B35) by using lefuneste's original shaderfix code but changing filename for new CRC. However, I can't find the shader for icons etc.
I am trying to dump existing shaders and whilst I get the dump directories created on startup, when pressing the NUMLOCK6 to dump currently disabled vs shader, i get no message on the debug hud, nor do I get any shader code dumped. I can't seem to get any shader code dumped/written using the debug dll. Other default keys seem to work fine, just cant dump shaders.
I know this isn't really a place for requests and in essence this really even isn't one, but rather just more of a reminder. Earlier in this thread I along some others asked if one of you wonderful people who know how to fix this stuff could maybe take a look at a few games that came out a few moths a go. Games such as Lucius, Painkiller - Hell and Damnation and Deadlight. I'm just wondering if there's a chance if some these would be given a look at at some point? I've held off from playing these games until there's either a fix of some kind or if there's a mention that they're not fixable/not going to be fixed at all. Once again a huge thanks to Helix, eqzitara and many others for keeping 3D Vision alive!
I know this isn't really a place for requests and in essence this really even isn't one, but rather just more of a reminder. Earlier in this thread I along some others asked if one of you wonderful people who know how to fix this stuff could maybe take a look at a few games that came out a few moths a go. Games such as Lucius, Painkiller - Hell and Damnation and Deadlight. I'm just wondering if there's a chance if some these would be given a look at at some point? I've held off from playing these games until there's either a fix of some kind or if there's a mention that they're not fixable/not going to be fixed at all. Once again a huge thanks to Helix, eqzitara and many others for keeping 3D Vision alive!
Intel i5 2500K @ 4.5GHz
Asus P8P67 PRO
Corsair XMS3 DDR3 8GB
nVidia GTX 660 SLI + nVidia 3D Vision
Asus Xonar Essence ST with AKG K601/Sennheiser HD 595
Corsair Force GT 120GB SSD + 5TB HDD Storage
Corsair AX 850 PSU
Coolermaster HAF 932 Case
[quote="BazzaLB"]Hi,
I am trying to get lefuneste's Rise of flight working on the latest exe (1.129). I can't seem to get any shader code dumped/written using the debug dll. Other default keys seem to work fine, just cant dump shaders.
Any help would be greatly appreciated.[/quote]
As my fix is still working on my system with the 1.29 verison of Rof, I'm very suprised by the shader change with your PC.
This remind me the strange problem I had before (see page 103). As RoF ask for a directX update, maybe you have the same problem ? Unforunately I have no solution for this problem, except restoring a system backup...
This time I did not allow the directX update for the RoF 1.29 install, because of the above problem.
Anyway, as RoF is still working on my PC, there is no reason to dump the shaders, you just have to rename them with the new references, that you will find by disabling the shader one by one with the debug library.
I remember that I use a shader that make the screen black to for the jauges.
I am trying to get lefuneste's Rise of flight working on the latest exe (1.129). I can't seem to get any shader code dumped/written using the debug dll. Other default keys seem to work fine, just cant dump shaders.
Any help would be greatly appreciated.
As my fix is still working on my system with the 1.29 verison of Rof, I'm very suprised by the shader change with your PC.
This remind me the strange problem I had before (see page 103). As RoF ask for a directX update, maybe you have the same problem ? Unforunately I have no solution for this problem, except restoring a system backup...
This time I did not allow the directX update for the RoF 1.29 install, because of the above problem.
Anyway, as RoF is still working on my PC, there is no reason to dump the shaders, you just have to rename them with the new references, that you will find by disabling the shader one by one with the debug library.
I remember that I use a shader that make the screen black to for the jauges.
[quote="lefuneste"]As my fix is still working on my system with the 1.29 verison of Rof, I'm very suprised by the shader change with your PC.
This remind me the strange problem I had before (see page 103). As RoF ask for a directX update, maybe you have the same problem ? Unforunately I have no solution for this problem, except restoring a system backup...
This time I did not allow the directX update for the RoF 1.29 install, because of the above problem.
Anyway, as RoF is still working on my PC, there is no reason to dump the shaders, you just have to rename them with the new references, that you will find by disabling the shader one by one with the debug library.
I remember that I use a shader that make the screen black to for the jauges.[/quote]
Thanks for the feedback. This is wierd. I never let dx get updated by the installers. Oh well. I have tried unsuccessfully to determine the new CRCs for your original fixes for anything other than the labels. Labels was VS number 3 in debug. If you get a chance, could you possibly indicate which shader number via the debug exe the shaders are for you? I will then just get the CRCs for those numbered shaders and see if that works.
Anyway, thanks for your feedback.
lefuneste said:As my fix is still working on my system with the 1.29 verison of Rof, I'm very suprised by the shader change with your PC.
This remind me the strange problem I had before (see page 103). As RoF ask for a directX update, maybe you have the same problem ? Unforunately I have no solution for this problem, except restoring a system backup...
This time I did not allow the directX update for the RoF 1.29 install, because of the above problem.
Anyway, as RoF is still working on my PC, there is no reason to dump the shaders, you just have to rename them with the new references, that you will find by disabling the shader one by one with the debug library.
I remember that I use a shader that make the screen black to for the jauges.
Thanks for the feedback. This is wierd. I never let dx get updated by the installers. Oh well. I have tried unsuccessfully to determine the new CRCs for your original fixes for anything other than the labels. Labels was VS number 3 in debug. If you get a chance, could you possibly indicate which shader number via the debug exe the shaders are for you? I will then just get the CRCs for those numbered shaders and see if that works.
I seem to remember someone recommended a book on shader programming in this thread, but can't seem to find it - anyone know what it is? I would love to be able to contribute more to this endeavour, but the whole thing about having a wife, kids, and a job keeps getting in the way... Not forgetting actually playing games of course.
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
I have managed to get Bioshock to look pretty good in 3D by disabling one Vertex Shader and turning off "Shadow Maps", "High Detail Post Processing", "Distortion" and "Directx 10 Feature" in graphic settings. There are much fewer issues once the Vertex Shader is removed.
2D19FD90 - Disabling this VS shader made a world of difference. Removed the ambient effects that messed up the 3D. Keep in mind that is by no means a fix. The contents of 2D19FD90.txt is
vs_3_0
dcl_position v0
dcl_position o0
This has worked for me using Helix Debug DLL (just F11 to turn off red text at top) before playing. I can adjust depth and convergence by quite a bit to get my desired look.
See this URL for clarity on how to disable an effect
http://helixmod.blogspot.ca/2012/04/how-to-guide-remove-effects-from-game.html
I'm not sure if creating the same txt file that I have in the ShaderOverride/VertexShaders folder will work for you...if it doesn't you can always use the above link to learn how to cycle through the shaders and disable those that affect your game...disabling is very easy to do....sorry that this is not an actual fix, but might be of use for you and get you by until there is a legitimate fix.....I have enjoyed Bioshock 1 in 3D after disabling that one VS and above mentioned graphic settings. I have enjoyed the games immersion in 3D
Hope this helps...
Co-founder/Web host of helixmod.blog.com
Donations for web hosting @ paypal -eqzitara@yahoo.com
or
https://www.patreon.com/user?u=791918
Unfortunately this modifications are not working yet: the sky remains at screen depth. So I searched for the sovngarde's sky shader again and found another one.
So I tried to figure out the lines you edited previously to 'inject' (and adapt) them in this new shader. I found these modifications you made:
5. def c200, 750.0, 0, -100, 0 // I know this is for setting new depth to 750. why c200? why -100?
...
10. dcl_2d s0 // shader 2d mode?
...
44. dp4 r10.w, c183, r3 // no idea what it does
...
80. mov r10.xyz, r0 // no idea what is this for
81. mul r10.xyzw, r10, c200.x
82. mov o0, r10
I hope that is not asking too much, just trying to go further somehow...
Definitely. ;)
Cheers!
Helixmod fixes for 3Dvision / 3Dtvplay
My 3D stereo screenshots
Skyrim Natural Realizm - The 3Dvision Immersive ENB Hub page on Nexus
Skyrim Natural Realizm - The 3Dvision Immersive ENB Gallery
CPU: i7 @ 3.40
GhzRAM: 8Go DDR3
GPU(s): GTX980ti
Display(s): HTC Vive and OptomaHD33 projector with 3D-RF system (3DTVplay)
Result: Gorgious 3D gaming and VR experiences! :D
I used Helix Debug file to remove Player shadows in PES2013, the only annoying thing left ist vertex shader 66373B07, which I couldn't remove nor set back.
Maybe someone could give advise...
Thank All of You, especially Helix for his tool!!!!!
https://dl.dropbox.com/u/2878489/PES2013NoPlayerShadows.zip
https://dl.dropbox.com/u/2878489/66373B07.txt
Maybe someone could provide the files elsewhere, they are on dropbox now...
Cheers,
Mzsk
The demo can be found here: http://www.eurotrucksimulator2.com/download.php
The shader is pretty simple, here is the before and after:
BEFORE
vs_3_0
dcl_position v0
dcl_normal v1
dcl_color v2
dcl_texcoord v3
dcl_texcoord1 v4
dcl_position o0
dcl_color o1
dcl_texcoord o2.xyz
dcl_texcoord1 o3.xyz
dcl_texcoord2 o4
dp4 o0.x, v0, c0
dp4 o0.y, v0, c1
dp4 o0.z, v0, c2
dp4 o0.w, v0, c3
dp4 o2.x, v0, c4
dp4 o2.y, v0, c5
dp4 o2.z, v0, c6
dp3 o3.x, v1, c4
dp3 o3.y, v1, c5
dp3 o3.z, v1, c6
mov o1, v2
mov o4.xy, v3
mov o4.zw, v4.xyxy
AFTER
vs_3_0
def c220, 10000, 0, 0, 0
dcl_position v0
dcl_normal v1
dcl_color v2
dcl_texcoord v3
dcl_texcoord1 v4
dcl_position o0
dcl_color o1
dcl_texcoord o2.xyz
dcl_texcoord1 o3.xyz
dcl_texcoord2 o4
dp4 r10.x, v0, c0
dp4 r10.y, v0, c1
dp4 r10.z, v0, c2
dp4 r10.w, v0, c3
mul r10, r10, c220.x
mov o0, r10
dp4 o2.x, v0, c4
dp4 o2.y, v0, c5
dp4 o2.z, v0, c6
dp3 o3.x, v1, c4
dp3 o3.y, v1, c5
dp3 o3.z, v1, c6
mov o1, v2
mov o4.xy, v3
mov o4.zw, v4.xyxy
I attach a before and after jps screenshot as well as one with the shader removed so you can see how different bits are affected.
https://www.dropbox.com/sh/dggascskoqn4prv/KtZQmazN1N
Any ideas on if this can be fixed?
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
I tried adding that shader txt to the override folder but it didn't do anything to fix the game as I saw it, so could you pls upload it somewhere?
And I would add $10 to the bioshock pot mentioned before, not much but im poor sorry.
All hail 3d modders DHR, MasterOtaku, Losti, Necropants, Helifax, bo3b, mike_ar69, Flugan, DarkStarSword, 4everAwake, 3d4dd and so many more helping to keep the 3d dream alive, find their 3d fixes at http://helixmod.blogspot.com/ Also check my site for spanish VR and mobile gaming news: www.gamermovil.com
I am trying to get lefuneste's Rise of flight working on the latest exe (1.129). I am running the debug exe and have been able to fix the shader for labels (VSED87B35) by using lefuneste's original shaderfix code but changing filename for new CRC. However, I can't find the shader for icons etc.
I am trying to dump existing shaders and whilst I get the dump directories created on startup, when pressing the NUMLOCK6 to dump currently disabled vs shader, i get no message on the debug hud, nor do I get any shader code dumped. I can't seem to get any shader code dumped/written using the debug dll. Other default keys seem to work fine, just cant dump shaders.
Any help would be greatly appreciated.
Intel i5 2500K @ 4.5GHz
Asus P8P67 PRO
Corsair XMS3 DDR3 8GB
nVidia GTX 660 SLI + nVidia 3D Vision
Asus Xonar Essence ST with AKG K601/Sennheiser HD 595
Corsair Force GT 120GB SSD + 5TB HDD Storage
Corsair AX 850 PSU
Coolermaster HAF 932 Case
HELIX MOD - A must for any 3D Vision gamer
As my fix is still working on my system with the 1.29 verison of Rof, I'm very suprised by the shader change with your PC.
This remind me the strange problem I had before (see page 103). As RoF ask for a directX update, maybe you have the same problem ? Unforunately I have no solution for this problem, except restoring a system backup...
This time I did not allow the directX update for the RoF 1.29 install, because of the above problem.
Anyway, as RoF is still working on my PC, there is no reason to dump the shaders, you just have to rename them with the new references, that you will find by disabling the shader one by one with the debug library.
I remember that I use a shader that make the screen black to for the jauges.
Thanks for the feedback. This is wierd. I never let dx get updated by the installers. Oh well. I have tried unsuccessfully to determine the new CRCs for your original fixes for anything other than the labels. Labels was VS number 3 in debug. If you get a chance, could you possibly indicate which shader number via the debug exe the shaders are for you? I will then just get the CRCs for those numbered shaders and see if that works.
Anyway, thanks for your feedback.