Complete replacement set of LaserSights for all! Red dot, Holographic, Sniper crosshair etc..
2 / 2
I'm not quite sure where it's getting the game profile data from initially. The nvstres.dll does contain profile data, first entry under RC Data in PE Explorer. However if you change it, it will just revert. Also the drivers create resource.dat, resource.old and sometimes resource.new under c:\ProgramData\NVIDIA and those files also contain the profiles, but changing them and not allowing the system or any service to change them doesn't work either. Making the drivers unable to change nvstres.dll even got my computer to only list anaglyph mode as an option at some point, making me have to reinstall the stereo driver, as just changing back the permissions had no effect.
Anyway, I'm not sure which of the files the driver uses to actually get it's profile info from to use, nor do I know where it gets the original info from to revert the nvstres.dll. A shame, as I was trying to make the driver NOT recognize launcher.exe as WRC 2010, as there are other games using the same exe name.
EDIT: In any case, it's very much possible these are all just listings for the control panel and ingame comments on the 3d profile...
I'm not quite sure where it's getting the game profile data from initially. The nvstres.dll does contain profile data, first entry under RC Data in PE Explorer. However if you change it, it will just revert. Also the drivers create resource.dat, resource.old and sometimes resource.new under c:\ProgramData\NVIDIA and those files also contain the profiles, but changing them and not allowing the system or any service to change them doesn't work either. Making the drivers unable to change nvstres.dll even got my computer to only list anaglyph mode as an option at some point, making me have to reinstall the stereo driver, as just changing back the permissions had no effect.
Anyway, I'm not sure which of the files the driver uses to actually get it's profile info from to use, nor do I know where it gets the original info from to revert the nvstres.dll. A shame, as I was trying to make the driver NOT recognize launcher.exe as WRC 2010, as there are other games using the same exe name.
EDIT: In any case, it's very much possible these are all just listings for the control panel and ingame comments on the 3d profile...
[quote name='Xerion404' date='15 November 2011 - 02:48 PM' timestamp='1321386518' post='1327120']
I'm not quite sure where it's getting the game profile data from initially. The nvstres.dll does contain profile data, first entry under RC Data in PE Explorer. However if you change it, it will just revert. Also the drivers create resource.dat, resource.old and sometimes resource.new under c:\ProgramData\NVIDIA and those files also contain the profiles, but changing them and not allowing the system or any service to change them doesn't work either. Making the drivers unable to change nvstres.dll even got my computer to only list anaglyph mode as an option at some point, making me have to reinstall the stereo driver, as just changing back the permissions had no effect.
Anyway, I'm not sure which of the files the driver uses to actually get it's profile info from to use, nor do I know where it gets the original info from to revert the nvstres.dll. A shame, as I was trying to make the driver NOT recognize launcher.exe as WRC 2010, as there are other games using the same exe name.
EDIT: In any case, it's very much possible these are all just listings for the control panel and ingame comments on the 3d profile...
[/quote]
If you're talking about the game profiles with the relevant exe locations and things, they are in the registry. You can make your own profiles. In WinXP they used to be in HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\Stereo3D\GameConfigs
Now I think they are in wow6432node or something like that
[quote name='Xerion404' date='15 November 2011 - 02:48 PM' timestamp='1321386518' post='1327120']
I'm not quite sure where it's getting the game profile data from initially. The nvstres.dll does contain profile data, first entry under RC Data in PE Explorer. However if you change it, it will just revert. Also the drivers create resource.dat, resource.old and sometimes resource.new under c:\ProgramData\NVIDIA and those files also contain the profiles, but changing them and not allowing the system or any service to change them doesn't work either. Making the drivers unable to change nvstres.dll even got my computer to only list anaglyph mode as an option at some point, making me have to reinstall the stereo driver, as just changing back the permissions had no effect.
Anyway, I'm not sure which of the files the driver uses to actually get it's profile info from to use, nor do I know where it gets the original info from to revert the nvstres.dll. A shame, as I was trying to make the driver NOT recognize launcher.exe as WRC 2010, as there are other games using the same exe name.
EDIT: In any case, it's very much possible these are all just listings for the control panel and ingame comments on the 3d profile...
If you're talking about the game profiles with the relevant exe locations and things, they are in the registry. You can make your own profiles. In WinXP they used to be in HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\Stereo3D\GameConfigs
Now I think they are in wow6432node or something like that
AMD Phenom II X3 720 @ 2.8GHZ
8GB RAM
Mitsubishi Diamond Pro 2070sb @ 2048x1536 @ 85hz
Edimensional glasses and Nvidia 3D Vision
[quote name='oracletriplex' date='16 November 2011 - 05:03 AM' timestamp='1321412615' post='1327333']
If you're talking about the game profiles with the relevant exe locations and things, they are in the registry. You can make your own profiles. In WinXP they used to be in HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\Stereo3D\GameConfigs
Now I think they are in wow6432node or something like that
[/quote]
The only things in the registry are those games for which a single process name can point to multiple games (which is an issue I'm having where a game is recognized as another, but adding a registry key for it doesn't change a thing) and settings you save yourself, like convergence and whether the nvidia crosshair should show and whatever. The predefined profiles however, are not there. Perhaps one can actually override the parameters through the registry but it doesn't seem to work for me.
[quote name='oracletriplex' date='16 November 2011 - 05:03 AM' timestamp='1321412615' post='1327333']
If you're talking about the game profiles with the relevant exe locations and things, they are in the registry. You can make your own profiles. In WinXP they used to be in HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\Stereo3D\GameConfigs
Now I think they are in wow6432node or something like that
The only things in the registry are those games for which a single process name can point to multiple games (which is an issue I'm having where a game is recognized as another, but adding a registry key for it doesn't change a thing) and settings you save yourself, like convergence and whether the nvidia crosshair should show and whatever. The predefined profiles however, are not there. Perhaps one can actually override the parameters through the registry but it doesn't seem to work for me.
[quote name='Xerion404' date='16 November 2011 - 02:41 PM' timestamp='1321472482' post='1327779']
The only things in the registry are those games for which a single process name can point to multiple games (which is an issue I'm having where a game is recognized as another, but adding a registry key for it doesn't change a thing) and settings you save yourself, like convergence and whether the nvidia crosshair should show and whatever. The predefined profiles however, are not there. Perhaps one can actually override the parameters through the registry but it doesn't seem to work for me.
[/quote]
If two games have the same exe name, as of right now there is no way for the nvidia driver to tell the difference. If that's what you're asking. It's impossible unless Nvidia fixes it, we've been telling them this since the dawn of time.
The way it worked with the old forceware 3d driver was that in order for Doom 3 to work, I made a registry key for it called Doom3. That was the name of the key. And when you ran the game in 3D and save settings it saved them under that key because it recognized the executable name. You could also tweak the registry settings for that game under that key, like specifying if it was OpenGL in quad buffer mode.
I have no idea how it works now, I assumed that the current 3D driver does the same thing. But now that I think about it you are right, the newer games do not have keys in there that we can modify.
Maybe Andrew can help us out on where they are stored.
[quote name='Xerion404' date='16 November 2011 - 02:41 PM' timestamp='1321472482' post='1327779']
The only things in the registry are those games for which a single process name can point to multiple games (which is an issue I'm having where a game is recognized as another, but adding a registry key for it doesn't change a thing) and settings you save yourself, like convergence and whether the nvidia crosshair should show and whatever. The predefined profiles however, are not there. Perhaps one can actually override the parameters through the registry but it doesn't seem to work for me.
If two games have the same exe name, as of right now there is no way for the nvidia driver to tell the difference. If that's what you're asking. It's impossible unless Nvidia fixes it, we've been telling them this since the dawn of time.
The way it worked with the old forceware 3d driver was that in order for Doom 3 to work, I made a registry key for it called Doom3. That was the name of the key. And when you ran the game in 3D and save settings it saved them under that key because it recognized the executable name. You could also tweak the registry settings for that game under that key, like specifying if it was OpenGL in quad buffer mode.
I have no idea how it works now, I assumed that the current 3D driver does the same thing. But now that I think about it you are right, the newer games do not have keys in there that we can modify.
Maybe Andrew can help us out on where they are stored.
AMD Phenom II X3 720 @ 2.8GHZ
8GB RAM
Mitsubishi Diamond Pro 2070sb @ 2048x1536 @ 85hz
Edimensional glasses and Nvidia 3D Vision
The links in the registry seem to be where the .exe names are actually different but where the process name is the same it seems. Look at "Game" and "CLIENT" and such. I guess my problem is different because both the process name and .exe name seem to be the same, but also I can't just change the .exe name and make a profile, because the .exe file is actually started from another program, really annoying :p
EDIT: Actually the links under game are not all to .exe files, so they might be to other files in order to differentiate, however I then still have no idea how to make a separate profile and not make it load the wrong one.
The links in the registry seem to be where the .exe names are actually different but where the process name is the same it seems. Look at "Game" and "CLIENT" and such. I guess my problem is different because both the process name and .exe name seem to be the same, but also I can't just change the .exe name and make a profile, because the .exe file is actually started from another program, really annoying :p
EDIT: Actually the links under game are not all to .exe files, so they might be to other files in order to differentiate, however I then still have no idea how to make a separate profile and not make it load the wrong one.
Good job on this mod. It really reveals how inferior the devs are for nvidia 3d vision. If I was programming nvidia 3d vision I would of left these files to be moddable. Andrew stick up for your devs instead of deleting the post. Let's face it your devs are morons.
There is no excuse for encrypting these non-critical files and forcing users to go to such extreme methods.
Good job on this mod. It really reveals how inferior the devs are for nvidia 3d vision. If I was programming nvidia 3d vision I would of left these files to be moddable. Andrew stick up for your devs instead of deleting the post. Let's face it your devs are morons.
There is no excuse for encrypting these non-critical files and forcing users to go to such extreme methods.
OK got it. Stop stereoscopic service, change nvstres.dll, delete resource.dat (and .old and .new if present), restart stereoscopic service. Then resource.dat is recreated from the info in the changed nvstres.dll. Still this probably doesn't change anything, the driver is now giving the profile info I put in on ctrl+alt+insert, but the real settings are not there, just rating and comments. That said, it's funny because I can put in anything I want now /wink.gif' class='bbc_emoticon' alt=';)' /> Who shall we troll? XD
OK got it. Stop stereoscopic service, change nvstres.dll, delete resource.dat (and .old and .new if present), restart stereoscopic service. Then resource.dat is recreated from the info in the changed nvstres.dll. Still this probably doesn't change anything, the driver is now giving the profile info I put in on ctrl+alt+insert, but the real settings are not there, just rating and comments. That said, it's funny because I can put in anything I want now /wink.gif' class='bbc_emoticon' alt=';)' /> Who shall we troll? XD
Try PMing Neo, he'll have 32 and 64 bit versions, ask him to upload them here.
[url]https://forums.geforce.com/default/topic/490056/3d-vision/how-to-make-your-own-nvidia-lasersights/post/5057253/#5057253[/url]
He should be able to provide you with something. If you can't contact him, I may still have some that I downloaded years ago, on a disc somewhere.
Anyway, I'm not sure which of the files the driver uses to actually get it's profile info from to use, nor do I know where it gets the original info from to revert the nvstres.dll. A shame, as I was trying to make the driver NOT recognize launcher.exe as WRC 2010, as there are other games using the same exe name.
EDIT: In any case, it's very much possible these are all just listings for the control panel and ingame comments on the 3d profile...
Anyway, I'm not sure which of the files the driver uses to actually get it's profile info from to use, nor do I know where it gets the original info from to revert the nvstres.dll. A shame, as I was trying to make the driver NOT recognize launcher.exe as WRC 2010, as there are other games using the same exe name.
EDIT: In any case, it's very much possible these are all just listings for the control panel and ingame comments on the 3d profile...
Current Rig: |Intel Core i7 920 @ 3.6GHz, EVGA X58 Classified 4-way SLI, 6 GB ram, Geforce GTX670| -> |Acer H5360 + Nvidia 3D Vision|
I'm not quite sure where it's getting the game profile data from initially. The nvstres.dll does contain profile data, first entry under RC Data in PE Explorer. However if you change it, it will just revert. Also the drivers create resource.dat, resource.old and sometimes resource.new under c:\ProgramData\NVIDIA and those files also contain the profiles, but changing them and not allowing the system or any service to change them doesn't work either. Making the drivers unable to change nvstres.dll even got my computer to only list anaglyph mode as an option at some point, making me have to reinstall the stereo driver, as just changing back the permissions had no effect.
Anyway, I'm not sure which of the files the driver uses to actually get it's profile info from to use, nor do I know where it gets the original info from to revert the nvstres.dll. A shame, as I was trying to make the driver NOT recognize launcher.exe as WRC 2010, as there are other games using the same exe name.
EDIT: In any case, it's very much possible these are all just listings for the control panel and ingame comments on the 3d profile...
[/quote]
If you're talking about the game profiles with the relevant exe locations and things, they are in the registry. You can make your own profiles. In WinXP they used to be in HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\Stereo3D\GameConfigs
Now I think they are in wow6432node or something like that
I'm not quite sure where it's getting the game profile data from initially. The nvstres.dll does contain profile data, first entry under RC Data in PE Explorer. However if you change it, it will just revert. Also the drivers create resource.dat, resource.old and sometimes resource.new under c:\ProgramData\NVIDIA and those files also contain the profiles, but changing them and not allowing the system or any service to change them doesn't work either. Making the drivers unable to change nvstres.dll even got my computer to only list anaglyph mode as an option at some point, making me have to reinstall the stereo driver, as just changing back the permissions had no effect.
Anyway, I'm not sure which of the files the driver uses to actually get it's profile info from to use, nor do I know where it gets the original info from to revert the nvstres.dll. A shame, as I was trying to make the driver NOT recognize launcher.exe as WRC 2010, as there are other games using the same exe name.
EDIT: In any case, it's very much possible these are all just listings for the control panel and ingame comments on the 3d profile...
If you're talking about the game profiles with the relevant exe locations and things, they are in the registry. You can make your own profiles. In WinXP they used to be in HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\Stereo3D\GameConfigs
Now I think they are in wow6432node or something like that
AMD Phenom II X3 720 @ 2.8GHZ
8GB RAM
Mitsubishi Diamond Pro 2070sb @ 2048x1536 @ 85hz
Edimensional glasses and Nvidia 3D Vision
Sticky this.
Sticky this.
If you're talking about the game profiles with the relevant exe locations and things, they are in the registry. You can make your own profiles. In WinXP they used to be in HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\Stereo3D\GameConfigs
Now I think they are in wow6432node or something like that
[/quote]
The only things in the registry are those games for which a single process name can point to multiple games (which is an issue I'm having where a game is recognized as another, but adding a registry key for it doesn't change a thing) and settings you save yourself, like convergence and whether the nvidia crosshair should show and whatever. The predefined profiles however, are not there. Perhaps one can actually override the parameters through the registry but it doesn't seem to work for me.
If you're talking about the game profiles with the relevant exe locations and things, they are in the registry. You can make your own profiles. In WinXP they used to be in HKEY_LOCAL_MACHINE\SOFTWARE\NVIDIA Corporation\Global\Stereo3D\GameConfigs
Now I think they are in wow6432node or something like that
The only things in the registry are those games for which a single process name can point to multiple games (which is an issue I'm having where a game is recognized as another, but adding a registry key for it doesn't change a thing) and settings you save yourself, like convergence and whether the nvidia crosshair should show and whatever. The predefined profiles however, are not there. Perhaps one can actually override the parameters through the registry but it doesn't seem to work for me.
Current Rig: |Intel Core i7 920 @ 3.6GHz, EVGA X58 Classified 4-way SLI, 6 GB ram, Geforce GTX670| -> |Acer H5360 + Nvidia 3D Vision|
The only things in the registry are those games for which a single process name can point to multiple games (which is an issue I'm having where a game is recognized as another, but adding a registry key for it doesn't change a thing) and settings you save yourself, like convergence and whether the nvidia crosshair should show and whatever. The predefined profiles however, are not there. Perhaps one can actually override the parameters through the registry but it doesn't seem to work for me.
[/quote]
If two games have the same exe name, as of right now there is no way for the nvidia driver to tell the difference. If that's what you're asking. It's impossible unless Nvidia fixes it, we've been telling them this since the dawn of time.
The way it worked with the old forceware 3d driver was that in order for Doom 3 to work, I made a registry key for it called Doom3. That was the name of the key. And when you ran the game in 3D and save settings it saved them under that key because it recognized the executable name. You could also tweak the registry settings for that game under that key, like specifying if it was OpenGL in quad buffer mode.
I have no idea how it works now, I assumed that the current 3D driver does the same thing. But now that I think about it you are right, the newer games do not have keys in there that we can modify.
Maybe Andrew can help us out on where they are stored.
The only things in the registry are those games for which a single process name can point to multiple games (which is an issue I'm having where a game is recognized as another, but adding a registry key for it doesn't change a thing) and settings you save yourself, like convergence and whether the nvidia crosshair should show and whatever. The predefined profiles however, are not there. Perhaps one can actually override the parameters through the registry but it doesn't seem to work for me.
If two games have the same exe name, as of right now there is no way for the nvidia driver to tell the difference. If that's what you're asking. It's impossible unless Nvidia fixes it, we've been telling them this since the dawn of time.
The way it worked with the old forceware 3d driver was that in order for Doom 3 to work, I made a registry key for it called Doom3. That was the name of the key. And when you ran the game in 3D and save settings it saved them under that key because it recognized the executable name. You could also tweak the registry settings for that game under that key, like specifying if it was OpenGL in quad buffer mode.
I have no idea how it works now, I assumed that the current 3D driver does the same thing. But now that I think about it you are right, the newer games do not have keys in there that we can modify.
Maybe Andrew can help us out on where they are stored.
AMD Phenom II X3 720 @ 2.8GHZ
8GB RAM
Mitsubishi Diamond Pro 2070sb @ 2048x1536 @ 85hz
Edimensional glasses and Nvidia 3D Vision
EDIT: Actually the links under game are not all to .exe files, so they might be to other files in order to differentiate, however I then still have no idea how to make a separate profile and not make it load the wrong one.
EDIT: Actually the links under game are not all to .exe files, so they might be to other files in order to differentiate, however I then still have no idea how to make a separate profile and not make it load the wrong one.
Current Rig: |Intel Core i7 920 @ 3.6GHz, EVGA X58 Classified 4-way SLI, 6 GB ram, Geforce GTX670| -> |Acer H5360 + Nvidia 3D Vision|
There is no excuse for encrypting these non-critical files and forcing users to go to such extreme methods.
Face the music son.
There is no excuse for encrypting these non-critical files and forcing users to go to such extreme methods.
Face the music son.
Current Rig: |Intel Core i7 920 @ 3.6GHz, EVGA X58 Classified 4-way SLI, 6 GB ram, Geforce GTX670| -> |Acer H5360 + Nvidia 3D Vision|
Current Rig: |Intel Core i7 920 @ 3.6GHz, EVGA X58 Classified 4-way SLI, 6 GB ram, Geforce GTX670| -> |Acer H5360 + Nvidia 3D Vision|
Really want them! Links anyone?
Thanks
https://forums.geforce.com/default/topic/490056/3d-vision/how-to-make-your-own-nvidia-lasersights/post/5057253/#5057253
He should be able to provide you with something. If you can't contact him, I may still have some that I downloaded years ago, on a disc somewhere.