Hi guys.

 

About 3 months ago i've bougth my new PC, assembled for FSX only:

i7 3770k @ 4.5ghz with Noctua NH-D14

MSI GD67

8gb corsair vengeance 1600MHz

660Ti

Samsung SSD 840Pro 128GB

WD Caviar Black 2TB for storage

 

In last month i flown constantly tweaking my cfg, and about a couple of weeks ago i've finally found a great setting. I'll not explain what i've done, the FSX Guide of Avsim and the Word Not Allowed's one were my bible.

 

Surprisngly, from the last week, i've tried to disable the HT on CPU, i've obtained a agood improvement on FPS, but my scenery is now completely blurried... Now, editing some twaks i fixed a lot the situation: AM from 84 to 14, FFTF from 0.1 to 0.25. But is still blurry!

 

For absourd i tried to set FFTF to 0.9. The scenery rendering is better, but not sharp as usual.

 

Please help me, i'm gonna out crazy!

Today i get a new cfg deleteing the mine, and i reapplied all the tweaks following the AVSIM's guide. But there are no sharpness improvement in my scenery.

 

Due to the FFTF high value required to get my scenery sharper i think i've something wrong, but i don't know what!

 

 

My actual tweaks:

Highmemfix=1

Texture_max_load=2048

ALLOW_SHADER_30=1

TEXTURE_BANDWIDTH_MULT=120 <- generally i use 40, but now is unusable 40... causes a lot of blur

FIBER_FRAME_TIME_FRACTION=0.25 <- 0.9 to get something better, but obviously FPS drops down and is not possibile to fly in this state..

AFFINITY_MASK= 14 <-with HT disabled, 84 if enabled

Usepools=0

Here is what I posted recently in another thread -

 

I saw some slow rendering a little with my i7 2600K with the GTX 580 too. The system was overclocked to 4.4GHz.  I had my LOD_Radius set to 6.5 and my Texture_Max_Load set to 2048 (HD) (LOD_Radius provides for sharper textures in the distance).  I used the default FSX settings and DX10.  I think that if you have too many tweaks they slow down the rendering.  Bufferpools doesn't work for every system.  If you use Autogen, make sure the Autogen "tweak" is in the Terrain section (http://support.microsoft.com/kb/555739):

 

Terrain_Max_Autogen_Trees=1000

Terrain_Max_Autogen_Buildings=800

 

Then you can push your Autogen to the max if you want.  I don't use Autogen as I fly almost exclusively in MSE V2 photoscenery.  I sometimes fly in Orbx/FTX stuff and use Autogen (Normal) then.  Autogen is a memory hog.  I know you have been around for a long time in the flight sim community and so I don't think I need to be telling you any of this but just in case. 

 

Now, for the real reason I posted a response, I just upgraded to the Haswell 4770K and now have a GTX 780 with 3GB's of memory and still use the same LOD_Radius 6.5 and TML of 2048.  With my photoscenery I saw no rendering as you go of any textures or mesh.  Everything was instantaneous. Even in the Orbx/FTX areas - instant gratification....  I haven't overclocked yet as I've been too busy moderating and reinstalling Windows 7 and FSX/Acceleration and all my addons.  I am slowly getting disappointed though as the more addons, the slower FSX seems to be running.  I started out with just FSX/Acceleration and had fps easily running at a minimum of 150 fps and as high as 275 and maybe 290 (no overclock).  Most of my addons are now installed and things are getting back to reality with some fps as low as in the teens and rarely above 60 fps (and that would be at FL240 in the PMDG 737 wing view over MSE V2 Illinois).  But, the photoscenery is still rendering instantly both with MSE V2 stuff and with Orbx/FTX.  So I'm not too unhappy.  I just had to do a lot of things to continue to get instant rendering and that was disabling all of my addon scenery except for the areas in my flightplan.  I use the Scenery Config Editor utility to enable/disable scenery.  If you ever run Process Monitor, it's unbelievable what's running in the background and what continues to load if you have all scenery loaded.  This takes up an inordinate amount of resources running in the background.  I ran this configuration with default fsx.cfg (except for LOD and TML) and default display driver settings for fsx. 

 

Another method to increasing resolution is to use the zoom setting in all of your views.  In the PMDG 737 I’ll hit the minus key two times to zoom things out a little and on the spot and wing views I’ll hit the minus key about 4 times to widen the view aspect to about 0.5 or 0.6.  It will make your textures render faster and give your textures a look of high resolution.

 

As I stated, I kept my fsx/display driver settings close to the default, but recently I read a post by NickN and decided to implement his settings - http://www.simforums.com/forums/gtx-780-settings-discussion-haswell-revealed_topic46112_page1.html.  He believes in fewer tweaks too in the FSX config and has one or two including my LOD and TML settings.  He drastically changed the display driver (NI) settings though.  I had a test situation where I was sitting at MSE V2 State of Virginia, FlightBeam KIAD, with real world weather at 6 pm, and in the PMDG737NGX VC.  Without Nick's settings, I was getting 12-15 fps sitting on R/W 1L.  I am now getting an additional 5 or 6 fps increase with his FSX and NI settings.  I’m probably going back to my default settings as I covered above as it is not a whooping increase in frames and I do not like the Bufferpool setting whatsoever. Maybe for older systems… I found my largest bottleneck was the PMDG737 VC and I proved it this morning when I tested the default Boeing 737 instead.  The fps jumped from 15-20 with the PMDG to 45 and sometimes higher with the default.  I’m still testing but I'd rather be flying rather than testing....  It’s going to end soon.

 

Hope this helps somewhat in resolving your question(s).

 

Best regards,

Jim

Thanks a lot Firehawk... but i haven't any improvement with this fixes.

 

It's so strange. With my cfg I neved had same problem. I haven't installed any addon in the last weeks...

Blurry textures are a result of high fsx/display driver settings.  FSX cannot render the textures at high settings.  One or more is too high.

 

Best regards,

Jim