Come on DX10 gurus, help a guy out! 

 

 

Come on DX10 gurus, help a guy out!

 

You'll need to provide more information.

 

1.  Screenshots of how you have DX10 Controller configured

2.  FSX.CFG settings

3.  Your hardware, CPU, RAM, GPU(s), etc.

4.  nVidia Inspector settings (if you have an nVidia CPU)

Come on DX10 gurus, help a guy out! 

 

With your rig you should get a much better FPS. Did you follow the advices here in the forum and read carefully "How-to.."?

Spirit

Rob,

Will you please provide Nvidia Inspector settings . Some reason I cannot activate NI??? I installed new Nvidia Driver GF 331.58 WHQL-[r331_54-5]

Thanks

You'll need to provide more information.

 

 

Yessir.

 

1) DX10 Fixer Options

 

DX10:

 

Legacy Options:

 

General Shader Options:

 

Water Shader Options:

 

Rain Shader Options:

 

2) fsx.cfg is attached in the post, feel free to peruse as you wish

 

3) Hardware is listed in the My PC section under my profile picture to the left of this post.

 

4) NI Settings:

 

Will you please provide Nvidia Inspector settings

 

 

 

4) NI Settings:

 

Your DX10 controller settings, uncheck 8bit Texture Fix unless you really need it.  If you are running REX, use DXT1 Wave animation.

 

FSX.CFG For All Cases:

 

[DISPLAY.Device.NVIDIA GeForce GTX TITAN.0.0]

Mode=2560x1600x32

Anisotropic=1

AntiAlias=1

 

[JOBSCHEDULER]

AffinityMask=680

[bufferPools]

UsePools=0

Poolsize=0

 

[Display]

TextureMaxLoad=27

BLOOM_EFFECTS=1

SKINNED_ANIMATIONS=1

TEXTURE_BANDWIDTH_MULT=80

UPPER_FRAMERATE_LIMIT=30

WideViewAspect=False

 

[GRAPHICS]

HIGHMEMFIX=1

ForceWindowedVSync=1

TEXTURE_MAX_LOAD=2048

NUM_LIGHTS=8

AIRCRAFT_SHADOWS=1

AIRCRAFT_REFLECTIONS=1

COCKPIT_HIGH_LOD=1

LANDING_LIGHTS=1

AC_SELF_SHADOW=1

EFFECTS_QUALITY=2

GROUND_SHADOWS=0

TEXTURE_QUALITY=3

IMAGE_QUALITY=0

See_Self=1

Text_Scroll=1

D3D10=1

ForceFullScreenVSync=1

 

[Weather]

CLOUD_DRAW_DISTANCE=12

DETAILED_CLOUDS=1

CLOUD_COVERAGE_DENSITY=8

THERMAL_VISUALS=0

 

[Main]

FIBER_FRAME_TIME_FRACTION=0.66

DisablePreload=1

HideInfoText=0

 

Other Items that affect performance:

 

[sCENERY]

ObjectsToBatchPerFrame=50

MAX_ASYNC_BATCHING_JOBS=4

SmallPartRejectRadius=1

LENSFLARE=1

DAWN_DUSK_SMOOTHING=1

IMAGE_COMPLEXITY=5

 

[TrafficManager]

AirlineDensity=10

GADensity=10

FreewayDensity=10

ShipsAndFerriesDensity=10

LeisureBoatsDensity=5

IFROnly=0

AIRPORT_SCENERY_DENSITY=3

 

[TERRAIN]

SWAP_WAIT_TIMEOUT=2

IMAGE_PIXELS_FOR_AUTOGEN_POLYGONS=2048

BATCH_AUTOGEN2=1

LOD_RADIUS=8.500000

MESH_COMPLEXITY=100

MESH_RESOLUTION=25

TEXTURE_RESOLUTION=29

AUTOGEN_DENSITY=5

DETAIL_TEXTURE=1

WATER_EFFECTS=4

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=4500

TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=3000

 

For Medium Quality (minimal shimmers):

 

[GRAPHICS]

MultiSampleQuality=4

MultiSamplesPerPixel=4

 

 

For Best Quality (zero shimmers)

 

[GRAPHICS]

MultiSampleQuality=4

MultiSamplesPerPixel=8

 

 

The only item I change based on aircraft type is LOD_RADIUS=8.500000 ... this will vary from 6.5 to 11.0 and is more to do with memory usage than performance.

 

You may want to delete your Sharders10 folder (it will get recreated) -- it's located ..\Users\[YourUserID]\AppData\Local\Microsoft\FSX

 

I'm not making ANY CLAIMS ... this works for me.

 

Rob

 

Trying it now, will be report back shortly.

Okay, update: Your settings made no difference, so I think I'll have to go with an FSX re-install? 

Okay, update: Your settings made no difference, so I think I'll have to go with an FSX re-install? 

No Aamir, why would you do that?  

 

I have been struggling with NI settings and DX10 and thought that NI should be controlling AA.  PJ is going to make me walk the plank when he reads this but I was having a display issue until I changed the AA settings to what he has published in the guide... I am really stubborn (I think?) and I thought there must be some way to overcome the shimmering and other display anomalies outside of FSX.

 

I have always ticked AA (to use DX10) and used Anisotropic in FSX but I wanted more refinement and set AA as you have in NI but realized NI was making it worse for me display wise.  My "workaround" (sorry PJ) is to let NI allow FSX to control AA.  If I remember correctly both Michael Greenblatt (FSGS) and Bojote insisted that controls are best left to the application (FSX) because it works better that way.  But with NI we could override and improve the setting but only in DX9.

 

I see in your NI settings Rob that you have AA - Mode set to "Override any application setting", do you find that it improves the linear jaggies that appear on horizontal planes?

 

I have been playing around with FSX.cfg just as you have Rob, testing each tweak one by one and I can say without a doubt that for me the following are what works the best and makes FSX a charm to fly:

 

[bufferPools]

UsePools=0  //GPU with greater than 1 Gb Memory

 

[GRAPHICS]

HIGHMEMFIX=1

 

[Main]

FIBER_FRAME_TIME_FRACTION=0.12  // I do not have photoreal scenery and ~0.12 I get smoothness in the VC and beautiful ground textures - no blurries!

 

 

There are other .cfg entries that I employ but those 3 are the most important for me, I've added my .cfg below.

 

I think I am at the point where I cannot improve how FSX displays any more than I have but then again I am using a 40" LED display which is purely for my entertainment.

 

 

 

 

:LMAO:    Halmich - you'd be at the end of that plank if you lived here in cold, windy and wet southern Ontario!!!    :LMAO: 

 

AA is contr.... aaaah, forget it - you don't listen anyway!!     (  :friends:)  (I'm the ugly one...)

 

While I have your attention, though, Rob - the line "Texture filtering - negative LOD bias - needs to be set to "Allow" in order to use a LOD Bias. (-1.0000) (two lines above).

 

Some great posts!  

 

All the Best,

 

peej 

Aye Cap'n.  :blush:

 

 

While I have your attention, though, Rob - the line "Texture filtering - negative LOD bias - needs to be set to "Allow" in order to use a LOD Bias. (-1.0000) (two lines above).

That was something I missed, I forgot to set the values back to +0000.  Negative LOD Bias=Clamp was a throwback to Nvidia nHancer and for me I found the result was best when set to clamp.  The setting was much simpler then as I do not think it had any numerical value tied to it.

 

Having played around with different settings I have yet to find any that improve graphics much more than when it's set to Clamp, I would like to know if anyone has had any success in FSX with different settings because I would be eager to give them a try.

 

Can't wait to give FSX another go tomorrow, it just keeps getting better and better.

 

 

While I have your attention, though, Rob - the line "Texture filtering - negative LOD bias - needs to be set to "Allow" in order to use a LOD Bias. (-1.0000) (two lines above).

 

Oh, two Rob's present in this thread ... if it's me, then I'm pretty sure I tried those setting and didn't notice any difference ... but I'm getting old and I've experimented so much it's hard to know these days so I'll try your suggestion again Paul.

 

For a complete shimmer free experience (in my case) was:

FSX - MultiSamplesPerPixel=8

NI - 8X Sparce Grid Supersampling

 

(these needed to match up)

 

Rob

 

.....

[JOBSCHEDULER]

AffinityMask=680

....

 

Hi Rob,

for a i7 3770 CPU this affinity mask sounds pretty odd for me. I would recommend 1364. Maybe you can share your thoughts why to set 680?

Spirit

 

 

for a i7 3770 CPU this affinity mask sounds pretty odd for me. I would recommend 1364. Maybe you can share your thoughts why to set 680?

 

I've tried 1364 but when using Fraps to record video I would get a big hit in FPS (almost 50%).  At 680, I loose less than 5% fps and FSX seems to run well.  But honestly, it's just a case of trial and error ... I'd recommend folks go with whatever works for them as there are so many variables to how Affinity will work such as OS version, to BIOS, to CPU model, HT ON, HT OFF, etc. ... I honestly don't want to get involved in what Affinity settings "should be".