Some screenshots, files are large in size - they are not modified at all and come direct from Fraps screen capture as PNGs (2560 x 1600).

 

LOD 9.5  (no OOMs even with TO from FSDT Vancouver)

4096 Texture max

REX clouds 4096 (theme, not real world weather)

FPS average 42 - low 31, max 70

AC - RealAir Duke Turbine

Scenery enabled MSE Washington, MSE Oregon, FSDT Vancouver

 

http://robainscough.com/images/563ec85173648e89cea13d33c2d8c934.png

 

http://robainscough.com/images/43e0b1448a64144d6fe81813649349c3.png

 

http://robainscough.com/images/1bdbc9edc23697d1bfa51f06358fed1c.png

 

http://robainscough.com/images/c3c328e1b44803d40691b3f940312757.png

 

http://robainscough.com/images/099176ce2b6371c72bf6ea4bbb2b1833.png

 

Altitude 19000 ft, about 200 kts indicated

 

 

 

Thats as real as it gets!

 

HLJAMES

Wow.  If anyone gets that to work with autogen somehow, I'll have to keep a cooling fan on my debit card.

Robains very nice. I run at the same resolution as you. May I please ask for your settings you use in fsx.cfg and your nvidia inspector settings? I'm surprised at the framerates your getting. Thanks!

May I please ask for your settings you use in fsx.cfg and your nvidia inspector settings?

 

My NVIDIA Inspector settings: http://www.robainscough.com/images/056a6299317d9f42bc6d2ff0dd06e115.jpg

 

Also to note, I started this flight from FSDT CYVR (with 4096 textures), with ATC using RealAir Turbine Duke, DX10 mode ... took a small detour as destination was Lincoln City OR (cancelled ATC).  WideFS connection to FS Commander running also and GSX was used at CYVR.  Memory usage still showing 1.1GB free (about 1/2 way into flight).  But again, the key for me was not just FSX.CFG, but only having FSDT Vancouver and MSE 2.0 Washington and MSE Oregon 2.0 enabled.  It seems scenery enable/Disable process is working very well for me in terms of performance and memory usage.

 

FSX.CFG (not all settings, but most of the relevant ones) - note I reverted back to my GTX 680 4GB Classified card, having some issues with my Titan 6GB card (not FSX related):

 

[DISPLAY.Device.NVIDIA GeForce GTX 680.0.0]

MipBias=10

Mode=2560x1600x32

AntiAlias=1

Anisotropic=1

 

[JOBSCHEDULER]

AffinityMask=14

[bufferPools]

UsePools=0

Poolsize=50000000

RejectThreshold=126976

[FSDREAMTEAM]

AntiPopUp=1

AltitudeCull=1

 

[TERRAIN]

SWAP_WAIT_TIMEOUT=2

IMAGE_PIXELS_FOR_AUTOGEN_POLYGONS=2048

BATCH_AUTOGEN2=1

LOD_RADIUS=9.500000

MESH_COMPLEXITY=100

MESH_RESOLUTION=25

TEXTURE_RESOLUTION=29

AUTOGEN_DENSITY=5

DETAIL_TEXTURE=1

WATER_EFFECTS=4

 

[sCENERY]

ObjectsToBatchPerFrame=50

MAX_ASYNC_BATCHING_JOBS=4

SmallPartRejectRadius=0

LENSFLARE=1

DAWN_DUSK_SMOOTHING=1

IMAGE_COMPLEXITY=5

 

[TrafficManager]

AirlineDensity=10

GADensity=10

FreewayDensity=10

ShipsAndFerriesDensity=10

LeisureBoatsDensity=5

IFROnly=0

AIRPORT_SCENERY_DENSITY=3

 

[GRAPHICS]

MultiSampleQuality=4

MultiSamplesPerPixel=16

NIGHT_THRESHOLD=4096

DAY_THRESHOLD=32768

SHADER_CACHE_PRIMED_10=1693500672

STALE_BUFFER_THRESHOLD=2147483647

HIGHMEMFIX=1

ForceWindowedVSync=0

ForceFullScreenVSync=1

SHADER_CACHE_PRIMED=1693500672

TEXTURE_MAX_LOAD=4096

NUM_LIGHTS=8

AIRCRAFT_SHADOWS=1

AIRCRAFT_REFLECTIONS=1

COCKPIT_HIGH_LOD=1

LANDING_LIGHTS=1

AC_SELF_SHADOW=1

EFFECTS_QUALITY=2

GROUND_SHADOWS=0

TEXTURE_QUALITY=3

IMAGE_QUALITY=0

See_Self=1

Text_Scroll=1

D3D10=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=0

DownloadWindsAloft=0

DisableTurbulence=1

CLOUD_DRAW_DISTANCE=7

DETAILED_CLOUDS=1

CLOUD_COVERAGE_DENSITY=8

THERMAL_VISUALS=0

 

[PANELS]

VIRTUAL_COCKPIT_TEXTURES_SCALE=2.0

IMAGE_QUALITY=1

DEFAULT_VIEW=0

QUICKTIPS=1

PANEL_OPACITY=100

PANEL_MASKING=1

PANEL_STRETCHING=1

UNITS_OF_MEASURE=0

 

[Main]

FIBER_FRAME_TIME_FRACTION=0.99

DisablePreload=1

HideInfoText=0

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

Maximized=1

Location=-8,7,2568,1593,\\.\DISPLAY1

HideMenuNormal=0

HideMenuFullscreen=1

ProcSpeed=10175

PerfBucket=7

SimObjectPaths.6=SimObjects\JFTraffic360

 

[sOUND]

AmbientUIMusicVolume=-6.000000

SOUND_FADER1=0.500000

SOUND_FADER2=0.500000

SOUND_FADER3=0.500000

SOUND_FADER4=0.500000

AmbientUIMusic=FSX01

SOUND=1

SOUND_QUALITY=2

SOUND_LOD=0

UISound=1

AmbientUI=1

PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03}

VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03}

 

[Display]

RUNWAY_LIGHTS_STROBE_SCALAR=0.9

RUNWAY_LIGHTS_APPROACH_SCALAR=0.9

RUNWAY_LIGHTS_VASI_SCALAR=0.9

RUNWAY_LIGHTS_SURFACE_SCALAR=0.9

TextureMaxLoad=30

ChangeTime=4.000000

TransitionTime=4.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=False

InfoSlewEnable=False

InfoStallEnable=False

InfoOverspeedEnable=False

BLOOM_EFFECTS=0

SKINNED_ANIMATIONS=1

TEXTURE_BANDWIDTH_MULT=80

UPPER_FRAMERATE_LIMIT=0

WideViewAspect=False

 

Rob.

 

 

Wow. If anyone gets that to work with autogen somehow, I'll have to keep a cooling fan on my debit card.

 

The only problem is, if you added autogen back in at Rob's settings, you'd probably be right back to OOM'ing.   TANSTAAFL.  :-)

 

Nice shots, sir!

 

Scott

Your bufferpool settings conflict. You turn the buffer off but then have a poolsize and rejecthreshold. Usepools=0 is all you need. Unless you want to use the buffer and RT then Usepools=1 or you may not even need that entry. I think Usepools=1 is default

 

 

Your bufferpool settings conflict.

 

Over the months/years, I've tried various settings UsePools On/Off and they've made no difference at all (the other entries are there so I didn't have to re-type them when turning UsePools On/Off).  I "think" that under DX10 mode they are not used  ... if they are, they don't seem to have any type of impact (positive or negative).  They don't "conflict", they're just not used when UsePools=0.

 

 

The only problem is, if you added autogen back in at Rob's settings

 

I have AutoGen cranked up

 

AUTOGEN_DENSITY=5

 

... takeoff from FSDT Vancouver was looking pretty good with AutoGen ... just when I moved into MSE area there is no AutoGen.  I'm not a big fan of AutoGen (how in works in FSX just doesn't look good to me) but I can understand the desire for some "depth" to ground objects (I think we all would like that).  AutoGen upto about 1500-2000 ft looks good, but above 2000 ft it just look out of place and awkward with no blending.

 

But I understand what you mean, AutoGen consumes ALOT of memory ... it doesn't seem to make much difference in frame rates on my system.  What will kill frame rates are New York City X or San Francisco City X ... those will bring my system to it's knees (think 8-12 fps - especially MSE 1.0 CA + San Francisco City X + FSDT KSFO).

 

I'm not making any claims to great performance or a magic bullet, I can, like many others, bring FSX to it's FPS knees with the right combination of products/settings.  If I crank up AI to 50 rather than 10, AirTraffic 360 will bring my system to it's knees.  FSX is all about finding balance/harmony ... may the Force be with you all.

FSX is all about finding balance/harmony

 

This is exactly what, Ryan from PMDG, said also.  FSX is NOT a perfect world.  It is backward, crippled and anemic, but still has the potential of being a lot of fun if managed correctly.

 

By the way, your screenshots are awesome.  There is nothing like the real McCoy when flying over scenery.

I have Orbx, but still plan on using MSEv.2 for the same regions, depending on my mood swings.

I purchased Washington, so your pictures really get me excited.  I have several other states to download and install, before Washington though.  I'm really looking forward to trying it.

Robains thanks very much for your config. Didn't realize that disabling scenery that you don't use has such an effect on performance. I notice you're using DX10 also, so maybe that's why you're able to get such good results. I am in DX9. I'm going to experiment first by disabling all scenery that's not in use and see what kind of performance gains I get.

Robains, I notice a setting under your [GRAPHICS] section that has the following:

NIGHT_THRESHOLD=4096
DAY_THRESHOLD=32768

What exactly does this do? I do not have this in my fsx.cfg.

Also this

[FSDREAMTEAM]
AntiPopUp=1
AltitudeCull=1

 

I almost have a similar setup as yours, and just did a test. Used the PMDG 737 at KLAX (FSDT), I have Ultimate Traffic 2 set at 100% commercial and 0% GA. Flying at night set to FTX Global, hybrid mode on, vector road lights on, use orbx trees on, I have REX+OD, using the lowest settings for clouds and water textures. I have my water at high2x, 10% road traffic, 10% ferries, 10% ships, cloud density max, cloud draw distance max, LOD=8.5, Textures=4096, autogen max, pretty much most of my sliders are maxed out. After the plane finishes initializing, FPS stayed around 15-16fps, upon take off, it slowly increased to around 20fps and up, then I started hearing the warning ding noises in the background which I know I'm almost out of memory, and then OOM. So I'm not sure how you are running at LOD=9.5. I even deactivated all the scenery that I don't use, and just kept FSDT KLAX, my fs global ultimate meshes, and utx and the default stuff checked, everything else is pretty much off.

 

 

NIGHT_THRESHOLD=4096
DAY_THRESHOLD=32768

What exactly does this do?

 

 

For the dusk/dawn textures some people feel, subjectively, the result is too dark or too light. There are 2 items that allow the transition time to be changed:

[GRAPHICS]

DAY_THRESHOLD

NIGHT_THRESHOLD

 

acceptible values are 0 to 65535. 

Defaults:

DAY: 32768

NIGHT: 4096

 

These represent the amount of 'ambient' light at the ends of the day/night blend threshold. Zero is perfect dark, 65535 is full day sun at noon in the summer.

 

This is from Phil Taylor's blog.  Doesn't really do anything for performance.

 

 

 

[FSDREAMTEAM]
AntiPopUp=1
AltitudeCull=1

 

This are used by FSDT Airports and are specific to those products.  Apparently FSDT didn't want to use the OS registry to store these so they are in the FSX.CFG.  FSX itself does nothing with them.  What they do for FSDT products I don't know.

 

I have the PMDG NGX, but this particular flight was using the RealAir Turbine Duke (one of my favorites) ... PMDG will produce different performance and memory usage.  You might want to consider trying DX10 and Steve's patch, no harm to any DX9 files so it's easy to switch back.

 

Disabling the scenery in a particular flight makes a huge difference for me, but keep in mind I have about 350+ scenery entries (and growing).

 

I'm currently using Traffic 360, but if you are running AirlineDensity=100 that might be the cause of your FPS difference.  I like AirlineDensity=10 as it produces "enough" AI but not so much that I can't taxi, or takeoff, or land.  I tried AirlineDensity=100 once but took a huge frame rate hit at FSDT KSFO and I eventually gave up trying to get takeoff clearance from ATC ... not to mention the chatter.

 

Oh, also running AccFeel 2.0 and FSUIPC 4.91 with WideFS.

 

 

 

I purchased Washington, so your pictures really get me excited.

 

Washington is such a nice state with all the geological activity and lush green ... I have all the other MSE states and some states are flat as pancakes which can tend to emphasize the lack of AGN.  Now I don't know if those states really are that flat as I honestly haven't visited many states real world (Florida, Nevada, California, Oregon, Washington, Arizona, Utah, Hawaii and that's it).

Well my airline traffic slider in FSX is set to 0 since I am using UT2 for AI, are you referring that I should set that to 10%? I am also running Accufeel, EZDok, OpusFSX, FSRecorder, WinchX, SquawkBox, AICarriers, and a few other addons as well. I have a large collection of add-on scenery as well, probably the same amount as you. So I'm trying to see the comparison between our setups. I'm thinking it's because of DX10 you're able to run that high of settings vs me running DX9 and the possibility of AI traffic set to high like you mentioned. 

 

How did those FSDT config entries end up in your fsx.cfg? I am curious to know what exactly they do and if it will improve my performance when using their airport scenery.

 

Could you do me a favor if you have a chance, can you load up FSX, and start at KLAX (FSDT) with the PMDG 737NGX and have the engines running but sit idle at the runway, along with enabling FTX Global, orbx trees on, vector road light on, and hybrid mode on, and ftx night light mode on and tell me what kind of FPS you get? Thanks.

Don't have FTX Global or Orbx Trees, sorry.

 

I just recorded a flight out of Vancouver (FSDT) that uses AGN until I get into WA ... I'll post that up later, but I have fraps to record at 30 fps 1/2 size which in itself adds a little bit of a performance hit.