I have another question: I want to make a hotkey that offers the possibility to switch the depth of the interaction HUD. I adjusted the depth of the HUD to arm's length which is usefull for most interactions with objects. But You also need the HUD for aming during triangulations to find out where You are located on the map. In this case a HUD at more/maximum depth would be usefull.
So I would need two different constants for different shaders.
Until now (godrays) I have used DefVSConst1 = 250 and Const1=... in DX9Settings.ini and c250.x in the godray shader.
I tried to add DefVSConst2 = 251 and c251.x in the shader for the HUD. But it has no effect!
So I used DefVSConst1 = 250 and c250.x to switch the HUD depth. It works => the shader for switching the HUD depth is per se correct.
I tried DefVSConst1 = 251 and c251.x in the godray and then in the HUD shader. It worked => 251 per se should work, also 252, 253, etc.
I replaced DefVSConst1 = 250 with DefVSConst2 = 250 and Const2 = ... in DX9Settings.ini. It didn't work =>
So "Const2" is not accepted, same with "Const3", etc.
On the other hand Helix's fix for Mass Effect 3 contains several Hotkeys that use different constants. There is DefVSConst2 = 254 and Const2 =... even Const3, Const4 and Const5 without a line that says DefVSConst3 = ... etc. BTW DefVSConst2 = 254 didn't work in Miasmata, too.
I don't understand why I can't use any other constant than Const1 in Miasmata...
Here is the code I tried:
---------------------
DX9Settings.ini:
[general]
overridemethod = 1
Preset1Key = 48
Preset2Key = 57
Preset3Key = 56
Preset4Key = 55
DefPreset = 1
DefVSConst1 = 250
DefVSConst2 = 251
[Preset1]
UseSepSettings = true
Convergence = 0x3fac4a26
Const1 = 0x3f800000
Const2 = 0x3e051eb8
[Preset2]
Const1 = 0x00000000
[Preset3]
Const2 = 0x3fc00000
[Preset4]
Const2 = 0x3e051eb8
----------------------------
Preset 1 (= standard): low HUD + normal godrays, preset 2: diffuse godrays, preset3: max depth HUD, preset4: low HUD (without changing the actual godray mode).
----------------------------
in the godray shader (works)
...
mov r14.x, c250.x
if_eq r14.x, c100.x
...
--------------------------
in the HUD-shader (has no effect...)
...
mul r1.x, r1.x, -c251.x
...
--------------------------
Do I have to add an additonal line to DX9Settings.ini that allows me to use Connst2 (besides fromDefVSConst2)?
ME3 uses OverrideMethod = 0 whereas I have to use OverrideMethod = 1 in Miasmata. Could this make a difference?
Of course I also tried the release.dll for ME3, the actual release.dll and the debug.dll with no result.
The hotkeys per se are recognised (for testing I combined them with depth-presets and it had effect).
I have another question: I want to make a hotkey that offers the possibility to switch the depth of the interaction HUD. I adjusted the depth of the HUD to arm's length which is usefull for most interactions with objects. But You also need the HUD for aming during triangulations to find out where You are located on the map. In this case a HUD at more/maximum depth would be usefull.
So I would need two different constants for different shaders.
Until now (godrays) I have used DefVSConst1 = 250 and Const1=... in DX9Settings.ini and c250.x in the godray shader.
I tried to add DefVSConst2 = 251 and c251.x in the shader for the HUD. But it has no effect!
So I used DefVSConst1 = 250 and c250.x to switch the HUD depth. It works => the shader for switching the HUD depth is per se correct.
I tried DefVSConst1 = 251 and c251.x in the godray and then in the HUD shader. It worked => 251 per se should work, also 252, 253, etc.
I replaced DefVSConst1 = 250 with DefVSConst2 = 250 and Const2 = ... in DX9Settings.ini. It didn't work =>
So "Const2" is not accepted, same with "Const3", etc.
On the other hand Helix's fix for Mass Effect 3 contains several Hotkeys that use different constants. There is DefVSConst2 = 254 and Const2 =... even Const3, Const4 and Const5 without a line that says DefVSConst3 = ... etc. BTW DefVSConst2 = 254 didn't work in Miasmata, too.
I don't understand why I can't use any other constant than Const1 in Miasmata...
Here is the code I tried:
---------------------
DX9Settings.ini:
[general]
overridemethod = 1
Preset1Key = 48
Preset2Key = 57
Preset3Key = 56
Preset4Key = 55
DefPreset = 1
DefVSConst1 = 250
DefVSConst2 = 251
[Preset4]
Const2 = 0x3e051eb8
----------------------------
Preset 1 (= standard): low HUD + normal godrays, preset 2: diffuse godrays, preset3: max depth HUD, preset4: low HUD (without changing the actual godray mode).
----------------------------
in the godray shader (works)
...
mov r14.x, c250.x
if_eq r14.x, c100.x
...
--------------------------
in the HUD-shader (has no effect...)
...
mul r1.x, r1.x, -c251.x
...
--------------------------
Do I have to add an additonal line to DX9Settings.ini that allows me to use Connst2 (besides fromDefVSConst2)?
ME3 uses OverrideMethod = 0 whereas I have to use OverrideMethod = 1 in Miasmata. Could this make a difference?
Of course I also tried the release.dll for ME3, the actual release.dll and the debug.dll with no result.
The hotkeys per se are recognised (for testing I combined them with depth-presets and it had effect).
My original display name is 3d4dd - for some reason Nvidia changed it..?!
I want two presets for godrays (already working) and in addition two presets for the HUD depth.
My DX9Settings.ini is in the last post.
This is the complete shader for the HUD:
--------------------------------
vs_3_0
def c0, 0.5, 1, 0, 0
def c220, 0.13, 0, 0.0625, 0
dcl_position v0
dcl_texcoord v1
dcl_2d s0
dcl_position o0
dcl_texcoord o1.xy
mov r3.xy, v0
mov r3.zw, c0.xyxy
texldl r1, c220.z, s0
mul r1.x, r1.x, -c251.x
add r3.x, r3.x, -r1.x
mov o0, r3
mov o1.xy, v1
-----------------------------
The line
mul r1.x, r1.x, -c251.x
should switch between the depth presets when I use the hotkey for preset 3 and 4, preset 1 also contains const2 (->251) as these are the standard settings when the game starts.
Unfortunately using the hotkeys and const2 for the HUD has no effect.
For testing I used const1 (->250) for switching between the HUD presets and it worked.
So the problem is not the shader for the HUD but the fact that only const1 and not const2 works with Helixmod and this game...
I want two presets for godrays (already working) and in addition two presets for the HUD depth.
My DX9Settings.ini is in the last post.
This is the complete shader for the HUD:
--------------------------------
vs_3_0
def c0, 0.5, 1, 0, 0
def c220, 0.13, 0, 0.0625, 0
dcl_position v0
dcl_texcoord v1
dcl_2d s0
dcl_position o0
dcl_texcoord o1.xy
mov r3.xy, v0
mov r3.zw, c0.xyxy
texldl r1, c220.z, s0
mul r1.x, r1.x, -c251.x
add r3.x, r3.x, -r1.x
mov o0, r3
mov o1.xy, v1
-----------------------------
The line
mul r1.x, r1.x, -c251.x
should switch between the depth presets when I use the hotkey for preset 3 and 4, preset 1 also contains const2 (->251) as these are the standard settings when the game starts.
Unfortunately using the hotkeys and const2 for the HUD has no effect.
For testing I used const1 (->250) for switching between the HUD presets and it worked.
So the problem is not the shader for the HUD but the fact that only const1 and not const2 works with Helixmod and this game...
My original display name is 3d4dd - for some reason Nvidia changed it..?!
Ive never tried it that way tbh. But CONST2 is y. x is CONST1. z is CONST3. w is CONST4.
X,Y,Z,W
I dont have your dx9settings so you have to test it without your current one. Keys are O + P
Heres how I do it. I like writing it so the dx9settings is just an ON/OFF switch and the shaders are all done in the shader via IF statements. It gets confusing to do it anyother way to me so I never bothered.
-------------------------------------------------
vs_3_0
def c0, 0.5, 1, 0, 0
def c220, 0.13, 0, 0.0625, 0
def c221, .80, 0, 0, 0
dcl_position v0
dcl_texcoord v1
dcl_2d s0
dcl_position o0
dcl_texcoord o1.xy
mov r3.xy, v0
mov r3.zw, c0.xyxy
texldl r1, c220.z, s0
mov r13.x, c220.x //MOVE DEPTH VALUE TO R13. DEFAULT, DEPTH IS AT .13.
mov r14.x, c250.w
if_eq r14.x, c220.w
mov r13.x, c221.x // MOVETO R13 IF P IS PRESSED DEPTH IS .80. IF O IS PRESSED REVERT BACK TO DEFAULT
endif
mul r1.x, r1.x, -r13.x //DEPTH VALUE IS R13.X
add r3.x, r3.x, -r1.x
mov o0, r3
mov o1.xy, v1
------------------
dx9 settings
[general]
Preset1Key = 79
Preset2Key = 80
DefVSConst1 = 250
[Preset1]
Const4 = 0x3f800000
[Preset2]
Const4 = 0x00000000
Ive never tried it that way tbh. But CONST2 is y. x is CONST1. z is CONST3. w is CONST4.
X,Y,Z,W
I dont have your dx9settings so you have to test it without your current one. Keys are O + P
Heres how I do it. I like writing it so the dx9settings is just an ON/OFF switch and the shaders are all done in the shader via IF statements. It gets confusing to do it anyother way to me so I never bothered.
-------------------------------------------------
vs_3_0
def c0, 0.5, 1, 0, 0
def c220, 0.13, 0, 0.0625, 0
def c221, .80, 0, 0, 0
dcl_position v0
dcl_texcoord v1
dcl_2d s0
dcl_position o0
dcl_texcoord o1.xy
mov r3.xy, v0
mov r3.zw, c0.xyxy
texldl r1, c220.z, s0
mov r13.x, c220.x //MOVE DEPTH VALUE TO R13. DEFAULT, DEPTH IS AT .13.
mov r14.x, c250.w
if_eq r14.x, c220.w
mov r13.x, c221.x // MOVETO R13 IF P IS PRESSED DEPTH IS .80. IF O IS PRESSED REVERT BACK TO DEFAULT
endif
mul r1.x, r1.x, -r13.x //DEPTH VALUE IS R13.X
add r3.x, r3.x, -r1.x
mov o0, r3
mov o1.xy, v1
@eqzitara:
You will find here: [url]http://dl.free.fr/h11h2fgKC[/url] a zip file containing
The "War thunder (beta) Helix" Mod
a read me file
2 jps showing the effect of the Mod
I will be very proud if you add these little fix in the Helix blog.
The URL is only valid for a month.
@equzitara: Thank You for the help! It works now :) I didn't know that Const2 means y. I thought if I write DefVSConst2 = 251 and Const2 = NN, then NN is the value for 251.x and not the value for 250.y !!!
Would be great if You could post the fix in the blog!
[url]http://www48.zippyshare.com/v/55253644/file.html[/url]
The download also includes the info text and screenshots for the blog. I would recommend to pair the pictures like that:
miasmata_before/miasmata_after
distinct_godrays/diffuse_godrays
armslength_HUD/triangulation_HUD
@equzitara: Thank You for the help! It works now :) I didn't know that Const2 means y. I thought if I write DefVSConst2 = 251 and Const2 = NN, then NN is the value for 251.x and not the value for 250.y !!!
Would be great if You could post the fix in the blog! http://www48.zippyshare.com/v/55253644/file.html
The download also includes the info text and screenshots for the blog. I would recommend to pair the pictures like that:
miasmata_before/miasmata_after
distinct_godrays/diffuse_godrays
armslength_HUD/triangulation_HUD
My original display name is 3d4dd - for some reason Nvidia changed it..?!
How come Helix won't let us beta test his DX11 wrapper? I want to play Far Cry 3 in 3D!!! It seems like all there is wrong is the shadows. If he can fix that, then the game can be played as-is.
How come Helix won't let us beta test his DX11 wrapper? I want to play Far Cry 3 in 3D!!! It seems like all there is wrong is the shadows. If he can fix that, then the game can be played as-is.
He didnt even say he was doing farcry 3. No such thing as beta testing a fix. You have manually rewrite code, and he is only one even capable of doing it. Its a lot of work....so don't make it sound easy.
@3d4dd
Your hud picture has one thats broken. So I couldnt.
He didnt even say he was doing farcry 3. No such thing as beta testing a fix. You have manually rewrite code, and he is only one even capable of doing it. Its a lot of work....so don't make it sound easy.
@3d4dd
Your hud picture has one thats broken. So I couldnt.
@eqzitara: Thank You for posting the fix snd sorry for causing inconvenience! Next time I have a fix to offer I will make my own post ;)
Regarding Far Cry 3: I have looked in the DX9 version for a way to disable the shadows. There seem to be dozens of shaders alone for the shadwos. A single person had 3 different shadow shaders! I have spent hours with switching through the shaders and there are still shadows that only appear when You are moving. And as soon as You drive around for 2 minutes and get in another environment there are 2-3 new shadows You haven't discovered before. IMHO if there ever is a chance to fix or at least disable the shadows it only can be done by an automated process. I think Helix did something like this using lua code with Dishonored. But I have no idea if this could be done with FC3...
@eqzitara: Thank You for posting the fix snd sorry for causing inconvenience! Next time I have a fix to offer I will make my own post ;)
Regarding Far Cry 3: I have looked in the DX9 version for a way to disable the shadows. There seem to be dozens of shaders alone for the shadwos. A single person had 3 different shadow shaders! I have spent hours with switching through the shaders and there are still shadows that only appear when You are moving. And as soon as You drive around for 2 minutes and get in another environment there are 2-3 new shadows You haven't discovered before. IMHO if there ever is a chance to fix or at least disable the shadows it only can be done by an automated process. I think Helix did something like this using lua code with Dishonored. But I have no idea if this could be done with FC3...
My original display name is 3d4dd - for some reason Nvidia changed it..?!
Is whatever you have done? I can give you a blogspot access or add it I guess.
Co-founder/Web host of helixmod.blog.com
Donations for web hosting @ paypal -eqzitara@yahoo.com
or
https://www.patreon.com/user?u=791918
GTX 980 Ti, Intel core i7-7700K GPU 4.6 GHz, HMZ T-3 HTC VIVE
So I would need two different constants for different shaders.
Until now (godrays) I have used DefVSConst1 = 250 and Const1=... in DX9Settings.ini and c250.x in the godray shader.
I tried to add DefVSConst2 = 251 and c251.x in the shader for the HUD. But it has no effect!
So I used DefVSConst1 = 250 and c250.x to switch the HUD depth. It works => the shader for switching the HUD depth is per se correct.
I tried DefVSConst1 = 251 and c251.x in the godray and then in the HUD shader. It worked => 251 per se should work, also 252, 253, etc.
I replaced DefVSConst1 = 250 with DefVSConst2 = 250 and Const2 = ... in DX9Settings.ini. It didn't work =>
So "Const2" is not accepted, same with "Const3", etc.
On the other hand Helix's fix for Mass Effect 3 contains several Hotkeys that use different constants. There is DefVSConst2 = 254 and Const2 =... even Const3, Const4 and Const5 without a line that says DefVSConst3 = ... etc. BTW DefVSConst2 = 254 didn't work in Miasmata, too.
I don't understand why I can't use any other constant than Const1 in Miasmata...
Here is the code I tried:
---------------------
DX9Settings.ini:
[general]
overridemethod = 1
Preset1Key = 48
Preset2Key = 57
Preset3Key = 56
Preset4Key = 55
DefPreset = 1
DefVSConst1 = 250
DefVSConst2 = 251
[Preset1]
UseSepSettings = true
Convergence = 0x3fac4a26
Const1 = 0x3f800000
Const2 = 0x3e051eb8
[Preset2]
Const1 = 0x00000000
[Preset3]
Const2 = 0x3fc00000
[Preset4]
Const2 = 0x3e051eb8
----------------------------
Preset 1 (= standard): low HUD + normal godrays, preset 2: diffuse godrays, preset3: max depth HUD, preset4: low HUD (without changing the actual godray mode).
----------------------------
in the godray shader (works)
...
mov r14.x, c250.x
if_eq r14.x, c100.x
...
--------------------------
in the HUD-shader (has no effect...)
...
mul r1.x, r1.x, -c251.x
...
--------------------------
Do I have to add an additonal line to DX9Settings.ini that allows me to use Connst2 (besides fromDefVSConst2)?
ME3 uses OverrideMethod = 0 whereas I have to use OverrideMethod = 1 in Miasmata. Could this make a difference?
Of course I also tried the release.dll for ME3, the actual release.dll and the debug.dll with no result.
The hotkeys per se are recognised (for testing I combined them with depth-presets and it had effect).
My original display name is 3d4dd - for some reason Nvidia changed it..?!
I need your files either way. Dx9settings + hud. Dont give me what you tried.
Co-founder/Web host of helixmod.blog.com
Donations for web hosting @ paypal -eqzitara@yahoo.com
or
https://www.patreon.com/user?u=791918
My DX9Settings.ini is in the last post.
This is the complete shader for the HUD:
--------------------------------
vs_3_0
def c0, 0.5, 1, 0, 0
def c220, 0.13, 0, 0.0625, 0
dcl_position v0
dcl_texcoord v1
dcl_2d s0
dcl_position o0
dcl_texcoord o1.xy
mov r3.xy, v0
mov r3.zw, c0.xyxy
texldl r1, c220.z, s0
mul r1.x, r1.x, -c251.x
add r3.x, r3.x, -r1.x
mov o0, r3
mov o1.xy, v1
-----------------------------
The line
mul r1.x, r1.x, -c251.x
should switch between the depth presets when I use the hotkey for preset 3 and 4, preset 1 also contains const2 (->251) as these are the standard settings when the game starts.
Unfortunately using the hotkeys and const2 for the HUD has no effect.
For testing I used const1 (->250) for switching between the HUD presets and it worked.
So the problem is not the shader for the HUD but the fact that only const1 and not const2 works with Helixmod and this game...
My original display name is 3d4dd - for some reason Nvidia changed it..?!
X,Y,Z,W
I dont have your dx9settings so you have to test it without your current one. Keys are O + P
Heres how I do it. I like writing it so the dx9settings is just an ON/OFF switch and the shaders are all done in the shader via IF statements. It gets confusing to do it anyother way to me so I never bothered.
-------------------------------------------------
vs_3_0
def c0, 0.5, 1, 0, 0
def c220, 0.13, 0, 0.0625, 0
def c221, .80, 0, 0, 0
dcl_position v0
dcl_texcoord v1
dcl_2d s0
dcl_position o0
dcl_texcoord o1.xy
mov r3.xy, v0
mov r3.zw, c0.xyxy
texldl r1, c220.z, s0
mov r13.x, c220.x //MOVE DEPTH VALUE TO R13. DEFAULT, DEPTH IS AT .13.
mov r14.x, c250.w
if_eq r14.x, c220.w
mov r13.x, c221.x // MOVETO R13 IF P IS PRESSED DEPTH IS .80. IF O IS PRESSED REVERT BACK TO DEFAULT
endif
mul r1.x, r1.x, -r13.x //DEPTH VALUE IS R13.X
add r3.x, r3.x, -r1.x
mov o0, r3
mov o1.xy, v1
------------------
dx9 settings
[general]
Preset1Key = 79
Preset2Key = 80
DefVSConst1 = 250
[Preset1]
Const4 = 0x3f800000
[Preset2]
Const4 = 0x00000000
Co-founder/Web host of helixmod.blog.com
Donations for web hosting @ paypal -eqzitara@yahoo.com
or
https://www.patreon.com/user?u=791918
You will find here: http://dl.free.fr/h11h2fgKC a zip file containing
The "War thunder (beta) Helix" Mod
a read me file
2 jps showing the effect of the Mod
I will be very proud if you add these little fix in the Helix blog.
The URL is only valid for a month.
Would be great if You could post the fix in the blog!
http://www48.zippyshare.com/v/55253644/file.html
The download also includes the info text and screenshots for the blog. I would recommend to pair the pictures like that:
miasmata_before/miasmata_after
distinct_godrays/diffuse_godrays
armslength_HUD/triangulation_HUD
My original display name is 3d4dd - for some reason Nvidia changed it..?!
Co-founder/Web host of helixmod.blog.com
Donations for web hosting @ paypal -eqzitara@yahoo.com
or
https://www.patreon.com/user?u=791918
My original display name is 3d4dd - for some reason Nvidia changed it..?!
1080 GTX 8GB SLI | I7-4770K@4.5GHz | 16GB RAM | Win10x64
Asus ROG Swift PG278Q | 3D Vision 2
@3d4dd
Your hud picture has one thats broken. So I couldnt.
Co-founder/Web host of helixmod.blog.com
Donations for web hosting @ paypal -eqzitara@yahoo.com
or
https://www.patreon.com/user?u=791918
Regarding Far Cry 3: I have looked in the DX9 version for a way to disable the shadows. There seem to be dozens of shaders alone for the shadwos. A single person had 3 different shadow shaders! I have spent hours with switching through the shaders and there are still shadows that only appear when You are moving. And as soon as You drive around for 2 minutes and get in another environment there are 2-3 new shadows You haven't discovered before. IMHO if there ever is a chance to fix or at least disable the shadows it only can be done by an automated process. I think Helix did something like this using lua code with Dishonored. But I have no idea if this could be done with FC3...
My original display name is 3d4dd - for some reason Nvidia changed it..?!