Hi Paul, are the setting shown in the how-to doc (dated Aug 31st) reflective of the optimal settings to pair with the DX10 fixer?

 

Just wondering if you have any new suggested options for Nvidia Inspector to get the best out of the tool.

 

Also, would you be able to please comment if you use any of the following items in your fsx.cfg:

 

[Display]

TextureMaxLoad=XX

 

[TERRAIN]

BATCH_AUTOGEN2=1

SWAP_WAIT_TIMEOUT=2

 

[sCENERY]

MAX_ASYNC_BATCHING_JOBS=3
SmallPartRejectRadius=4.0

 

Thanks!

Dylan

Hi Dylan: Good Morning!

 

Yeah - the settings in are "sort-of" reflective of a starting point - a basis where you can work from. It's no use starting with say, "BufferPools=0"  when you have a 4.4-gig proc and a 560, Ti or not, as the results will not be good - better just leave it out of the cfg and work with medium settings for everything, test it, note the frames, save the (in-flight) flight as the default flight) then repeat and repeat and repeat - that same test flight, having increased one of the base settings (those settings which son't have a slider) and watching for a change. Sooner or later, you will have Texture_Bandwidth_Multi , Fiber_Frame_Time_Fraction, Affinity Mask and Max_Async_Batching_Jobs + any other setting that you might see or hear of (ignore any "that doesn't do anything" comments) all where you reckon they should be. Add in the BufferPools, and if the GPU IS faster than the existing proc speed - make it "0", and leave it. If there's no gain, then make it a "1" and ad a small RejectThreshold, Test and test, changing the RT, until the fps is stable, with few or very few dips. Then you can begin on getting traffic, scenery density and autogen, etc., up to wher she starts to fluctuate. At that point go back to the base settings and repeat the tests. It takes a while to do this - but you will end up with a more reliable FSX than you had before, as everything is now geared toward balance and stability.

 

Th "How-To" guide now has to be re-written, in oorder to encompass the released Fixer, so that'll take a day or three, I expect.

 

[Display]

TextureMaxLoad=XX      Not used. Take this out entirely: it pretty much does the same thing as the Texture_Bandwidth_Multi. It's (SP2) value is 6. Bojote worked with this and made recommendations, but I've not been able to confirm any gains from it's use.

 

[TERRAIN]

BATCH_AUTOGEN2=1  Not used.

            Both these entries were originally brought to light by ******* Altuve (aka Bojote), the first supposedly affecting the AG batching process, (which is dumping a large amount of autogen all at the same time, very noticeable with FSX, and not done this way with FS9). As with the testing bit above, use them, changing the values each time and test: and see where there are gains, if any.

 

SWAP_WAIT_TIMEOUT=2  - Not used at this moment, but should be tried.

 

[sCENERY]

SmallPartRejectRadius=4.0   Not used, as I don't think this is used with SP2. This modifies the AF, as small objects with 1 pixel in size far in distance are normally hidden by FSX, until the aircraft is approaching close enough.  Ex FS9.

 

MAX_ASYNC_BATCHING_JOBS=3  Yes - used by me. Impacts autogen popping.

 

Phew!   Don't forget - much of this is quite subjective, and there are several "ideas' (including mine) of what settings are part of FSX SP2, and impacts which they may have - the issue we have as DX10'ers - is that much of our DX9 settings will be different - and have different impacts when used with DX10 - so it's a little bit of a crap-shoot at times.

Not everyone is right, Dylan - again including me!

 

All the Best,

 

pj

Thank you for the fantastic and detailed Response Paul! Your insight very much appreciated as always   :drinks:

 

Now I wonder if I'll actually get more flying than tweaking time... :Just Kidding:

I hope so! - and if you are successful in making the transition, I think you will find, as I have - that that is indde the case. I do fiddle with the odd addition to the cfg now and again, but most often I can fire it up and just fly.  :biggrin: 

 

All the Best,

 

pj