How do you turn off the green nvidia "laser on/off" notification?
2 / 3
Thanks for the support guys. It looks like this functionality is not part of 3D Vision currently.
If there was a 3D Vision SDK for .NET I could write the functionality in 15 minutes and put it up for download. A 3D Vision SDK could give us an API that gives state information on the current running DX game then we could execute functions based upon the data. We could also create a much better profile manager for each game.
Thanks for the support guys. It looks like this functionality is not part of 3D Vision currently.
If there was a 3D Vision SDK for .NET I could write the functionality in 15 minutes and put it up for download. A 3D Vision SDK could give us an API that gives state information on the current running DX game then we could execute functions based upon the data. We could also create a much better profile manager for each game.
Cool, then we could start with different convergence / depth combinations mapped to keys, until such stuff is available.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not /laugh.gif' class='bbc_emoticon' alt=':laugh:' /> .
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
Cool, then we could start with different convergence / depth combinations mapped to keys, until such stuff is available.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not /laugh.gif' class='bbc_emoticon' alt=':laugh:' /> .
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
Cool, then we could start with different convergence / depth combinations mapped to keys, until such stuff is available.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not /laugh.gif' class='bbc_emoticon' alt=':laugh:' /> .
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
Cool, then we could start with different convergence / depth combinations mapped to keys, until such stuff is available.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not /laugh.gif' class='bbc_emoticon' alt=':laugh:' /> .
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
[quote name='tritosine' date='13 November 2010 - 02:11 AM' timestamp='1289614293' post='1145797']
Cool, then we could start with different convergence / depth combinations mapped to keys, until such stuff is available.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not /laugh.gif' class='bbc_emoticon' alt=':laugh:' /> .
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
[/quote]
If you set the crosshair to 100% transaperence then what is the point of turning it on? You're saying by setting 100% transparence it prevents the green text on the bottmo from showing up but won't that also make the crosshair unseeable? hehe
That's a good find on the registry. But I hope NVIDIA does the work, not me heheh
[quote name='tritosine' date='13 November 2010 - 02:11 AM' timestamp='1289614293' post='1145797']
Cool, then we could start with different convergence / depth combinations mapped to keys, until such stuff is available.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not /laugh.gif' class='bbc_emoticon' alt=':laugh:' /> .
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
If you set the crosshair to 100% transaperence then what is the point of turning it on? You're saying by setting 100% transparence it prevents the green text on the bottmo from showing up but won't that also make the crosshair unseeable? hehe
That's a good find on the registry. But I hope NVIDIA does the work, not me heheh
[quote name='tritosine' date='13 November 2010 - 02:11 AM' timestamp='1289614293' post='1145797']
Cool, then we could start with different convergence / depth combinations mapped to keys, until such stuff is available.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not /laugh.gif' class='bbc_emoticon' alt=':laugh:' /> .
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
[/quote]
If you set the crosshair to 100% transaperence then what is the point of turning it on? You're saying by setting 100% transparence it prevents the green text on the bottmo from showing up but won't that also make the crosshair unseeable? hehe
That's a good find on the registry. But I hope NVIDIA does the work, not me heheh
[quote name='tritosine' date='13 November 2010 - 02:11 AM' timestamp='1289614293' post='1145797']
Cool, then we could start with different convergence / depth combinations mapped to keys, until such stuff is available.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not /laugh.gif' class='bbc_emoticon' alt=':laugh:' /> .
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
If you set the crosshair to 100% transaperence then what is the point of turning it on? You're saying by setting 100% transparence it prevents the green text on the bottmo from showing up but won't that also make the crosshair unseeable? hehe
That's a good find on the registry. But I hope NVIDIA does the work, not me heheh
Assume, we have two buttons for crosshair , instead of ctrl+f12
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
Assume, we have two buttons for crosshair , instead of ctrl+f12
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
Assume, we have two buttons for crosshair , instead of ctrl+f12
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
Assume, we have two buttons for crosshair , instead of ctrl+f12
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
[quote name='tritosine' date='14 November 2010 - 08:45 AM' timestamp='1289724317' post='1146315']
Assume, we have two buttons for crosshair , instead of ctrl+f12
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
[/quote]
Oh I see what you mean.
1. Set Transparence to 100%
2. Turn on crosshair
3. Set Transparence to 0 two seconds later when the notification is gone.
yes?
But how would we change depth & conv based upon FOV using the registry?
[quote name='tritosine' date='14 November 2010 - 08:45 AM' timestamp='1289724317' post='1146315']
Assume, we have two buttons for crosshair , instead of ctrl+f12
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
Oh I see what you mean.
1. Set Transparence to 100%
2. Turn on crosshair
3. Set Transparence to 0 two seconds later when the notification is gone.
yes?
But how would we change depth & conv based upon FOV using the registry?
[quote name='tritosine' date='14 November 2010 - 08:45 AM' timestamp='1289724317' post='1146315']
Assume, we have two buttons for crosshair , instead of ctrl+f12
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
[/quote]
Oh I see what you mean.
1. Set Transparence to 100%
2. Turn on crosshair
3. Set Transparence to 0 two seconds later when the notification is gone.
yes?
But how would we change depth & conv based upon FOV using the registry?
[quote name='tritosine' date='14 November 2010 - 08:45 AM' timestamp='1289724317' post='1146315']
Assume, we have two buttons for crosshair , instead of ctrl+f12
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
Oh I see what you mean.
1. Set Transparence to 100%
2. Turn on crosshair
3. Set Transparence to 0 two seconds later when the notification is gone.
yes?
But how would we change depth & conv based upon FOV using the registry?
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
[quote name='tritosine' date='14 November 2010 - 09:14 AM' timestamp='1289726042' post='1146322']
No :(
/haha.gif' class='bbc_emoticon' alt=':haha:' />
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
[/quote]
Oh duh, you're saying use transparence as the on & off switch. Very good idea. I like that.
[quote name='tritosine' date='14 November 2010 - 09:14 AM' timestamp='1289726042' post='1146322']
No :(
/haha.gif' class='bbc_emoticon' alt=':haha:' />
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
Oh duh, you're saying use transparence as the on & off switch. Very good idea. I like that.
[quote name='tritosine' date='14 November 2010 - 09:14 AM' timestamp='1289726042' post='1146322']
No :(
/haha.gif' class='bbc_emoticon' alt=':haha:' />
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
[/quote]
Oh duh, you're saying use transparence as the on & off switch. Very good idea. I like that.
[quote name='tritosine' date='14 November 2010 - 09:14 AM' timestamp='1289726042' post='1146322']
No :(
/haha.gif' class='bbc_emoticon' alt=':haha:' />
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
Oh duh, you're saying use transparence as the on & off switch. Very good idea. I like that.
If there was a 3D Vision SDK for .NET I could write the functionality in 15 minutes and put it up for download. A 3D Vision SDK could give us an API that gives state information on the current running DX game then we could execute functions based upon the data. We could also create a much better profile manager for each game.
If there was a 3D Vision SDK for .NET I could write the functionality in 15 minutes and put it up for download. A 3D Vision SDK could give us an API that gives state information on the current running DX game then we could execute functions based upon the data. We could also create a much better profile manager for each game.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
Cool, then we could start with different convergence / depth combinations mapped to keys, until such stuff is available.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
[/quote]
If you set the crosshair to 100% transaperence then what is the point of turning it on? You're saying by setting 100% transparence it prevents the green text on the bottmo from showing up but won't that also make the crosshair unseeable? hehe
That's a good find on the registry. But I hope NVIDIA does the work, not me heheh
Cool, then we could start with different convergence / depth combinations mapped to keys, until such stuff is available.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
If you set the crosshair to 100% transaperence then what is the point of turning it on? You're saying by setting 100% transparence it prevents the green text on the bottmo from showing up but won't that also make the crosshair unseeable? hehe
That's a good find on the registry. But I hope NVIDIA does the work, not me heheh
Cool, then we could start with different convergence / depth combinations mapped to keys, until such stuff is available.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
[/quote]
If you set the crosshair to 100% transaperence then what is the point of turning it on? You're saying by setting 100% transparence it prevents the green text on the bottmo from showing up but won't that also make the crosshair unseeable? hehe
That's a good find on the registry. But I hope NVIDIA does the work, not me heheh
Cool, then we could start with different convergence / depth combinations mapped to keys, until such stuff is available.
Those should be as simple as calling different *.reg files while the game is running.
Just tried, setting 100% transparence on the crosshair removes it , PLUS, no annoying poop up.
Let's find the registry key for transparency. Now we can argue if its part of it or not
I happen to know how to find the convergence value:
you have to set the whole heap of "3d vision" registry settings 'read only' . Then if you run the game , and try to save settings by CTRL + F7, for some reason convergence value is displayed instead. Write it down and search for the value.
If you set the crosshair to 100% transaperence then what is the point of turning it on? You're saying by setting 100% transparence it prevents the green text on the bottmo from showing up but won't that also make the crosshair unseeable? hehe
That's a good find on the registry. But I hope NVIDIA does the work, not me heheh
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
Assume, we have two buttons for crosshair , instead of ctrl+f12
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
[/quote]
Oh I see what you mean.
1. Set Transparence to 100%
2. Turn on crosshair
3. Set Transparence to 0 two seconds later when the notification is gone.
yes?
But how would we change depth & conv based upon FOV using the registry?
Assume, we have two buttons for crosshair , instead of ctrl+f12
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
Oh I see what you mean.
1. Set Transparence to 100%
2. Turn on crosshair
3. Set Transparence to 0 two seconds later when the notification is gone.
yes?
But how would we change depth & conv based upon FOV using the registry?
Assume, we have two buttons for crosshair , instead of ctrl+f12
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
[/quote]
Oh I see what you mean.
1. Set Transparence to 100%
2. Turn on crosshair
3. Set Transparence to 0 two seconds later when the notification is gone.
yes?
But how would we change depth & conv based upon FOV using the registry?
Assume, we have two buttons for crosshair , instead of ctrl+f12
numpad + , and numpad -
_____________________________
if you press the + button, your program outside the game updates the registry value of "transparency" , held down for 1 sec you reach 100% . Ingame all you see is the crosshair vanishing.
Assume we have numpad keys 1-2-3- , set up for depth / convergence presets
_________________________
press numpad 1 , program outside updates registry values for d/c. All you see D/C is instantly swapped ingame . Cutscene? Press the "cutscene preset 1 " cutscene preset 2" etc.
This stuff sounds so easy anyone could do it . (but not me LOL! ) .
Oh I see what you mean.
1. Set Transparence to 100%
2. Turn on crosshair
3. Set Transparence to 0 two seconds later when the notification is gone.
yes?
But how would we change depth & conv based upon FOV using the registry?
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
No :(
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
[/quote]
Oh duh, you're saying use transparence as the on & off switch. Very good idea. I like that.
No :(
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
Oh duh, you're saying use transparence as the on & off switch. Very good idea. I like that.
No :(
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
[/quote]
Oh duh, you're saying use transparence as the on & off switch. Very good idea. I like that.
No :(
You don't have to turn off the crosshair , ever , you just modify the transparence setting on teh fly. Button held down would mean a jump to 100% , whereas you could also set up say , 65% easily.
Why the FOV talk? Just make 5 different presets for each game, FOV won't drift then I guess!
Oh duh, you're saying use transparence as the on & off switch. Very good idea. I like that.
This is driving me nuts.
Every time I turn on the crosshair I GET SPAMMED ON THE BOTTOM.
Every time I turn off the crosshair I GET SPAMMED AGAIN ON THE BOTTOM.
LOL, please with respect, we really need to be able to turn OFF the notification.
This is driving me nuts.
Every time I turn on the crosshair I GET SPAMMED ON THE BOTTOM.
Every time I turn off the crosshair I GET SPAMMED AGAIN ON THE BOTTOM.
LOL, please with respect, we really need to be able to turn OFF the notification.
This is driving me nuts.
Every time I turn on the crosshair I GET SPAMMED ON THE BOTTOM.
Every time I turn off the crosshair I GET SPAMMED AGAIN ON THE BOTTOM.
LOL, please with respect, we really need to be able to turn OFF the notification.
This is driving me nuts.
Every time I turn on the crosshair I GET SPAMMED ON THE BOTTOM.
Every time I turn off the crosshair I GET SPAMMED AGAIN ON THE BOTTOM.
LOL, please with respect, we really need to be able to turn OFF the notification.