Sign in to follow this  
riccardo74

Proper Nvidia Inspector settings wiht DX10 fixer?

Recommended Posts

Hi guys, please could be someone so kind to help me on proper setting of NI for use with DX10 Fixer? I've reinstalled FSX from scratch and gone a bit missed.

 

1) which are the basic setting in NI?

 

2) the latest version of fixer? I downloaded now from FSStore, suppose is the last.

 

3) in FSX: AA on and AF on trilinear?

 

4) setting FXAA on NI what means, does it improve graphics or performance?

 

5) do you use bloom? do you find it reduce performance?

 

Many many thanks

  • Upvote 1

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

I recommend to study the "How-To" thread and also look around at the forum. There are many, many samples to find.

Spirit

Share this post


Link to post

I recommend to study the "How-To" thread and also look around at the forum. There are many, many samples to find.

Spirit

Thanks Spirit, I know that guide, I was referring to how specifically setting up NI with DX10 Fixer, not with Shader Fixer.

 

So the NI settings is the same?

Share this post


Link to post

I'll take a screeshot of mine when I arrive home tonight and will post it here.

Share this post


Link to post

Am I the only one not using Nvidia Inspector?

 

I have it installed but find settings are fine as they are without tweaking.

 

I've tried various tweaks suggested here and elsewhere but always end up going back to a "vanilla" setup which improves performance and FPS.

 

Just wondering!

Share this post


Link to post

On my rig it makes a difference, undoubtedly!

Share this post


Link to post

Here is a "normal" Inspector setting, Riccardo. All of these settings apply to FSX when using DX10 - whether the shader patches or using the retail DX10 Fixer. 

 

Nov_19.jpg

 

1). The first setting is under "Compatibility", at the very top:-

"AntiAliasing compatibility (DX1x)" .........set this to "BioShock". (Courtesy of "VeryBumpy")

This will fix the AA for aircraft shadows on the ground.

 

2). AntiAliasing - Behavior Flags - "None", as AA is controlled from FSX.

 

3). AntiAliasing - Mode - "Application-controlled" - because Inspector cannot force AA with FSX DX10. AA must be ticked in the FSX "Settings" facility.

 

4). AntiAliasing - Setting - "Application-controlled/Off".  Same reason.

 

5). AntiAliasing - TransparencySuperSampling - "4x SGSS" (in this case) to control shimmering in water  and trees, etc. This number should be the same as the MultiSamplesPerPixel, as set by the DX10 Fixer entry in the FSX.cfg, under [Graphics]  Usually set to 2x, 4x or 8x (8x is a big load on the system)

 

6). Nvidia Pre-defined FXAA Usage - "Allowed". (if you wish) This will clean up the spinning aircraft jaggies, and will add some post-processing AA.

 

7). Toggle FXAA On/Off - "Off" (in this case) I don't care whether the spinning aircraft has jaggies or not.

 

8). Anisotropic Filtering Mode - "Application-controlled" - set in FSX's Settings

 

9). Anisotropic Filtering setting - "16x" - for good non-blurry lines, edges as the objects recede. Study a yellow taxi line with this on and off, to see the result.

 

10). LOD Bias - Set to "-1.0000", re this doc. to compensate for blurring caused by SGSS.

 

11). Texture Filtering - Negative LOD Bias - Set to "Allow" so that 10). above can work.

 

12). The next three are fairly self-explanatory.

 

13) and 14). These two are required for fullscreen Vsync control, and will need "DisablePreLoad=1" in the fsx.cfg (under [Main]), and "30" fps being set as the UpperFrameLimit under [Display]

 

OK!

  • Upvote 4

Share this post


Link to post

Here is a "normal" Inspector setting, Riccardo. All of these settings apply to FSX when using DX10 - whether the shader patches or using the retail DX10 Fixer.

 

Posted Image

 

1). The first setting is under "Compatibility", at the very top:-

"AntiAliasing compatibility (DX1x)" .........set this to "BioShock". (Courtesy of "VeryBumpy")

This will fix the AA for aircraft shadows on the ground.

 

2). AntiAliasing - Behavior Flags - "None", as AA is controlled from FSX.

 

3). AntiAliasing - Mode - "Application-controlled" - because Inspector cannot force AA with FSX DX10. AA must be ticked in the FSX "Settings" facility.

 

4). AntiAliasing - Setting - "Application-controlled/Off". Same reason.

 

5). AntiAliasing - TransparencySuperSampling - "4x SGSS" (in this case) to control shimmering in water and trees, etc. This number should be the same as the MultiSamplesPerPixel, as set by the DX10 Fixer entry in the FSX.cfg, under [Graphics] Usually set to 2x, 4x or 8x (8x is a big load on the system)

 

6). Nvidia Pre-defined FXAA Usage - "Allowed". (if you wish) This will clean up the spinning aircraft jaggies, and will add some post-processing AA.

 

7). Toggle FXAA On/Off - "Off" (in this case) I don't care whether the spinning aircraft has jaggies or not.

 

8). Anisotropic Filtering Mode - "Application-controlled" - set in FSX's Settings

 

9). Anisotropic Filtering setting - "16x" - for good non-blurry lines, edges as the objects recede. Study a yellow taxi line with this on and off, to see the result.

 

10). LOD Bias - Set to "-1.0000", re this doc. to compensate for blurring caused by SGSS.

 

11). Texture Filtering - Negative LOD Bias - Set to "Allow" so that 10). above can work.

 

12). The next three are fairly self-explanatory.

 

13) and 14). These two are required for fullscreen Vsync control, and will need "DisablePreLoad=1" in the fsx.cfg (under [Main]), and "30" fps being set as the UpperFrameLimit under [Display]

 

OK!

Thank you very much Paul, it's very kind of you.

Share this post


Link to post

Thanks Paul!!  I thought I'd read somewhere about not using a LOD bias (don't remember what it was in relation to now but I thought something with DX10) so I've had it on clamp.  However as you mention while SGSS is great at transparency AA and stopping the cockpit shimmers, it also makes things a bit fuzzy.  Thankfully not NEARLY as bad as DX9 though for whatever reason. I'll definitely be testing with LOD bias on now.

 

I used to run SweetFX with the lumasharpen effect on to counteract the fuzzy, but that was in DX9 and it would randomly kill FSX on me. I never bothered to set it up and re-tweak for DX10 because I found my settings file reacted differently in DX10 with much stronger contrast etc. from the curves effect and some others.

Share this post


Link to post

I wonder if Vsyc works at all when working across 3 monitors.    Even with Half-Refresh and FPS locked at 30fps I get tears, especially when panning up quickly.   I have tried everything.  Maybe I have mistyped something but it is making the process of doing videos daunting as I can't eliminate the tears.

Share this post


Link to post

 

 

I wonder if Vsyc works at all when working across 3 monitors. 
- Yup, it do, Kuragi, but saying that - I'm assuming you're talking about FSX (and Windows) seeing the three monitors as one single wide monitor, as with the Matrox TH2Go system, or Nvidia's Surround system - right? 

 

Many times people use two plus one, or some other such configuration, and have lots of problems - some fixable, some not.

Share this post


Link to post

- Yup, it do, Kuragi, but saying that - I'm assuming you're talking about FSX (and Windows) seeing the three monitors as one single wide monitor, as with the Matrox TH2Go system, or Nvidia's Surround system - right? 

 

Many times people use two plus one, or some other such configuration, and have lots of problems - some fixable, some not.

 

 

Yeah.  It's configured in 3 screen as 1 mode.   All my 3rd party add-ons that have displays and stuff run on my laptop next to my PC via SimConnect and WideFS such as Aivlasoft's EFB so I don't need or want to fly in windowed mode.    My frames are smooth for the most part just can't seem to rid myself of tearing.

Share this post


Link to post

Hmmm good stuff! Well, Kuragi, here's an Inspector example that works - just copy the bottom two lines, set "30" in your FSX settings or [Display]Upper_FrameRate_Limit, and put "DisablePreLoad=1" under [Main].

 

This will give you Vsync in FullScreen.

 

C'mon back if it doesn't!

 

pj

Share this post


Link to post

Hmmm good stuff! Well, Kuragi, here's an Inspector example that works - just copy the bottom two lines, set "30" in your FSX settings or [Display]Upper_FrameRate_Limit, and put "DisablePreLoad=1" under [Main].

 

This will give you Vsync in FullScreen.

 

C'mon back if it doesn't!

 

pj

 

And of course the ForceVsync line as well?     4xSGSS.... T_T    If only that setting didn't utterly absolutely destroy my frame rate whenever a cloud appears on the screen.     I use 1024 clouds and weather I am at 60 miles or my preferred 100 miles draw distance, clouds murder me if I turn on SGSS.  With it off, smooth as glass but a get a few shimmering pixels here and there in the cockpit.

Share this post


Link to post
And of course the ForceVsync line as well?  

No. 

ForceWindowedVsync=1  <<<<<<   This one is the only one which should be used inside the fsx.cfg, It makes FSX manage it's Vsync when in the windowed mode. When using fullscreen it is better to let the GPU driver do it.

 

Did you try 2x SGSS?

Share this post


Link to post

No. 

ForceWindowedVsync=1  <<<<<<   This one is the only one which should be used inside the fsx.cfg, It makes FSX manage it's Vsync when in the windowed mode. When using fullscreen it is better to let the GPU driver do it.

 

Did you try 2x SGSS?

 

Hey Paul, thanks for the help.    The tearing stopped when I disabled the Forcing in the CFG file.  The flight out of KSFO was beautiful... right up until the point I was turning left and the game crashed with a MSVCR80.dll fault... which is new.   I have never had that one stop my game before.    I changed the SGSS to 2x but left AA to 4x in DX 10 Fixer.    Could that seriously have caused this new sudden crash?   I just.. wanna...  cry....   every time I fix something, something else breaks.   Apparently you a Masters Degree in order to fly FSX for any extended period of time..  :(

Share this post


Link to post

Hmmmph.

 

Nope.

 

Good and Bad, right!  What aircraft were you flying?

Share this post


Link to post

Hmmmph.

 

Nope.

 

Good and Bad, right!  What aircraft were you flying?

 

PMDG 737 NGX.     I set everything to 2x and redid the flight on VatSIM today and no crash.    Such a fickle beast.

Share this post


Link to post

I just wondered.... I had the F1/Coolsky DC-9, and the install became a nightmare because of that dll. I actually had to download and re-install a new one. sfc /scannow didn't fix it: neither did chkdsk , but the DC-9 relied on that file as part of it's security setup.

 

I wouldn't say it's fickle, though, Kuragi.... if that were true there wouldn't be guys on the forums that never have pc problems - hardware, software or even FSX, and there are lots of them around.

 

Anyway - glad you had at least one flight that went the right way!

 

All the Best,

 

pj

Share this post


Link to post

..well guys, I had the same error yesterday on a flight from kjfk to ksea with the 321 ext. , and when I selected the star..crash!

But I don't think that is a problem of the nvidia setting..

We'll see today...same flight!

Share this post


Link to post

I am soooo confused on the NI settings.  No matter what I do, there seems to be no changes in FSX.  I set my computer back to factory default, reinstalled FSX Acc, EZDOK, and DX10SceneryFixer.  Then I searched through all the threads looking for different NI settings, and, I think I've tried five or six, and nothing seems to make a difference. 

 

So, what is NI supposed to do?  The below are my specs.

 

Windows 8

i7-3770K CPU @ 3.50GHz

GTX 660

Driver version:  331.82

 

FSX Accelerator

DX10SceneryFixer

EZDOK

Some Orbx sceneries

 

I guess what I'm trying to do is not see blurry scenery out about 5-10 nm from the aircraft.  The changes I made in FSX.CFG file are:  HIGHMEMFIX=1, changed LOD_RADIUS=4.5 to 5.5.

 

Is there anything I need to do in the NVIDIA Control Settings?  And/or, do those settings need to match NI settings?

 

I hope I've given enough info for someone to assist me.  Thanks for any suggestions.

 

Rod

Share this post


Link to post

 

 


Is there anything I need to do in the NVIDIA Control Settings? And/or, do those settings need to match NI settings?

 

The display driver settings will change as you make the changes in NI.  Make sure you have FSX Profile selected and not the Global Driver Profile.  A lot of people innocently miss that when they open up NI.  Make sure you click on Apply Changes in the upper right hand corner of NI after making your changes.

 

If you want to see some really great (actually awesome) settings and information, please check out the new AVSIM Basic FSX/P3D/FS9 Configuration Guide.  Version 2 was just released.  A link to the download is in my signature.

 

Best regards,

Share this post


Link to post

Jim.....Thanks a lot for the response.  I'll check out the guide...thanks.

 

I'm sure I had selected FSX Profile and would select Apply.  But, you never know, I might've had some brain cramps happening...ha.

 

Again....Thanks a lot.

 

Rod

Share this post


Link to post

Hi Rod; You have my commiserations for the troubles you're having, but you should know - we've all been there at one time or other, and that lightbulb comes on for different folks at different times!  I will try and put you into a position where it's a little slower to achieve the success which you would like, but will be a lot less confusing, and with a bit more reading! If you've been following the P3D discussions - there are as many "Issues" as we have here, and this has been the case with FS 2000, 2002, 2004, and FSX - even SP1 to SP2! Nothing is new.

 

To answer your written questions, and get them out of the way - 

 

1). HIGHMEMFIX=1 has to be in the fsx.cfg. It was left out of SP2 when it was released, and is very necessary.. 

 

2). Put your LOD Radius back to 4.5 - your processor doesn't have the ability to create this number of objects, while creating all the rest of the needed objects. Start off with a minimal configuration, (and minimal expectations) - and then build on it by good testing. Here are the performance killers.

 

Firstly - go to the top of the Discussion forum and read the How-To guide. It's a little dated (as the retail fixer is out now), but much/most of the cfg settings will still be valid.

 

The first thing you need to do is to move that processor to 4.2 - 4.4 GHZ.  FSX in any form is better as the processor is woken up. Below 4.2 GHz one may as well stay with FS9.

 

Secondly - use only Inspector to control the graphics driver, ads it has a number of extras (that are needed) over the Control Panel. The one in the How-To is adequate - you might drop the SGSS down to 2x, that's all.

 

Last - it's difficult - actually near impossible - for anyone here, to give "an educated opinion" of the settings beneficial to your particular pc system, and so I would ask that you copy your existing fsx.cfg and rename the copy as "Rod_fsx.txt", and then attach it your reply by using the "More Reply Options" (bottom-right).

From this we can give/suggest settings which, while not being the "prettiest" settings, will at least give you some decent performance, and a baseline for you to build on. 

Meantime - read the doc, read the Fixer manual, with particular attention to the AA settings, and it's two entries into the fsx.cfg. (I will expand on this in the next reply post).

 

For thousands of FSX'ers - the DX10 option is going to be the alternate to P3D for those folks who don't want to go through the aggravation and cost of that change. FSX - DX10 is pretty smooth: it doesn't suffer from OOM's: some parts of it are prettier: it "feels" solid, with very few CTD's or blackscreens; and most everything that was DX9 now works just fine in DX10. With a half-decent system - one can find a pretty good FSX experience following the move. 

 

It's getting on bed-time here in Ontario, so -

 

All the Best, Talk at you tomorrow,

 

pj

Share this post


Link to post

Thanks a bunch Paul.  I'll see what I can do with your ideas and suggestions and let you know.  Hopefully tomorrow.

 

Rod

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this