22" Widescreen with max (not tweeked) LOD. I know.. it is a low res image. If you look at my Radar Contact window in the lower left when in the sim the text is very clear. That should give you a gauge what the compression did to the shot plus the weather was a bit hazey and that was taken at I think 9 or 10,000 alt.

Yes, thats what I mean, those letters look blurry like the scenery, like your driver is set at performance mode instead of high quality texture mode.Ok, its 22" what resolution is that? My 24" is 1920x1200.

Well guys, after more testing (a flight int KJFK) spikes galore but what is funny about it is that is was actually realativly smoother than without the BP of 0. I almost hate I read this ding dang thread as now it has me tweeking again and not flying so curse you who started all this. :( So I also read in this novel of a thread that lowering the FPS lock may help. So thats what I did.... I swallowed my pride and set the FPS lock to 26 from 30, set my BP to 200,000,000 and was able to fly in NYC very nicely. SO it seems to me that and actually make sense if you think about it that lowering your FPS lock in heavy hitting scenery areas gives much better performance. Sure I can fly at 30 FPS in most places without issue but I HATE HATE HATE when comming into a big scenery area of the fps surges that happen, so for me at least for today :( I will stay wit the lower FPS lock and will further test different BP settings to see if I can make it better. Have fun guys with this I'm out. :(

Well guys, after more testing (a flight int KJFK) spikes galore but what is funny about it is that is was actually realativly smoother than without the BP of 0. I almost hate I read this ding dang thread as now it has me tweeking again and not flying so curse you who started all this. :( So I also read in this novel of a thread that lowering the FPS lock may help. So thats what I did.... I swallowed my pride and set the FPS lock to 26 from 30, set my BP to 200,000,000 and was able to fly in NYC very nicely. SO it seems to me that and actually make sense if you think about it that lowering your FPS lock in heavy hitting scenery areas gives much better performance. Sure I can fly at 30 FPS in most places without issue but I HATE HATE HATE when comming into a big scenery area of the fps surges that happen, so for me at least for today :( I will stay wit the lower FPS lock and will further test different BP settings to see if I can make it better. Have fun guys with this I'm out. :(

The goal for any tweaking should be to get the best visuals quality while still having a smooth flight. FSX average fps should not be used as a goal. If you get a smooth flight with acceptable visual quality - the goal of your tweaking is satisfied.My two cents B)

.... and today, after charting each change of the things that aren't tweakable in the Settings->Display for a couple of hours, (and not furthering the cause) I dug into the FIBER_FRAME_TIME_FRACTION, and found that (A2A Spit, 1200ft, 240kts, 340deg over 34C) by progressively lowering that setting well below the "normal" setting - FSX became smoother and smoother and smoother... FPS locked at 24.FIBER_FRAME_TIME_FRACTION=0.025 // 0.0125 // 0.025 // 0.05 // 0.10 // .15 It's been at .25 for a while - taken from someone else's post, but I hadn't played with it, and I thought "nothing to lose" . I started off by dropping it to the last figure - 0.15 - and the difference was noticeable, so I continued..... Whether it works for the older quad series procs I don't know, but it definitely made a huge difference to PNW on my clunker.

Whether it works for the quad pc's I don't know, but it definitely made a huge difference to PNW on my clunker.

Your not using the quad in your sig?

Your not using the quad in your sig?

No - it's an i7: I'm aware that the i7 is a "quad", but it's not named a "Quad", whereas the previous generation of procs are /were actually called Intel Core2 Quad processors - like the Q6600 through Q9650: before that there were the Core 2 Duo procs.

.... and today, after charting each change of the things that aren't tweakable in the Settings->Display for a couple of hours, (and not furthering the cause) I dug into the FIBER_FRAME_TIME_FRACTION, and found that (A2A Spit, 1200ft, 240kts, 340deg over 34C) by progressively lowering that setting well below the "normal" setting - FSX became smoother and smoother and smoother... FPS locked at 24.FIBER_FRAME_TIME_FRACTION=0.025 // 0.0125 // 0.025 // 0.05 // 0.10 // .15 It's been at .25 for a while - taken from someone else's post, but I hadn't played with it, and I thought "nothing to lose" . I started off by dropping it to the last figure - 0.15 - and the difference was noticeable, so I continued..... Whether it works for the quad pc's I don't know, but it definitely made a huge difference to PNW on my clunker.

Paul, where is that setting at or where does it go? It is not in the cfg file unless I am now as blind as a bat as well as losing my marbles.Stephen

Paul, where is that setting at or where does it go? It is not in the cfg file unless I am now as blind as a bat as well as losing my marbles.Stephen

Oh no, here we go again...Stephan gets yet another 10-20% FPS increase! :(

Oh no, here we go again...Stephan gets yet another 10-20% FPS increase! :(

.... maybe I won't tell him! :(

losing my marbles.......Stephen

You're from the east coast, aren't you? On the rock, maybe?Just add it into the [Main] section, Stephen.. :(

This very much contradicts what NickN wrote in his tweaking article... but hey, if it's working and is NOT a placebo effect ;-)Testing as I write too...

This very much contradicts what NickN wrote in his tweaking article... but hey, if it's working and is NOT a placebo effect ;-)

Yeah - I thought that, too, Word Not Allowed: PNW is a hog, but there are numbers of posts where "I get 30 fps", and "between 28 - 40fps" and so on. I can't run with a BP of 0 without arties and ground flashing, so it's worked upwards to 400k. With the setting below I can do 22.9/23 locked and solid, PNW, KSEA, lots of GA & airline, which is what I had bPNW. It means I can do 28 locked and solid with the default (GEX/UT_USA). The one thing I changed - I think for the worse - is the gpu driver. Stephen had suggested the 185.85 Vista 64 bit, so I found it and loaded it: the colors seem more vibrant, but I think it pulls down the default FSX performance. I think I had better results with the 196.34 Win7 driver, so I'm going to switch back and test again.... and again... and again.... :( TEXTURE_BANDWIDTH_MULT=100UPPER_FRAMERATE_LIMIT=23ForceFullScreenVSync=TrueForceVSync=TrueWideViewAspect=TrueDisablePreload=1 // FTXFIBER_FRAME_TIME_FRACTION=0.025 //0.0125 //0.025 //0.05 //0.10 //.15[bufferPools]PoolSize=400000 //200000 // 50000//40000 //100000 //5000 //3000 // 1000 // 100AirlineDensity=26GADensity=26FreewayDensity=12ShipsAndFerriesDensity=0LeisureBoatsDensity=0IFROnly=0AIRPORT_SCENERY_DENSITY=0[TERRAIN]LOD_RADIUS=3.500000MESH_COMPLEXITY=50MESH_RESOLUTION=22TEXTURE_RESOLUTION=28AUTOGEN_DENSITY=2DETAIL_TEXTURE=1WATER_EFFECTS=2TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=800 // 2500 // FTX // 800 // 300 // 4500TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=700 // FTX // 2000 // 4500 // 3000

You get flashes because your tbm is set too high

You get flashes because your tbm is set too high

I rather disagree. I have also tested many settings on TBM, and flashes happen on both low and high. I still can't really pinpoint why, though. I think, as I said also many times before, it's a fubared FSX engine...

I rather disagree. I have also tested many settings on TBM, and flashes happen on both low and high. I still can't really pinpoint why, though. I think, as I said also many times before, it's a fubared FSX engine...

In this case 413x3 is right, Kost... I dropped it to 60 from 100 and had just one or two going off Renton, out over SEA and in to BFI. I was blaming BP for the flashing. GRRRRrrrrrrr... Now to move BP back down again. This morning I was trying to stop the stuttering, and those were the settings I had when I started to play with the FFTF. Ya never stop learning!

Oh no, here we go again...Stephan gets yet another 10-20% FPS increase! :(

LOLOLOL :( When I get my new i7 930 next week and overclock the thing to 4.2, it might even be objectively true!Stephen