Hi, followed the guide, but having some issues:

 

First, I use 2 GTX 580 in SLi, and have 2 monitors, a 30 inch and a 19 inch. No probs in DX9 mode, but in DX10, FSX runs on the smaller screen. I cant figure out why. I tried remming out details of the 2nd monitor in the .cfg file but did not help. Here is a link to my .cfg file: http://www.mediafire.com/?l04xbdmmulkru92 ( The widget would not let me upload for some reason....)

 

Second issue: I dont seem to have any AA working ? - Again, followed trhe settings as advised in the giude. I use NVinspector in DX9, so the its presumably starting when FSX runs, as I linked the proflie to the .exe but it seems to make no difference...

 

Thirdly, what about the affinity mask entry in the .cfg file? No mention in the guide..Do we still need this? ( Would have thought so...)

 

Thanks, Mark

Hi, followed the guide, but having some issues:

 

First, I use 2 GTX 580 in SLi, and have 2 monitors, a 30 inch and a 19 inch. No probs in DX9 mode, but in DX10, FSX runs on the smaller screen. I cant figure out why. I tried remming out details of the 2nd monitor in the .cfg file but did not help. Here is a link to my .cfg file: http://www.mediafire...l04xbdmmulkru92 ( The widget would not let me upload for some reason....)

 

Second issue: I dont seem to have any AA working ? - Again, followed trhe settings as advised in the giude. I use NVinspector in DX9, so the its presumably starting when FSX runs, as I linked the proflie to the .exe but it seems to make no difference...

 

Thirdly, what about the affinity mask entry in the .cfg file? No mention in the guide..Do we still need this? ( Would have thought so...)

 

Thanks, Mark

 

Hi Mark,

 

You mentioned that you are running two 580 in SLI and two monitors and the smaller of the two is running FSX. What you have to do first is have matching monitors. By that I mean you have to have two or more montors at the same resolution 1920+1080 / 27 inch for example. You do not need monitors that size, it is up to you what size you want but they have to match. I run 3 - 27inch monitors.

 

In order for this to work you will need Nvidia cards which you have stated.

1. plug the monitors into the back of the cards and through the Nvidia surround sound setup your monitors for SLI and the surround which will then show you which is #1-2-3 etc.

2. If the monitor that shows the task bar that would be the one you would want to click on and drag it to the the center possition.

3. this step would be your bezel correction which aligns the monitors visually so everything will line up when you go to full screen and fly.

4. *NOTE* Nvidia card are the only cards that will let you do this.

I saved $300.00 + doing it this way verses buying TRIPPLEHEAD2GO. I can run FSX @ 5960x1080x32 or 5940x1080x32. Some will say that I still purchased three monitors, thats true, but I would have had do that same thing with the TRIPPLEHEAD2GO. It isn't a difficult thing to do and can be done. I am in hopes this will get you going in the right direction as I had done exactly the same thing you are trying right now in running more than one monitor. Take a look at my computer specs on the left. I now run PMDG aircraft @ 25fps to 29.8 fps and in DX10.

Les

Hey Mark! So you're giving it a shot, eh? :good:

 

I use 2 GTX 580 in SLi, and have 2 monitors, a 30 inch and a 19 inch. No probs in DX9 mode, but in DX10, FSX runs on the smaller screen. I cant figure out why. I tried remming out details of the 2nd monitor in the .cfg file but did not help. Here is a link to my .cfg file:http://www.mediafire...l04xbdmmulkru92 ( The widget would not let me upload for some reason....)

Second issue: I dont seem to have any AA working ? - but it seems to make no difference...

Thirdly, what about the affinity mask entry in the .cfg file? No mention in the guide..

 

These two :

#[DISPLAY.Device.NVIDIA GeForce GTX 580.1] // DX9

#Mode=1440x900x32

 

[DISPLAY.Device.NVIDIA GeForce GTX 580.0] // DX9

Mode=2560x1600x32

TriLinear=1

AntiAlias=1

 

are your DX9 cards, Mark, and these two :

 

 

[DISPLAY.Device.NVIDIA GeForce GTX 580.0.0] // DX10

Mode=2560x1600x32

TriLinear=1

AntiAlias=1

 

[DISPLAY.Device.NVIDIA GeForce GTX 580.0.1] // DX10

Mode=1280x800x32

 

Are used with DX10, which (as the last entry - the small monitor - has no setting) might explain why the lack of AA.

 

As far as the ignored Affinity Mask - I must confess to not using it anymore, Mark, remaining unconvinced of it's benefit, and rather allowing FSX SP2 to manage it's core choices itself. I do, however inhibit core parking, as it is known as a cause of microstuttering, though perhaps more of a DX9 issue than 10.

 

Apart from that - I don't see a lot too wrong with the cfg, but it's a mid-range system, and it's a "first-time" run at DX10, and so my notes below are made with that consideration and maybe a bit conservative. One can always move any particular one upwards once a stable environment is achieved. FSX - DX10 does respond differently to FSX-DX9.

 

Soooo....

 

1). You might lower (to 4) the two AA entries in the Graphics section for performance...

2). TBM would be better at 80.

3). The Cloud settings are a bit high - Distance ought be no more than 3, with Density about 7

4). Image Complexity and Autogen can be 5 and 4.

5). All else looks good to go!

 

Try these suggestions, and let us know how you make out.

 

All the Best, :wink:

Hi guys, sorry,, I may have confused you regarding the two monitors. I don't run FSX on the 2 monitors, the second monitor is purely there for use in falcon4, where I oputput cockpit gauges to it. So I just want FSX to output only to my 30 inch screen. Which it does no problem in DX9 mode. Oh, and I don't use autogen, as I run photoscenery and think it spoils it.

 

Paul, why are there lines relating to DX9 in the config file, if this is a new file, purely set up for DX10 as per your guide? These lines only appeared after I saved the settings in the FSX GUI, they were not there when the file was first generated. What does that mean do you think?

 

Would it be useful to see my DX9 .cfg file for comparison? And what settings do you recommend for nvidia inspector ?

 

Rgds, Mark

No - no need to see the DX9 cfg - I have no problem in comprehending your difficulty, Mark.

 

Among one or two other "extras", FSX will write the GPU device info into the cfg for any gpu it finds, depending upon the DirectX version, Mark. Your DX9 and DX10 entries are below, and are written when that mode is used, DirectX 9 using different functionality to that employed by DX10: the technology is different, as DX9 to DX10 to DX11. All new GPU's are compatible with those technologies.

 

 

My thoughts would be to edit the cfg like this, and then start FSX :-

 

 

#[DISPLAY.Device.NVIDIA GeForce GTX 580.1] // DX9 <---- uncomment these lines, and ignore them

#Mode=1440x900x32

 

[DISPLAY.Device.NVIDIA GeForce GTX 580.0] // DX9 <----- ignore, also - these only apply to DX9

Mode=2560x1600x32

TriLinear=1

AntiAlias=1

 

 

[DISPLAY.Device.NVIDIA GeForce GTX 580.0.0] // DX10 <-------- modify this line, so that it's the #1 device

Mode=2560x1600x32

TriLinear=1

AntiAlias=1

 

[DISPLAY.Device.NVIDIA GeForce GTX 580.0.1] // DX10 <------- by exchanging these two numbers (0 and 1)

Mode=1280x800x32

 

...so they look like this:-

 

 

[DISPLAY.Device.NVIDIA GeForce GTX 580.0.1] // DX10 <-------- Now this is the #1 device

Mode=2560x1600x32

TriLinear=1 <---------------------- make this Anisotropic for DX10

AntiAlias=1

 

[DISPLAY.Device.NVIDIA GeForce GTX 580.0.0] // DX10 <------- ...and this is the #0 device

Mode=1280x800x32

 

Try this - if it works - fine - if not, then it may be that it needs to be set in the Nvidia Control Panel, in the Multi-Display.

Lastly - if this doesn't fix it - or no-one else jumps in with the right - or a better answer - post over in the Video Card forum, where there are more knowledgeable folks. Also - just a thought - you might try googling the various wideview forums if it doesn't get fixed by someone here.

 

Keep in touch,

 

All the Best,

Hi Paul, thanks for the advice, will try shortly and let you know. I am just wondering why / how the .cfg file got written to with DX9 versions as well, as it was a new file created the first time I ran FSX in DX10 mode.... weird..

 

Finally one point, ( to make sure I have this correct) in the guide, you say select Trilinear flitering and make sure AntiAliasing box is ticked within FSX when first setting up. But above, you say change the Trilinear entry to Anisotropic. Why is this? Would you just not select Anisotropic in the FSX GUI instead of Tri linear? And which is correct? Sorry, I am confused..!!

TriLinear for DX9 - this will allow you to force AF using Inspector, but AF and AA inside FSX when using DX10, with "Application-controlled" as the filtering mode. I made a somewhat ambiguous mistake in the doc, as either way will work with some experimenting, and dependent upon the system and other settings, but to start a first-time setup - you're right - so I have to thank you! It is changed, even as we speak... so to speak.. B)

Hey Paul, monitor issue solved, by swapping the 0 & 1 as suggested - Thanks! So, I have it running, its pretty good, but I have to say, not as smooth and reliably pegged at 30 FPS as my DX9 set up, with the same settings for scenery etc. Where I am getting a solid 30 FPS in DX9, over LAX, with REX clouds @1024 and no traffic, DX9 pegged at 30, smooth as silk, DX10 fluctuating between 25 & 30....What do you think the best place to look for the culprit is?

 

When fiddling with DX10 before, I was always able to get awesome frames, up in the 70's regularly before, certainly almost double the comparable FPS in DX9, but that was on a previous install, this one is fresh. So I know the performance is there somewhere..!

 

rgds,Mark

Well, I found that the two that made the most difference, Mark, were the BufferPool setting - size and RT, Inspector (minimum of 4xSGSS, though), the TBM - start at 60 and work up by 5's, the multisamplesperpixel and it's mate, but start off with a moderate slider Complexity and AG sliders - the others can mostly be to the full right - actually, when I did the testing to get this "ProcSpeed=20448" reading in the fdsx.cfg, these wee the settings I used - or ended up with, for literally hundreds and hundreds of repetitive circuits around the downtown core of Jon Patch's Vancouver Plus. The result was 29.9 everywhere. Read the doc, and pay attention to all pieces of it, whether killing background processes, or adding alpha textures. Read particularly Phil Taylor's blog (at the beginning of the doc) as he gives some insight as to the changes which DX10 brings vs DX9: DX10 will also respond differently to the various cfg (et al), settings, as it manages memory and graphics quite a bit differently to DX9, and hence able to carry a heavier load for the same frame rate - and this becomes noticeable as your tweaking progresses. Takes a while!

Hey Paul, wonder if you can help out with this problem. I am still tweaking, and wanted to make a new dx9 .cfg base file, to work with for comparison. I have 2 FSX folders in my app data folder, one DX9 & one DX10, as you suggested.

 

I swapped back in my DX9 folder and renamed my DX9 .cfg file so FSX would bulld another one. However, when I load a flight, on getting into the cockpit, I get graphics artifacts, black screen and then a BSOD.

 

Any ideas? I am thinking its related to the shaders, but not sure how to revert to DX9 version of set up.......

 

Cheers, Mark

Hi Mark;

 

I think the answer is probably that you didn't delete the Shaders and Shaders10 folders within the

C:\Users\{Mark}\AppData\Local\Microsoft\FSX\ folder. This will result in the current FSX system talking to an "different" set of cache folders., Just delete them and restart the sim - ok!

 

:smile:

Hi Paul, even though I have two FSX folders within the sub directory, one I use for DX10 and one for DX9? I had swapped in the DX9 file....so FSX should not have been looking at anything DX10 related.......

 

I had back up files of my FSX app data folder and my shaders folder, and have restored them both, yet everytime I run FSX in DX9 now it blue screens.must be another file somewhere else affected....

Yes - but the Shaders and Shaders10 folders are cache's of the actual "in-use" hlsl output that the gpu will use, and if there's any difference between in main ShadersHLSL folder and those cache folders , before/after - the sim will bomb. Always best to delete both cache folders. FSX will rebuild them without issue, as it starts.