Hello, folks,

 

After almost a decade, I´m back fo FS community, this time using FSX and a new computer made specially for it:

 

i7-2600k OC to 5Ghz

16Gb RAM 2000mhz Corsair

2 SSD - Samsung Pro 256mb for system and a 500gb for FSX

1 Seagate 3Tb for adicional scenery

Asus Geforce GTX 780 CU-II

Corsair obsidian 950d

Corsair watercooler H100i

Corsair PSU -  AX1200

Asus monitor 27 inches

 

Well, after installing everything, some scenery, FSgenesis, some Aerosoft, Ultimate Terrain, many third party airports, Tileproxy, I purchased many Megascenery Earth states scenery

Then, I notice in Megascenery Earth that I can´t use even a Learjet. I have to fly at a minimum speed in order to have sharp textures around the aircraft.

When I fly, better textures appear here and there, slowly, till all area is covered.

 

I made some tweaks on fsx.cfg in order to improve this, like raising Lod radius to 6.5 ( improved but when I fly above 80knots same thing )

I remember that with Tileproxy I could fly on every aircraft keeping sharp textures. After some days teaking FSX, I´m almost to give up from Megascenery Earth.

I can only get full sharp resolutions if I stop the aircraft, then, slowly, texture high resolution around the aircraft begins to improve to the maximum quality.

Fiber parameter is set to 0.70 already.

I increased Lod radius to 9.0 and even to 15 and this improved a lot, but I get Out of memory crashes. FSX is a thing that when it begins to get good it crashes...

 

Any hints how to solve this problem ?

 

Thanks in advance,

 

Dihelson Mendonça

What drive do you have the MSE textures loaded onto? If it's the 3TB Seagate, what are the specs of this drive?

 

I set LOD_RADIUS to 8.0 as maximum and leave the Fiber setting at default.

 

Sounds like slow loading of textures from the drive, especially if you do eventually get the full resolution images.

Hello, Dean ( PC Aviator ),

 

Thanks for the quick answer to my question. Indeed, all Megascenery Earth states are placed on the 3tb seagate drive, which is very fast for a spinup drive, it keeps around 200mb/s measured on HDtune, half of a SSD. If we suspect it´s the drive transfer speed, I´ll make a test, will install one of the states on the SSD drive. The problem is that SSD ( 500Gb ) is almost full with other scenery. BTW, I didn´t find this problem with tileproxy even when it was installed on the 3Tb drive. It was a surprise to me when I changed from tileproxy ( which has a better resolution indeed ) to Megascenery Earth, which I thought it had at least the same resolution, around 30cm without converting to 2 meters, you can fly almost half altitude and is still good. But MSE when in full resolution is good, unless for some states like Illinois, Indiana, which have a dreadful washed color ( green all the time ). Some states are better, like Washington and Colorado. I´ll make the test and come back to tell how it was. Lod Radius 8.0 gives me out of memory when combines MSE with Aerosoft Chicago and other scenery. If used 6.5 they work together. Indeed ORBx Pacific Northwest also works. They complement very nice.

Well, after installing everything, some scenery, FSgenesis, some Aerosoft, Ultimate Terrain, many third party airports, Tileproxy, I purchased many Megascenery Earth states scenery

Then, I notice in Megascenery Earth that I can´t use even a Learjet. I have to fly at a minimum speed in order to have sharp textures around the aircraft.

When I fly, better textures appear here and there, slowly, till all area is covered.

 

I made some tweaks on fsx.cfg in order to improve this, like raising Lod radius to 6.5 ( improved but when I fly above 80knots same thing )

I remember that with Tileproxy I could fly on every aircraft keeping sharp textures. After some days teaking FSX, I´m almost to give up from Megascenery Earth.

I can only get full sharp resolutions if I stop the aircraft, then, slowly, texture high resolution around the aircraft begins to improve to the maximum quality.

Fiber parameter is set to 0.70 already.

I increased Lod radius to 9.0 and even to 15 and this improved a lot, but I get Out of memory crashes. FSX is a thing that when it begins to get good it crashes...

 

Dihelson, welcome back. Ive never used MSE and so I have no idea how it looks and feels on my PC. But in regards to blurry textures, sharpness and having to pause your flight just so FSX catches up with loading scenery sounds just like the same problem I had some years ago. One way I had to resolve these issues was by  properly organizing my scenery.cfg file which is located by default in C:\ProgramData\Microsoft\FSX. I have noticed that FSX makes weird adjustments when ever a new scenery is installed and this causes the numbered sequence to get a bit out of whack. There is a tool call FSTscenery.exe from Steve Greenwood http://www.simforums.com/forums/uploads/12417/FSTscenery.zip. This tool does wonders for me and it seems I need to use it everytime I install new scenery or have to organize my scenery area as per developer installation instructions. Anyways, I found that running this executable does fix the numbered sequence and gets rid of my blurries. However with MSE, I don't know if this would work for you, but its the Holy Grail for my FSX configuration.

 

I'm also running FSX on a 500GB SSD drive and it runs beautifully, however my understanding is that their should be some 10%-15% of available space on that drive so that it continues to run efficiently. You mentioned yours is almost full. My Samsung Magician software recommends Over Provisioning (46.5GB) so that it helps manage functionality of he drive. Did you do this by chance?

 

Also, try to get you hands on the Scenery Configuration Editor at http://sourceforge.net/projects/fs-sceditor/. This is a nifty little tool almost every FSX simmer is using. It quickly enables/disables only the scenery you want to use right from your desktop and definitely help frees up FSX resources. Hope this helps.

 

Troy

H

 

Dihelson, welcome back. Ive never used MSE and so I have no idea how it looks and feels on my PC. But in regards to blurry textures, sharpness and having to pause your flight just so FSX catches up with loading scenery sounds just like the same problem I had some years ago. One way I had to resolve these issues was by  properly organizing my scenery.cfg file which is located by default in C:\ProgramData\Microsoft\FSX. I have noticed that FSX makes weird adjustments when ever a new scenery is installed and this causes the numbered sequence to get a bit out of whack. There is a tool call FSTscenery.exe from Steve Greenwood http://www.simforums.com/forums/uploads/12417/FSTscenery.zip. This tool does wonders for me and it seems I need to use it everytime I install new scenery or have to organize my scenery area as per developer installation instructions. Anyways, I found that running this executable does fix the numbered sequence and gets rid of my blurries. However with MSE, I don't know if this would work for you, but its the Holy Grail for my FSX configuration.

 

I'm also running FSX on a 500GB SSD drive and it runs beautifully, however my understanding is that their should be some 10%-15% of available space on that drive so that it continues to run efficiently. You mentioned yours is almost full. My Samsung Magician software recommends Over Provisioning (46.5GB) so that it helps manage functionality of he drive. Did you do this by chance?

 

Also, try to get you hands on the Scenery Configuration Editor at http://sourceforge.net/projects/fs-sceditor/. This is a nifty little tool almost every FSX simmer is using. It quickly enables/disables only the scenery you want to use right from your desktop and definitely help frees up FSX resources. Hope this helps.

 

Troy

 

Hello, Troy, thanks for your nice suggestion. You gave me nice ideas. I was just suspecting about my scenery.cfg because Tileproxy created large number of entries, and may even when not used, every scenery takes too long to load, specially when I installed MSE, so may be kind of a conflict. In order to test this, perhaps I would have to install FSX from scratch and test with a single MSE scenery or test your suggestions and softwares. I see it looks almost impossible to have all scenery activated at the same time in order to fly without limitations. Perhaps one should choose which sceneries should be active before a flight. I´ll make some tests and come back to discuss further. Thank you very much, perhaps you are right and that will be a solution. Let´s see...

Here is an example of the problem. Notice that areas near the aircraft is blurry and areas away is sharp ( Logic would suggest the contrary ). I tried to post on my last post, but couldn´t edit the message.

 

 

Another example:

 

 

 

1 minute later:

 

 

It would be interesting if we could set PRIORITIES on loading textures: First ( sharp ) on areas near aircraft, and later, areas far away from aircraft. What matter having sharp areas away when near is blurry ? It is valid to notice that this is happening ONLY with Megascenery Earth. This doesn´t happen for instance with Switzerland photoscenery, or FranceVFR. Strange, no ?

One of the biggest causes of blurries is running with unlimited frames. If you are doing so, try locking at 30 inside FSX. Set FFTF to 0.33 in FSX cfg, set autogen to sparse for photo scenery. Then of course simply reduce other aspects of the FSX settings to help reduce the load on the CPU.

 

I don't often use photo scenery, but in addition to what the guys have said about the higher LOD, I personally have seen improvements by using these suggestions.

 

BTW, ref the blurry issue being more pertinent to MSE and not other sceneries, it may simply be a case that the MSE sceneries are a higher resolution. Also, and I'm only throwing this out there as I have no idea, but it may also be that MSE loads larger photo tiles as opposed to other photo sceneries, just a thought.

One of the biggest causes of blurries is running with unlimited frames. If you are doing so, try locking at 30 inside FSX. Set FFTF to 0.33 in FSX cfg, set autogen to sparse for photo scenery. Then of course simply reduce other aspects of the FSX settings to help reduce the load on the CPU.

 

I don't often use photo scenery, but in addition to what the guys have said about the higher LOD, I personally have seen improvements by using these suggestions.

 

BTW, ref the blurry issue being more pertinent to MSE and not other sceneries, it may simply be a case that the MSE sceneries are a higher resolution. Also, and I'm only throwing this out there as I have no idea, but it may also be that MSE loads larger photo tiles as opposed to other photo sceneries, just a thought.

 

Hello, Rockliffe, thanks for the nice comment about this issue. Indeed, I run with FPS locked to 30 inside FSX and with nVidia inspector set to 1/2 vertical refresh of the 60hz monitor, which gives incredible stability to the FPS and other settings on nVidia which eliminated all kinds of stutters and flickering. The set of FFTF to 0.33 was the initial value, so I pushed to 0.7 in order to give more priority to CPU to texture loading, just trying to solve this problem. 

 

Here´s some other important parameters set in msx.cfg:

 

TEXTURE_BANDWIDTH_MULT=40

TextureMaxLoad=12

TransitionTime=4.000000

UPPER_FRAMERATE_LIMIT=30

HIGHMEMFIX=1

IMAGE_QUALITY=0

TEXTURE_MAX_LOAD=1024

TEXTURE_QUALITY=3

SHADER_CACHE_PRIMED_10=1693458432

SHADER_CACHE_PRIMED=1693458432

...

[bufferPools]

RejectThreshold=131072

...

FIBER_FRAME_TIME_FRACTION=0.70

...

[JOBSCHEDULER]

AffinityMask=84

...

[TERRAIN]

AUTOGEN_DENSITY=2

DETAIL_TEXTURE=1

LOD_RADIUS=9.000000

MESH_COMPLEXITY=100

MESH_RESOLUTION=25

SWAP_WAIT_TIMEOUT=2

TEXTURE_RESOLUTION=29

WATER_EFFECTS=4

 

See I raised LOD_RADIUS to 9 and it improved a lot, but I don´t know if VAS ( Virtual memory used by FSX would support, sometimes I get out of memory errors, but so far, so good. ( Indeed, I installed microsoft software named PROCESS EXPLORER, but it doesn´t show VAS correctly, only display 2k ( ajajaja ).

Now, I deactivated almost all scenery leaving only the basics and MSE Illinois and noticed that it improved. Along with Lod-radius=9.000000 it´s very good, but I have to make some more tests activating other scenery, that´s when the problem rise...looks like the quantity of installed scenery or the active ones affect the problem.

 

 

One of the biggest causes of blurries is running with unlimited frames. If you are doing so, try locking at 30 inside FSX.

 

To me it seems to work exactly the opposite, when I had frames limited to 30 inside FSX I got a lot of blurries (not to even mention severely lower FPS). 

 

When set frames to unlimited inside FSX & then locked them to 30 using external FPS limiter everything works fine. Don't know if that's because I'm using ATI card, anyway I think using an external limiter instead of the internal one is worth trying. 

To me it seems to work exactly the opposite, when I had frames limited to 30 inside FSX I got a lot of blurries (not to even mention severely lower FPS).

 

When set frames to unlimited inside FSX & then locked them to 30 using external FPS limiter everything works fine. Don't know if that's because I'm using ATI card, anyway I think using an external limiter instead of the internal one is worth trying.

 

Hi matey, sure, that is often the case and seems to be dictated very much to an individual's hardware setup. Interesting the way things work. I have always suffered with more blurries in FSX with frames set at unlimited, but in P3d, the sim was unflyable at any setting other than set at unlimited!

Here´s some other important parameters set in msx.cfg:

 

TEXTURE_BANDWIDTH_MULT=40

TextureMaxLoad=12

TransitionTime=4.000000

UPPER_FRAMERATE_LIMIT=30

HIGHMEMFIX=1

IMAGE_QUALITY=0

TEXTURE_MAX_LOAD=1024

TEXTURE_QUALITY=3

SHADER_CACHE_PRIMED_10=1693458432

SHADER_CACHE_PRIMED=1693458432

...

[bufferPools]

RejectThreshold=131072

...

FIBER_FRAME_TIME_FRACTION=0.70

...

[JOBSCHEDULER]

AffinityMask=84

...

[TERRAIN]

AUTOGEN_DENSITY=2

DETAIL_TEXTURE=1

LOD_RADIUS=9.000000

MESH_COMPLEXITY=100

MESH_RESOLUTION=25

SWAP_WAIT_TIMEOUT=2

TEXTURE_RESOLUTION=29

WATER_EFFECTS=4

 

See I raised LOD_RADIUS to 9 and it improved a lot, but I don´t know if VAS ( Virtual memory used by FSX would support, sometimes I get out of memory errors, but so far, so good. ( Indeed, I installed microsoft software named PROCESS EXPLORER, but it doesn´t show VAS correctly, only display 2k ( ajajaja ).

Now, I deactivated almost all scenery leaving only the basics and MSE Illinois and noticed that it improved. Along with Lod-radius=9.000000 it´s very good, but I have to make some more tests activating other scenery, that´s when the problem rise...looks like the quantity of installed scenery or the active ones affect the problem.

Have you managed to get any more improvements with your blurries Dihelson?

 

It will also be helpful to assign more texture loaders. AffinityMask=84 only gives you 2 texture loaders and that is not enough if you want to fly fast over photo scenery. Try AffinityMask=249. That gives you 5 texture loaders and is what got me best texture loading when I had a quad core i7 (with hyperthreading active). Watch the CPU temperatures though as it will be a lot hotter compared to AM=84.

 

My current system has a 6core i7 that I normally run with 9 texture loaders for best MSE experience. Having red this thread I tried flying around New Hampshire and Vermont a bit using AM=84 tonight and boy do I notice a difference. You can't fly fast at all before the ground goes blurry using only 2 texture loaders, and it takes ages for it to catch up when you slow down as well.

 

One analogy I can make is a bucket of water with a hole in the bottom. When you start a flight the bucket of water is full (you have all textures as sharp as they can be).

 

As you fly forward the water level in the bucket lowers (you get blurrier textures). The faster you fly, the larger the hole in the bottom gets. If you stop, the hole gets plugged. To avoid the water level in the bucket to get too low (blurry textures) you have to top it up as you fly along.

 

You fill the bucket with a tap (a texture loader), but once that tap is open at full flow it can't fill the bucket any quicker. If the hole in the bottom is too large (you fly too fast) if won't even fill the bucket. It will just drain slower.

 

What you could do is using a larger bucket (using a higher LOD setting). That will make the time it takes before the water is running low longer, but unless the drain hole in the bottom is smaller that what the tap can fill, the water will eventually run low.

 

At that point, even when you plug the hole it's gonna take a long while to fill that large bucket again. It's actually quicker to fill up the smaller bucket when the hole is plugged.

 

What you do need though is more taps over the bucket (more texture loaders). If you have 5 taps open at full flow over that bucket you can have a larger hole in the bottom of the bucket without the water level getting low and if it does you'll fill up the bucket quickly again when you plug it. Even if the bucket is large.

 

Your CPU decides how many taps you have. The AffinityMask is what decides which taps you open over the bucket. The LOD setting is the size of the bucket.

 

I hope it makes some sense.

Have you managed to get any more improvements with your blurries Dihelson?

 

It will also be helpful to assign more texture loaders. AffinityMask=84 only gives you 2 texture loaders and that is not enough if you want to fly fast over photo scenery. Try AffinityMask=249. That gives you 5 texture loaders and is what got me best texture loading when I had a quad core i7 (with hyperthreading active). Watch the CPU temperatures though as it will be a lot hotter compared to AM=84.

 

My current system has a 6core i7 that I normally run with 9 texture loaders for best MSE experience. Having red this thread I tried flying around New Hampshire and Vermont a bit using AM=84 tonight and boy do I notice a difference. You can't fly fast at all before the ground goes blurry using only 2 texture loaders, and it takes ages for it to catch up when you slow down as well.

 

One analogy I can make is a bucket of water with a hole in the bottom. When you start a flight the bucket of water is full (you have all textures as sharp as they can be).

 

As you fly forward the water level in the bucket lowers (you get blurrier textures). The faster you fly, the larger the hole in the bottom gets. If you stop, the hole gets plugged. To avoid the water level in the bucket to get too low (blurry textures) you have to top it up as you fly along.

 

You fill the bucket with a tap (a texture loader), but once that tap is open at full flow it can't fill the bucket any quicker. If the hole in the bottom is too large (you fly too fast) if won't even fill the bucket. It will just drain slower.

 

What you could do is using a larger bucket (using a higher LOD setting). That will make the time it takes before the water is running low longer, but unless the drain hole in the bottom is smaller that what the tap can fill, the water will eventually run low.

 

At that point, even when you plug the hole it's gonna take a long while to fill that large bucket again. It's actually quicker to fill up the smaller bucket when the hole is plugged.

 

What you do need though is more taps over the bucket (more texture loaders). If you have 5 taps open at full flow over that bucket you can have a larger hole in the bottom of the bucket without the water level getting low and if it does you'll fill up the bucket quickly again when you plug it. Even if the bucket is large.

 

Your CPU decides how many taps you have. The AffinityMask is what decides which taps you open over the bucket. The LOD setting is the size of the bucket.

 

I hope it makes some sense.

 

Hello, SAAB340,

 

I just saw your nice answer and explanation of the way FSX loads texture. Thank you, Thank you so much! Indeed I changed now Affinity Mask to 249 and I notice an improvement on loading textures, certainly, I can fly at higher speeds, but perhaps could be better, one problem persists, which it should have a priority of loading textures UNDER the aircraft, or on it´s path. It happens that I like to view from outside the aircraft, and although there´s much sharper textures away from the aircraft, most of the time just under it there´s a delay or lack of priority, so it´s one of the last places where I view it sharp most of the time. My LOD_RADIUS=6.500000  and I can´t make it higher, because I get memory error. Sometimes, with other kind of scenery I could get 9 or 10 and it´s fantastic, but on everyday use it doesn´t work right, have you any idea on how to solve this ?

 

I have another question, please describe your machine better, i7 6 cores ? running at what speed ? What CPU brand ? What machine description ?

Now I run an i7 2600k at 4.8Ghz with a Corsair H100i water cooler, temperature is not a problem, even at full 100% CPU use, so we could push more. With current configuration, and affinity mask to 249 I get 75% use of CPU ( with 84 I got 40% or 50% of CPU use ). 

 

This is my FSX config file, I hope you could point to some improvements I could make on it yet, and I thank you in advance:

 

...........................................................................................................................................

// This file was tweaked on Apr 21, 2014 at 05:50 GMT using Bojote's automated FSX 

 

Tweaking & Tuning Service

// Your 'original' fsx.CFG file was backed up at 

 

http://www.venetubo.com/fsx/8c420b408a920c183408edcf9608bbd1/backup/fsx_backup.cfg

// This file is optimized as follows: 8 core(s), CPU speed 5, HT 1, GPU 4, PREF 2

// You can visit Bojote's FSX Tweaking & Tuning service at 

 

http://www.venetubo.com/fsx.html

[bufferPools]

RejectThreshold=131072

[VirtualCopilot]

VirtualCopilotActive=1

[sOUND]

AmbientUI=1

AmbientUIMusicVolume=-6.000000

PrimaryDevice={00000000-0000-0000-0000-000000000000}

SOUND=1

SOUND_LOD=1

SOUND_QUALITY=2

UISound=1

VoiceDevice={00000000-0000-0000-0000-000000000000}

[slewTextInfo.1]

AirSpeed=1,5

Altitude=1,3

Heading=1,4

Latitude=1,1

Longitude=1,2

[AContain]

LabelColor=FFFF0000

LabelDelay=1000

ShowLabelAirline=0

ShowLabelAirlineAndFlightNumber=0

ShowLabelAirspeed=0

ShowLabelAltitude=1

ShowLabelContainerId=0

ShowLabelDistance=1

ShowLabelFlightPlan=0

ShowLabelHeading=0

ShowLabelManufacturer=1

ShowLabelModel=1

ShowLabelTailNumber=0

ShowLabels=1

ShowUserLabel=0

[ATC]

AutoOpenAirTrafficWindow=1

COMM_MSG_AI_ATC_COLOR=FFFF7840

COMM_MSG_ATC_AI_COLOR=FF00FF00

COMM_MSG_ATC_USER_COLOR=FFB6FFB6

COMM_MSG_NONE_COLOR=FFFFFFFF

COMM_MSG_USER_ATC_COLOR=FFFFD21B

PilotVoice=0

ShowATCText=1

UsePilotVoice=1

[TextInfo.1]

AirSpeed=1,5

Altitude=1,3

Heading=1,4

Latitude=1,1

Longitude=1,2

WindDirectionAndSpeed=1,6

[iNTERNATIONAL]

ASLAT=2

ASLON=1

MEASURE=0

[CONTROLS]

Controls_Current=Standard

Controls_Default=Standard

KBDAIL=64

KBDELEV=64

KBDRUD=64

[FACILITIES]

CITY=Hartford

COUNTRY=United States

GTL_BUTTON=1252

STATE=Connecticut

[TextInfo.3]

AirSpeed=1,5

Altitude=1,3

FrameRate=2,1

FuelPercentage=2,4

GForce=2,3

Heading=1,4

Latitude=1,1

LockedFrameRate=2,2

Longitude=1,2

WindDirectionAndSpeed=1,6

[PointOfInterestSystem]

CycleSetting=0

[GRAPHICS]

AC_SELF_SHADOW=1

AIRCRAFT_REFLECTIONS=1

AIRCRAFT_SHADOWS=1

ALLOW_SHADER_30=1

COCKPIT_HIGH_LOD=1

D3D10=0

EFFECTS_QUALITY=0

ForceFullScreenVSync=1

ForceWindowedVSync=1

GROUND_SHADOWS=1

HIGHMEMFIX=1

IMAGE_QUALITY=0

LANDING_LIGHTS=1

NUM_LIGHTS=8

See_Self=1

TEXTURE_MAX_LOAD=1024

TEXTURE_QUALITY=3

Text_Scroll=1

SHADER_CACHE_PRIMED_10=1693458432

SHADER_CACHE_PRIMED=1693458432

[TrafficManager]

AIRPORT_SCENERY_DENSITY=0

AirlineDensity=0

FreewayDensity=0

GADensity=0

IFROnly=0

LeisureBoatsDensity=4

ShipsAndFerriesDensity=0

[DynamicHeadMovement]

HeadMoveTimeConstant=1.000000

LonAccelOnHeadLon=-0.020000

LonAccelOnHeadPitch=-0.010000

MaxHeadAngle=5.000000

MaxHeadOffset=0.300000

RollAccelOnHeadLat=0.010000

RollAccelOnHeadRoll=0.100000

YawAccelOnHeadLat=-0.100000

[DISPLAY.Device.NVIDIA GeForce GTX 780.0]

Anisotropic=1

Mode=1920x1080x32

AntiAlias=1

[REALISM]

AutoCoord=True

AutoTrim=False

CrashDetection=False

CrashTolerance=0.000000

CrashWithDyn=False

GEffect=False

General=0.000000

GyroDrift=False

GyroEffect=0.000000

ManualLights=False

PFactor=0.000000

RealMixture=False

StressDamage=False

Torque=0.000000

TrueAirspeed=False

UnlimitedFuel=True

[Weather]

AdjustForMagVarInDialog=1

CLOUD_COVERAGE_DENSITY=8

CLOUD_DRAW_DISTANCE=3

DETAILED_CLOUDS=1

DisableTurbulence=0

DownloadWindsAloft=0

DynamicWeather=0

MaxGustRampSpeed=200

MaxGustTime=500

MaxVarRampSpeed=75

MaxVarTime=50

MinGustRampSpeed=1

MinGustTime=10

MinVarRampSpeed=10

MinVarTime=5

THERMAL_VISUALS=0

TurbulenceScale=1.000000

WeatherGraphDataInDialog=0

WeatherServerAddress=fs2k.zone.com

WeatherServerPort=80

WindshieldPrecipitationEffects=1

[Misc]

Com_Rate=7

[Main]

FIBER_FRAME_TIME_FRACTION=0.70

HideMenuFullscreen=1

HideMenuNormal=0

Location=0,0,1920,1080,\\.\DISPLAY1

Maximized=1

SimObjectPaths.0=SimObjects\Airplanes

SimObjectPaths.1=SimObjects\Rotorcraft

SimObjectPaths.2=SimObjects\GroundVehicles

SimObjectPaths.3=SimObjects\Boats

SimObjectPaths.4=SimObjects\Animals

SimObjectPaths.5=SimObjects\Misc

User Objects=Airplane, Helicopter

ProcSpeed=11909

PerfBucket=7

[Trusted]

C:\Program Files (x86)\myoddweb\courseplanner

 

\FSConnectorDll.dll.rhbtukinnnwbonczzqhowkrcoqaoltckaiiqneoa=-1

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Aerosoft

 

\ASE_DATA\AseData.dll.czuozzuntzieonrqwzktkckakhibkkrwtknnttch=-1

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FS_Earth

 

\fs_earth.dll.czhwerzkrazkelqtwrrkcwznknouczickctcehhl=-1

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES

 

\Bell_206B.DLL.twuqauuklihlluqrkhatbhqcltqcihwneqwnwbbr=2

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES

 

\Bendix_King_Radio.DLL.ltawhhlwbhnawteenlrnkluweoneckallcbnzabl=2

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES

 

\Cessna.DLL.oorurbqorokkwqtiulakunnrwruaqancbilaoarl=2

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES

 

\Cessna172.DLL.buzznwethuhknuahcrihurruohlnkatecbchweot=2

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES

 

\Cessna182s.DLL.waliohhwwtqznwlwwzeakzbuiqznctkkoeuaabqr=2

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES

 

\CessnaWAlpha.DLL.euniwubceariihbqnahiwaqiibbklinrlkkozoti=2

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules

 

\FSUIPC4.dll.ibciuartkktterzeqillzqiwreknaoqibnnknowt=-1

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_AU

 

\FTXAA_YBCS\scenery\ObjectFlow_YBCS.dll.whzhaknqrkbbuekrzkucbuqnulzkhnqhhnircwko=1

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NZ

 

\FTX_NZNI_05_SCENERY\scenery

 

\ObjectFlow_NZNI.dll.iaqzlteqcntqbzzqwqnoutenzbbzcwruzwcihuwn=1

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs

 

\PMDG_HUD_interface.dll.rbnztaunrikiiuilataiahkiaaocnwcuqaeteiab=-1

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare

 

\ViMaCoreX.dll.ccnonhbnheeqnehkqwatqbnotkocuooabiubtcni=-1

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES

 

\BoeingGeneric.DLL.toteaircutrkokhkhrcakilllzozockwnkhoiurn=2

F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES

 

\Magnetic_Compass.DLL.rloitnazezentrqkqrenekeueowoanhieorblzae=2

[TextInfo.2]

FrameRate=1,1

FuelPercentage=1,4

GForce=1,3

LockedFrameRate=1,2

[uSERINTERFACE]

Map_Orientation=2

OpenATCOnCreate=0

PAUSE_ON_LOST_FOCUS=0

PROMPT_ON_EXIT=1

PageID=1

SHOW_MISSION_CAPTIONS=0

SITUATION=C:\Users\dihelson\Documents\Flight Simulator X Files\DIH - St Louis 02

ShowAllACPaintSchemes=1

SelectAircraftManufacturer=All

SelectAircraftPublisher=All

SelectAircraftType=All

[sIM]

SYSCLOCK=1

[Display]

ActiveWindowTitleBackGroundColor=0,28,140,64

ActiveWindowTitleTextColor=255,255,255

BLOOM_EFFECTS=0

ChangeTime=4.000000

InfoBrakesEnable=True

InfoLowerLeftBackGroundColor=255,0,0,128

InfoLowerLeftTextColor=255,255,255

InfoLowerRightBackGroundColor=255,0,0,128

InfoLowerRightTextColor=255,255,255

InfoOverspeedEnable=True

InfoParkingBrakesEnable=True

InfoPauseEnable=True

InfoSlewEnable=True

InfoStallEnable=True

InfoUpperRightBackGroundColor=0,0,0,0

InfoUpperRightTextColor=255,0,0

NonActiveWindowTitleBackGroundColor=24,33,87,64

NonActiveWindowTitleTextColor=255,255,255

SKINNED_ANIMATIONS=0

TEXTURE_BANDWIDTH_MULT=400

TextureMaxLoad=12

TransitionTime=4.000000

UPPER_FRAMERATE_LIMIT=30

WideViewAspect=False

[JOBSCHEDULER]

AffinityMask=249

[slewTextInfo.3]

AirSpeed=1,5

Altitude=1,3

FrameRate=2,1

Heading=1,4

Latitude=1,1

LockedFrameRate=2,2

Longitude=1,2

[WeatherMap]

SHOW_AIRPORTS=0

SHOW_AIRSPACE=0

SHOW_APPROACHES=0

SHOW_DATATAGS=1

SHOW_FLIGHTPLAN=1

SHOW_INTERSECTIONS=0

SHOW_JET=0

SHOW_NDBS=0

SHOW_TERRAIN=1

SHOW_VICTOR=0

SHOW_VORS=0

SHOW_WEATHERSTATIONS=1

SHOW_WEATHERSYSTEMS=1

[PANELS]

DEFAULT_VIEW=0

IMAGE_QUALITY=1

PANEL_MASKING=1

PANEL_OPACITY=100

PANEL_STRETCHING=1

QUICKTIPS=0

UNITS_OF_MEASURE=0

[sTARTUP]

DEMO=0

LoadWindow=1

SHOW_OPENING_SCREEN=1

STARTUP_DEMO=0

[slewTextInfo.2]

FrameRate=1,1

LockedFrameRate=1,2

[TERRAIN]

AUTOGEN_DENSITY=2

DETAIL_TEXTURE=1

LOD_RADIUS=6.500000

MESH_COMPLEXITY=100

MESH_RESOLUTION=22

SWAP_WAIT_TIMEOUT=2

TEXTURE_RESOLUTION=25

WATER_EFFECTS=4

[sCENERY]

DAWN_DUSK_SMOOTHING=1

IMAGE_COMPLEXITY=5

LENSFLARE=1

MAX_ASYNC_BATCHING_JOBS=3

SmallPartRejectRadius=4.0

[MAPVIEW_MAP]

SHOW_AIRPORTS=1

SHOW_VORS=1

SHOW_NDBS=1

SHOW_APPROACHES=0

SHOW_INTERSECTIONS=0

SHOW_VICTOR=0

SHOW_JET=0

SHOW_AIRSPACE=0

SHOW_FLIGHTPLAN=0

SHOW_WEATHERSTATIONS=1

SHOW_WEATHERSYSTEMS=1

SHOW_DATATAGS=1

SHOW_TERRAIN=1

show_flight_history=0

[FlightPlanMap]

LineWidth=2

SHOW_AIRPORTS=1

SHOW_VORS=1

SHOW_NDBS=1

SHOW_APPROACHES=1

SHOW_INTERSECTIONS=1

SHOW_VICTOR=0

SHOW_JET=0

SHOW_AIRSPACE=1

SHOW_FLIGHTPLAN=1

SHOW_WEATHERSTATIONS=1

SHOW_WEATHERSYSTEMS=1

SHOW_DATATAGS=1

SHOW_TERRAIN=1

show_waypoints=1

show_airways=1

show_markers=1

show_volume_boundaries=1

show_ac_twr=1

[MULTIPLAYER]

condAccoutPassword=0

BTW, SAAB340, before I forget to ask: How can I push to run with 9 texture loaders instead of 5 with affinity mask 249 ???

 

Thanks in advance

BTW, SAAB340, before I forget to ask: How can I push to run with 9 texture loaders instead of 5 with affinity mask 249 ???

 

Thanks in advance

Unfortunately you can't on your 2600K. You need a 6-core CPU with hyper threading for that. I use a SandyBridge-E 3930K @4.3GHz.

 

I notice that you use reject threshold and not BP=0 in your cfg. (you might have a reason). BP=0 does help a little with texture loading as well.

 

Having the photo scenery on a SSD instead of a HDD is next on the list to improve on textureloading now that you make use of hyperthreading with help of the affinity mask. SSDs does help a lot more than I've previously been able to show. I'm currently at the end phase of testing texture loading between WD Green, Black, Velociraptor, Seagate SSHD and Samsung 840EVO. I will soon post my full findings. All the HDDs and the SSD have been properly tested but the SSHD needs hours and hours of extra time to get good data from...

 

Some times affinitymask 244 will actually give you better textureloading than 249 even though it actually gives you one less texture loader. That's cause FSX has one Main-thread and several texture loader, all allocated with the affinity mask. But it also has another thread running that isn't controlled by the affinitymask that as far as I can understand is responsible for scenery loading and loading textures that arn't ground textures. Stalling/slowing down this thread will also stall ground texture loading just as stealing resources from the main thread would slow down texture loading as well as FPS. That's why its not desirable to ever have 100% CPU load in taskmanager when running FSX on a hyperthreaded CPU. That's why you have to leave at least 2 unassigned cores with the affinitymask. Depending on your other addons leaving 3 unassigned cores with AM244 will work better than AM249

 

There's nothing we can do about the order FSX loads the texture tiles I'm afraid. In general they are loaded north to south and as you fly forward it will skip tiles and start sharpning tiles were it thinks its best in order for things not to get too blurry down route. The FSX engine is designed to be able to handle everything from slow taxi on the ground to be in fast orbit high above earth.

 

I hope something made sense. =)

There's no way to get around the OutOfMemory as the LOD value is increased. Its a very hard limitation of FSX being a 32bit program. As long as you use 64bit windows and have 4GB RAM or morre there's nothing you can do really. Using less addons, less complex aircraft together with your photo scenery would let you use a higher LOD setting, but its only about prioritising on what you want to use your maxmum of 4GB virtual address space on. Airports, weather, aircraft, traffic, photo scenery? We can't have it all unfortunatly as when we hit the 4GB limit the OOM error will happen.