Luthier-Will SLI be fixed in the patch?

The problem we have with SLI is that Luthier believes it isn't broken, if it stays this way then it will never get fixed. The last word from Luthier on SLI was that Nvidia's next driver release would have a profile for CLOD in it, there have been at least 5 driver release since with no mention of CLOD. Luthier's track record with SLI is somewhat shady, I asked in 2009 if CLOD would support SLI, after many avoided posts Luthier finally answered and said ;why wouldn't it work' he then went on to say that he would talk no more about SLI.

Then on release he blamed the 'Epilepsy filter' for killing SLI, but when it was removed SLI still didn't work.... strange that. Since then Luthier claims that SLI as been fixed but now it's Nvidia's fault for not releasing a driver to support it. We know that Luthier would never tell us any pork pies he has stressed this on many occasions, so I guess he's just been unlucky with this particular problem in that other comapanies like Ubisoft with the epilepsy filter and Nvidia with no driver support effect the perfectly good code of Luthiers game.

[Wolf_Rider]

There's more of a problem with nVidia and whether or not SLI is working (which, why bother as stutter is an inherent faultwith SLI)... the bigger bug is How any game with a "Launcher.exe" as the name of the exe gets picked up as another game.
The driver doesn't differentiate by path, it just assumes that any "Launcher.exe" which triggers is the game it has listed in profiles.

Originally Posted by Wolf_Rider

There's more of a problem with nVidia and whether or not SLI is working (which, why bother as stutter is an inherent faultwith SLI)... the bigger bug is How any game with a "Launcher.exe" as the name of the exe gets picked up as another game.
The driver doesn't differentiate by path, it just assumes that any "Launcher.exe" which triggers is the game it has listed in profiles.

Yes I do believe you are right with the launcher.exe issue Wolf, Its a school boy error by the Dev's IMHO.

[Flanker35M]

S!

CrossFire or SLI still have problems in many games no matter brand. Really strange this support has not been more widespread as even so long back as Voodoo II I used 2 cards and it worked out of the box, for example in EAW and Jane's WW2 Fighters Since then been sticking to single card configuration as has less hassle and problems with good performance.

[RickRuski]

Luthier has said just after the release of CoD that Sli had been broken and they were working to fix it. So far there has been nothing from the development team to say that it has been fixed so I'm sticking with my own work around. That was nearly 12 months ago, guess we won't see any thing happen until the release of BoM. Very frustrating.

[Wolf_Rider]

Originally Posted by Tree_UK

Yes I do believe you are right with the launcher.exe issue Wolf, Its a school boy error by the Dev's IMHO.

perhaps a naivity on the various developers' part, in having file names entitled the same, but is more a childish balls up by nVidia in not having a profile system which doesn't follow the path to the required program's exe, when adding a custom profile

[r0bc]

Originally Posted by Wolf_Rider

is more a childish balls up by nVidia in not having a profile system which doesn't follow the path to the required program's exe

That's not true, Nvidia won't support it until the bugs are fixed

Originally Posted by senseispcc

For what I can judge the SLI for two GeForce gfx580 1.5go ddr5 works without any problem.

You can force it but its never worked properly

[Thee_oddball]

That should be possible.

According to the nVidia docs, you can query this via NVCPL.DLL (liked to documentation).

The call to be used is NvCplGetDataInt() (page 67), with the argument NVCPL_API_NUMBER_OF_SLI_GPUS or NVCPL_API_SLI_MULTI_GPU_RENDERING_MODE you should obtain the information required.

In oder to access this information, you'll need P/Invoke. If it is OK to statistically link NVCPL.DLL you just have to create the correct import (static external method) and you're fine. Otherwise, you can also choose the LoadLibrary and GetEntryPoint way and use the Marshal class to create an instance of a delegate (declared with the correct arguments) which represents the function to be called.

Edit: The following snippet may get you started (I don't have a nVidia card though, so that's completely untested and on your own risk ):

public const int NVCPL_API_NUMBER_OF_GPUS =7;    // Graphics card number of GPUs. 
public const int NVCPL_API_NUMBER_OF_SLI_GPUS = 8;    // Graphics card number of SLI GPU clusters available. 
public const int NVCPL_API_SLI_MULTI_GPU_RENDERING_MODE = 9;    // Get/Set SLI multi-GPU redering mode.  

[DllImport("NVCPL.DLL", CallingConvention=CallingConvention.Cdecl)]
public static extern bool nvCplGetDataInt([In] int lFlag, [Out] out int plInfo);

public static void Main()       {
        int sliGpuCount;
        if (nvCplGetDataInt(NVCPL_API_NUMBER_OF_SLI_GPUS, out sliGpuCount)) {
                // we got the result
                Console.WriteLine(string.Format("SLI GPU present: {0}", sliGpuCount));
        } else {
                // something did go wrong
                Console.WriteLine("Failed to query NV data");
        }
}

source: http://stackoverflow.com/questions/1...mode-is-active