Search the Community

Dear Simmers, I've been reading a lot of information regarding tips and tricks to get the most out of FSX. To be honest it gets very confusing as there's too many opinions differing from each other. I recently got a very nice built but it seems my specs aren't enough to get the most out of FSX without doing additional tweaking or tuning. My CPU: - PROCESSOR:Intel Core i7-990X BX80613I7990X Processor Extreme Edition - Six Core, 12MB L3 Cache, 1.5MB L2 Cache, 3.46 GHz (3.73 GHz Max Turbo). - MOTHERBOARD: GIGABYTE G1.Assassin Intel X58 Motherboard - ATX, Socket B (LGA1366), Intel X58 Chipset, 2200MHz DDR3, SATA 6.0 Gb/s, RAID, 7.1-CH Audio, CrossFireX/SLI Ready, Gigabit LAN, USB 3.0. - VIDEO CARDS: 2 (two) GTX-570, 2.5 GB each. - MEMORY: 12GB, DDR3, 2000 MHZ. - HARD DRIVE: Western Digital WD1002FAEX Caviar Black Hard Drive - 1TB, 7200RPM, 64MB, SATA 6G. - Windows 7, 64 Bits Now the question is, which of the following tips should I follow to get the most out of FSX based on the above specifications. As previously mentioned, there are too many opinions and maybe some of the ones I read are out of date. 1.- Bojote's Tweak Vs. Buying Xtreme FSX PC V2: Is Bojote's tweak enough for boosting performance? Is it worth spending money on Xtreme FSX? Which one will give more FPS´s? 2.- Downloading Shader Model 3 from Bojote Vs. Buying Mogwaisoft Shade: Do I need both? Is there any difference between them? What is the purpose of the shader? Will I get more FPS? 3.- Overclocking the CPU: Will I really boost performance by overclocking the CPU up to 4.5GHZ. Will the CPU get overheated? Is this really necessarily? 4.- Disk Defrag: I've heard of the O&O Defrag. Some say is good, some say is useless. Would any defrag work? Should I defrag the whole dics or just FSX's folder? 5.- FPS Limiter 0.2: Can someone please explain what is this? Will this limit the FPS outside the FSX? Should I set the FPS in the FSX to "unlimited"? 6.- NVIDIA Inspector:What is it with this tool? I really don't understand the following statement (taken out of this forum): " Make your CPU do all the work that it can. Use "Nvidia Inspector" for AA settings ..ect NOT FSX. Turn off AA in FSX and drop Filtering to Trilinear." I'm really not an expert in this topics. Even though I've been using FS for more than 15 years, I've never tweaked nor tuned anything in the program. I just thought that by buying a computer with such specs would make the simulator run completely smooth, but with my add ons and graphic settings sometimes the FPS comes down to 10 (which is unacceptable for the money I spent). Please help me on this. Thanks

I get a message pop-up from FSX on load telling me the drivers for my secondary gfx card (5770) need updating. It's annoying so to prevent it from popping up I simply remove the display device listing from FSX.cfg. Well if I edit the graphics options within FSX of course it changes the .cfg and re-adds the display device entries. So I went in today to remove them again and actually bothered to look at them instead of just highlighting it all and deleting and noticed there are a lot of settings that don't show for my main display. Dunno why I didn't take note before: [DISPLAY.Device.ATI Radeon HD 5700 Series.3]Mode=1024x720x32Disable=1Filter=0Dither=0MipMap=0Fog=0FullScreenFiltering=0VolShadow=0SoftShadow=0AnimWater=0Water20=0VolTexture=0TnL=0DXTn=0TextureForce=0PanelAsTexture=0TEXBEM=0UseShaders=0TableFog=0Shader20Plus=0 Woah. What do they all mean? I did some searching of the individual properties but nothing came up except matches to other people's posted .cfg files that included them. Here's my main display profile: [DISPLAY.Device.ATI Radeon HD 5800 Series.0]Anisotropic=1Mode=1680x1050x32AntiAlias=1 Can I apply any of the above to here for any effect? If no one knows I'll probably experiment... guessing if it hasn't been discussed already it's probably nothing though.

Hello, I noticed today that wing flex wasn't displaying on some aircraft, and sure enough, when I looked at the settings, "Advanced Animations" was unchecked. Thus, I re-checked it and then closed FSX so I could set the LOD Radius value back to where I keep it (which of course is reset down to 4.5 when you modify settings). However, when I re-opened FSX, I found that it was still unchecked. At first I thought this might have been caused by FSX Booster, which I use, but when I closed FSX and reopened it without closing and reopening FSX Booster or saving its settings (which causes FSX booster to modify the fsx.cfg file). However, my setting for Advanced Animations had still been overridden. What's going on? (and what is the variable for advanced animations in the fsx.cfg file, too. That might help.)Thanks,boeing247

Just updated my mobo/ram/gpu/cpu. Still trying to get things stable. I am experiencing some CTDs in Orbx PNW. I didn't reinstall windows or FSX; rather, I upgraded parts and tried to follow Word Not Allowed's guide. [bufferPools] Poolsize=0 [JobScheduler] AffinityMask=14 [LANGUAGE] DLL=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\language.dll [GRAPHICS] ForceFullScreenVSync=1 HIGHMEMFIX=1 STALE_BUFFER_THRESHOLD=26 SHADER_CACHE_PRIMED_10=1693500672 SHADER_CACHE_PRIMED=1693500672 D3D10=0 TEXTURE_MAX_LOAD=4096 NUM_LIGHTS=8 AIRCRAFT_SHADOWS=0 AIRCRAFT_REFLECTIONS=1 COCKPIT_HIGH_LOD=1 LANDING_LIGHTS=1 AC_SELF_SHADOW=0 EFFECTS_QUALITY=2 GROUND_SHADOWS=0 TEXTURE_QUALITY=3 IMAGE_QUALITY=0 See_Self=1 Text_Scroll=1 [sOUND] AmbientUIMusicVolume=-6.000000 SOUND_FADER1=0.500000 SOUND_FADER2=0.500000 SOUND_FADER3=0.500000 SOUND_FADER4=1.000000 AmbientUIMusic=FSX01 PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03} VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03} SOUND=1 SOUND_QUALITY=2 SOUND_LOD=0 UISound=1 AmbientUI=0 [Display] ChangeTime=0.000000 TransitionTime=0.000000 ActiveWindowTitleTextColor=255,255,255 ActiveWindowTitleBackGroundColor=0,28,140,64 NonActiveWindowTitleTextColor=255,255,255 NonActiveWindowTitleBackGroundColor=24,33,87,64 InfoUpperRightTextColor=255,0,0 InfoUpperRightBackGroundColor=0,0,0,0 InfoLowerLeftTextColor=255,255,255 InfoLowerLeftBackGroundColor=255,0,0,128 InfoLowerRightTextColor=255,255,255 InfoLowerRightBackGroundColor=255,0,0,128 InfoBrakesEnable=False InfoParkingBrakesEnable=False InfoPauseEnable=True InfoSlewEnable=True InfoStallEnable=False InfoOverspeedEnable=False BLOOM_EFFECTS=0 SKINNED_ANIMATIONS=1 TEXTURE_BANDWIDTH_MULT=40 UPPER_FRAMERATE_LIMIT=30 WideViewAspect=True [Main] User Objects=Airplane, Helicopter SimObjectPaths.0=SimObjects\Airplanes SimObjectPaths.1=SimObjects\Rotorcraft SimObjectPaths.2=SimObjects\GroundVehicles SimObjectPaths.3=SimObjects\Boats SimObjectPaths.4=SimObjects\Animals SimObjectPaths.5=SimObjects\Misc SimObjectPaths.6=SimObjects\UT2 Aircraft ProcSpeed=19434 PerfBucket=7 HideMenuNormal=0 HideMenuFullscreen=1 DisablePreload=1 //Fiber_Frame_Time_Fraction=0.25 //Maximized=1 //Location=440,130,1480,908,\\.\DISPLAY1 [PANELS] IMAGE_QUALITY=1 DEFAULT_VIEW=0 QUICKTIPS=1 PANEL_OPACITY=100 PANEL_MASKING=1 PANEL_STRETCHING=1 UNITS_OF_MEASURE=0 [Weather] WindshieldPrecipitationEffects=1 MinGustTime=10 MaxGustTime=500 MinGustRampSpeed=1 MaxGustRampSpeed=200 MinVarTime=5 MaxVarTime=50 MinVarRampSpeed=10 MaxVarRampSpeed=75 TurbulenceScale=0.500000 WeatherServerAddress=fs2k.zone.com WeatherServerPort=80 WeatherGraphDataInDialog=0 AdjustForMagVarInDialog=1 DynamicWeather=1 DownloadWindsAloft=0 DisableTurbulence=0 CLOUD_DRAW_DISTANCE=4 DETAILED_CLOUDS=1 CLOUD_COVERAGE_DENSITY=8 THERMAL_VISUALS=0 [DISPLAY.Device.NVIDIA GeForce GTX 680.0] Mode=1920x1080x32 Anisotropic=1 [AccelerationPack] ControlsFirstRun=0 HomePageFirstRun=0 [CONTROLS] Controls_Default=Standard Controls_Current=Standard KBDAIL=64 KBDELEV=64 KBDRUD=64 [TextInfo.1] Latitude=1,1 Longitude=1,2 Altitude=1,3 Heading=1,4 AirSpeed=1,5 WindDirectionAndSpeed=1,6 [TextInfo.2] FrameRate=1,1 LockedFrameRate=1,2 GForce=1,3 FuelPercentage=1,4 [TextInfo.3] Latitude=1,1 Longitude=1,2 Altitude=1,3 Heading=1,4 AirSpeed=1,5 WindDirectionAndSpeed=1,6 FrameRate=2,1 LockedFrameRate=2,2 GForce=2,3 FuelPercentage=2,4 [slewTextInfo.1] Latitude=1,1 Longitude=1,2 Altitude=1,3 Heading=1,4 AirSpeed=1,5 [slewTextInfo.2] FrameRate=1,1 LockedFrameRate=1,2 [slewTextInfo.3] Latitude=1,1 Longitude=1,2 Altitude=1,3 Heading=1,4 AirSpeed=1,5 FrameRate=2,1 LockedFrameRate=2,2 [Trusted] [DynamicHeadMovement] LonAccelOnHeadLon=-0.020000 LonAccelOnHeadPitch=-0.010000 RollAccelOnHeadLat=0.010000 YawAccelOnHeadLat=-0.100000 RollAccelOnHeadRoll=0.100000 MaxHeadAngle=5.000000 MaxHeadOffset=0.300000 HeadMoveTimeConstant=1.000000 [VirtualCopilot] VirtualCopilotActive=0 [uSERINTERFACE] ShowAllACPaintSchemes=1 SelectAircraftManufacturer=All SelectAircraftPublisher=All SelectAircraftType=All PageID=1 OpenATCOnCreate=0 SHOW_MISSION_CAPTIONS=0 PAUSE_ON_LOST_FOCUS=0 PROMPT_ON_EXIT=1 SITUATION=FLIGHTS\OTHER\FLTSIM Map_Orientation=2 DisplayFuelAsWeight=1 [ATC] ShowATCText=0 COMM_MSG_NONE_COLOR=FFFFFFFF COMM_MSG_ATC_USER_COLOR=FFB6FFB6 COMM_MSG_USER_ATC_COLOR=FFFFD21B COMM_MSG_ATC_AI_COLOR=FF00FF00 COMM_MSG_AI_ATC_COLOR=FFFF7840 AutoOpenAirTrafficWindow=1 UsePilotVoice=1 PilotVoice=0 [PointOfInterestSystem] CycleSetting=0 [sCENERY] LENSFLARE=1 DAWN_DUSK_SMOOTHING=1 IMAGE_COMPLEXITY=5 [TrafficManager] AirlineDensity=20 GADensity=18 FreewayDensity=10 ShipsAndFerriesDensity=10 LeisureBoatsDensity=10 IFROnly=0 AIRPORT_SCENERY_DENSITY=0 [TERRAIN] LOD_RADIUS=4.500000 MESH_COMPLEXITY=100 MESH_RESOLUTION=23 TEXTURE_RESOLUTION=27 AUTOGEN_DENSITY=3 DETAIL_TEXTURE=1 WATER_EFFECTS=6 TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=800 TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=700 [AContain] ShowLabels=0 ShowUserLabel=0 ShowLabelManufacturer=1 ShowLabelModel=1 ShowLabelTailNumber=0 ShowLabelDistance=1 ShowLabelAltitude=1 ShowLabelAirline=0 ShowLabelAirlineAndFlightNumber=0 ShowLabelFlightPlan=1 ShowLabelContainerId=0 ShowLabelAirspeed=0 ShowLabelHeading=0 LabelDelay=1000 LabelColor=FFFF0000 [iNTERNATIONAL] ASLAT=2 ASLON=1 MEASURE=0 [REALISM] PFactor=1.000000 Torque=1.000000 GyroEffect=1.000000 CrashTolerance=1.000000 General=1.000000 UnlimitedFuel=False AllowEngineDamage=False TrueAirspeed=False AutoCoord=False RealMixture=True StressDamage=False GEffect=True ManualLights=True GyroDrift=True CrashWithDyn=False CrashDetection=False AutoTrim=False [sIM] SYSCLOCK=1 [sTARTUP] DEMO=0 SHOW_OPENING_SCREEN=1 STARTUP_DEMO= LoadWindow=1 [FACILITIES] COUNTRY= STATE= CITY= GTL_BUTTON=1232 [Misc] Com_Rate=7 [MULTIPLAYER] condAccoutPassword=0

Hi All, After Re-Installing Windows because of some series of problems,I Installed fsx and tweaked it like before. But Now i'm experiencing strange behaviors: "Blurry Textures",but 'mostly' on pop-up 2D panels http://xum.ir/image/boMy http://xum.ir/image/boZ7 http://xum.ir/image/boZM http://xum.ir/image/boZb http://xum.ir/image/boZF http://xum.ir/image/boZn http://xum.ir/image/boZq p.s. my AA settings on graphics CP is 16X.

Hi every body, Something happens to my fsx.cfg , I do not know what. I need to rebuild my fsx.cfg or xml files. How I can do that?reinstall ? I'm lost snif snif :(

I don't know if this has ever been covered (Google and a forum search told me otherwise though), so in the worst case take it as a reminder or flame me for posting already known stuff. Anyway, did you know the you can easily run FSX in multiple configurations? All it takes is copying the FSX.exe and naming the copy, I don't know, FSX_Airliner.exe or so. FSX will then generate a fresh fsx_airliner.cfg in the configuration folder. Tweak fsx_airliner.cfg for flying airliners (no autogen, LOD_RADIUS=200000000000, no loaded helicopters or whatever). Finally, just create a short cut to FSX_Airliner.exe and that's it. You can do this for every scenario imaginable, like for easily switching between DX9 and DX10 or airline and GA flying or full fidelity and barebones for development or benchmarking or... (The scenery.cfg stays unaffected though.) (I, for myself, welcome my new "configuration possibility" overlord.)

Hey guys, I've been searching around and reading tons of helpful guides on using the Bufferpools tweaks in my fsx.cfg file. I've tried using UsePools=1/0, Poolsize=0/490000000 (and a few in between), as well as RejectedThreshold=131072. I've messed around with plenty of different combinations of the three, enabling one while the other is disabled, tweaking values of one or the other and testing, etc. However I seem to be at a standstill. For testing I'm using BluePrint Simulations' KLAX, along with Aerosoft USCitiesX LA, and flying the PMDG 737-800NGX. My problem is this: no matter how much I mess with these three tweaks I'm not seeing ANY boost in performance, and on top of that, according to GPU-Z I'm still not even using more than 1005MB of my 2048MB GTX 550Ti. Here are my specs: ASUS M4A79XTD Evo MOBO Kingston HyperX Blu 4GB 1333Mhz AMD Phenom II X4 840 OC'd @ 3.5Ghz EVGA GTX 550Ti 2GB OC'd @ 1000Mhz Core 2040Mhz Shader Windows 7 Home Prem 64Bit With my video settings, which are tweaked quite a lot (I average around 25FPS and my game looks and runs GREAT, mid flight, except in some of my CS and PMDG aircraft and near large Payware airports). I'm just trying to get a nice little boost on the ground and near bigger hubs. My tests at LAX were giving me around 11fps on the ground in the NGX. BARELY playable. Not very smooth at all and it makes it quite hard to make precise control adjustments when your skipping along at 11fps... Is there something I'm doing wrong to not be seeing ANY fps or smoothness boost out of these tweaks?? My video card certainly isn't reflecting that I've even done anything at all!! Never goes above 45% mem usage. I know it can handle it because I'm not even using half of my memory normally! Any help would be greatly appreciated. I've been working on this for a while trying to figure out what's going on. Also: I am using Bojote's tweaked config file as well as HighMemFix Thanks in advance! Brick

Hello friends, I need help. I am trying to configure affinitymask for my processor, I tried with values ​​62 or 63-64, FSX works for a few minutes with all cores, but then the rest stops working attached some screenshots Core 0 1 (first physical core) 1 2 (first logical core) 2 4 (2nd physical core) 3 8 (2nd logical core) 4 16 (3rd physical ... 5 32 6 64 7 128 8 256 9 512 10 1024 11 2048

hey all, Since I am the proud owner of a GTX670 4Gb Edition and a i7-3770K I am able to enjoy fsx way more because of the awesome performance I get out of this rig. but I'm still experiencing a little stutters and I think it's because of the bufferpools entry in my fsx.cfg I'm using UsePools=0 and the default RejectThreshold from the Venetubo fsx tweak. So my question is; is there any best recommended setting for those two tweaks to achieve super ultimate smoothness in fsx? much appreciated! specs: CPU: Intel Core i7-3770K GPU: Asus GTX670 4Gb Edition HDD: Crucial M4 SSD Mobo: Asus Z77 Sabertooth Mem: Corsair Vegeance 16Gb DDR3-1600 FSX: Gold Edition with PMDG737 (I always fly it)

Hi guys, I searched in the forum but didn't found recent posts on this argument; so I decided to open a new thread about the very essential changes you should make, in your opinion, in FSX.CFG I run FSX:SE DX10 (Steave FX) on a not up-to-date machine so, out of the box, with MD11, NGX and DASH8 and ASN (on client pc) I got about 18-21 fps on ground with 70% of AI traffic But I'm curios about: 1) do you use HT? 2) AffinityMask 3) FFTF 4) other? Thanks a lot, Ric

Shortly after installing a new display driver, I opened FSX to find that the default resolution was set to 1024x768x32 instead of 1920x1080x16. When I checked the fsx.cfg file, I saw that there were two DISPLAY.Device entries, one towards the top and one towards the bottom. I check the "mode" variable for each and, sure enough, one was set to the lower resolution. I've tried deleting the new entry, setting the new entry to the higher res and deleting the old one, etc... but nothing seems to work, even deleting the .cfg file and letting FSX create a new one. Anybody know what's doing on?Edit: Also, the [Multiplayer] field keeps appearing beneath the new entry for whatever reason...

Ive installed FSX on a seperate drive (128GB SSD) called the F drive. Opposed to the normal C drive in hopes of making the sim run faster. However, i cant find the cfg. I know under normal circumstances, it would be under appdata, etc. However, when i installed FSX on the F drive, there was nothing currently on that drive, not one folder. I created a folder called Microsoft Flight Simulator X and thats what the game was installed into. Where would i go about finding the .cfg? Would i have to add a new one? The game runs fine, so im sure there has to be one somewhere on that drive. Thanks- Matt

Hi all! I've never had any problems with OOMs in FSX since I switched to a 64bit OS. But recently there was a discussion in another forum about FSX RAM usage and how GPUs with large amounts of video memory might cause OOMs. The discussion was inspired by these two threads here on Avsim: http://forum.avsim.n...x/#entry2160874 http://forum.avsim.n...25#entry2100237 There were some questions whether GPUs with high amounts of VRAM installed could actually deprive FSX of virtual address space and cause an OOM. So I ran a few tests trying to prove it. I only have a GPU with 1GB VRAM, but since the GPU drivers can throw in some shared system memory if the installed VRAM is not enough (dxdiag reports around 4GB video memory on my system), I was hoping to show that if I tell FSX that there's plenty of video memory available using the VideoMemoryOverride switch in fsx.cfg I could actually cause OOMs. Well, the result in short is that I couldn't find that VideoMemoryOverride does anything at all. Neither increasing nor decreasing the values seemed to have any effect on VAS usage or VRAM usage as reported by Nvidia Inspector. I was only able to show that use of the DX10 preview mode can actually reduce VAS usage significantly. However I would be interested if that's just my system or if other people can't make this tweak work as well. So I will write up the test details here, hoping that someone will be able to reproduce my findings. Theoretical Background (I do not know much about DirectX, so this stuff is just what I read somewhere else. Please correct me if I'm wrong.) FSX is a 32bit application that --when run on a 64bit OS-- can address at most 4GB of virtual memory (->Virtual Address Space, VAS). DirectX9 applications must use their in-process VAS to address the GPU's video memory. Hence the more video memory FSX uses, the less address space is left for the actual application. There is an undocumented tweak found by ******* 'Bojote' Altuve called VideoMemoryOverride that is supposed to limit the maximum amount of video memory used by FSX. It should go in the section of fsx.cfg that contains the actual graphics card being used by the app: [DISPLAY.Device.NVIDIA GeForce GTX 460 SE.0] //VideoMemoryOverride=268435456 //0.25 GB //VideoMemoryOverride=536870912 //0.5 GB //VideoMemoryOverride=1073741824 //1.0 GB //VideoMemoryOverride=1610612736 //1.5 GB //VideoMemoryOverride=2147483648 //2.0 GB //VideoMemoryOverride=2684354560 //2.5 GB //VideoMemoryOverride=3221225472 //3.0 GB //VideoMemoryOverride=3758096384 //3.5 GB //VideoMemoryOverride=4294967296 //4.0 GB Mode=1680x1050x16 Anisotropic=1 AntiAlias=1 [DISPLAY.Device.NVIDIA GeForce GTX 460 SE.0.0] Mode=1680x1050x32 Anisotropic=1 AntiAlias=1 //VideoMemoryOverride=268435456 //0.25 GB //VideoMemoryOverride=536870912 //0.5 GB //VideoMemoryOverride=1073741824 //1.0 GB //VideoMemoryOverride=1610612736 //1.5 GB //VideoMemoryOverride=2147483648 //2.0 GB //VideoMemoryOverride=2684354560 //2.5 GB //VideoMemoryOverride=3221225472 //3.0 GB //VideoMemoryOverride=3758096384 //3.5 GB //VideoMemoryOverride=4294967296 //4.0 GB I don't know why I have two entries in my config (with suffix .0 and .0.0). I guess the second one is for a specific display (I only have one monitor connected to my GPU). Test Setup Since I do not have problems with OOMs the way I use FSX, I tried to conceive a scenario that would bring FSX down to its knees. I chose the PMDG 737 NGX and OrbX's PNW demo area for the tests, since these two are the most complex aircraft/scenery addons I have on my system. For these tests I programmed a Flight KSEA->KHQM->KSEA and recorded VAS usage on the return leg at 25nm distance to KSEA. I chose this scenario because the flight goes both over FSX default terrain as well as OrbX's addon scenery. Also, there is a lot of AI traffic at KSEA. I disabled all addons in dll.xml and exe.xml that could possibly interact with FSX during the tests and thus mess with the results (except the PMDG/OrbX libraries of course). FSUIPC unreg was also disabled. I actually wanted to record VAS usage even closer to KSEA (7nm) because it showed in some preliminary tests that VAS usage was highest there. However I got g3d.dll errors on the return leg pretty consistently shortly after passing the 25nm distance mark (at approx 24.5 nm), so I had to choose the 25nm mark as the point to record the test data. The programmed flight was low and slow to put max stress on the scenery engine (155kts, 1400ft altitude). I also opened a second window in fly-by view to keep the scenery engine busy. Additionally, I used the thunderstorms weather theme and enabled the NGX's head up display and ND terrain mode, hoping that it would further increase memory usage. The tests were all performed using a saved situation to ensure that the tests are repeatable. After loading the situation, I only pressed the NGX's TOGA clickspot, took off and enabled the autopilot at 400ft AGL (I left the gear extended). No messing around with view points or anything durring the flight. I recorded VAS usage using VMMap and GPU VRAM usage with NVidia Inspector. After each test, FSX was restarted. Once the test situation was loaded, I reset the stats in NVidia Inspector and selected the fsx.exe process to monitor in VMMAp. At the 25nm mark on the return leg, I pressed F5 in VMMap to display the current memory usage and took a screenshot to record the results. Additional test and system details: Windows 7 Pro 64bit FSX Acceleration NGX Sp1c Orbx PNW demo area (the current one with KHQM) Latest Orbx libs at that time (120328) FTX night mode on REX2 with HD textures installed (DXT5) Bojote's shader 3.0 mod JustFlight's TrafficX with recompiled traffic bgl All kinds of freeware replacement textures by Aime Leclerq installed (including TreeX) FSX ran in windowed mode for the tests, window maximized at 1680x1050 resolution (minus what the Windows task bar and window frame steal from that) Screensaver disabled NVidia driver v295.73, NVidia inspector v1.9.5.11 GPU settings as detailed here, using 8xS settings, frames locked to 30fps in the driver, no VSync My fsx.cfg and the saved situation files are included as attachments (please rename to .zip): Test Results I ran tests using VideoMemoryOverride (VMO) settings for 0.25,0.5, 1 and 3 GB of video memory. This is a screenshot of a typical test situation: During these tests, VAS usage was pretty high (300-500 MB free VAS left). Occasionally, VAS usage went further up (100-200MB free VAS) but dropped shortly thereafter. However, sometimes during these VAS usage peaks an OOM would occur. In those cases where I didn't get a g3d.dll error at 25nm before KSEA, I let the test run to see what happens when getting closer to KSEA with all its AI traffic. At approx 10nm distance, VAS usage went up (100-200MB free VAS left), but unlike above, it stayed at this level. I did not include these test results as there were too few of them. Furthermore, I ran a series of tests using FSX's DX10 preview mode. As expected, the VAS usage was significantly lower during these tests. But the VideoMemoryOverride switch didn't work there either, which I didn't expect since video memory is adressed differently anyway. The actual VRAM usage was a little higher in DX10, but it was the same for all values of VideoMemoryOverride. Also, here is a representative screenshot from one of the DX10 tests: Summary As you can see, there is little variation in the numbers apart from the differences between DX9 and DX10 which leads me to the conclusion that the VideoMemoryOverride config switch does not work. However, I do not want to write off this switch so early. There's still a possibility that the switch can work in other situations. So I would be interested if someone else (especially those people with a 3GB GPU) can try these tests on his or her system and post their findings.

For a few years I have messed with FSX and always had in some situations received those flickering / flashing problems on textures and buildings (not just like the mosquito noise of what Land Detailed Textures causes, but I mean full flickering and/or shimmering). That was until I discovered the below document. I followed the below guide and installed a third-party tool called Nvidia Inspector, and basically copied his settings. http://#####.wordpress.com/fsx-software-and-hardware-guide/ I finally after years bought a new comp (nothing fancy, just i5 @ 3.1ghz w/ GTX 660 2g + 8gb System Ram), I was dissapointed at first because even though my frame rates were higher I couldn't get scenery looking much better. Don't get me wrong there may be better tweak guides out there, and possibly a bunch of the settings are hurting my FPS from that guide, but for now I don't care because I am getting 25-30 fps 80% of the time except in congested or unique areas, and FINALLY the shimmering/flashing of textures is 95% gone. And that is using ORBX + Rex with only an I5, and no shimmering, so not bad at all. I wasn't tweaking for an increase in FPS, first I just wanted to see HOW GOOD can it look, then another day I'll go back and remove one thing at a time and see if I get any reverse benefit from removing some stuff I added. BOY let me tell you it made all the difference in the world for Orbx stuff. It literally looks close to PhotoReal now except for the mountains and some trees, but at certain distances in some areas the trees look PhotoReal at times (KBZN - Bozeman Airport probably has best looking trees). I'm a semi-casual "fair weather" simmer. I was using TileProxy for a year or so on and off but had partially lost interest with FSX due to Tile Proxy's inconsistent performance and its issues with having to re-load areas that were already cached. I knew about OrbX, but I didn't want to dump tons of money into because I still thought even in the videos that the trees and mountains really needed to look less pixelated / blocky. I still think Orbx could improve the look of mountains, and maybe trees in some places, but let me tell you this is GOOD ENOUGH now that I got this tweaked, and I'm finally having fun again in FSX. Orbx is worth the money and is a nice change from using PhotoReal Scenery, just make sure you tweak. Also, definitely REX is a must (or any of the similar weather engines), I had used the FREE stuff like Oscar and HDE-v2 for a long time, those do ok for clouds (and sometimes could even arguably look better), but the majority of the time they lack the variety of Rex textures. The REX real-time weather engine isn't the best, but it's not that bad, and I'll get one of the other additional weather add-ons later. New PC + new REX version + ORBX Stuff = WIN WIN!

GOOD NIGHT! I am with problems about my FSX.CFG [JOBSCHEDULER] AffinityMask=14 [GRAPHICS] HIGHMEMFIX=1 ForceFullScreenVSync=1 Allow_Shader_30=1 Stale_Buffer_Threshold=2147483647 SHADER_CACHE_PRIMED=1693458432 D3D10=1 TEXTURE_MAX_LOAD=4096 NUM_LIGHTS=7 AIRCRAFT_SHADOWS=1 AIRCRAFT_REFLECTIONS=1 COCKPIT_HIGH_LOD=1 LANDING_LIGHTS=1 AC_SELF_SHADOW=1 EFFECTS_QUALITY=2 GROUND_SHADOWS=1 TEXTURE_QUALITY=3 IMAGE_QUALITY=0 See_Self=1 Text_Scroll=1 SHADER_CACHE_PRIMED_10=1693500672 [sOUND] AmbientUIMusicVolume=-6.000000 PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03} VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03} SOUND=1 SOUND_QUALITY=2 SOUND_LOD=0 UISound=1 AmbientUI=1 [Display] RUNWAY_LIGHTS_VASI_SCALAR=0.5 RUNWAY_LIGHTS_SURFACE_SCALAR=0.4 RUNWAY_LIGHTS_STROBE_SCALAR=0.7 RUNWAY_LIGHTS_APPROACH_SCALAR=0.5 ChangeTime=1 TransitionTime=1 windowTitleTextColor=255,255,255 ActiveWindowTitleBackGroundColor=0,28,140,64 NonActiveWindowTitleTextColor=255,255,255 NonActiveWindowTitleBackGroundColor=24,33,87,64 InfoUpperRightTextColor=255,0,0 InfoUpperRightBackGroundColor=0,0,0,0 InfoLowerLeftTextColor=255,255,255 InfoLowerLeftBackGroundColor=255,0,0,128 InfoLowerRightTextColor=255,255,255 InfoLowerRightBackGroundColor=255,0,0,128 InfoBrakesEnable=True InfoParkingBrakesEnable=True InfoPauseEnable=True InfoSlewEnable=True InfoStallEnable=True InfoOverspeedEnable=True BLOOM_EFFECTS=1 SKINNED_ANIMATIONS=1 TEXTURE_BANDWIDTH_MULT=400 TextureMaxLoad=9 UPPER_FRAMERATE_LIMIT=29 WideViewAspect=True [Main] DisablePreload=1 HideInfoText=1 FIBER_FRAME_TIME_FRACTION=N/A User Objects=Airplane, Helicopter SimObjectPaths.0=SimObjects\Airplanes SimObjectPaths.1=SimObjects\Rotorcraft SimObjectPaths.2=SimObjects\GroundVehicles SimObjectPaths.3=SimObjects\Boats SimObjectPaths.4=SimObjects\Animals SimObjectPaths.5=SimObjects\Misc ProcSpeed=7787 PerfBucket=7 Location=124,110,1156,876,\\.\DISPLAY1 Maximized=1 HideMenuNormal=1 HideMenuFullscreen=1 SimObjectPaths.6=SimObjects\TrafficX [DynamicHeadMovement] LonAccelOnHeadLon=-0.020000 LonAccelOnHeadPitch=-0.010000 RollAccelOnHeadLat=0.010000 YawAccelOnHeadLat=-0.100000 RollAccelOnHeadRoll=0.100000 MaxHeadAngle=5.000000 MaxHeadOffset=0.300000 HeadMoveTimeConstant=1.000000 [PANELS] IMAGE_QUALITY=1 DEFAULT_VIEW=0 QUICKTIPS=0 PANEL_OPACITY=100 PANEL_MASKING=1 PANEL_STRETCHING=1 UNITS_OF_MEASURE=1 [Weather] WindshieldPrecipitationEffects=1 MinGustTime=10 MaxGustTime=500 MinGustRampSpeed=1 MaxGustRampSpeed=200 MinVarTime=5 MaxVarTime=50 MinVarRampSpeed=10 MaxVarRampSpeed=75 TurbulenceScale=1.000000 WeatherServerAddress=fs2k.zone.com WeatherServerPort=80 WeatherGraphDataInDialog=0 AdjustForMagVarInDialog=1 DynamicWeather=2 DownloadWindsAloft=0 DisableTurbulence=0 CLOUD_DRAW_DISTANCE=4 DETAILED_CLOUDS=1 CLOUD_COVERAGE_DENSITY=6 THERMAL_VISUALS=0 [DISPLAY.Device.NVIDIA GeForce GTS 250.0] Mode=1280x1024x32 AntiAlias=0 [CONTROLS] Controls_Default=Standard Controls_Current=Standard KBDAIL=64 KBDELEV=64 KBDRUD=64 JOYSTICKS=1 [TextInfo.1] Latitude=1,1 Longitude=1,2 Altitude=1,3 Heading=1,4 AirSpeed=1,5 WindDirectionAndSpeed=1,6 [TextInfo.2] FrameRate=1,1 LockedFrameRate=1,2 GForce=1,3 FuelPercentage=1,4 [TextInfo.3] Latitude=1,1 Longitude=1,2 Altitude=1,3 Heading=1,4 AirSpeed=1,5 WindDirectionAndSpeed=1,6 FrameRate=2,1 LockedFrameRate=2,2 GForce=2,3 FuelPercentage=2,4 [slewTextInfo.1] Latitude=1,1 Longitude=1,2 Altitude=1,3 Heading=1,4 AirSpeed=1,5 [slewTextInfo.2] FrameRate=1,1 LockedFrameRate=1,2 [slewTextInfo.3] Latitude=1,1 Longitude=1,2 Altitude=1,3 Heading=1,4 AirSpeed=1,5 FrameRate=2,1 LockedFrameRate=2,2 [Trusted] C:\Program Files (x86)\EZCA\EZCA.exe.rbzqacwnrzwlocblcbniqkztwcnauzqukaznwihn=1 F:\FSDiscover!\FSDiscoverFSX.dll.anwawekuonwiuzuhzbotiztulauwhzkuzwuhnltw=1 F:\Flight Simulator X\A2A\Shared\A2A_Service.dll.rztineetrqkbceweurlhineubzwrchwlbwzqbwnn=1 F:\Flight Simulator X\GAUGES\ezgpsv4.GAU.obrblzoobokuqlrtneaqhizrlnwnqenbcnqcraeo=2 F:\Flight Simulator X\SimObjects\Airplanes\A2A_PiperJ3\panel\A2A_PiperJ3s.DLL.btwulnzbobkubluukaktobuocwrqzuinlccwbqoo=2 F:\Flight Simulator X\SimObjects\Airplanes\A2A_PiperJ3\panel\A2A_PiperSound.DLL.hknboccwctrhlnacenqniockieoelibtuiocubcu=2 F:\Flight Simulator X\GAUGES\Cessna.DLL.nrukurokucnqzqqwzututlclahnuanbhnlewahbw=2 F:\Flight Simulator X\GAUGES\Cessna172.DLL.kirukbaiwknniikockcrltcccauuazoaiebnbetz=2 F:\Flight Simulator X\GAUGES\Cessna182s.DLL.tclunioarkqkulaqkairlkthnznqnkicqhtwziru=2 F:\Flight Simulator X\GAUGES\CessnaWAlpha.DLL.oooneoeqrzccwciubtkhkbqewrebtlkkhoizkhel=2 F:\Flight Simulator X\GAUGES\Bendix_King_Radio.DLL.niicceihcazltloiqithwoqqeqrqnrihuuntelur=2 F:\Flight Simulator X\GAUGES\Bell_206B.DLL.btarlihizhwiockbwhzkuqhbkocruubqeuhoqqkk=2 F:\Flight Simulator X\GAUGES\CLS_FSX_SOUND.DLL.zhakicllokabtroohonccniuecittqhrkbborark=2 F:\Flight Simulator X\GAUGES\BoeingGeneric.DLL.raiwknzlbnqahuucrtziowakalquoltuocalieqe=2 C:\Program Files (x86)\EZCA\EZCA.exe.irnorlunlklhouqkiutizziezaorikbakeraqlan=1 F:\Flight Simulator X\SimObjects\Airplanes\Ants Drifter A-582\panel\Drifter.GAU.hzouuhcqlwekenkqiwzuakrqweutualorlbqbhnr=2 F:\Flight Simulator X\SimObjects\Airplanes\IRIS A-10A Warthog – CL\Panel\A10_sound.DLL.ehqwnozkkkinoilrohzoibalrbobthrzuwlkzieo=2 F:\Flight Simulator X\SimObjects\Airplanes\WoP3_Spitfire\panel\A2A_spit.DLL.kqwrlqlzkekqtqnnaqwrninlkqriqezqnbkrohic=2 F:\Flight Simulator X\GAUGES\HHDA20.DLL.wlnolrizchwrtoiekizkakcqkcbkbhualczztiei=2 C:\Program Files (x86)\EZCA\EZCA.exe.oieahuakokwkhruiuuhthtziuqtkewaqrwilatne=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\iFly737NG.dll.lqakieuqohlakzlqerhleqrcukuiwiblhwohitii=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Aerosoft\Flight Recorder\AS-FlightRecorder.dll.ocqwrinhwhlbuurwhutheqqolzthnzbecuonbkow=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_HUD_interface.dll.cnlnzanqhkhrketuzwonhcuncrzobowntkaoozck=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDGOptions.dll.obnuwbzuqleiabkkchkrlhkwabikrhiwrrnarwte=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDGEvents.dll.utelcaknnqwebqrazkqqrilckwaetotezbhercca=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDGSounds.dll.zieebbbuwuarkuttwhcleokhebaqhhawhuoblwqu=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll.abzknbncotucoqrnztwotkwzizobtztlchtkrzzn=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_747400_Main.DLL.entarlctarzerubnazztcqulzczwrhtuinbhioht=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_747400_ACS.DLL.zuzancwqwkrabznlkirqloboqaletkznolnkuezu=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_747400_Overhead.DLL.bquiqcurbwrrkhuzctzblawzlcoriuekokhznkql=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_747400_Center.DLL.rkwtbbzieunqquutwwqiaozbobakoknlhzrinhib=2 [DynamicHeadMovement] LonAccelOnHeadLon=-0.020000 LonAccelOnHeadPitch=-0.010000 RollAccelOnHeadLat=0.010000 YawAccelOnHeadLat=-0.100000 RollAccelOnHeadRoll=0.100000 MaxHeadAngle=5.000000 MaxHeadOffset=0.300000 HeadMoveTimeConstant=1.000000 [VirtualCopilot] VirtualCopilotActive=1 [uSERINTERFACE] PageID=1 OpenATCOnCreate=0 SHOW_MISSION_CAPTIONS=0 PAUSE_ON_LOST_FOCUS=1 PROMPT_ON_EXIT=1 SITUATION=C:\Users\Phil\Documents\Flight Simulator X Files\Bakewell Showgroun South Map_Orientation=2 ShowAllACPaintSchemes=1 SelectAircraftManufacturer=All SelectAircraftPublisher=All SelectAircraftType=All [ATC] ShowATCText=0 COMM_MSG_NONE_COLOR=FFFFFFFF COMM_MSG_ATC_USER_COLOR=FFB6FFB6 COMM_MSG_USER_ATC_COLOR=FFFFD21B COMM_MSG_ATC_AI_COLOR=FF00FF00 COMM_MSG_AI_ATC_COLOR=FFFF7840 AutoOpenAirTrafficWindow=0 UsePilotVoice=0 PilotVoice=0 [PointOfInterestSystem] CycleSetting=0 [sCENERY] SmallPartRejectRadius=1 LENSFLARE=1 DAWN_DUSK_SMOOTHING=1 IMAGE_COMPLEXITY=5 PERF_MODE=MegaScenery [TrafficManager] AirlineDensity=60 GADensity=100 FreewayDensity=99 ShipsAndFerriesDensity=100 LeisureBoatsDensity=100 IFROnly=0 AIRPORT_SCENERY_DENSITY=5 [TERRAIN] IMAGE_PIXELS_FOR_AUTOGEN_POLYGONS=1024 TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=800 TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=1700 LOD_RADIUS=9.0 <== Increase coverage around the aircraft; Default=4.5 MESH_COMPLEXITY=100 MESH_RESOLUTION=25 TEXTURE_RESOLUTION=29 AUTOGEN_DENSITY=5 DETAIL_TEXTURE=1 WATER_EFFECTS=7 [AContain] ShowLabels=0 ShowUserLabel=0 ShowLabelManufacturer=1 ShowLabelModel=1 ShowLabelTailNumber=0 ShowLabelDistance=1 ShowLabelAltitude=1 ShowLabelAirline=0 ShowLabelAirlineAndFlightNumber=0 ShowLabelFlightPlan=0 ShowLabelContainerId=0 ShowLabelAirspeed=0 ShowLabelHeading=0 LabelDelay=1000 LabelColor=FFFF0000 [iNTERNATIONAL] ASLAT=2 ASLON=1 MEASURE=1 [REALISM] PFactor=0.000000 Torque=0.000000 GyroEffect=0.000000 CrashTolerance=0.000000 General=0.000000 UnlimitedFuel=True TrueAirspeed=False AutoCoord=True RealMixture=False StressDamage=False GEffect=False ManualLights=False GyroDrift=False CrashWithDyn=False CrashDetection=False AutoTrim=False [sIM] SYSCLOCK=0 [sTARTUP] DEMO=0 SHOW_OPENING_SCREEN=0 STARTUP_DEMO=0 LoadWindow=1 [FACILITIES] COUNTRY=United Kingdom STATE= CITY=Derby GTL_BUTTON=1196 [Misc] Com_Rate=7 [DISPLAY.Device.NVIDIA GeForce GTS 250.0.0] Mode=1280x1024x32 AntiAlias=1 Anisotropic=1 [bufferPools] UsePools=0 PoolSize=0 RejectThreshold=54288 [MULTIPLAYER] condAccoutPassword=0 [AccelerationPack] ControlsFirstRun=0 [DISPLAY.Device.AMD Radeon HD 7700 Series.0.0] Mode=1440x900x32 Anisotropic=1 AntiAlias=1 CAN YOU HELP?! PLZ! Inside the PDG 738.. He takes 20 fps 20-25 :( Without any scenaries! If you can help! Thanks too much! Sorry about my english im from brazil :(

Hi all, Some months ago I updated my computer. ​Old one was a i7 2400k, mid-end amd gpu.... So went for new config and here it is: ASUS Maximus VII Hero Intel I7 4790K running at 4.8Ghz 32GB of DDR3 (4x KHX1600C9D3K2/8GX) 500GB SSD EVO 850 And last but not least: EVGA GTX980 AC2.0 (4gb) First installed windows 8.1, but when I tried to play FSX steam edition, things looked realy bad. I wasn't able to get it in widescreen for some reason. So after a while I thought to give it a shot with windows 10, because I realy wanted it running again. It has been a while since my last tweaking, so started searching some tweaks again... But for some reason i'm messing up. ​When I test the game and look at GPU-Z. Memory of the GPU stays the same, there is no load, only the clock and memory speed go slightly up. Used Nvidia configurator to set texturing and AA options... Or should it realy be nvidia inspector? These are some options I tested with in fsx.cfg (So don't have to put all of .cfg in here: [GRAPHICS] HIGHMEMFIX=1 TEXTURE_MAX_LOAD=4096 [BUFFERPOOLS] POOLSIZE=0 BufferPools=1 UsePools=1 RejectThreshold=126976 Poolsize=490000000 [JOBSCHEDULER] [DISPLAY] TEXTURE_BANDWIDTH_MULT=40 UPPER_FRAMERATE_LIMIT=40 [Main] FIBER_FRAME_TIME_FRACTION=0.15 [DISPLAY.Device.NVIDIA GeForce GTX 980.0] Mode=1920x1080x32 Anisotropic=1 [SCENERY] LENSFLARE=0 DAWN_DUSK_SMOOTHING=1 IMAGE_COMPLEXITY=5 [TERRAIN] LOD_RADIUS=5.500000 MESH_COMPLEXITY=100 MESH_RESOLUTION=23 TEXTURE_RESOLUTION=27 AUTOGEN_DENSITY=4 DETAIL_TEXTURE=1 WATER_EFFECTS=7 Is there anybody who can point me to the right direction or even better with a smooth running .cfg with a kinda identical system? For those who respond... thx already!