SLI is not supposed to work in FSX but using Nvidia Inspector I seem to have all my cards working according to MSI Afterburner readings. I am sure you could force all cards to work in PD3 as well. 

 

 

SLI is not supposed to work in FSX but using Nvidia Inspector

 

Run time frame analysis (Fraps logging) with frames unlocked and no Vsync with and without SLI enabled ... that will tell you if SLI is really working in FSX.  The ONLY time I could get SLI to work under FSX is Cockpit view (no VC).

 

SLI is officially support for P3D by nVidia, it's officially supported for FSX ... key distinction (I'm not aware of nVidia doing any profiles for FSX or FSX-SE).  Like I posted originally in this thread I'm seeing about 33% increase overall at 4K res and dense clouds no longer reduce FPS as much even with very high AA settings.  Your mileage will vary.

 

I haven't tried the latest drivers 353.62 ... if you want to get a close (but not exact) compare with FSX or FSX-SE, you need to disable these in P3D:

 

1.  Volumetric Fog (3 pass render)

2.  Cloud Shadows (and maybe a few other shadow settings, SimObjects, NO flag content)

3.  Tessellation

4.  HDR

5.  Water = Medium

 

That'll get you close to FSX/FSX-SE ... in this scenario I'm seeing significant FPS and VAS gains in P3D over FSX/FSX-SE (single GPU).   And more to come in the future as LM keep developing P3D.

 

Cheers, Rob.

Before I tried Nvidia Inspector I could not see any difference in using one or all three cards. Even Afterburner showed one dominant card and two weak ones that were mostly at idle. 

 

Now with the correct settings in Inspector I have seen a difference in smoothness with all three cards running and in Afterburner all three cards are hitting 1345mhz at times such as heavy clouds or stormy weather over large cities. 

 

Nividia does have a profile for FSX sli and it is Force Predefined Mode AFR2. 

 

I wish PD3 would have run better for me as I like the idea of having  progressive software but until I can see a difference I will stick with FSX. Now when they come out with version v3 or whatever is next I will for sure try it again.

 

I wish PD3 would have run better for me as I like the idea of having  progressive software but until I can see a difference I will stick with FSX.

 

Shame you aren't able to realize the difference, many others using similar hardware seem to have much better success than you, might want to check in with those folks and see how they are accomplishing it.

 

I see you have several threads in the P3D forum indicating your desire to run FSX over P3D because of performance issues ... I'm sure someone can give you some insight on how to get the most out of your setup for P3D.

 

Cheers, Rob.

Hi Rob !

 

Are you using these Inspector settings together with the 2.5 settings on your website ?

I try using 2.5 settings as some kind of reference point.

 

BR

 

Bigsweede

 

 

My settings are pretty close to MJ's:

 

 

This DID cure artifacts, but it does have a tendency to drop FPS/stutter here and there and it has my GPU's running at 99% mid dense clouds.

 

Someone needs to do a compare without SLI to see if these settings with SLI is actually a performance benefit.  Fraps time frames.

 

EDIT: these settings do seem to make my menu font's look odd ... it looks to me like AA is being processed against the menu text also, which is not desirable.  But, since the menu is rarely active during most of my flight it's a very minor sacrifice since the render issues are resolved.

 

Cheers, Rob.

 

 

Are you using these Inspector settings together with the 2.5 settings on your website ?

 

For my day to day flights, no.  For screenshots only I use NI to get SGSS AA.  The settings in that link are for SLI with NO artifacts ... but be aware those settings can introduce stutters in some situations.

 

My light weight aircraft daily settings are these (maybe some minor changes here and there but basically the same): http://www.robainscough.com/P3D_Titan_X_4K_Set.html

 

For heavy weight aircraft (close to this): http://www.robainscough.com/P3D_4K_Long_Haul.html

 

This is with a full suite of add-ons:

ASN

GSX

Complex airports

ProATCX

Orbx Region/Global

REX

 

Cheers, Rob.

Just a quick question about the latest nVidia driver. Is ist correct that most effects like lightning or rotorwash arent working and the SLI will loose focus when entering the menu. I do have still these bugs so im wondering if anyone else encounter them.

 

Thanks....

Mickey - yes - some people still get them even with the new drivers. Fortunately, I don't see them.

 

Vic

Hello everyone, quick question.  Is anyone still getting the "Display driver nvlddmkm stopped responding and has successfully recovered." error?  I saw it mentioned back on page 5 or 6 by Rob and not much since.  I just did a clean install on my computer with the latest build of Win10 Pro x64, P3D w/hotfix 4, and nVIDIA's 353.62 driver and I can't even get off the ground before the error occurs.  

 

I'm running the following:

-i7-4790K @4.4

-2x 980 Hybrids in SLI

-16GB RAM @1600

 

So far I've tried to do numerous flights in the NGX/777/AirbusX products at various payware airports to no avail.  I've run through the various NI profiles listed throughout this thread to see if they would help, but I can't even get through an abbreviated pre-flight before the screen goes dark and I get the error message on screen.  I haven't tried running P3D on a single card yet, saving that for tomorrow as I need to hit the sack.  I'd appreciate any feedback/suggestions you guys might have!  

 

Josh

Mickey - yes - some people still get them even with the new drivers. Fortunately, I don't see them.

 

Vic

 

Thanks Vic,

 

do you still run your NI profile?

 

Hello everyone, quick question.  Is anyone still getting the "Display driver nvlddmkm stopped responding and has successfully recovered." error?  I saw it mentioned back on page 5 or 6 by Rob and not much since.  I just did a clean install on my computer with the latest build of Win10 Pro x64, P3D w/hotfix 4, and nVIDIA's 353.62 driver and I can't even get off the ground before the error occurs.  

 

I'm running the following:

-i7-4790K @4.4

-2x 980 Hybrids in SLI

-16GB RAM @1600

 

So far I've tried to do numerous flights in the NGX/777/AirbusX products at various payware airports to no avail.  I've run through the various NI profiles listed throughout this thread to see if they would help, but I can't even get through an abbreviated pre-flight before the screen goes dark and I get the error message on screen.  I haven't tried running P3D on a single card yet, saving that for tomorrow as I need to hit the sack.  I'd appreciate any feedback/suggestions you guys might have!  

 

Josh

 

Hi Josh,

 

cant help you out here dont have Win10 and i will pass for now. I dont trust the new OS.

 

 

Is anyone still getting the "Display driver nvlddmkm stopped responding and has successfully recovered." error?  I saw it mentioned back on page 5 or 6 by Rob and not much since.

 

Is this a different Rob?  I didn't mention anything about "nvlddmkm" errors?  I'm not getting those errors ... have you tried going the latest DDU route and boot to safe mode - removes existing drivers completely, then install new nVidia drivers?

 

The only other time I've seen "nvlddmkm" errors (not on my systems) is when the wrong chipset driver was installed and/or people changing .inf files.

 

Cheers, Rob.

Thanks Vic, interesting when I selected this I got an nvlddmkm stopped responding, kernel error.  It recovered but that's something new for me.

 

Cheers, Rob.

This was the post I was referring to Rob, if you weren't referencing your system I apologize for making the wrong assumption.  

 

I experimented for some time and was about to try your suggestion, but then I came across this thread: http://www.avsim.com/topic/470158-does-sli-users-have-seen-less-visual-artefacts-with-35306-nvidia-drivers/page-2.  I applied Vic's recommendations and so far the issue seems to be fixed, thanks Vic!

 

I did notice that prior to applying Vic's settings I was having anywhere from a 50-200MHz core clock difference at times between my two gpus while P3D was running.  Nothing else looked out of place in PrecisionX, but now with the new settings both cards are in sync all the time and I haven't had a driver crash yet.  I've stuck with Win10/latest nVidia drivers and so far I haven't come across any artifacts nor do the gpus get out of sync if I click on the menu bar while flying.  As I'm still pretty new to all of this (SLI) I'd like to try and figure out what in those settings made it work with my setup.

 

I'll keep reinstalling all of my addons and report back if that changes in future flights.  Very impressed with the performance so far, definitely pleased with my new setup!  Appreciate the input!

 

Josh       

This was the post I was referring to Rob, if you weren't referencing your system I apologize for making the wrong assumption.  

 

Hi Josh,

 

Oh I see ... that was me experimenting with someone else's NI settings (not mine) that caused the nvlddmkm errors.  But typically I don't use NI, but no doubt NI has cured issues so it's good to see the experimentation and sharing of information ... glad Vic's settings are working for you.

 

I know I probably sound like a broken record, but more good stuff to come around SLI fixes from the LM crew ... 

 

Cheers, Rob.

I am back in the SLI camp with the install of a second 980 Ti and the results, so far, pretty much mirrors my earlier tests with two 980's. I do get more FPS but not a massive jump. What I do have is a much smoother experience especially when under load with heavy clouds. I'm curious about using NI though.

 

Rob,

 

You mentioned you don't use NI. Is there any reason why? Do you modify any global settings in the NVidia control panel?

 

To those that do use NI, do you notice a difference in performance either way?

 

 

You mentioned you don't use NI. Is there any reason why?

 

I use NI for testing out settings, but for my daily flying I restore to default profile and the only change I make is set the Power management mode = "Prefer maximum performance" ... but keep in mind I'm running 4K resolution so my need for high levels of AA are less.

 

Cheers, Rob.