Hi.

I`ve been having issues with my setup and put my NI back to standard.

My frame rate issue has gone now.

I`ve not been on the sim long enough to see what I`ve sacrificed by doing this.

 

I`ve set the DX10 fixer to 8x and all is still ok.

What have I affected by doing this?

 

What is the bare minimum setting on NI I need?

 

HAPPY NEW YEAR GUYS.

As stated in the AVSIM FSX Configuration Guide (see link in my signature), the AA, Transparency Supersampling setting is the frame rate killer.  I have mine at 2x's.

 

Best regards,

Happy New Year to you, too, my friend!

 

Here's your belated Christmas present.  :drinks:

 

..and a revised version of the How-To guide will give you settings for the NI.

 

All the Best,

 

pj

Happy New Year to you, too, my friend!

 

Here's your belated Christmas present.  :drinks:

 

..and a revised version of the How-To guide will give you settings for the NI.

 

All the Best,

 

pj

I was there mate.

Donnington Park 1991.

Cant believe that was over 20 years ago.

Many thanks

I know - I have the DVD - I saw you there - you were sitting next to that girl who pulled up her sweater!  B)

 

One of the greatest shows ever! 

Hi.

Tried your settings in NI.

I`ve lost all my fonts in FSX Menu.

Title bar is still there, and the drop downs also still there, but no lettering.

Not seen than before.

OK.. don't know why that should happen: try 4x in the Fixer, make sure the fsx.cfg shows this:-

 

[GRAPHICS]

MultiSamplesPerPixel=4

MultiSampleQuality=0

 

and change the 2x SGSS to 4x SGSS, and turn off FXAA. This will give decent AA, and almost no shimmering. If you still have it after this, would you post the fsx.cfg (as .txt) in the reply. I've seen this before, but can't remember off-hand, but it's in my notes somewhere, so I'll dig for it while you're trying these settings.

 

pj

Thankyou for this.

The mrs in bed with a hangover at the moment.

 

Just fired it up, and still the same.

 

Bit confused with this bit.......

 

You must set the Sparse Grid Sample number to the exact same amount of multi

-

samples. In other words

if you are using 4XSparse Grid you also MUST use 4xMSAA in the profile. Otherwise you will end up with

a blurry mess.

You also are goin

g to have to set the LOD bias so there is no blurring. You must change the LOD bias

setting from clamp to allow. This is a general guideline on LOD bias settings.

2x MSAA + 2x SGSSAA:

-

0.500

4x MSAA + 4x SGSSAA:

-

1.000

8x MSAA + 8x SGSSAA:

-

1.500

 

Is this the problem?

I had the loss of menu/graphics issue while experimenting with DX10 yesterday. I concluded it was an improper NI setting of the LOD BIAS. -0.5000 etc. Not being matched properly. Gave up, again.

No - shouldn't be, but it could be, we can always change it back. I use 2x because it's a very light load, but 4x gives much better control over shimmering, and I'm changing the doc to reflect that. As far as the LOD Bias is concerned - take it out and see what happens. It shouldn't have any effect, but .... this is fsx....

 

Would you open up your dll.xml using Notepad, and then copy/paste it here, so I can take a peep at it?

 

Ta.

It could be LOD Bias settings, but I've been using these for a long time without issue. - but not all monitors/GPU's/drivers respond equally to these settings, and certainly those fonts have been an unusual, infrequent pain in the butt for a long time, too.

The dll.xml is one of the most common causes of garbled, or indistinct menu bar wording - usually it's been corrupted by an addon that modifies it but using the Unix command set for end-of-line/carriage returns.  You can verify those characters by using Notepad++, choosing "View->Show Symbol->Show all characters". At the end of each line there should be two small black squares, one with a white "CR" inside, and the other with a white "LF" inside. Every line should have this.

 

Below is a complete, working dll.xml, and below that - a few lines of the same file, but as a snip from the Notepad++ view:

 

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">

  <Descr>Launch</Descr>

  <Filename>dll.xml</Filename>

  <Disabled>False</Disabled>

  <Launch.ManualLoad>False</Launch.ManualLoad>

  <Launch.Addon>

    <Name>ObjectFlow_KSFF.dll</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>F:\Flight Simulator X\ORBX\FTX_NA\FTX_AA_KSFF\Scenery\ObjectFlow_KSFF.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>ObjectFlow_S43.dll</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>F:\Flight Simulator X\ORBX\FTX_NA\FTX_AA_S43\Scenery\ObjectFlow_S43.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>ObjectFlow_EGML.dll</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>F:\Flight Simulator X\ORBX\FTX_EU\FTX_AA_EGML\Scenery\ObjectFlow_EGML.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>as_connect</Name>

    <Disabled>False</Disabled>

    <Path>as_srv\as_btstrp.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>FSUIPC 4</Name>

    <Disabled>False</Disabled>

    <Path>Modules\FSUIPC4.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>A2A Feel</Name>

    <Disabled>True</Disabled>

    <Path>Modules\A2A_Feel.dll</Path>

    <DllStartName>module_init</DllStartName>

    <DllStopName>module_deinit</DllStopName>

  </Launch.Addon>

  <Launch.Addon>

    <Name>AccuFeelMenu</Name>

    <Disabled>True</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>Modules\AccuFeelMenu.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

<Name>AIDupe</Name>

<Disabled>False</Disabled>

<Path>F:\Flight Simulator X\Modules\Modules\AIDupe.dll</Path>

</Launch.Addon>

 </SimBase.Document>

 

Now, viewed with Notepad++

 

 

Compare these to yours.

 

Happy New Year to you, too, my friend!

 

Here's your belated Christmas present.  :drinks:

 

..and a revised version of the How-To guide will give you settings for the NI.

 

All the Best,

 

pj

 

Thank you for the the revised guide! During the DX9-era forums were bombarded with tweaks and good advice, however there was little to no game-play improvement regardless of tweaking. What makes the DX10 guide so great is the instant and visible improvement of the simulator.

Thanks, 767 - though I don't know that i have any special tweaking talent (!!!) - and I'm not a C++ programmer, but you've raised an interesting point.

 

There are two things at play here, the first being the reason for that "instant and visible improvement". I believe that when using DX10 the individual setting will mostly impact either the CPU only - or the GPU only - and therefore it has that much greater impact.

Secondly, I think, too for the purposes of writing a "How-To" doc, that it is important to discover - and explain, and provide a logical reason for any particular setting, rather than just say "do this" or "set this to xxx", and so that's what I try to do in the doc. By this means, the sim flyer will get an expected response to a setting change, while at the same time becoming more technically knowledgeable about what he or she just did.

At this point not everything is understandable by us, (me included) but the days of the DX9-era, where everyone was a sheep, simply putting in values because someone else did, are numbered for us DX10-ers. We know a lot more about FSX now.

 

Anyway - it's comments like yours that makes the day that much brighter, and I appreciate it!

 

Thank you again, 767, and have a happy and prosperous new year!  :wink:

 

pj

Thanks, 767 - though I don't know that i have any special tweaking talent (!!!) - and I'm not a C++ programmer, but you've raised an interesting point.

 

There are two things at play here, the first being the reason for that "instant and visible improvement". I believe that when using DX10 the individual setting will mostly impact either the CPU only - or the GPU only - and therefore it has that much greater impact.

Secondly, I think, too for the purposes of writing a "How-To" doc, that it is important to discover - and explain, and provide a logical reason for any particular setting, rather than just say "do this" or "set this to xxx", and so that's what I try to do in the doc. By this means, the sim flyer will get an expected response to a setting change, while at the same time becoming more technically knowledgeable about what he or she just did.

At this point not everything is understandable by us, (me included) but the days of the DX9-era, where everyone was a sheep, simply putting in values because someone else did, are numbered for us DX10-ers. We know a lot more about FSX now.

 

Anyway - it's comments like yours that makes the day that much brighter, and I appreciate it!

 

Thank you again, 767, and have a happy and prosperous new year!  :wink:

 

pj

 

Wishes of a happy and prosperous year back to you - I have noticed you do a tremendous job for the community! Thanks to DX10 2014 could become another exciting year for flight simmers. With the boost of DX10, I feel confident «old» simmers would be interested getting back into the game. The question is whether they are aware of (DX10) it or not.