Official NVIDIA 3D Vision 260.63/CD 1.36 kit Feedback Thread Including 3D Vision and 3D Vision Surro
7 / 15
[quote name='typeholder' post='1118038' date='Sep 15 2010, 09:11 PM']MMOs use fake full screen a lot(including WoW, Aion). It's so the user can alt-tab in to and out of the game quickly.
You can't enable 3d vision until it's true fullscreen[/quote]
Ya I think FFXIV is actually the opposite, where they have a fake fullscreen wrapper to prevent users from Alt-Tabing out of the game. If you Alt-tab in FFXIV it breaks fullscreen and the client gives you a "no D3D device detected" error message.
[quote name='typeholder' post='1118038' date='Sep 15 2010, 09:11 PM']MMOs use fake full screen a lot(including WoW, Aion). It's so the user can alt-tab in to and out of the game quickly.
You can't enable 3d vision until it's true fullscreen
Ya I think FFXIV is actually the opposite, where they have a fake fullscreen wrapper to prevent users from Alt-Tabing out of the game. If you Alt-tab in FFXIV it breaks fullscreen and the client gives you a "no D3D device detected" error message.
[quote name='typeholder' post='1118038' date='Sep 15 2010, 09:11 PM']MMOs use fake full screen a lot(including WoW, Aion). It's so the user can alt-tab in to and out of the game quickly.
You can't enable 3d vision until it's true fullscreen[/quote]
Ya I think FFXIV is actually the opposite, where they have a fake fullscreen wrapper to prevent users from Alt-Tabing out of the game. If you Alt-tab in FFXIV it breaks fullscreen and the client gives you a "no D3D device detected" error message.
[quote name='typeholder' post='1118038' date='Sep 15 2010, 09:11 PM']MMOs use fake full screen a lot(including WoW, Aion). It's so the user can alt-tab in to and out of the game quickly.
You can't enable 3d vision until it's true fullscreen
Ya I think FFXIV is actually the opposite, where they have a fake fullscreen wrapper to prevent users from Alt-Tabing out of the game. If you Alt-tab in FFXIV it breaks fullscreen and the client gives you a "no D3D device detected" error message.
[quote name='chiz' post='1118443' date='Sep 16 2010, 09:19 PM']The latest drivers do not have the proper DX9 AA compatibility flag enabled. You can modify this yourself using Nvidia's SLI Tool.
Run the tool, Choose Export and save it wherever you like, like Desktop.
Open the File with Notepad, should be titled Nvidia Profiles.txt by default
Hit Ctrl-F and search for Mafia, then find Mafia 2's profile
Insert this DX9 AA flag setting anywhere after the executable names: Setting ID_0x00d55f7d = 0x000d02c4
Save the file, then choose Import SLI Profiles and select Nvidia Profiles.txt to re-import the game profile changes.
Every time a new driver comes out, I archive the default profile flags and also save my current version which has any changes I made for better performance or compatibility, this way its very easy for me to compare which flags have changed from driver to driver. So for example I will have Nvidia Profiles 259.32.txt (default) and Nvidia Profiles 259.32a.txt (edited) and the current working copy will be Nvidia Profiles.txt always.[/quote]
Thank you very much, chiz. That is really great information.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.
[quote name='chiz' post='1118443' date='Sep 16 2010, 09:19 PM']The latest drivers do not have the proper DX9 AA compatibility flag enabled. You can modify this yourself using Nvidia's SLI Tool.
Run the tool, Choose Export and save it wherever you like, like Desktop.
Open the File with Notepad, should be titled Nvidia Profiles.txt by default
Hit Ctrl-F and search for Mafia, then find Mafia 2's profile
Insert this DX9 AA flag setting anywhere after the executable names: Setting ID_0x00d55f7d = 0x000d02c4
Save the file, then choose Import SLI Profiles and select Nvidia Profiles.txt to re-import the game profile changes.
Every time a new driver comes out, I archive the default profile flags and also save my current version which has any changes I made for better performance or compatibility, this way its very easy for me to compare which flags have changed from driver to driver. So for example I will have Nvidia Profiles 259.32.txt (default) and Nvidia Profiles 259.32a.txt (edited) and the current working copy will be Nvidia Profiles.txt always.
Thank you very much, chiz. That is really great information.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.
[quote name='chiz' post='1118443' date='Sep 16 2010, 09:19 PM']The latest drivers do not have the proper DX9 AA compatibility flag enabled. You can modify this yourself using Nvidia's SLI Tool.
Run the tool, Choose Export and save it wherever you like, like Desktop.
Open the File with Notepad, should be titled Nvidia Profiles.txt by default
Hit Ctrl-F and search for Mafia, then find Mafia 2's profile
Insert this DX9 AA flag setting anywhere after the executable names: Setting ID_0x00d55f7d = 0x000d02c4
Save the file, then choose Import SLI Profiles and select Nvidia Profiles.txt to re-import the game profile changes.
Every time a new driver comes out, I archive the default profile flags and also save my current version which has any changes I made for better performance or compatibility, this way its very easy for me to compare which flags have changed from driver to driver. So for example I will have Nvidia Profiles 259.32.txt (default) and Nvidia Profiles 259.32a.txt (edited) and the current working copy will be Nvidia Profiles.txt always.[/quote]
Thank you very much, chiz. That is really great information.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.
[quote name='chiz' post='1118443' date='Sep 16 2010, 09:19 PM']The latest drivers do not have the proper DX9 AA compatibility flag enabled. You can modify this yourself using Nvidia's SLI Tool.
Run the tool, Choose Export and save it wherever you like, like Desktop.
Open the File with Notepad, should be titled Nvidia Profiles.txt by default
Hit Ctrl-F and search for Mafia, then find Mafia 2's profile
Insert this DX9 AA flag setting anywhere after the executable names: Setting ID_0x00d55f7d = 0x000d02c4
Save the file, then choose Import SLI Profiles and select Nvidia Profiles.txt to re-import the game profile changes.
Every time a new driver comes out, I archive the default profile flags and also save my current version which has any changes I made for better performance or compatibility, this way its very easy for me to compare which flags have changed from driver to driver. So for example I will have Nvidia Profiles 259.32.txt (default) and Nvidia Profiles 259.32a.txt (edited) and the current working copy will be Nvidia Profiles.txt always.
Thank you very much, chiz. That is really great information.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.
[quote name='Nobsi' post='1118463' date='Sep 16 2010, 04:58 PM']Thank you very much, chiz. That is really great information.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.[/quote]
Np, glad it helped. :)
Just reverse engineering using accumulated knowledge from the insight nHancer (and coolbits before it) provided us in the past. Previously, nHancer dealt with the setting IDs and then mapped the various hex values to easily toggleable compatiblity check boxes to change the hex flag. You could also do the same with manually editing the Nvapps.xml file, but Nvidia provided the setting names in plain english. With the R256 drivers, Nvidia changed this up on us a bit with the actual Setting ID codes with the hex values. I just compared known hex value compatibility settings from previous drivers in certain titles to figure out which Setting IDs were relevant to the settings I most often needed to change in previous drivers for SLI and AA compatibility. As a result, I've found the following:
[b]For AA: [/b]
[list]
[*]Setting ID_0x00d55f7d = DX9 AA compatibility
[*]Setting ID_0x00e32f8a = DX10/11 AA compatibility
[/list]
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.
[quote name='Nobsi' post='1118463' date='Sep 16 2010, 04:58 PM']Thank you very much, chiz. That is really great information.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.
Np, glad it helped. :)
Just reverse engineering using accumulated knowledge from the insight nHancer (and coolbits before it) provided us in the past. Previously, nHancer dealt with the setting IDs and then mapped the various hex values to easily toggleable compatiblity check boxes to change the hex flag. You could also do the same with manually editing the Nvapps.xml file, but Nvidia provided the setting names in plain english. With the R256 drivers, Nvidia changed this up on us a bit with the actual Setting ID codes with the hex values. I just compared known hex value compatibility settings from previous drivers in certain titles to figure out which Setting IDs were relevant to the settings I most often needed to change in previous drivers for SLI and AA compatibility. As a result, I've found the following:
For AA:
Setting ID_0x00d55f7d = DX9 AA compatibility
Setting ID_0x00e32f8a = DX10/11 AA compatibility
For SLI:
Setting ID_0x1095def8 = DX9 SLI compatibility
Setting ID_0x00a06946 = DX10/11 SLI compatibility
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.
[quote name='Nobsi' post='1118463' date='Sep 16 2010, 04:58 PM']Thank you very much, chiz. That is really great information.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.[/quote]
Np, glad it helped. :)
Just reverse engineering using accumulated knowledge from the insight nHancer (and coolbits before it) provided us in the past. Previously, nHancer dealt with the setting IDs and then mapped the various hex values to easily toggleable compatiblity check boxes to change the hex flag. You could also do the same with manually editing the Nvapps.xml file, but Nvidia provided the setting names in plain english. With the R256 drivers, Nvidia changed this up on us a bit with the actual Setting ID codes with the hex values. I just compared known hex value compatibility settings from previous drivers in certain titles to figure out which Setting IDs were relevant to the settings I most often needed to change in previous drivers for SLI and AA compatibility. As a result, I've found the following:
[b]For AA: [/b]
[list]
[*]Setting ID_0x00d55f7d = DX9 AA compatibility
[*]Setting ID_0x00e32f8a = DX10/11 AA compatibility
[/list]
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.
[quote name='Nobsi' post='1118463' date='Sep 16 2010, 04:58 PM']Thank you very much, chiz. That is really great information.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.
Np, glad it helped. :)
Just reverse engineering using accumulated knowledge from the insight nHancer (and coolbits before it) provided us in the past. Previously, nHancer dealt with the setting IDs and then mapped the various hex values to easily toggleable compatiblity check boxes to change the hex flag. You could also do the same with manually editing the Nvapps.xml file, but Nvidia provided the setting names in plain english. With the R256 drivers, Nvidia changed this up on us a bit with the actual Setting ID codes with the hex values. I just compared known hex value compatibility settings from previous drivers in certain titles to figure out which Setting IDs were relevant to the settings I most often needed to change in previous drivers for SLI and AA compatibility. As a result, I've found the following:
For AA:
Setting ID_0x00d55f7d = DX9 AA compatibility
Setting ID_0x00e32f8a = DX10/11 AA compatibility
For SLI:
Setting ID_0x1095def8 = DX9 SLI compatibility
Setting ID_0x00a06946 = DX10/11 SLI compatibility
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.
[quote name='Nobsi' post='1117935' date='Sep 15 2010, 10:55 PM']I can no longer force AA (any level) in the nVidia Control Panel for Mafia 2 with the new driver. This worked fine with the 258.96 driver in 2D and 3D mode an a GTX280 and a GTX480 in Win7 32bit.[/quote]
nvidia inspector allows you to edit every profile. simply set the aa-behaviour flag for mafia 2 to none.
[url="http://blog.orbmu2k.de/tools/nvidia-inspector-tool"]http://blog.orbmu2k.de/tools/nvidia-inspector-tool[/url]
[quote name='Nobsi' post='1117935' date='Sep 15 2010, 10:55 PM']I can no longer force AA (any level) in the nVidia Control Panel for Mafia 2 with the new driver. This worked fine with the 258.96 driver in 2D and 3D mode an a GTX280 and a GTX480 in Win7 32bit.
nvidia inspector allows you to edit every profile. simply set the aa-behaviour flag for mafia 2 to none.
NVIDIA TITAN X (Pascal), Intel Core i7-6900K, Win 10 Pro,
ASUS ROG Rampage V Edition 10, G.Skill RipJaws V 4x 8GB DDR4-3200 CL14-14-14-34,
ASUS ROG Swift PG258Q, ASUS ROG Swift PG278Q, Acer Predator XB280HK, BenQ W710ST
[quote name='Nobsi' post='1117935' date='Sep 15 2010, 10:55 PM']I can no longer force AA (any level) in the nVidia Control Panel for Mafia 2 with the new driver. This worked fine with the 258.96 driver in 2D and 3D mode an a GTX280 and a GTX480 in Win7 32bit.[/quote]
nvidia inspector allows you to edit every profile. simply set the aa-behaviour flag for mafia 2 to none.
[url="http://blog.orbmu2k.de/tools/nvidia-inspector-tool"]http://blog.orbmu2k.de/tools/nvidia-inspector-tool[/url]
[quote name='Nobsi' post='1117935' date='Sep 15 2010, 10:55 PM']I can no longer force AA (any level) in the nVidia Control Panel for Mafia 2 with the new driver. This worked fine with the 258.96 driver in 2D and 3D mode an a GTX280 and a GTX480 in Win7 32bit.
nvidia inspector allows you to edit every profile. simply set the aa-behaviour flag for mafia 2 to none.
NVIDIA TITAN X (Pascal), Intel Core i7-6900K, Win 10 Pro,
ASUS ROG Rampage V Edition 10, G.Skill RipJaws V 4x 8GB DDR4-3200 CL14-14-14-34,
ASUS ROG Swift PG258Q, ASUS ROG Swift PG278Q, Acer Predator XB280HK, BenQ W710ST
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.[/quote]
Again, many thanks.
I googled a bit and it seems that both nHancer and RivaTuner are outdated and can not be used for editing the settings of 256 or newer drivers, due to the changed profile mechanism. At least the nHancer author has said that he will most probably write a new nHancer version from scratch for the new driver generation (based on Windows Presentation Framework), but has unfortunately currently no time to work on the project.
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.
Again, many thanks.
I googled a bit and it seems that both nHancer and RivaTuner are outdated and can not be used for editing the settings of 256 or newer drivers, due to the changed profile mechanism. At least the nHancer author has said that he will most probably write a new nHancer version from scratch for the new driver generation (based on Windows Presentation Framework), but has unfortunately currently no time to work on the project.
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.[/quote]
Again, many thanks.
I googled a bit and it seems that both nHancer and RivaTuner are outdated and can not be used for editing the settings of 256 or newer drivers, due to the changed profile mechanism. At least the nHancer author has said that he will most probably write a new nHancer version from scratch for the new driver generation (based on Windows Presentation Framework), but has unfortunately currently no time to work on the project.
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.
Again, many thanks.
I googled a bit and it seems that both nHancer and RivaTuner are outdated and can not be used for editing the settings of 256 or newer drivers, due to the changed profile mechanism. At least the nHancer author has said that he will most probably write a new nHancer version from scratch for the new driver generation (based on Windows Presentation Framework), but has unfortunately currently no time to work on the project.
[quote name='jade0732' post='1117599' date='Sep 15 2010, 06:08 PM']Sorry for this but I'v got another Question if the test is not a indication of computability with the 3D TV play then is my tv computabile. (LG 47LX6500) 3d modes Top & Bottom, Side by Side, Checker Board, Single Frame Sequential, Frame Packing and 1.4 HDMI. :unsure:[/quote]
Hallo Nvidia enyone there? /alien.gif' class='bbc_emoticon' alt=':alien:' />
[quote name='jade0732' post='1117599' date='Sep 15 2010, 06:08 PM']Sorry for this but I'v got another Question if the test is not a indication of computability with the 3D TV play then is my tv computabile. (LG 47LX6500) 3d modes Top & Bottom, Side by Side, Checker Board, Single Frame Sequential, Frame Packing and 1.4 HDMI. :unsure:
[quote name='jade0732' post='1117599' date='Sep 15 2010, 06:08 PM']Sorry for this but I'v got another Question if the test is not a indication of computability with the 3D TV play then is my tv computabile. (LG 47LX6500) 3d modes Top & Bottom, Side by Side, Checker Board, Single Frame Sequential, Frame Packing and 1.4 HDMI. :unsure:[/quote]
Hallo Nvidia enyone there? /alien.gif' class='bbc_emoticon' alt=':alien:' />
[quote name='jade0732' post='1117599' date='Sep 15 2010, 06:08 PM']Sorry for this but I'v got another Question if the test is not a indication of computability with the 3D TV play then is my tv computabile. (LG 47LX6500) 3d modes Top & Bottom, Side by Side, Checker Board, Single Frame Sequential, Frame Packing and 1.4 HDMI. :unsure:
I've got a GTX 460 card and an ASUS VG236H connected via Dual-Link DVI (and a secondary LG 24 " monitor connected via HDMI). When I installed 260.63, my system (Win 7 64-bit) didn't properly detect my monitors. The LG was listed as a Generic (which was OK), but it detected my ASUS as an "Ancor" (???) model, and neither the 3D Vision Player nor PowerDVD 10 Mark II would recognize that I had a valid 3D display. Any ideas as to why this might happen???? (fyi, rolling back to CD 1.34 put everything back to normal ....)
I've got a GTX 460 card and an ASUS VG236H connected via Dual-Link DVI (and a secondary LG 24 " monitor connected via HDMI). When I installed 260.63, my system (Win 7 64-bit) didn't properly detect my monitors. The LG was listed as a Generic (which was OK), but it detected my ASUS as an "Ancor" (???) model, and neither the 3D Vision Player nor PowerDVD 10 Mark II would recognize that I had a valid 3D display. Any ideas as to why this might happen???? (fyi, rolling back to CD 1.34 put everything back to normal ....)
You can't enable 3d vision until it's true fullscreen[/quote]
Ya I think FFXIV is actually the opposite, where they have a fake fullscreen wrapper to prevent users from Alt-Tabing out of the game. If you Alt-tab in FFXIV it breaks fullscreen and the client gives you a "no D3D device detected" error message.
You can't enable 3d vision until it's true fullscreen
Ya I think FFXIV is actually the opposite, where they have a fake fullscreen wrapper to prevent users from Alt-Tabing out of the game. If you Alt-tab in FFXIV it breaks fullscreen and the client gives you a "no D3D device detected" error message.
-=HeliX=- Mod 3DV Game Fixes
My 3D Vision Games List Ratings
Intel Core i7 5930K @4.5GHz | Gigabyte X99 Gaming 5 | Win10 x64 Pro | Corsair H105
Nvidia GeForce Titan X SLI Hybrid | ROG Swift PG278Q 144Hz + 3D Vision/G-Sync | 32GB Adata DDR4 2666
Intel Samsung 950Pro SSD | Samsung EVO 4x1 RAID 0 |
Yamaha VX-677 A/V Receiver | Polk Audio RM6880 7.1 | LG Blu-Ray
Auzen X-Fi HT HD | Logitech G710/G502/G27 | Corsair Air 540 | EVGA P2-1200W
You can't enable 3d vision until it's true fullscreen[/quote]
Ya I think FFXIV is actually the opposite, where they have a fake fullscreen wrapper to prevent users from Alt-Tabing out of the game. If you Alt-tab in FFXIV it breaks fullscreen and the client gives you a "no D3D device detected" error message.
You can't enable 3d vision until it's true fullscreen
Ya I think FFXIV is actually the opposite, where they have a fake fullscreen wrapper to prevent users from Alt-Tabing out of the game. If you Alt-tab in FFXIV it breaks fullscreen and the client gives you a "no D3D device detected" error message.
-=HeliX=- Mod 3DV Game Fixes
My 3D Vision Games List Ratings
Intel Core i7 5930K @4.5GHz | Gigabyte X99 Gaming 5 | Win10 x64 Pro | Corsair H105
Nvidia GeForce Titan X SLI Hybrid | ROG Swift PG278Q 144Hz + 3D Vision/G-Sync | 32GB Adata DDR4 2666
Intel Samsung 950Pro SSD | Samsung EVO 4x1 RAID 0 |
Yamaha VX-677 A/V Receiver | Polk Audio RM6880 7.1 | LG Blu-Ray
Auzen X-Fi HT HD | Logitech G710/G502/G27 | Corsair Air 540 | EVGA P2-1200W
Run the tool, Choose Export and save it wherever you like, like Desktop.
Open the File with Notepad, should be titled Nvidia Profiles.txt by default
Hit Ctrl-F and search for Mafia, then find Mafia 2's profile
Insert this DX9 AA flag setting anywhere after the executable names: Setting ID_0x00d55f7d = 0x000d02c4
Save the file, then choose Import SLI Profiles and select Nvidia Profiles.txt to re-import the game profile changes.
Every time a new driver comes out, I archive the default profile flags and also save my current version which has any changes I made for better performance or compatibility, this way its very easy for me to compare which flags have changed from driver to driver. So for example I will have Nvidia Profiles 259.32.txt (default) and Nvidia Profiles 259.32a.txt (edited) and the current working copy will be Nvidia Profiles.txt always.[/quote]
Thank you very much, chiz. That is really great information.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.
Run the tool, Choose Export and save it wherever you like, like Desktop.
Open the File with Notepad, should be titled Nvidia Profiles.txt by default
Hit Ctrl-F and search for Mafia, then find Mafia 2's profile
Insert this DX9 AA flag setting anywhere after the executable names: Setting ID_0x00d55f7d = 0x000d02c4
Save the file, then choose Import SLI Profiles and select Nvidia Profiles.txt to re-import the game profile changes.
Every time a new driver comes out, I archive the default profile flags and also save my current version which has any changes I made for better performance or compatibility, this way its very easy for me to compare which flags have changed from driver to driver. So for example I will have Nvidia Profiles 259.32.txt (default) and Nvidia Profiles 259.32a.txt (edited) and the current working copy will be Nvidia Profiles.txt always.
Thank you very much, chiz. That is really great information.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.
Run the tool, Choose Export and save it wherever you like, like Desktop.
Open the File with Notepad, should be titled Nvidia Profiles.txt by default
Hit Ctrl-F and search for Mafia, then find Mafia 2's profile
Insert this DX9 AA flag setting anywhere after the executable names: Setting ID_0x00d55f7d = 0x000d02c4
Save the file, then choose Import SLI Profiles and select Nvidia Profiles.txt to re-import the game profile changes.
Every time a new driver comes out, I archive the default profile flags and also save my current version which has any changes I made for better performance or compatibility, this way its very easy for me to compare which flags have changed from driver to driver. So for example I will have Nvidia Profiles 259.32.txt (default) and Nvidia Profiles 259.32a.txt (edited) and the current working copy will be Nvidia Profiles.txt always.[/quote]
Thank you very much, chiz. That is really great information.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.
Run the tool, Choose Export and save it wherever you like, like Desktop.
Open the File with Notepad, should be titled Nvidia Profiles.txt by default
Hit Ctrl-F and search for Mafia, then find Mafia 2's profile
Insert this DX9 AA flag setting anywhere after the executable names: Setting ID_0x00d55f7d = 0x000d02c4
Save the file, then choose Import SLI Profiles and select Nvidia Profiles.txt to re-import the game profile changes.
Every time a new driver comes out, I archive the default profile flags and also save my current version which has any changes I made for better performance or compatibility, this way its very easy for me to compare which flags have changed from driver to driver. So for example I will have Nvidia Profiles 259.32.txt (default) and Nvidia Profiles 259.32a.txt (edited) and the current working copy will be Nvidia Profiles.txt always.
Thank you very much, chiz. That is really great information.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.[/quote]
Np, glad it helped. :)
Just reverse engineering using accumulated knowledge from the insight nHancer (and coolbits before it) provided us in the past. Previously, nHancer dealt with the setting IDs and then mapped the various hex values to easily toggleable compatiblity check boxes to change the hex flag. You could also do the same with manually editing the Nvapps.xml file, but Nvidia provided the setting names in plain english. With the R256 drivers, Nvidia changed this up on us a bit with the actual Setting ID codes with the hex values. I just compared known hex value compatibility settings from previous drivers in certain titles to figure out which Setting IDs were relevant to the settings I most often needed to change in previous drivers for SLI and AA compatibility. As a result, I've found the following:
[b]For AA: [/b]
[list]
[*]Setting ID_0x00d55f7d = DX9 AA compatibility
[*]Setting ID_0x00e32f8a = DX10/11 AA compatibility
[/list]
[b]For SLI: [/b]
[list]
[*]Setting ID_0x1095def8 = DX9 SLI compatibility
[*]Setting ID_0x00a06946 = DX10/11 SLI compatibility
[/list]
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.
Np, glad it helped. :)
Just reverse engineering using accumulated knowledge from the insight nHancer (and coolbits before it) provided us in the past. Previously, nHancer dealt with the setting IDs and then mapped the various hex values to easily toggleable compatiblity check boxes to change the hex flag. You could also do the same with manually editing the Nvapps.xml file, but Nvidia provided the setting names in plain english. With the R256 drivers, Nvidia changed this up on us a bit with the actual Setting ID codes with the hex values. I just compared known hex value compatibility settings from previous drivers in certain titles to figure out which Setting IDs were relevant to the settings I most often needed to change in previous drivers for SLI and AA compatibility. As a result, I've found the following:
For AA:
For SLI:
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.
-=HeliX=- Mod 3DV Game Fixes
My 3D Vision Games List Ratings
Intel Core i7 5930K @4.5GHz | Gigabyte X99 Gaming 5 | Win10 x64 Pro | Corsair H105
Nvidia GeForce Titan X SLI Hybrid | ROG Swift PG278Q 144Hz + 3D Vision/G-Sync | 32GB Adata DDR4 2666
Intel Samsung 950Pro SSD | Samsung EVO 4x1 RAID 0 |
Yamaha VX-677 A/V Receiver | Polk Audio RM6880 7.1 | LG Blu-Ray
Auzen X-Fi HT HD | Logitech G710/G502/G27 | Corsair Air 540 | EVGA P2-1200W
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.[/quote]
Np, glad it helped. :)
Just reverse engineering using accumulated knowledge from the insight nHancer (and coolbits before it) provided us in the past. Previously, nHancer dealt with the setting IDs and then mapped the various hex values to easily toggleable compatiblity check boxes to change the hex flag. You could also do the same with manually editing the Nvapps.xml file, but Nvidia provided the setting names in plain english. With the R256 drivers, Nvidia changed this up on us a bit with the actual Setting ID codes with the hex values. I just compared known hex value compatibility settings from previous drivers in certain titles to figure out which Setting IDs were relevant to the settings I most often needed to change in previous drivers for SLI and AA compatibility. As a result, I've found the following:
[b]For AA: [/b]
[list]
[*]Setting ID_0x00d55f7d = DX9 AA compatibility
[*]Setting ID_0x00e32f8a = DX10/11 AA compatibility
[/list]
[b]For SLI: [/b]
[list]
[*]Setting ID_0x1095def8 = DX9 SLI compatibility
[*]Setting ID_0x00a06946 = DX10/11 SLI compatibility
[/list]
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.
But how do now what ID must be changed to what value for improvements. The entry names and values all look rather crypted to me.
Np, glad it helped. :)
Just reverse engineering using accumulated knowledge from the insight nHancer (and coolbits before it) provided us in the past. Previously, nHancer dealt with the setting IDs and then mapped the various hex values to easily toggleable compatiblity check boxes to change the hex flag. You could also do the same with manually editing the Nvapps.xml file, but Nvidia provided the setting names in plain english. With the R256 drivers, Nvidia changed this up on us a bit with the actual Setting ID codes with the hex values. I just compared known hex value compatibility settings from previous drivers in certain titles to figure out which Setting IDs were relevant to the settings I most often needed to change in previous drivers for SLI and AA compatibility. As a result, I've found the following:
For AA:
For SLI:
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.
-=HeliX=- Mod 3DV Game Fixes
My 3D Vision Games List Ratings
Intel Core i7 5930K @4.5GHz | Gigabyte X99 Gaming 5 | Win10 x64 Pro | Corsair H105
Nvidia GeForce Titan X SLI Hybrid | ROG Swift PG278Q 144Hz + 3D Vision/G-Sync | 32GB Adata DDR4 2666
Intel Samsung 950Pro SSD | Samsung EVO 4x1 RAID 0 |
Yamaha VX-677 A/V Receiver | Polk Audio RM6880 7.1 | LG Blu-Ray
Auzen X-Fi HT HD | Logitech G710/G502/G27 | Corsair Air 540 | EVGA P2-1200W
nvidia inspector allows you to edit every profile. simply set the aa-behaviour flag for mafia 2 to none.
[url="http://blog.orbmu2k.de/tools/nvidia-inspector-tool"]http://blog.orbmu2k.de/tools/nvidia-inspector-tool[/url]
nvidia inspector allows you to edit every profile. simply set the aa-behaviour flag for mafia 2 to none.
http://blog.orbmu2k.de/tools/nvidia-inspector-tool
NVIDIA TITAN X (Pascal), Intel Core i7-6900K, Win 10 Pro,
ASUS ROG Rampage V Edition 10, G.Skill RipJaws V 4x 8GB DDR4-3200 CL14-14-14-34,
ASUS ROG Swift PG258Q, ASUS ROG Swift PG278Q, Acer Predator XB280HK, BenQ W710ST
nvidia inspector allows you to edit every profile. simply set the aa-behaviour flag for mafia 2 to none.
[url="http://blog.orbmu2k.de/tools/nvidia-inspector-tool"]http://blog.orbmu2k.de/tools/nvidia-inspector-tool[/url]
nvidia inspector allows you to edit every profile. simply set the aa-behaviour flag for mafia 2 to none.
http://blog.orbmu2k.de/tools/nvidia-inspector-tool
NVIDIA TITAN X (Pascal), Intel Core i7-6900K, Win 10 Pro,
ASUS ROG Rampage V Edition 10, G.Skill RipJaws V 4x 8GB DDR4-3200 CL14-14-14-34,
ASUS ROG Swift PG258Q, ASUS ROG Swift PG278Q, Acer Predator XB280HK, BenQ W710ST
[list]
[*]Setting ID_0x00d55f7d = DX9 AA compatibility
[*]Setting ID_0x00e32f8a = DX10/11 AA compatibility
[/list]
[b]For SLI: [/b]
[list]
[*]Setting ID_0x1095def8 = DX9 SLI compatibility
[*]Setting ID_0x00a06946 = DX10/11 SLI compatibility
[/list]
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.[/quote]
Again, many thanks.
I googled a bit and it seems that both nHancer and RivaTuner are outdated and can not be used for editing the settings of 256 or newer drivers, due to the changed profile mechanism. At least the nHancer author has said that he will most probably write a new nHancer version from scratch for the new driver generation (based on Windows Presentation Framework), but has unfortunately currently no time to work on the project.
For SLI:
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.
Again, many thanks.
I googled a bit and it seems that both nHancer and RivaTuner are outdated and can not be used for editing the settings of 256 or newer drivers, due to the changed profile mechanism. At least the nHancer author has said that he will most probably write a new nHancer version from scratch for the new driver generation (based on Windows Presentation Framework), but has unfortunately currently no time to work on the project.
[list]
[*]Setting ID_0x00d55f7d = DX9 AA compatibility
[*]Setting ID_0x00e32f8a = DX10/11 AA compatibility
[/list]
[b]For SLI: [/b]
[list]
[*]Setting ID_0x1095def8 = DX9 SLI compatibility
[*]Setting ID_0x00a06946 = DX10/11 SLI compatibility
[/list]
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.[/quote]
Again, many thanks.
I googled a bit and it seems that both nHancer and RivaTuner are outdated and can not be used for editing the settings of 256 or newer drivers, due to the changed profile mechanism. At least the nHancer author has said that he will most probably write a new nHancer version from scratch for the new driver generation (based on Windows Presentation Framework), but has unfortunately currently no time to work on the project.
For SLI:
Figuring out the hex values themselves is still kind of hit or miss, mainly I stick to known values for other games that have provided similar success especially if they are using the same engine (UE3, Anvil, GameBryo etc), but simply searching through the Nvidia Profiles.txt you can come up with a list of all used compatibility flags. Like UE3 games for instance I tend to use the common AA and SLI compatibility flags that have provided the best results in other games. The nHancer forums and various others still have people who tweak and document this kind of stuff, so generally if you know the setting ID you need to change, you can throw that into google along with the title name to come up with more than a few hex flags to try.
Again, many thanks.
I googled a bit and it seems that both nHancer and RivaTuner are outdated and can not be used for editing the settings of 256 or newer drivers, due to the changed profile mechanism. At least the nHancer author has said that he will most probably write a new nHancer version from scratch for the new driver generation (based on Windows Presentation Framework), but has unfortunately currently no time to work on the project.
Hallo Nvidia enyone there?
Hallo Nvidia enyone there?
Hallo Nvidia enyone there?
Hallo Nvidia enyone there?
I got LG W2363D monitor, and seems there's a little bit more bottom part ghosting, but almost none on top (except usual 'contrast' ghosting).
I got LG W2363D monitor, and seems there's a little bit more bottom part ghosting, but almost none on top (except usual 'contrast' ghosting).
I got LG W2363D monitor, and seems there's a little bit more bottom part ghosting, but almost none on top (except usual 'contrast' ghosting).
I got LG W2363D monitor, and seems there's a little bit more bottom part ghosting, but almost none on top (except usual 'contrast' ghosting).
Thanks!
Thanks!