Originally Posted by EfemaN
Essentially, I was in a hurry and the "devs and" portion of it was a mistake; I know it's implemented by Nvidia and through drivers. Another solid write-up though.
EDIT: Though it makes me wonder... I don't know how the profiles actually work, what they account for, etc. I know they vary from game to game, so does it come down to the devs sending some specific information to Nvidia? Does Nvidia just take a copy of the game, analyze it, and spit out the profile?
Thanks, and it's all good
RE: the 2nd question, that is an interesting one for which I have no answer, only guesses.
I do know lots of games are developed with nVidia's assistance, so I'm sure in these cases they know a lot about the game code already. In cases where they aren't part of the dev process I'd imagine they would indeed request various info from the devs and leverage that info to give them a logical starting point for their testing.
I'd also guess that all games based on the same game engine like Unreal probably utilize very similar profile content to one another.
Ultimately though I'd bet that taking a copy of the game and testing it using various profile settings to see what works best would be part of the process in every case.
Here's a screenie from nV Inspector which exposes a good deal more of the 'stuff' that is actually stored in a 'gaming profile' aside from the subset of settings that you can actually play around with in NVCP.
At the top in the green bar you can see the names of all the .exe's for which the '3dMark11' profile will be applied when they are run.
You can see that there's a couple SLI-related fields in the top section (Compatibility Bits), as well as a 'dedicated' SLI section a little ways down. That collection of settings is what makes up the 'SLI Profile' portion of the Gaming Profile (and there may well be others that aren't exposed through the nVInspector interface, not 100% on that).
Also here's perhaps some of the 'proof' that FD was asking about earlier, here's a screenie of NVCP from the previous driver set, the 266.30. Note how there is no profile in the dropdown for 3dMark11 at all?
Well, it's very easy to confirm that if you install these drivers, SLI will NOT work on 3dMark11, whereas SLI works perfect on the 266.58 drivers. This is due to the presence of a properly configured gaming profile (and it's subset, the SLI Profile) for 3dMark11, which points at the proper .exe, all of which I pointed out in the first screenshot
Edited by brettjv - 4/10/11 at 6:02pm