Well I'm totally lost in modifying the shader VSD3AD9F08 (wrote some posts before) in DCS World.
I tried to use the "DefVSConst" feature without success, and the "CheckTexCRC" feature is also a fealure. So I made a little change to try to understand where the problem is.
When I just add this line : "def c220 1, 0, 0, 0" just after of before the line "def c4, 1, 0, 0, 0" the modified shader works no more !
If I comment this line, the shader become again activated...Tried to use another number for the added const, still the same problem.
It seems that I can't use any cxxx register in the shader whithout breaking it !
I need to have a different value of the c4 reg. for the HUD, but neither the "CheckTexCRC" feature nor the "DefVSConst" works. I wonder why...
Well I'm totally lost in modifying the shader VSD3AD9F08 (wrote some posts before) in DCS World.
I tried to use the "DefVSConst" feature without success, and the "CheckTexCRC" feature is also a fealure. So I made a little change to try to understand where the problem is.
When I just add this line : "def c220 1, 0, 0, 0" just after of before the line "def c4, 1, 0, 0, 0" the modified shader works no more !
If I comment this line, the shader become again activated...Tried to use another number for the added const, still the same problem.
It seems that I can't use any cxxx register in the shader whithout breaking it !
I need to have a different value of the c4 reg. for the HUD, but neither the "CheckTexCRC" feature nor the "DefVSConst" works. I wonder why...
@eqzitara: thanks for suggestions! ...unfortunately renaming doesn't do the job though :(
@lefuneste: I believe you've only missed the comma after c220... you could have probably written "def c220 1, 0, 0, 0" in place of "def c220[b],[/b] 1, 0, 0, 0" ...I say this becouse shaders usually breaks with syntax errors. Otherwise look at the generated log.txt file.
@eqzitara: thanks for suggestions! ...unfortunately renaming doesn't do the job though :(
@lefuneste: I believe you've only missed the comma after c220... you could have probably written "def c220 1, 0, 0, 0" in place of "def c220, 1, 0, 0, 0" ...I say this becouse shaders usually breaks with syntax errors. Otherwise look at the generated log.txt file.
my cfg: i5 2500k, 8gb ram, GTX 570, Asus VG278H, Windows 8 Pro x64
Thanks, that actually worked however, when I click a link I got them same problem. I also tried to replace the url with the .co.uk appendix but that didn;t help.
Thanks, that actually worked however, when I click a link I got them same problem. I also tried to replace the url with the .co.uk appendix but that didn;t help.
[quote="mana84"]
@lefuneste: I believe you've only missed the comma after c220... you could have probably written "def c220 1, 0, 0, 0" in place of "def c220[b],[/b] 1, 0, 0, 0" [/quote]
Thanks, it was really a silly error !
However, I give up with the "CheckTexCRC" feature. No way to make it works. But I finnaly found a register that I can use for the DefVSConst, it makes a fix usable. I have now to test the fix.
mana84 said:
@lefuneste: I believe you've only missed the comma after c220... you could have probably written "def c220 1, 0, 0, 0" in place of "def c220, 1, 0, 0, 0"
Thanks, it was really a silly error !
However, I give up with the "CheckTexCRC" feature. No way to make it works. But I finnaly found a register that I can use for the DefVSConst, it makes a fix usable. I have now to test the fix.
omg what a stupid mistake! :D ...I had problems fixing unreal tournament 3 becouse I wrote "texldl r11.x" instead of "texldl r11" so I wasn't storing convergence into r11.y!! ...sorry @eqzitara for stupid questions I made :) ...now it works and I can proceed fixing the other shaders... and I believe I could release it in the blog soon. I'm working on other fixes too and I hope I should be able to share some new fixes soon (flatout ultimate carnage and others..)... although I'm working on shaders only after dinner time (I'm still busy during the day) and I'm helping eincrou with darksiders too.
...Anyway, good work and good play for you all! :)
omg what a stupid mistake! :D ...I had problems fixing unreal tournament 3 becouse I wrote "texldl r11.x" instead of "texldl r11" so I wasn't storing convergence into r11.y!! ...sorry @eqzitara for stupid questions I made :) ...now it works and I can proceed fixing the other shaders... and I believe I could release it in the blog soon. I'm working on other fixes too and I hope I should be able to share some new fixes soon (flatout ultimate carnage and others..)... although I'm working on shaders only after dinner time (I'm still busy during the day) and I'm helping eincrou with darksiders too.
...Anyway, good work and good play for you all! :)
my cfg: i5 2500k, 8gb ram, GTX 570, Asus VG278H, Windows 8 Pro x64
My fix don't work anymore with War thunder and Rise of flight
I can still save shaders with the debug lib, but can no more load a modified shader, nor select the preset settings defined in DX9Settings.ini !
The LOG.txt seems OK but nothing is working !
The only thing i noticed was the directX update made by the war thunder game...
Any idea ?
EDIT : I had to restore my system from a 3 month old backup. No idea of the problem I encoutered, I hope that nobody else will have it....
My fix don't work anymore with War thunder and Rise of flight
I can still save shaders with the debug lib, but can no more load a modified shader, nor select the preset settings defined in DX9Settings.ini !
The LOG.txt seems OK but nothing is working !
The only thing i noticed was the directX update made by the war thunder game...
Any idea ?
EDIT : I had to restore my system from a 3 month old backup. No idea of the problem I encoutered, I hope that nobody else will have it....
@eqzitara : update for "war thunder" fix
I made a new version of the "war thunder" beta Fix, because they improve 3Dvision support in the 1.25 version. They made a great support of shadow in 1.25 but removed it with the 1.25.20 because of performance problem. They seems to care of 3Dvision users, I hope that one day there will be no more need of a Helix fix.
Anyway I remove all the useless shaders in the fix: http://dl.free.fr/f8heU7CHC
Can you please publish the last fix in the Helix blog ?
@eqzitara : update for "war thunder" fix
I made a new version of the "war thunder" beta Fix, because they improve 3Dvision support in the 1.25 version. They made a great support of shadow in 1.25 but removed it with the 1.25.20 because of performance problem. They seems to care of 3Dvision users, I hope that one day there will be no more need of a Helix fix.
Anyway I remove all the useless shaders in the fix: http://dl.free.fr/f8heU7CHC
Can you please publish the last fix in the Helix blog ?
Hi,
I'm playing Mass Effect 3 with the helix mod and it looks GREAT! Thanks for the fix!!
However, I'm having a big problem.
It's working great on 1920/1080 but I'm playing on 3 screens (6000/1080).
The fix still works great but I'm having an issue with the crosshair, it's off. I need to target next to the place where I want to hit. At first I thought the problem was caused by the fix I use to enable playing on 3 screens (flawless widescreen) but that wasn't the case. If I turn 3D off, the crosshair is working correctly again.
There are 2 shortcut keys that help a bit (K and L, I believe) but unfortunately not enough).
One of them pushes the crosshair further into the screen, but not far enough.
So my question is:
Is it possible to change some value in the fixed shaders, so that if I use the shortcut key it pushes my crosshair further into the screen?
Any help/suggestions would be highly appreciated!
I'm playing Mass Effect 3 with the helix mod and it looks GREAT! Thanks for the fix!!
However, I'm having a big problem.
It's working great on 1920/1080 but I'm playing on 3 screens (6000/1080).
The fix still works great but I'm having an issue with the crosshair, it's off. I need to target next to the place where I want to hit. At first I thought the problem was caused by the fix I use to enable playing on 3 screens (flawless widescreen) but that wasn't the case. If I turn 3D off, the crosshair is working correctly again.
There are 2 shortcut keys that help a bit (K and L, I believe) but unfortunately not enough).
One of them pushes the crosshair further into the screen, but not far enough.
So my question is:
Is it possible to change some value in the fixed shaders, so that if I use the shortcut key it pushes my crosshair further into the screen?
Hello,
I noticed that only one binary shader is used for several shaders in DCS blackshark
The binary shader 0B9B70F4 is use for the shaders 778 to 784.
So I tried to rename the 0B9B70F4.txt in 0B9B70F4.txt.7, because I only want to correct the binary shader 0B9B70F4 for the 784th shader, and not for the others !
And this did not work, the modified shader seems inactive. Why ?
It seems that I am not talented at the use of Helix dll...
Maybe someone has an idea ?
Hello,
I noticed that only one binary shader is used for several shaders in DCS blackshark
The binary shader 0B9B70F4 is use for the shaders 778 to 784.
So I tried to rename the 0B9B70F4.txt in 0B9B70F4.txt.7, because I only want to correct the binary shader 0B9B70F4 for the 784th shader, and not for the others !
And this did not work, the modified shader seems inactive. Why ?
It seems that I am not talented at the use of Helix dll...
Maybe someone has an idea ?
I tried to use the "DefVSConst" feature without success, and the "CheckTexCRC" feature is also a fealure. So I made a little change to try to understand where the problem is.
When I just add this line : "def c220 1, 0, 0, 0" just after of before the line "def c4, 1, 0, 0, 0" the modified shader works no more !
If I comment this line, the shader become again activated...Tried to use another number for the added const, still the same problem.
It seems that I can't use any cxxx register in the shader whithout breaking it !
I need to have a different value of the c4 reg. for the HUD, but neither the "CheckTexCRC" feature nor the "DefVSConst" works. I wonder why...
@lefuneste: I believe you've only missed the comma after c220... you could have probably written "def c220 1, 0, 0, 0" in place of "def c220, 1, 0, 0, 0" ...I say this becouse shaders usually breaks with syntax errors. Otherwise look at the generated log.txt file.
my cfg: i5 2500k, 8gb ram, GTX 570, Asus VG278H, Windows 8 Pro x64
Helix mod 3d vision game fixes
Large parts of the helix mod page are unreachable. E.g. http://helixmod.wikispot.org/support
Gigabyte RTX2080TI Gaming OC, I7-6700k ~ 4.4Ghz, 3x BenQ XL2420T, BenQ TK800, LG 55EG960V (3D OLED), Samsung 850 EVO SSD, Crucial M4 SSD, 3D vision kit, Xpand x104 glasses, Corsair HX1000i, Win 10 pro 64/Win 7 64https://www.3dmark.com/fs/9529310
Co-founder/Web host of helixmod.blog.com
Donations for web hosting @ paypal -eqzitara@yahoo.com
or
https://www.patreon.com/user?u=791918
It working now! (I thing I'll download every fix from now on to be sure :-))
Thanks, it was really a silly error !
However, I give up with the "CheckTexCRC" feature. No way to make it works. But I finnaly found a register that I can use for the DefVSConst, it makes a fix usable. I have now to test the fix.
...Anyway, good work and good play for you all! :)
my cfg: i5 2500k, 8gb ram, GTX 570, Asus VG278H, Windows 8 Pro x64
Helix mod 3d vision game fixes
I can still save shaders with the debug lib, but can no more load a modified shader, nor select the preset settings defined in DX9Settings.ini !
The LOG.txt seems OK but nothing is working !
The only thing i noticed was the directX update made by the war thunder game...
Any idea ?
EDIT : I had to restore my system from a 3 month old backup. No idea of the problem I encoutered, I hope that nobody else will have it....
I made a new version of the "war thunder" beta Fix, because they improve 3Dvision support in the 1.25 version. They made a great support of shadow in 1.25 but removed it with the 1.25.20 because of performance problem. They seems to care of 3Dvision users, I hope that one day there will be no more need of a Helix fix.
Anyway I remove all the useless shaders in the fix: http://dl.free.fr/f8heU7CHC
Can you please publish the last fix in the Helix blog ?
I'm playing Mass Effect 3 with the helix mod and it looks GREAT! Thanks for the fix!!
However, I'm having a big problem.
It's working great on 1920/1080 but I'm playing on 3 screens (6000/1080).
The fix still works great but I'm having an issue with the crosshair, it's off. I need to target next to the place where I want to hit. At first I thought the problem was caused by the fix I use to enable playing on 3 screens (flawless widescreen) but that wasn't the case. If I turn 3D off, the crosshair is working correctly again.
There are 2 shortcut keys that help a bit (K and L, I believe) but unfortunately not enough).
One of them pushes the crosshair further into the screen, but not far enough.
So my question is:
Is it possible to change some value in the fixed shaders, so that if I use the shortcut key it pushes my crosshair further into the screen?
Any help/suggestions would be highly appreciated!
I noticed that only one binary shader is used for several shaders in DCS blackshark
The binary shader 0B9B70F4 is use for the shaders 778 to 784.
So I tried to rename the 0B9B70F4.txt in 0B9B70F4.txt.7, because I only want to correct the binary shader 0B9B70F4 for the 784th shader, and not for the others !
And this did not work, the modified shader seems inactive. Why ?
It seems that I am not talented at the use of Helix dll...
Maybe someone has an idea ?