[quote="greatxerox"]- nvidiaProfileInspector is now open source and licensed under MIT license.
(https://github.com/Orbmu2k/nvidiaProfileInspector)
[/quote]Nice - I just sent them a pull request to import the changes I made to CustomSettingNames to add all the stereo settings.
[quote="maffl0r"]I don't like posting on the Guru3D, a bunch of arrogant people never giving answers or are of any help. Especially the authors of those popular tools, like NvidiaInspector or RivaTuner. I asked/reported several things in the forums and never got any answer or feedback. Someone knows where I can download, without any virus, the old working NvidiaInspector before it was split? Which was the last non split version?[/quote]Now that it's open source you might consider using the Issue tracker:
https://github.com/Orbmu2k/nvidiaProfileInspector/issues
Nice - I just sent them a pull request to import the changes I made to CustomSettingNames to add all the stereo settings.
maffl0r said:I don't like posting on the Guru3D, a bunch of arrogant people never giving answers or are of any help. Especially the authors of those popular tools, like NvidiaInspector or RivaTuner. I asked/reported several things in the forums and never got any answer or feedback. Someone knows where I can download, without any virus, the old working NvidiaInspector before it was split? Which was the last non split version?
Any chance to add a way to swap profiles while in game via a hot key?
Perhaps it would be possible to cycle through all of the different CM profiles to see which one gives the best result more easily, for those that want to play a new game at launch that doesn't have an official profile?
Or to swap profiles on older games without alt tabbing?
Any chance to add a way to swap profiles while in game via a hot key?
Perhaps it would be possible to cycle through all of the different CM profiles to see which one gives the best result more easily, for those that want to play a new game at launch that doesn't have an official profile?
Or to swap profiles on older games without alt tabbing?
About your CustomSettingNames, does it apply the names to the setting in every profile or just a few select ones?
Such as
Setting ID_0x701eb457 = 0x2241ab21 InternalSettingFlag=V0 //MysteryStereoSetting
will it be labeled for every entry? Or just a few where you have added the label?
I ask because I tried to import your XML, but I'm not seeing the labels/naming scheme.
[quote="maffl0r"]-silent doesn't work/exist in the nvidiaProfileInspector.exe, fix this please. Why was this changed? This is unbelievable. You cant start/import profiles silently anymore like you could with the old exe...[/quote]
[color="green"]NVIDIA INSPECTOR 1.9.7.3[/color]
Can't find any link to download it, but I still have a copy if anyone is interested.
maffl0r said:-silent doesn't work/exist in the nvidiaProfileInspector.exe, fix this please. Why was this changed? This is unbelievable. You cant start/import profiles silently anymore like you could with the old exe...
NVIDIA INSPECTOR 1.9.7.3
Can't find any link to download it, but I still have a copy if anyone is interested.
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
Odd that all of the old downloads have disappeared. Perhaps it was a copyright/patent issue? (whatever you call it for software)
Found a post by Orbmu2k talking about exporting and importing profiles. Legacy vs Current implementation. Pretty much what we know already about it's expected behavior.
http://forums.guru3d.com/showpost.php?p=5267048&postcount=187
He fixed some of the errors on importing in the newer version see post #194
http://forums.guru3d.com/showthread.php?t=403676&page=8
I still prefer the old one, it does what I need
[quote="D-Man11"]About your CustomSettingNames, does it apply the names to the setting in every profile or just a few select ones?
Such as
Setting ID_0x701eb457 = 0x2241ab21 InternalSettingFlag=V0 //MysteryStereoSetting
will it be labeled for every entry? Or just a few where you have added the label?[/quote]It should show up in every entry.
[quote]I ask because I tried to import your XML, but I'm not seeing the labels/naming scheme.[/quote]Which version of nvidia profile inspector are you using? If you grabbed the latest from here [b][color="orange"]in the last few hours[/color][/b]:
https://ci.appveyor.com/project/Orbmu2k/nvidiaprofileinspector/build/artifacts
You [color="orange"]NO LONGER need to import the XML file[/color] - it is now embedded inside the executable, and all the new settings show up in their own section at the end called "Stereo" :)
Direct link to specific build artefact for my pull request (just in case it gets trumped by a more recent build before my pull request is merged): https://ci.appveyor.com/project/Orbmu2k/nvidiaprofileinspector/build/2.1.2.5/artifacts
If you are using an older version with a separate xml file you would replace that with mine.
You NO LONGER need to import the XML file - it is now embedded inside the executable, and all the new settings show up in their own section at the end called "Stereo" :)
I'm using 1.9.7.3, I'll try the new one.
Though lately, I've been using Nvidia's profile manager the majority of the time when trying different profiles and settings.
I can't say that I understand the ins and outs of the settings, but they can be pretty powerful in the way that they manipulate the stereo images. I can see some patterns in some of it, it would be nice to understand them fully though. It would be nice to see the full documentation from Nvidia for them.
I just played through the Walking Dead Season 1 & 2 with just a profile tweak and no fix, with only a few minor issues. The same for Michonne.
Thanks for adding that into the pull you made :)
Though lately, I've been using Nvidia's profile manager the majority of the time when trying different profiles and settings.
I can't say that I understand the ins and outs of the settings, but they can be pretty powerful in the way that they manipulate the stereo images. I can see some patterns in some of it, it would be nice to understand them fully though. It would be nice to see the full documentation from Nvidia for them.
I just played through the Walking Dead Season 1 & 2 with just a profile tweak and no fix, with only a few minor issues. The same for Michonne.
[quote="D-Man11"]Odd that all of the old downloads have disappeared. Perhaps it was a copyright/patent issue? (whatever you call it for software)[/quote]I doubt it's intentional, but I notice that the EU mirror still appears to download NVIDIA Inspector 1.9.7.3, while the author's mirror downloads 1.9.7.6.
If you're on the standalone NVIDIA Profile Inspector but aren't using the CI version with my pull request note that my file needs to be named 'CustomSettingNames.xml' (i.e. remove the '_en-EN'), but I recommend using the CI version as I merged the file with their latest changes.
[quote="D-Man11"]I can't say that I understand the ins and outs of the settings, but they can be pretty powerful in the way that they manipulate the stereo images. I can see some patterns in some of it, it would be nice to understand them fully though. It would be nice to see the full documentation from Nvidia for them.[/quote]We do have some documentation from our contact for most of the bit definitions of StereoTextureEnable and two compute shader bits in StereoFlagsDX10. Some of this is on the wiki:
http://wiki.bo3b.net/index.php?title=Driver_Profile_Settings
I'll PM you the definitions of StereoTextureEnable (EDIT: Oh wait, looks like I already sent these to you. Let me know if you need them resent).
D-Man11 said:Odd that all of the old downloads have disappeared. Perhaps it was a copyright/patent issue? (whatever you call it for software)
I doubt it's intentional, but I notice that the EU mirror still appears to download NVIDIA Inspector 1.9.7.3, while the author's mirror downloads 1.9.7.6.
If you're on the standalone NVIDIA Profile Inspector but aren't using the CI version with my pull request note that my file needs to be named 'CustomSettingNames.xml' (i.e. remove the '_en-EN'), but I recommend using the CI version as I merged the file with their latest changes.
D-Man11 said:I can't say that I understand the ins and outs of the settings, but they can be pretty powerful in the way that they manipulate the stereo images. I can see some patterns in some of it, it would be nice to understand them fully though. It would be nice to see the full documentation from Nvidia for them.
lol, I look at those things on the list and it's all french to me. I've looked at it several times but can't decipher anything from it. I'm sure it makes sense to you, but i do not see how that list translates into the profile settings.
Some of my observations I've posted in this thread.
https://forums.geforce.com/default/topic/801771/
Like how ID_0x709a1ddf has 3 different modifiers 96b, 968 or 969
ID_0x709a1ddf = 0x4b1cd96b
ID_0x709a1ddf = 0x4b1cd969
ID_0x709a1ddf = 0x4b1cd968
Which we know are the stereo cutoff for near and far. So that part isn't such a mystery.
lol, I look at those things on the list and it's all french to me. I've looked at it several times but can't decipher anything from it. I'm sure it makes sense to you, but i do not see how that list translates into the profile settings.
And for ID_0x70edb381, these are the available alternatives.
Setting ID_0x70edb381 = 0x24208b5c InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x242086a8 InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208b6c InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208b4f InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208b4e InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208a4c InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208b4d InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208bec InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208bcc InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208fa8 InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208b6e InternalSettingFlag=V0
Using Setting ID_0x70edb381 = 0x24208b5c InternalSettingFlag=V0 un-stereoizes the button prompts in the Tell Tale games and put them at screen depth in 2D.
Edit: BTW bo3b mentioned something about a couple of bugs and the fonts in Nvidia Inspector here
[url]https://forums.geforce.com/default/topic/946946/oculus/oculus-runtime-1-5-and-nvidia-inspector/post/4914154/#4914154[/url]
Using Setting ID_0x70edb381 = 0x24208b5c InternalSettingFlag=V0 un-stereoizes the button prompts in the Tell Tale games and put them at screen depth in 2D.
The author got back to me - turns out that NVIDIA Profile Inspector (since it was split off from NVIDIA Inspector) already parses the stereo setting names directly from the driver (much the same way my I did when I created that xml file), but they only show up if they are already present in a profile, or when 'Show unknown settings from NVIDIA predefined profiles' is enabled. However, it lacks a name for the mystery stereo setting, which is a pretty big oversight. I intend to revise my pull request to add just that and make a few of the known important settings show up by default.
[quote="D-Man11"]Some of my observations I've posted in this thread.
https://forums.geforce.com/default/topic/801771/
Like how ID_0x709a1ddf has 3 different modifiers 96b, 968 or 969
ID_0x709a1ddf = 0x4b1cd96b
ID_0x709a1ddf = 0x4b1cd969
ID_0x709a1ddf = 0x4b1cd968
Which we know are the stereo cutoff for near and far. So that part isn't such a mystery.[/quote]Can you please add that info to the wiki?
The author got back to me - turns out that NVIDIA Profile Inspector (since it was split off from NVIDIA Inspector) already parses the stereo setting names directly from the driver (much the same way my I did when I created that xml file), but they only show up if they are already present in a profile, or when 'Show unknown settings from NVIDIA predefined profiles' is enabled. However, it lacks a name for the mystery stereo setting, which is a pretty big oversight. I intend to revise my pull request to add just that and make a few of the known important settings show up by default.
"Mystery Stereo Setting" == "STEREO_STEREOPROFILE" (and we will name it "StereoProfile" when I send the revised pull request). Not sure where Orbmu2k found that name, but that solves one mystery ;-)
"Mystery Stereo Setting" == "STEREO_STEREOPROFILE" (and we will name it "StereoProfile" when I send the revised pull request). Not sure where Orbmu2k found that name, but that solves one mystery ;-)
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
[quote="DarkStarSword"]Can you please add that info to the wiki?[/quote]
I'm not really sure what I would add or say. I just try one or the other to see if the result changes and then go with the best choice.
The first part is some kind of known constant, where we know that 0x709a1ddf is a stereo cut off (whatever that is? I think it's screen planes?? like out of screen, screen depth, in screen, no idea)
I assume the second part is just a value? like 0x4b1cd96b could equal a multiplier or position or correction? (no idea)
SettingString ID_0x70b5603f = "D3D"
I see this setting quite often, I do not think that it does anything, I think it's just an internal note to list the renderer being used for reference if the profile is re-visted at a later time for modification. Do you know of a purpose for it?
I'm still trying to figure out if there is a hierarchy in the listings, like if they have to be listed in a certain order or the effect might be nulled if out of order. It kind of seems that way, but I've only recently experimented very much.
DarkStarSword said:Can you please add that info to the wiki?
I'm not really sure what I would add or say. I just try one or the other to see if the result changes and then go with the best choice.
The first part is some kind of known constant, where we know that 0x709a1ddf is a stereo cut off (whatever that is? I think it's screen planes?? like out of screen, screen depth, in screen, no idea)
I assume the second part is just a value? like 0x4b1cd96b could equal a multiplier or position or correction? (no idea)
SettingString ID_0x70b5603f = "D3D"
I see this setting quite often, I do not think that it does anything, I think it's just an internal note to list the renderer being used for reference if the profile is re-visted at a later time for modification. Do you know of a purpose for it?
I'm still trying to figure out if there is a hierarchy in the listings, like if they have to be listed in a certain order or the effect might be nulled if out of order. It kind of seems that way, but I've only recently experimented very much.
So Orbmu2k has never received any official documentation from Nvidia?
Also ask him if he can share any info that he has for SLI bits and pass those along to some of our SLI users like helifax.
[quote="D-Man11"]I'm not really sure what I would add or say. I just try one or the other to see if the result changes and then go with the best choice.
The first part is some kind of known constant, where we know that 0x709a1ddf is a stereo cut off (whatever that is? I think it's screen planes?? like out of screen, screen depth, in screen, no idea)
I assume the second part is just a value? like 0x4b1cd96b could equal a multiplier or position or correction? (no idea)[/quote]That level of information is fine - please add any observations and guesses you have to the wiki (marked as such) so that we have everything in one place.
[quote]SettingString ID_0x70b5603f = "D3D"
I see this setting quite often, I do not think that it does anything, I think it's just an internal note to list the renderer being used for reference if the profile is re-visted at a later time for modification. Do you know of a purpose for it?[/quote]I don't know of it's purpose, and don't see any differences on custom profiles without it, so I assume it is likely just informational. It could be an interesting experiment to lie in this field and see if anything changes.
[quote]I'm still trying to figure out if there is a hierarchy in the listings, like if they have to be listed in a certain order or the effect might be nulled if out of order. It kind of seems that way, but I've only recently experimented very much.[/quote]I know from my own experimentation that StereoTextureEnable is ignored without StereoProfile, and there could well be other cases of this.
[quote="D-Man11"]So Orbmu2k has never received any official documentation from Nvidia?[/quote]I probed him on this, but he didn't answer. It wouldn't surprise me if NVIDIA gave him the info but asked him not to reveal it, but of course that is just speculation.
D-Man11 said:I'm not really sure what I would add or say. I just try one or the other to see if the result changes and then go with the best choice.
The first part is some kind of known constant, where we know that 0x709a1ddf is a stereo cut off (whatever that is? I think it's screen planes?? like out of screen, screen depth, in screen, no idea)
I assume the second part is just a value? like 0x4b1cd96b could equal a multiplier or position or correction? (no idea)
That level of information is fine - please add any observations and guesses you have to the wiki (marked as such) so that we have everything in one place.
SettingString ID_0x70b5603f = "D3D"
I see this setting quite often, I do not think that it does anything, I think it's just an internal note to list the renderer being used for reference if the profile is re-visted at a later time for modification. Do you know of a purpose for it?
I don't know of it's purpose, and don't see any differences on custom profiles without it, so I assume it is likely just informational. It could be an interesting experiment to lie in this field and see if anything changes.
I'm still trying to figure out if there is a hierarchy in the listings, like if they have to be listed in a certain order or the effect might be nulled if out of order. It kind of seems that way, but I've only recently experimented very much.
I know from my own experimentation that StereoTextureEnable is ignored without StereoProfile, and there could well be other cases of this.
D-Man11 said:So Orbmu2k has never received any official documentation from Nvidia?
I probed him on this, but he didn't answer. It wouldn't surprise me if NVIDIA gave him the info but asked him not to reveal it, but of course that is just speculation.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Now that it's open source you might consider using the Issue tracker:
https://github.com/Orbmu2k/nvidiaProfileInspector/issues
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
Perhaps it would be possible to cycle through all of the different CM profiles to see which one gives the best result more easily, for those that want to play a new game at launch that doesn't have an official profile?
Or to swap profiles on older games without alt tabbing?
Such as
Setting ID_0x701eb457 = 0x2241ab21 InternalSettingFlag=V0 //MysteryStereoSetting
will it be labeled for every entry? Or just a few where you have added the label?
I ask because I tried to import your XML, but I'm not seeing the labels/naming scheme.
NVIDIA INSPECTOR 1.9.7.3
Can't find any link to download it, but I still have a copy if anyone is interested.
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
Found a post by Orbmu2k talking about exporting and importing profiles. Legacy vs Current implementation. Pretty much what we know already about it's expected behavior.
http://forums.guru3d.com/showpost.php?p=5267048&postcount=187
He fixed some of the errors on importing in the newer version see post #194
http://forums.guru3d.com/showthread.php?t=403676&page=8
I still prefer the old one, it does what I need
Which version of nvidia profile inspector are you using? If you grabbed the latest from here in the last few hours:
https://ci.appveyor.com/project/Orbmu2k/nvidiaprofileinspector/build/artifacts
You NO LONGER need to import the XML file - it is now embedded inside the executable, and all the new settings show up in their own section at the end called "Stereo" :)
Direct link to specific build artefact for my pull request (just in case it gets trumped by a more recent build before my pull request is merged): https://ci.appveyor.com/project/Orbmu2k/nvidiaprofileinspector/build/2.1.2.5/artifacts
If you are using an older version with a separate xml file you would replace that with mine.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
Though lately, I've been using Nvidia's profile manager the majority of the time when trying different profiles and settings.
I can't say that I understand the ins and outs of the settings, but they can be pretty powerful in the way that they manipulate the stereo images. I can see some patterns in some of it, it would be nice to understand them fully though. It would be nice to see the full documentation from Nvidia for them.
I just played through the Walking Dead Season 1 & 2 with just a profile tweak and no fix, with only a few minor issues. The same for Michonne.
Thanks for adding that into the pull you made :)
If you're on the standalone NVIDIA Profile Inspector but aren't using the CI version with my pull request note that my file needs to be named 'CustomSettingNames.xml' (i.e. remove the '_en-EN'), but I recommend using the CI version as I merged the file with their latest changes.
We do have some documentation from our contact for most of the bit definitions of StereoTextureEnable and two compute shader bits in StereoFlagsDX10. Some of this is on the wiki:
http://wiki.bo3b.net/index.php?title=Driver_Profile_Settings
I'll PM you the definitions of StereoTextureEnable (EDIT: Oh wait, looks like I already sent these to you. Let me know if you need them resent).
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
Some of my observations I've posted in this thread.
https://forums.geforce.com/default/topic/801771/
Like how ID_0x709a1ddf has 3 different modifiers 96b, 968 or 969
ID_0x709a1ddf = 0x4b1cd96b
ID_0x709a1ddf = 0x4b1cd969
ID_0x709a1ddf = 0x4b1cd968
Which we know are the stereo cutoff for near and far. So that part isn't such a mystery.
Setting ID_0x70edb381 = 0x24208b5c InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x242086a8 InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208b6c InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208b4f InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208b4e InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208a4c InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208b4d InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208bec InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208bcc InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208fa8 InternalSettingFlag=V0
Setting ID_0x70edb381 = 0x24208b6e InternalSettingFlag=V0
Using Setting ID_0x70edb381 = 0x24208b5c InternalSettingFlag=V0 un-stereoizes the button prompts in the Tell Tale games and put them at screen depth in 2D.
Edit: BTW bo3b mentioned something about a couple of bugs and the fonts in Nvidia Inspector here
https://forums.geforce.com/default/topic/946946/oculus/oculus-runtime-1-5-and-nvidia-inspector/post/4914154/#4914154
Can you please add that info to the wiki?
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword
I'm not really sure what I would add or say. I just try one or the other to see if the result changes and then go with the best choice.
The first part is some kind of known constant, where we know that 0x709a1ddf is a stereo cut off (whatever that is? I think it's screen planes?? like out of screen, screen depth, in screen, no idea)
I assume the second part is just a value? like 0x4b1cd96b could equal a multiplier or position or correction? (no idea)
SettingString ID_0x70b5603f = "D3D"
I see this setting quite often, I do not think that it does anything, I think it's just an internal note to list the renderer being used for reference if the profile is re-visted at a later time for modification. Do you know of a purpose for it?
I'm still trying to figure out if there is a hierarchy in the listings, like if they have to be listed in a certain order or the effect might be nulled if out of order. It kind of seems that way, but I've only recently experimented very much.
Also ask him if he can share any info that he has for SLI bits and pass those along to some of our SLI users like helifax.
I don't know of it's purpose, and don't see any differences on custom profiles without it, so I assume it is likely just informational. It could be an interesting experiment to lie in this field and see if anything changes.
I know from my own experimentation that StereoTextureEnable is ignored without StereoProfile, and there could well be other cases of this.
I probed him on this, but he didn't answer. It wouldn't surprise me if NVIDIA gave him the info but asked him not to reveal it, but of course that is just speculation.
2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit
Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD
Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword