Dont even touch the AffinityMask! it will make a mess and create frame rate volatility. The affinitymask should ONLY be tweaked on Quads/i7 or anything with at least 4 cores. and the ONLYvalues I would use are 14 or 12 (last 3 cores, or last 2) remember, the fiber (terrain system) will ALWAYS.. run in CORE0 it doesn't care what the AffinityMask is because is not bound to it. On dual cores, you are better off running the fiber and main scheduler on CORE0... CORE1 will load the textures and batch the objects, and that thread is very 'spike happy' goes to 100% comes down.. up again (during the pre-batchs) Now, since the fibers and main scheduler are sharing the same core, if you set FIBER_FRAME_TIME_FRACTION, to say 0.15 you will, of course, have a slight performance increase... because fibers will spend 'less' time making use or CPU resources. so.. go ahead, you should notice an improvement, and a 'little' blurries ;) so, if you can live with them... fine. I think after SP2 lots of things got moved off the terrain fiber, to the texture manager threads, so you'll see 'some' improvement, but nothing to write home about.

I feared this thread had come to an end, but *******, you have revived it again with your new tweaks. Thank you for your endless efforts to improve our game!I notice a difference between setting AffinityMask to 14 or 15. The latter giving me better results. In other forums I read different remarks about the AM, and so I am interested to learn your views.I have read that AM is not necessary when SP2 is installed. I have also read that 15 would be the better value rather than 14.Like I said, with AM 15 my flight is near perfect in crowded areas and I really thank you for what you are doing!Menno

An Indirect BenefitWhile reading the last few posts there was a mention of the Frame Fiber setting. It prompted me to take a look at it just to be sure. It was set at 0.6. Reset to 0.1 and now no stutters. I used to have to use the FSX frame limiter to avoid them.This is not to suggest any tweak but to show that you sometime may have an old forgotten tweak/setting that becomes a liability when you do some other tweak. After all, there are limited resources which means each system may have a different max performance balance point.2.4 ghz dualcore, nVidia 8600 256mb(PCie 4x), 2gb memory -- becoming a lo-end system.

After cleaning up and re-installing everything I noticed slower performance in the Seattle area.This morning I checked my cfg and noticed the fiber tweak missing. I added FIBER_FRAME_TIME_FRACTION=0.15 and loaded Seattle and noticed a 10 fps increase. I was in disbelief! So I removed the line just to see if I was just fooling myself - fps dropped. This just keeps getting better and better.I also wanted 35 fps. 30 is good, but 35 is just smoother. I raised to: TEXTURE_BANDWIDTH_MULT=300 Now I can run at 35 and I thought I was done tweaking.

In light of new findings, I have been testing yesterday only (had a really busy last week and this one is only gonna be worse), and found those tweaks real good. Only one thing puzzles me, as I usually get artifacts and crashes if I up it: LOD_RADIUS. Those who report good results with *******'s tweaks, what are you LOD_RADIUS settings? And I guess your TEXTURE_MAX_LOAD is at 1024. Anything more chokes my system. Even setting LOD_RADIUS higher starts choking it - even I leave all other settings low. My only problem is I love the radius 8.5, which looks GREAT on the scenery, so I would like to know, is there someone out there successfully running it?!

I have found that LOD_RADIUS of 6.5 to be a sweet spot. It gives you clear and formed texture miles around your aircraft position, and I have found no FPS or stutter hit. If I go beyond that to what some have had such as 9.5, it gets 'messy'. 6.5 is something I'd suggest you try over the default 4.5.Mitch

After cleaning up and re-installing everything I noticed slower performance in the Seattle area.This morning I checked my cfg and noticed the fiber tweak missing. I added FIBER_FRAME_TIME_FRACTION=0.15 and loaded Seattle and noticed a 10 fps increase. I was in disbelief! So I removed the line just to see if I was just fooling myself - fps dropped. This just keeps getting better and better.I also wanted 35 fps. 30 is good, but 35 is just smoother. I raised to: TEXTURE_BANDWIDTH_MULT=300 Now I can run at 35 and I thought I was done tweaking.

Hi, With a FIBER_FRAME_TIME_FRACTION=0.15, did you notice any texture bluring? RegardsBob

I have tried the new settings and I must say that this is a real breakthrough. I did a flight from KSEA to KFLL yesterday and I didn't have any black screens or texture corruption. I can't say that I saw any FPS increase but low FPS flying (10-15 FPS) seemed really smooth. THANK YOU *******!Before these settings, I was using NHancer and a fairly clean FSX.cfg - both set up according to Nicks settings. I have FPS locks to 30 in the sim and I haven't tried other options yet. There are a few negatives that I see with the new settings and I am wondering what I should be adjusting to try to correct them.1. In game AA seems like it has a harder performance hit than NHancer and the visuals are not as nice. NHancer gave me fantastic visuals. AA with the NVIDIA control panel doesn't seem to work in FSX. 2. Ground textures are muddy when you move away from the aircraft - coastlines are not defined in front of the aircraft and the waters textures look bad. Should I just play with LOD settings?3. PNW seems to run a lot slower that it did before. Is there something I should be changing to speed it up?4. I would also like to get HD clouds running again and increase the cloud coverage density to 12 but I'd like to get the above issues fixed before I play with those settings. (increasing it to 12 really looks great)Here are the important points from my FSX.CFG:[JOBSCHEDULER]AffinityMask=14[bufferpools]Poolsize=0[GRAPHICS]SHADER_CACHE_VERSION=2HIGHMEMFIX=1STALE_BUFFER_THRESHOLD=2147483647 SHADER_CACHE_PRIMED_10=1693500674SHADER_CACHE_PRIMED=1693500674TEXTURE_MAX_LOAD=1024NUM_LIGHTS=8AIRCRAFT_SHADOWS=0AIRCRAFT_REFLECTIONS=1COCKPIT_HIGH_LOD=1LANDING_LIGHTS=1AC_SELF_SHADOW=0EFFECTS_QUALITY=2GROUND_SHADOWS=0TEXTURE_QUALITY=3IMAGE_QUALITY=0See_Self=1Text_Scroll=1D3D10=0[Display]TextureMaxLoad=9ChangeTime=4.000000TransitionTime=4.000000BLOOM_EFFECTS=0SKINNED_ANIMATIONS=1TEXTURE_BANDWIDTH_MULT=70UPPER_FRAMERATE_LIMIT=30WideViewAspect=True[Main]ProcSpeed=14692PerfBucket=7Location=444,138,1476,904,\\.\DISPLAY1Maximized=1HideMenuNormal=0HideMenuFullscreen=1[Weather]CLOUD_DRAW_DISTANCE=3DETAILED_CLOUDS=1CLOUD_COVERAGE_DENSITY=8THERMAL_VISUALS=0

... remember, the fiber (terrain system) will ALWAYS.. run in CORE0 it doesn't care what the AffinityMask is because is not bound to it. ...

The emperical data I've seen when running Windows 7 does not support the above statement. If I use an FSX.cnfg affinity mask with my i7 860 that omits CPU0, i.e. any even valued affinity mask, CPU0 shows very little activity via task manager's performance graphs when FSX is running; CPU0 hops up to about 10% for second or two and drops back down to 0% for a second or so, over and over again; it does nothing but this during the entire duration of a flight. Since I'm observing this using Windows 7, my guess that these CPU0 blips are from OS related activities, unless that FSX terrain system thread, er fiber, really is that inactive (is it?). The cores specified in the affinity mask show a consistent 30% to 100% utilization. See my sig for my setup. Thanks for reading, TFM.

The emperical data I've seen when running Windows 7 does not support the above statement. If I use an FSX.cnfg affinity mask with my i7 860 that omits CPU0, i.e. any even valued affinity mask, CPU0 shows very little activity via task manager's performance graphs when FSX is running; CPU0 hops up to about 10% for second or two and drops back down to 0% for a second or so, over and over again; it does nothing but this during the entire duration of a flight. Since I'm observing this using Windows 7, my guess that these CPU0 blips are from OS related activities, unless that FSX terrain system thread, er fiber, really is that inactive (is it?). The cores specified in the affinity mask show a consistent 30% to 100% utilization. See my sig for my setup. Thanks for reading, TFM.

1) Disable vSync2) Set Frames to UnlimitedThe Above will FORCE FSX to produce an incredible 'high' number of Frames per second and make the 'fibers' more 'visible'you are right about the 'usage' being very light.. thats because most of the work was moved OFF from the fiber system. but there is STILL somethings running there, so you'll see them when over complex terrain, high FIBER_FRAME_TIME_FRACTION or high FPS.. and please, DO see for yourself, its very important not to blindly believe everything we read, we need to question, test, analyze! so please, do test again.

1) Disable vSync

Wouldn't that result in image tearing problems?

2) Set Frames to Unlimited

Introduces stutters and graphical artifacts on my system.

hi,thanks for this wesome help. finally we get fsx to work!just one question, i still suffer from bad blurries when moving above 200kts. what fsx.cfg-entries should i tweak to get rid off the,? i already have tried to set the fiber_frames from .1 to .6, no visual difference. i think my fps are high enough (take a lok at my attached picture)my specsfsx sp2 - asusP5ql pro- intel quad core @ 2,66 - 4gbram - geforce gtx280thanks for your help!regardschristopher

Wouldn't that result in image tearing problems?

Correct

Introduces stutters and graphical artifacts on my system.

Correct.and the point is that the user to whom I told him to test 'that' wants to make the sim produce the most number of frames per second so he can see the 'fibers' in action. capiche?

And now, ladies and gents, per his request we'll give ******* (and this unbelievable thread) a rest.He has summarized for us his work hereAll we can say is "muchas gracias amigo" :(