I am sure you wouldn't see a difference, I know I don't. I don't see a negative effect either, but still, I think there is no need for it at all.

 

I will take advise though from this thread and take AM out of my config though. I never really say a difference using it, but didn't pay attention to the texture load with it on or off either.

 

Either way, I am more of a purist when it comes to my fsx.cfg....the less the better I think. That is just my 2 cents.

It scores less because of the Radeon 6990.

 

I think Radeon 6990 is quite equal to GTX 670 even though FSX likes Nvidia cards more, FSX is heavily CPU dependent anyway and it doesn't really make that much of a difference if you run for example GTX 550 or GTX 590. 

 

If that thing could really be used to compare FSX performance on different systems it should definitely rank my 4.4ghz system way better than the other one with 3.10ghz even if I had much worse graphics card. 

You guys did an excellent job inspecting his fsx.cfg. With that being said. I have been running mine with old radius set to 8.5 a majority of the time, even in FTX regions and airports and I get a pretty consistent fps of 30fps running at 2560x1600 on a 30" monitor. My textures are set to 4096 and I have UT2 traffic at 100%, my sliders in FSX are set according to the FTX recommendations. I have FS Global Ultimate for meshes and it recommends you to set the lod radius to 8.5 which is how I got that number in the first place. I am using 2048 cloud textures in REX and OpusFSX for weather. So I think I'm pushing FSX pretty hard and yet my frame rates are surprisingly good with these insane settings. But I'd like to do some more tweaking on my end to see if I can make it better. I usually have to go in and change my lod radius back down to 4.5 when flying to and from extremely heavy urban areas such as KLAX or KJFK. Since I have quite a lot of add ons in those regions. If not I'll start to hear FSX "ding" noises in the background and shortly after that OOM.

 

So you guys think I should keep my textures at 2048 then instead of 4096? Not sure if you'd be able to tell a difference on a 30" monitor at 2560x1600. 

 

Nice bit of Add-ons sir, and even the more so on that monitor- better PPI!

 

One thing with respects to the high LOD and HD textures: Video card drivers settings have to match and should be listed or there is no point i.e; Highest Quality texture-Aniso filtering and negative unclamped LOD Bias of atleast -0.1 or 0.3 etc etc

 

Without these we just wont see what has improved.

how about the mipbias tweak? that does indeed make everything crispier.

can someone shed light on this setting?

I just read in the previous page that it is outdated.

 

Yep, Has to be done at the driver level.

Oh I'm using NVIDIA 320.49 drivers, and my specs are under "MY PC". I have Anisoptric setting enabled in FSX and AA controlled through NVIDIA Inspector. I will have to post my settings for you guys to see when I get back. But I'm surprised at how well my FSX runs even with a fairly large amount of add-ons I have. This is the best it has ever ran for me.

I have mine at 33.

 

32 is so yesterday

Yep, Has to be done at the driver level.

 

 

mmm, I clearly see a difference by using mipbias either in display.cfg with proper card entries or in fsx.cfg

Okay here's my current settings:

 

This is my fsx.cfg

[GRAPHICS]
AC_SELF_SHADOW=0
AIRCRAFT_REFLECTIONS=1
AIRCRAFT_SHADOWS=0
ALLOW_SHADER_30=1
COCKPIT_HIGH_LOD=1
D3D10=0
EFFECTS_QUALITY=2
GROUND_SHADOWS=0
HIGHMEMFIX=1 
IMAGE_QUALITY=0
LANDING_LIGHTS=1
MultiSampleQuality=8 
MultiSamplesPerPixel=4 
NUM_LIGHTS=8
See_Self=1
TEXTURE_MAX_LOAD=4096
TEXTURE_QUALITY=3
Text_Scroll=1
SHADER_CACHE_PRIMED_10=1693500672
SHADER_CACHE_PRIMED=1693500672

[TrafficManager]
AIRPORT_SCENERY_DENSITY=0
AirlineDensity=0
FreewayDensity=10
GADensity=0
IFROnly=0
LeisureBoatsDensity=10
ShipsAndFerriesDensity=10

[REALISM]
AllowEngineDamage=False
AutoCoord=False
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=5
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]
DisablePreload=1
FIBER_FRAME_TIME_FRACTION=0.10
HideInfoText=0
HideMenuFullscreen=0
HideMenuNormal=0
Location=366,37,2012,1073,\\.\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
but may result in stuttering: Lower than 0.1 may give blurring of ground textures when flying fast at low level.=0
ProcSpeed=10308
PerfBucket=7
SimObjectPaths.6=SimObjects\UT2 Aircraft

[SIM]
SYSCLOCK=1

[DISPLAY.Device.NVIDIA GeForce GTX 680.0]
Anisotropic=1
Mode=2560x1600x32

[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
RUNWAY_LIGHTS_APPROACH_SCALAR=0.75 
RUNWAY_LIGHTS_STROBE_SCALAR=0.75 
RUNWAY_LIGHTS_SURFACE_SCALAR=0.80 
RUNWAY_LIGHTS_VASI_SCALAR=0.6 
SKINNED_ANIMATIONS=1
TEXTURE_BANDWIDTH_MULT=120
TextureMaxLoad=12
TransitionTime=4.000000
UPPER_FRAMERATE_LIMIT=30
WideViewAspect=True

[JOBSCHEDULER]
AffinityMask=84
[SlewTextInfo.3]
AirSpeed=1,5
Altitude=1,3
FrameRate=2,1
Heading=1,4
Latitude=1,1
LockedFrameRate=2,2
Longitude=1,2

[PANELS]
DEFAULT_VIEW=1
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=8.500000
MESH_COMPLEXITY=100
MESH_RESOLUTION=24
SWAP_WAIT_TIMEOUT=2
TEXTURE_RESOLUTION=29
WATER_EFFECTS=4

[SCENERY]
DAWN_DUSK_SMOOTHING=1
IMAGE_COMPLEXITY=5
LENSFLARE=0
MAX_ASYNC_BATCHING_JOBS=3
SmallPartRejectRadius=4.0

And here's my nvidia inspector settings:

 

 

Please let me know if there's any settings I can change to improve my performance. Thanks.

It scores less because of the Radeon 6990.

There is no way FSX can determine anything meaningful for the GPU at any time: at what point it performs some fill rate tests or something similar to calculate the actual rendering performance? Not at any point. There aren't also any updated data base tables, where there would be some relevant data what kind of power some GPU holds relating to some other option, which would be used to make up part of the value for procspeed.

 

Same goes practically with CPUs. FSX can fetch from OS some clock speed data and possibly information about the amount of cores. It has no relevant information what is the clock-to-clock performance, for example, of something relatively new processor type compared to some earlier architectures which were common on FSX release or even at the time of its latest patch. Here also, it can use just some very basic information through OS, to determine some value it throws to that .cfg variable. All in all, main problem is that FSX doesn't perform any kind of reasonable benchmark test to determine a value that would have some practical use everytime a new generation of GPUs and CPUs are in use. It can use some basic information through OS, but that really tells nothing.

mmm, I clearly see a difference by using mipbias either in display.cfg with proper card entries or in fsx.cfg

 

Pretty sure it wont do a thing without Negative LOD being set in the driver, its a two part process. 

 

 

Hey Jim, so you don't use the Affinity Mask tweak in your cfg file why ?

 

From my understanding of the tweak, it's 14 or 84 depending on whether HyperThreading (HT) is on or off on a quad core CPU.  I do not use the "tweak" on my modern system.

 

Best regards,

Jim

I think Radeon 6990 is quite equal to GTX 670 even though FSX likes Nvidia cards more, FSX is heavily CPU dependent anyway and it doesn't really make that much of a difference if you run for example GTX 550 or GTX 590. 

 

 

Here's the rating on both, and yes - I don't use the AM as well. It has never made one iota of difference. 

About HT. Many years ago Nick Needham and a lot of simmers performed benchmark tests with FSX, me included, and it didn't take much effort to discover that enabling had no positive effect on FSX performance at all. On the contrary. HT will increase CPU temps and you'll need to downclock your OC.

 

HT enablded and increased performance? No, no, no. Placebo effect :rolleyes:

 

You'll find Nick's updated guide on hardware, OS setup and FSX here: http://www.simforums.com/forums/the-fsx-computer-system-the-bible-by-nickn_topic46211.html

 

Regarding the LOD_RADIUS setting I would expect FSX to use the default or max setting if any value greater than max value would be found in the config file. Would be very easy to test, but since I gave up simming a couple of years, I leave the scientific testing up to you guys. :wink:

 

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\DCrack_Concorde.DLL.ineqeqntrquztabtwennbklwnecbtiohqbhckzka=2

 

Gotta love blatant piracy....

About HT. Many years ago Nick Needham and a lot of simmers performed benchmark tests with FSX, me included, and it didn't take much effort to discover that enabling had no positive effect on FSX performance at all. On the contrary. HT will increase CPU temps and you'll need to downclock your OC.

 

HT enablded and increased performance? No, no, no. Placebo effect :rolleyes:

 

You'll find Nick's updated guide on hardware, OS setup and FSX here: http://www.simforums.com/forums/the-fsx-computer-system-the-bible-by-nickn_topic46211.html

 

Regarding the LOD_RADIUS setting I would expect FSX to use the default or max setting if any value greater than max value would be found in the config file. Would be very easy to test, but since I gave up simming a couple of years, I leave the scientific testing up to you guys. :wink:

 

Yeah for many old procs, sure.

HT enabled on my Haswell and it makes toast either way but is plenty stable and of course FSX never has made use of hyper-threading.

As for LOD settings, Higher than in-game were discovered and proven here many a moon ago and still hold true today unless there has been a rewrite of FSX.EXE you can share with us...

Yeah for many old procs, sure.

HT enabled on my Haswell and it makes toast either way but is plenty stable and of course FSX never has made use of hyper-threading.

As for LOD settings, Higher than in-game were discovered and proven here many a moon ago and still hold true today unless there has been a rewrite of FSX.EXE you can share with us...

 

Which haswell processor are you running and did you over clock it at all?