SimForums.com Homepage
Forum Home Forum Home > General Discussion Forums > Hardware, Software, and Computer Technology
  New Posts New Posts RSS Feed - NickN Nividia inspector SLi settings
  FAQ FAQ  Forum Search   Register Register  Login Login

NickN Nividia inspector SLi settings

 Post Reply Post Reply
Author
Message
markturner View Drop Down
Senior Member
Senior Member


Joined: March-10-2009
Location: United Kingdom
Points: 115
Post Options Post Options   Thanks (0) Thanks(0)   Quote markturner Quote  Post ReplyReply Direct Link To This Post Topic: NickN Nividia inspector SLi settings
    Posted: May-05-2012 at 7:50am
Hi, I am back flying FSX again after an 18 month break. Currently I have 2 GTX580 running SLi, powering a dell 30 inch at 2560 x 1600, plus a secondary 24 inc monitor for dragging windows, interent etc.

I was hoping NickN could give me some advice regarding the best settings for Nvidia inspector with this set up, particularly in the sections relating to SLi. There are a huge number of options and I would like to know the best settings. 

My preferred set up for FSX is using DX10 preview, as I can get a rock solid and very fluid 30 FPS using that, if I use DX9, it probably averages 25 and 20 in the clouds, which is not so great. I don't get any noticeable graphics issues either using DX10.

Incidentally, all my .cfg file settings are as Nick advises.

Thanks! Regards, Mark
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 19888
Post Options Post Options   Thanks (0) Thanks(0)   Quote NickN Quote  Post ReplyReply Direct Link To This Post Posted: May-05-2012 at 11:18am
there is no control of settings in FSX DX10, only FSX DX9
 
and I do not use SLi so I have no basis to advise on DX9 settings, if any, that would make a difference, which I doubt.
 
SLi in FSX is about filtering, not frames. And since the application is tied to CPU the higher filtering regardless of SLi will still hit the performance, just not quite as much, but its nothing like a modern game that has a rendering engine that is made to use the GPU
Back to Top
Herky130 View Drop Down
Senior Member
Senior Member


Joined: June-18-2010
Location: UK
Points: 235
Post Options Post Options   Thanks (0) Thanks(0)   Quote Herky130 Quote  Post ReplyReply Direct Link To This Post Posted: May-05-2012 at 11:20am
Hi, I have a single GTX580 Palit (3GB). I run a DEll Ultrasharp at 2560x1440, native resolution. I also run a 19" Acer, for Plan G, Guages etc.
 
I see 30 FPS,(locked anyway apart from cities and Mega Airports) but more important ( to me) is the smoothness of the flight. Its acceptably smooth.
 
I do not run FSX in DX 10. I thought it was broken?  I am interested to hear that you achieve a smoother flight in DX 10? Perhaps its the power of two GTX 580's thats doing it?
 
You do not say what specs you have, CPU, HDD,Mem etc....These are also pertinant to smooth flight.
 
As for SLI, I also understood that it does not help to provide a smoother rendering, but I may be wrong, as in your case it may do just that.
 
Hmmm, perhaps the new GTX 690 is the order of the future...?Tongue
 
 
 
If you search on the forum there was a very good post a while ago re SLI settings.
 
Cheers.
 
 
 
 
 
 
 
 

Visit my YouTube Chanel,"HERKY231"
Back to Top
markturner View Drop Down
Senior Member
Senior Member


Joined: March-10-2009
Location: United Kingdom
Points: 115
Post Options Post Options   Thanks (0) Thanks(0)   Quote markturner Quote  Post ReplyReply Direct Link To This Post Posted: May-05-2012 at 12:48pm
Hi Nick, thanks for that. Just to confirm I have this right, whatever settings you choose, across the board in Nvidia inspector, do not get applied to FSX if you run DX10 mode, correct?

My PC is Asus X58 sabretooth, i7 950 @3.7ghz  6gb ram and both windows and FSX on SSD's. windows is a fresh install, tweaked as per Nick guide.

I must admit I am a little surprised that I cant get better performance in DX9, last time around on a lesser spec PC, I could usually get 30 - 50 FPS, but using the same monitor.

here is my DX9 .cfg file if anyone fancies having a quick look and seeing if there is anything glaringly wrong:

DX 9

[RWW_WEATHER_MAP]
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
[BufferPools]
Poolsize=0
[VirtualCopilot]
VirtualCopilotActive=0
[DISPLAY.Device.NVIDIA GeForce GTX 580.0]
Mode=2560x1600x32
Anisotropic=1
[SOUND]
AmbientUI=0
AmbientUIMusic=0
AmbientUIMusicVolume=-6.000000
PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03}
SOUND=1
SOUND_FADER1=0.500000
SOUND_FADER2=0.500000
SOUND_FADER3=0.500000
SOUND_FADER4=0.500000
SOUND_LOD=1
SOUND_QUALITY=2
UISound=1
VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03}
[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
[AccelerationPack]
ControlsFirstRun=0
HomePageFirstRun=0
[INTERNATIONAL]
ASLAT=3
ASLON=0
MEASURE=0
[CONTROLS]
Controls_Current=Standard
Controls_Default=Standard
KBDAIL=64
KBDELEV=64
KBDRUD=64
[FACILITIES]
CITY=Christchurch
COUNTRY=New Zealand
GTL_BUTTON=1232
STATE=
[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=1
[GRAPHICS]
AC_SELF_SHADOW=1
AIRCRAFT_REFLECTIONS=1
AIRCRAFT_SHADOWS=0
ALLOW_SHADER_30=1T
COCKPIT_HIGH_LOD=1
D3D10=0
EFFECTS_QUALITY=2
GROUND_SHADOWS=0
HIGHMEMFIX=1
IMAGE_QUALITY=1
LANDING_LIGHTS=1
NUM_LIGHTS=8
See_Self=1
TEXTURE_MAX_LOAD=2048
#TEXTURE_QUALITY=3
Text_Scroll=1
SHADER_CACHE_PRIMED_10=1693500672
SHADER_CACHE_PRIMED=1693500672
TEXTURE_QUALITY=3
[TrafficManager]
AIRPORT_SCENERY_DENSITY=3
AirlineDensity=20
FreewayDensity=20
GADensity=20
IFROnly=0
LeisureBoatsDensity=40
ShipsAndFerriesDensity=40
[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
[REALISM]
AllowEngineDamage=True
AutoCoord=False
AutoTrim=False
CrashDetection=True
CrashTolerance=1.000000
CrashWithDyn=True
GEffect=True
General=1.000000
GyroDrift=False
GyroEffect=1.000000
ManualLights=True
PFactor=1.000000
RealMixture=True
StressDamage=True
Torque=1.000000
TrueAirspeed=False
UnlimitedFuel=False
[Weather]
AdjustForMagVarInDialog=1
CLOUD_COVERAGE_DENSITY=8
CLOUD_DRAW_DISTANCE=3
DETAILED_CLOUDS=1
DisableTurbulence=0
DownloadWindsAloft=0
DynamicWeather=2
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]
HideMenuFullscreen=1
HideMenuNormal=0
Location=12,15,2553,1549,\\.\DISPLAY1
Maximized=0
FIBER_FRAME_TIME_FRACTION=0.2
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=11822
PerfBucket=7
[Trusted]
C:\Program Files (x86)\AICarriers\aicarriers.exe.icakiaciezacthilznzahqaehuibnwrwkworqrtl=1
F:\AICarriers\aicarriers.exe.icakiaciezacthilznzahqaehuibnwrwkworqrtl=1
F:\Microsoft Flight Simulator X\GAUGES\CessnaRG2.GAU.ihccerkrccbqhiznwkraqkntnuobthwrllcuonai=2
F:\Microsoft Flight Simulator X\GAUGES\Money20F0.GAU.rlbobntliaqlirzlrlweeairwqzkzetktlwhtzaq=2
F:\Microsoft Flight Simulator X\GAUGES\Money20F1.GAU.uzbrbqiaihchuuioqowwozaaaoulkulalholzeqe=2
F:\Microsoft Flight Simulator X\GAUGES\Money20F2.GAU.hutneitqarhuwbcathzlbciwqlkqkwqwnihetbti=2
F:\Microsoft Flight Simulator X\GAUGES\Money20F3.GAU.uheielnatrbznanowbozacawzozlwrieqqelirnk=2
F:\Microsoft Flight Simulator X\GAUGES\Money20F4.GAU.wiulzbcqhrtkorontozznrakqcratiklaquuetuu=2
F:\Microsoft Flight Simulator X\GAUGES\Money20F7.GAU.izhahaoebulckbricltqokzeruabtraaanncluzt=2
F:\Microsoft Flight Simulator X\GAUGES\Money20FM.GAU.zhuratbinnthortekzlratiwtuctultlicrllrqb=2
F:\Microsoft Flight Simulator X\GAUGES\Money20FVFR.GAU.bitcizawotzoolhclhohzuehceckbknkkrlceenq=2
F:\Microsoft Flight Simulator X\GAUGES\RadioMoney.GAU.linltlohozbwhwrceqnwikqezeruwawqruhclrcq=2
F:\Microsoft Flight Simulator X\Modules\FSUIPC4.dll.lquutbzcnckhtwrihtehozhbutalbzznrawcrtel=1
F:\Microsoft Flight Simulator X\Modules\b21_vario\b21_vario.dll.eiktchuuqwnknizucuetnoqlithzrncttiwqrilq=1
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\Aerosoft F-16A 9\Panel\ASC.DLL.kaiiiqkolattozhzznnhhklnicuzlrqtteihokqo=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\Aerosoft F-16A 9\Panel\SCControl.DLL.tabhlttraobnqrntaknaownbkclnhcloelzwaeti=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\VRS_FA-18E\panel\FA18E\VRS_Fail.GAU.okhlhcionlwbewzllanclcoknbntloanquwqanlu=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\VRS_FA-18E\panel\FA18E\VRS_Fuel.GAU.noqcznzhznztlurwticbotzhzzoztlcekuewihuz=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\VRS_FA-18E\panel\FA18E\VRS_Persist.GAU.ihchtbbzkickeuzcwhkrioqrbhhhrhzcoqoirabr=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\VRS_FA-18E\panel\FA18E\VRS_Radar.GAU.uqenectkrqnoulizaoeuceczcrrqttlbaoarkatr=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\VRS_FA-18E\panel\FA18E\VRS_Rand.GAU.hwzkihbbobtieribhtqcuhtcwezekabrqeaharcn=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\VRS_FA-18E\panel\FA18E\VRS_Sound.GAU.ewnaoehbzlznzwzczzhlkizaqcitaozzobhbtzww=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\VRS_FA-18E\panel\FA18E\VRS_Traf_Fac.GAU.ztccwlloaoithblhkhtthnbnoneetlqoaozbbcoh=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\VRS_FA-18E\panel\FA18E\VRS_Windows.GAU.chwcukhwzzttrcbtaeeewtzoelirbiztbkewbizq=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\VRS_FA-18E\panel\FA18E\VRS_axis_control.GAU.etzaakckkukiwtauoiiieruizuhkqqbtetnrzhew=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\VRS_FA-18E\panel\FA18E\VRS_axis_control.GAU.kchnutioeeliwwwrtttktihbkttrzzeqwwathwew=2
F:\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_CEJ4\scenery\ObjectFlow_cej4.dll.znkuuzuwhonikrccwoukklzohrnchnzelkakizlt=1
F:\Microsoft Flight Simulator X\GAUGES\fa-18.DLL.ilituqenwnoqwikntlwqqbuqhhiqoohlotktwaab=2
F:\Microsoft Flight Simulator X\GAUGES\CessnaRG0.GAU.bhbzzqoreuiwoutrawznhcctlukwlezblourkbeq=2
F:\Microsoft Flight Simulator X\GAUGES\CessnaRG1.GAU.cucqozkhzewnziwaoiootzuilbontrhalekrwrwn=2
F:\Microsoft Flight Simulator X\GAUGES\CessnaRGVFR.GAU.tbuwcrtltcwhcqoqrualbqnbhizqizewqcnunueh=2
F:\Microsoft Flight Simulator X\GAUGES\CessnaRG4.GAU.kcbuatzlnruzzlzhcikiwtzobahtwbrlewbbiabu=2
F:\Microsoft Flight Simulator X\GAUGES\CessnaRG6.GAU.hubzciaiwzeuwncklcoqazzqbrwuhoqrrihkoikc=2
F:\Microsoft Flight Simulator X\GAUGES\CessnaRGRadios.GAU.kwunrckcneqalocnrhatckllcwcbbehuqktqhrtu=2
F:\Microsoft Flight Simulator X\GAUGES\CessnaRG3.GAU.bhocthcilnzccuzcbthkwklcwqrwbeakqckzqett=2
F:\Microsoft Flight Simulator X\GAUGES\CessnaRG7.GAU.tbrqqaknuqzikztnzozkwutrcketnuztnorlqcez=2
F:\Microsoft Flight Simulator X\GAUGES\CessnaRGM.GAU.waktuarneqliqtuonuwuotqneqkoztbbquzucbuh=2
F:\Microsoft Flight Simulator X\GAUGES\CessnaRG5.GAU.nozaaentiwetiezqciaronrkleaoqaonecrzwnhb=2
F:\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_7S3\Scenery\ObjectFlow_7S3.dll.uknoqcknlawiuuioiwrbthuwlheccikotlhhrbik=1
F:\Microsoft Flight Simulator X\FSDX.dll.leookzhtbiwobwaoawebutcllhhboulkihnkwhoh=1
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\FSD C115\panel\FSDCommander.DLL.uzricnnqzqakzhhwtuornlchlhbccnlerzonqcnu=2
F:\Microsoft Flight Simulator X\GAUGES\Cessna.DLL.haqchrwnrhibzeahziwcrhlkheatqoquaaicokrb=2
F:\Microsoft Flight Simulator X\GAUGES\CessnaWAlpha.DLL.nltrihckqnnwlkoqzlqobtineaizerhoicirribq=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\IRIS A-10A Warthog - CL\Panel\A10_sound.DLL.bwkllqhiirrozcncccuqtiaqbiothoolwtqzbiee=2
F:\Microsoft Flight Simulator X\GAUGES\Captain_Sim.c130.sound.GAU.bulqrrrbknbbclohkklriuokckticlzzutwqrlzl=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.main.GAU.rantucrkrqqlawwteitlwuarhnonqqwzzbtqucwt=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.electric.GAU.lrzzawkoluahhwkolkaleqooenbecbwbezkktaka=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.fuel.GAU.rzeehbwbbcoelikqrbcbnituhkaaaekqawkwzlia=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.left.GAU.hkkqbbttoiotezloltuhrqcocahulwaabkbzqnbb=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.engine.analogue.GAU.rlatcnzhwllenliqozwuablenzeqkltbeerwtuwr=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.icons.GAU.cqbqrauuzczahwzurautbbzuibulobbalikrtuen=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.right.GAU.rnrbaulzwqzhquhktachbqbhlolukkoiwrinbbze=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.GAU.tukizqhhabaacncaehhenbeliunikehkkauilwrr=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.navigator.GAU.aketlzuazeuetlcbwurrrzlrlhoiztzlbnclbrqu=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.iff.GAU.ukiwhkrbwbltcrqwloezihlhazanoaonibztqwnt=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.wheel.GAU.ockawalhcbcnhchwulouwthlqznciucqirqqazuz=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.vc.GAU.nqaotohzwqikwbztnckezthlcknlkwzeealiooaa=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.AuxRight.GAU.belorwihwlewauirkwahnllktirhwibuqrtnlcnl=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.engine.analogue.vc.GAU.bbezuictecwkoocblrezuttabaennzroliaolhww=2
F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_C130\panel\Captain_Sim.c130.oh.vc.GAU.ckothnrioqanlzqenntozanrewlrqruhbkcoorra=2
F:\Microsoft Flight Simulator X\Modules\FSUIPC4.dll.zucqannotqihezcubarzbcqhlcezrrklqnnblrbu=1
[TextInfo.2]
FrameRate=1,1
FuelPercentage=1,4
GForce=1,3
LockedFrameRate=1,2
[USERINTERFACE]
Map_Orientation=2
OpenATCOnCreate=0
PAUSE_ON_LOST_FOCUS=1
PROMPT_ON_EXIT=1
PageID=1
SHOW_MISSION_CAPTIONS=0
SITUATION=FLIGHTS\OTHER\FLTSIM
SelectAircraftManufacturer=All
SelectAircraftPublisher=Vertical Reality Simulations
SelectAircraftType=All
ShowAllACPaintSchemes=1
[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
RUNWAY_LIGHTS_APPROACH_SCALAR=0.6
RUNWAY_LIGHTS_STROBE_SCALAR=0.5
RUNWAY_LIGHTS_SURFACE_SCALAR=0.7 
RUNWAY_LIGHTS_VASI_SCALAR=0.5
SKINNED_ANIMATIONS=1
TEXTURE_BANDWIDTH_MULT=400
#TextureMaxLoad=12
#TransitionTime=4.000000
UPPER_FRAMERATE_LIMIT=30
WideViewAspect=True
TransitionTime=4.000000
[JOBSCHEDULER]
AffinityMask=14
[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=3
DETAIL_TEXTURE=1
LOD_RADIUS=6.500000
MESH_COMPLEXITY=100
MESH_RESOLUTION=25
SWAP_WAIT_TIMEOUT=2
TEXTURE_RESOLUTION=29
WATER_EFFECTS=4
[SCENERY]
DAWN_DUSK_SMOOTHING=1
IMAGE_COMPLEXITY=5
LENSFLARE=1
MAX_ASYNC_BATCHING_JOBS=3
SmallPartRejectRadius=4.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
[MAPVIEW_MAP]
SHOW_AIRPORTS=1
SHOW_VORS=1
SHOW_NDBS=1
SHOW_APPROACHES=1
SHOW_INTERSECTIONS=0
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_flight_history=1
[DISPLAY.Device.NVIDIA GeForce GTX 580.0.1]
Mode=1900x1200x32
[DISPLAY.Device.NVIDIA GeForce GTX 580.0.0]
Mode=2560x1600x32
TriLinear=1
#AntiAlias=1
[MULTIPLAYER]
condAccoutPassword=0


cheers, Mark

Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 19888
Post Options Post Options   Thanks (0) Thanks(0)   Quote NickN Quote  Post ReplyReply Direct Link To This Post Posted: May-05-2012 at 3:32pm
No, none of the settings in the Nv Control panel or NV Inspector will allow any change in FSX DX10
 
 
 
Take the cards out of SLi, use one card and one monitor, or, use one card and drive a Matrox Digital Th2Go for multi-monitor span however when you first set up a tune a FSX system it should always be on a single card, single monitor setup, then after you have achieved the goal of smooth flight with the right scenery settings, then and only then do you move to a multi-monitor span or setup. By doing so you know the initial setup was correct and any performance drops or issues are a direct result of adding in the additional monitors or span setup.
 
Set up Nv Inspector as outlined http://www.simforums.com/forums/settings-for-new-drivers-updated-v1959_topic36586.html  the latest version is linked in that post. Be aware that it is possible Nv Inspector settings may not initially hold and must be reset after a system reboot.
 
 
 
Move the current FSX.cfg out of the directory and boot the sim, let it build a new config by setting up the slider, checkboxes and screen resolution and do not use DX10.
 
Be aware the only reason DX10 may show perf increases is because of shader code and the DX10 API. Past that, you will be dealing with glitches, including flickering, missing scenery from some cities, and all sorts of other nonsense so keep it in DX9 mode.
 
Settings depend on many issues. Textures and landclass are different than photoscenery, and, scenes that mix photoscenery and texture/landclass can present even more problems to tune out and address.
 
 
Start with the setting I outlined at the end of this post: http://www.simforums.com/forums/topic34141_post198187.html#198187
 
under...

You are ready to TUNE FSX..

and make sure AA is unchecked and filtering is set to trilinear in FSX
 
 
Open the FSX.cfg  (and stay away from that Jesus tool)
 
Add the following to that config, these are not tweaks, they are fixes based on the hardware installed to start the process of tuning...
 

[Display]

TEXTURE_BANDWIDTH_MULT=120       

WideViewAspect=True //If you use a wide screen aspect ratio monitor

 
[Main]
DisablePreload=1
 
[GRAPHICS]
HIGHMEMFIX=1
 
Save the FSX.cfg
 
Now, realize this is not tweaking.. its tuning, basic tuning
 
The goal is to establish the sliders in the basic scenery environment first and establish the smoothest flight possible. This can take some time and if you are trying to do this over crazy 'over-stuffed' scenery packages like Orbx its going to be even harder.
 
I suggest the use of KSEA and a flight out of there using the pre defined weather "building storms", take off north, fly past the city of Seattle about 10 miles, turn around and land back at KSEA. This area has every element the sim will throw at the hardware from multiple airports to city models to water shaders, to mountain and rougher terrain.. its all on one location.
 
You tune everything from traffic to scenery settings using that flight, weather and flight path. The aircraft should not be a PMDG.. it should be the default Cessna and 747.
 
You may find that locking frames at 30 is too low in a high-scenery location. Check 30 locked, 60 locked and unlimited for best flight smoothness.
 
Once you have established the best setup you can, if you are seeing things like micro-stutters and other issues you cant get tuned out, which I doubt over default scenery and using default aircraft, then move to making some very basic changes/tweaks. There is a crap-load of different nonsense out there. There are only 2 tweaks out there with faster hardware in a system that may make a hill of beans difference and they are Bufferpools and FFTF. In the past FFTF over textures was not advised because of blur conditions, however with faster hardware it can assist with performance as long as the rest of the system can keep up and not blur the scene. Also, FFTF is useless with frame lock set to unlimited so if that is used, then a frame lock must be established and maintained, which means the scenery settings must allow the hardware to maintain a locked frame rate with FFTF in operation.
 
The first tweak you can try adding is bufferpools, however NOT BP=0
 
 
[BUFFERPOOLS]
UsePools=1
Poolsize=8388608
RejectThreshold=262144
 
 
dont set water to 2xHigh to fix spikes and flashes, thats nonsense
 
Be aware that you may see scenery spikes and flashes when the flight is first loaded.. we pan visually around the outside of the aircraft in lock-spot view around and around about 5-6 times to clear this. Its possible you may see one or two more, but that should clear up completely. If those flashes do not clear up, you are simply pushing too much scenery and that is all there is to it. If you set water to 2xHigh to reduce flashes and spikes,..  you will effectively drop performance which is counter to the entire process of performance tuning.
 
The effectiveness of Bufferpools is seen over a large number of models in the sim, a pine forest is the perfect location to define if bufferpools is working for a system and how well. Locate a pine forest in the sim (must be all pines) and note how smooth the flight is over the trees at 3-5000ft. Then close the sim and add the bufferpool entry above and recheck the same flight.. if its smoother, then bufferpools is working for the system and leave that edit as-is.
 
In order to properly use FFTF you must frame lock. Vsync issues are present with frame lock which is why we lock at 30 or 60, 30 being 1/2 the refresh rate of the typical LCD monitor, 60 being a match to the refresh rate. There are beta drivers out there that allow access to new Vsync settings, if you read the 2nd post in this thread,
 
 
 install the listed beta driver (uninstall from add/remove programs and reboot first, then run the clean install process) and set it all up as I outlined with the with the latest Nv Inspector and lock 30 in FSX graphics settings.. do not use frame limiters either external or in NV inspector , then you can use FFTF with effective results. The FFTF setting will depend on your system and how much you are pushing. It will be set to between .10 and .20, .15 being the most typical.
 
Thats about it Mark. After you have figured out setup and tweaking, then you move to the multi monitor setup and retune for the extended load as well as any scenery packages or aircraft you use. It all comes down to the fact that there is no such thing as one set of slider settings for every situation. You may need to back of autogen and scenery complexity in one scenery situation where in others you can run 100%
 
you have to make those calls.
 
you can add the runway and VASI and strob light scale adjustment to the config as well as items such as
 
[Main]
HideInfoText=1 to get rid of the messages on the screen, but dont put any of that other crap in your FSX.cfg.
 
If you add more junk to the config you are just making the job of tuning more complicated and convoluted for nothing
 
 
 
 
 
Back to Top
Herky130 View Drop Down
Senior Member
Senior Member


Joined: June-18-2010
Location: UK
Points: 235
Post Options Post Options   Thanks (0) Thanks(0)   Quote Herky130 Quote  Post ReplyReply Direct Link To This Post Posted: May-06-2012 at 8:47am
Well Mark, the Boss has spoken!Smile
 
Can not get a more complete answer!  Thats why I keep saying to people, FSX is not a game. You have to almost "engineer" it into your PC.
 
Fortunately we have NickN to engineer it for us.  Imagine what a crappy sim it would be if it was not installed and set up correctly, people would be installing "Flight" instead ShockedLOLClown.

Visit my YouTube Chanel,"HERKY231"
Back to Top
markturner View Drop Down
Senior Member
Senior Member


Joined: March-10-2009
Location: United Kingdom
Points: 115
Post Options Post Options   Thanks (0) Thanks(0)   Quote markturner Quote  Post ReplyReply Direct Link To This Post Posted: May-06-2012 at 4:34pm
Hi Herky, you are very correct, Nick has been a great source of help for me and others many times.

One thing I must note is that how FSX performs on your machine is very much an individual experience.  For example, I just followed all of Nicks instructions, rebuilt my .cfg file from scratch, just added the settings he put down. The only things I did not do, was unhook one of my cards, so it was all done using the 2 GTX 580's in SLI and I also did not use the new drivers to force the vsync. I set vsync at half in nvidia inspector ( I assumed that as long as I was limiting the frames at 30 I did not have to use the latest beta drivers to use the FFTF entry) and I used a saved flight over New Zealand south island Orbyx scenery, with orbyx weather 6 set.  FPS limited at 30 in the sim. running in windowed mode for all flights & 2560 x 1600. The results were interesting:

First run, with basic settings as advised above: An average, as best as I could see of 14 FPS

Second run, added the bufferpools 1 & the FFTF tweak:  An Average of 21 FPS

At this stage I was a bit nonplussed - that was all the Tweaking that Nick recommended and I had worst performance than before. So I decided to compare my old .cfg file and swapped it in ( I have a little batch file that does this in a single click..can print it if anyone wants to use it)

Third run, using the .cfg file shown above: an average of 25 FPS

In all the above cases, entering clouds dropped the FPS by about 30%

So, some entry or combination of entries in the file that I was using before starting from scratch, was giving me 20% better performance, I have no idea what though. Perhaps Nick or anyone can hazard a guess, all the entries are there for you to see.  Texture loading was pretty good, but still took about 20 seconds for all high res textures to snap in if I paused using the lower TBM setting. Using the 400 setting, it took about 4 seconds,.......

Then I swapped in the same ( old) .cfg file but with DX10 enabled, otherwise, identical. Rock solid 30FPS, clouds or not. Out of curiosity, I changed the FPS limit to zero in the same file. 

FPS averaged at least 70, with 80 -90 showing often. The same thing but using an identical DX9 .cfg file gave an FPS of an average 26. That's a massive difference on my machine and adds a huge question as to what's going on here...The simple conclusion for me on my machine is that DX10 is the way to go. The water looks a bit weird sometimes, but there are no other real issues I can report using DX10.

In my case, and following Nicks instructions, I have not had the results that he or I would have anticipated. I do appreciate that I have not followed exactly, but the essential things, (new .cfg file, only using the recommended tweaks, were all done)  , I hope that something in what I have described and shown in my cfg files will point to what's going on. Happy to do further testing, removing individual lines etc if Nick wants.  Please, I don't want anyone to take this the wrong way, I am not saying that I know better or anything, just reporting what I found when I followed the advice. I thought that Nick would be interested and intrigued as to what exactly was going on here.

Out of interest, what do these lines supposedly do?

TextureMaxLoad=12
TransitionTime=4.000000


Finally, this fresh install of FSX and windows is on a new machine, but I got better performance on my old i7 920 (overclocked by Nick, of course!)...go figure!

Regards, Mark
Back to Top
Herky130 View Drop Down
Senior Member
Senior Member


Joined: June-18-2010
Location: UK
Points: 235
Post Options Post Options   Thanks (0) Thanks(0)   Quote Herky130 Quote  Post ReplyReply Direct Link To This Post Posted: May-08-2012 at 11:55am
Hi Mark.
 
How does it run with just one GTX 580?  I surmise the two 580's in SLI have summat to do with all this?
 
If you only use the large monitor for flight, I'd just use one GTX 580. You can plug the second monitor into the second port on the 580.( thats my setup)  However, if your happy with your settings, well thats great.
 
I would only go SLI if I wanted Multi Monitors, ie, Surround. I messed with the notion a year or so ago. I was thinking of ATI Eyefinity, then Nvidia surround, then got fed up with the whole idea and got a nice big Dell single screen.  Hence my Palit, which I got originally with grandoise plans for SLI with two of the beasties. I even upped my PSU in readyness.....Wacko
 
So, in sort, I dunno is my answer. Useless to you, but honest.Embarrassed
 
Good Luck.
 
Oh, BTW. Texture max load in my config is 1024. I think it pertains to textures like clouds and HD aircraft. The higher the setting the sweeter the eye candy. But as is known, there's no free lunch with higher settings in FSX.  Actually, I can not see the difference between 1024/2048/etc, when I view aircraft. Aircraft like the Mustang and Beach Duke are superb in any setting. Its how they are painted. I dont have REX or FEX (yet) these bump up the texture load for clouds and may cost frame rate.  But thats another thread!
 
Transition time.....gawd knows?...The time it takes for me to get a beer from the refidgeratorLOL
 
 

Visit my YouTube Chanel,"HERKY231"
Back to Top
markturner View Drop Down
Senior Member
Senior Member


Joined: March-10-2009
Location: United Kingdom
Points: 115
Post Options Post Options   Thanks (0) Thanks(0)   Quote markturner Quote  Post ReplyReply Direct Link To This Post Posted: May-09-2012 at 5:15pm
Back to Top
markturner View Drop Down
Senior Member
Senior Member


Joined: March-10-2009
Location: United Kingdom
Points: 115
Post Options Post Options   Thanks (0) Thanks(0)   Quote markturner Quote  Post ReplyReply Direct Link To This Post Posted: May-09-2012 at 5:20pm
Hi Herky, I will try perhaps with one card . Surely there is no scenario where one card is going to be better than two though? I got the SLi set up to run 3 24 inch monitors, it was OK, but I really hated the stretched textures at the sides and the long narrow screen. like you, I think I prefer one big monster screen, hence back with the 30 inch as the main display. 

I am talking about the texture bandwidth multiplyer line not the texture max load line - the one I am talking about affects the speed at which textures are loaded and displayed. 

cheers, Mark
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 19888
Post Options Post Options   Thanks (0) Thanks(0)   Quote NickN Quote  Post ReplyReply Direct Link To This Post Posted: May-10-2012 at 8:26am
I know why Mark is seeing what he does with the different configs and I really do not have time to sit here and try and explain all the config changes and why, but I will sum it up
... 
 
1. CPU is being run at 3.7GHz instead of being clocked to 4.0 or above. And I have no idea what memory speed and timing is in use with this, but no matter..
 
2. Sli in use with multimonitor
 
3. The scenery (Orbx) is outragous and as such the hacks in the FSX.cfg file are robbing peter to pay paul and in the process I know you are not seeing the level of detail in scenery I expect and demand from my sim.
 
4. You went from a 920 to a 950 proc?   there is no difference between those.. if it was a lesser proc than a 920 then you must understand that the FSX application will behind the scenes see the hardware ability and will change how it renders (priority render system). It will throw more at your hardware automatically. In this case however, you should have purchased a SB proc and motharboard, clocked it to a minimum of 4.1GHz (with the Intel heatsink) or 4.7Ghz with a 3rd party cooling solution. Then you will see a difference and on the right FSX.cfg file without the nonsense hacks too. You wasted your money on that 950 because its not really an upgrade if you came from a 920 and even if you didn't, the SB proc is far better both clock per clock and at the memory controller level than a 950 which is really 3 year old technology by todays standards. In other words, you purchased a 3 year old upgrade.
 
5. You are effectively bottlenecking the CPU you run with the SLi high end cards ,, the CPU you use and the speed it runs cant take that pounding. Even if you are on a single 580GTX, A 3.7GHz 920/950 is still being bottlenecked with that Orbx scenery. So you add in the old 950 technology and slam it with SLi?   not! especially in DX9, however......
 
6. DX10 takes a chunk of the load off the CPU and puts it on the GPU in the DX API. Therefore the change you see in DX10 is a direct result of DX10. Also, there is no AA stress in DX10 mode. The mode only allows the DX API level AA set by FSX in the GRAPHICS settings, and no external upgrade of that. Therefore you do not deal with AA level stress in FSX DX10 but you will at one point see shimmers and other visual headache issues you can not remove in DX10.
 
 
 
Bottom line..  run what you think works best.
 
and by the way, I dont use Orbx products anymore, and never will again in the future.
 
 
and to answer the question
 
TextureMaxLoad=12
 
That value multiples the texture size in KB then TBM multiples that answer, the default value with no line in the config is 6
 
TML 12 x 685KB (average texture in KB) = 8220KB (or about 8MB) x TBM (400) = 3288000KB or 3.13GB
 
That would be for textures alone.. not geometry or models..  over 3GB of data to the video memory flying over textures and landclass
 
do you have a 3.8GB+ video card?
 
REDICULOUS!
 
 
The sim will ignore TBM if frame lock is set to unlimited and if I calculate the memory required the amount is quite out of range. Therefore the values will default and what you think you are seeing and getting with those numbers over textures and landclass is FALSE
 
If you are flying pure photo scenery, that is different as the sim handles photo scenery buffer different than textures and landclass. But make no mistake, you can not mix textures and landclass with photoscenery in the same scene and use a TBM of 400
 
 
Lets take that a step further.. when the sim sees a value that is OUT OF RANGE it defaults back to PERFBUCKET TBM set by the system when the first FSX.cfg file was built. In your case that would be 40
 
12 (TML) x 685KB x 40 (TBM) = 32800KB or 321MB or .314GB   IN RANGE
 
You dont know this is happening and therefore assume tweaks are doing something.
 
and here is the REALLY silly part.. I can accomplish the same task by leaving TML out of the config and setting TBM to 80
 
6 (TML DEFAULT) x 685KB x 80 (TBM) = 32800KB or 321MB or .314GB IN RANGE (same result as above)
 
A 580GTX video card with 1.2-1.6GB of memory (or above) can handle a TBM of 120 over textures and landclass, no problem, and without the TML edit in the config.
 
 
 
This is why I am not going to break down and tear up that FSX.cfg file ..  I can sit here and post why the difference using the config, then what will that mean? It means you will discover what you cut out of the scene and are missing in order to get the result, and, it will point out that the tweaks used such as TML 12 with TBM 400 are not actually doing anything over textures and landclass.
 
If you prefer DX10, then use it! You must not be sensitive to autogen tree, cockpit and fence shimmers because there is no shimmer AA control in DX10. In DX10 the application will ignore any external AA and filtering commands other than the checkbox and dropdowns in FSX.
 
That is another reason for the perf difference..  there is NO clean and sharp detail AA available in that mode. You are forced to run the low-grade MS hardware set level AA.
 
so stick with what you think works.  Wink
 
 
 I dont spend time debunking and getting into FSX.cfg files anymore..   people believe more crap that is not true with the config and 'calculations'  http://www.simforums.com/forums/fsx-tweaks-demystified_topic37948.html and the bottom line is, all they are doing is cutting out scenery or defaulting values that are out of range and get a result. It can be done in the config, or, in the sliders with the right hardware and clock speed.
 
The config method is simply a bit more stealth and more often than not a change that is seen it due to DUMB LUCK in hacking out scenery the user doesn't know is missing .. till one day when they get the right hardware and set it up right then and only then does the 'light bulb' come on and they see what they were missing all along LOL 
 
 
 
 
Back to Top
almwhit View Drop Down
New Member
New Member


Joined: March-25-2010
Location: Arkansas
Points: 34
Post Options Post Options   Thanks (0) Thanks(0)   Quote almwhit Quote  Post ReplyReply Direct Link To This Post Posted: May-17-2012 at 1:03pm
Nick,
I just bought a new system, but I am inexperienced in setting up a system for FSX, so I followed your instructions exactly.  I want to say everything runs great. However as I was following your instructions I felt like a monkey pressing buttons. However I did get the banana at the end!! Thank you very much!! 
 
My question for you is this: If I add a great deal more scenery after the initial set up should I run through the complete defrag process again?
 
Jim 
Back to Top
Zman View Drop Down
Senior Member
Senior Member


Joined: June-12-2010
Location: Syracuse, NY
Points: 698
Post Options Post Options   Thanks (0) Thanks(0)   Quote Zman Quote  Post ReplyReply Direct Link To This Post Posted: May-17-2012 at 11:31pm
Jim
I am Not Nick
But i can tell u if ran the named defrag per Nicks instructions ,,, and then u added more addons to fsx being aircraft , scenery  yes u should run the name defrag again ,,, exspecially if u added Scenery to the fsx Folder,,, scenery r usually very large ,,,
Darryl
Back to Top
NickN View Drop Down
Certified Professional
Certified Professional


Joined: November-21-2007
Points: 19888
Post Options Post Options   Thanks (0) Thanks(0)   Quote NickN Quote  Post ReplyReply Direct Link To This Post Posted: May-18-2012 at 8:16am
Originally posted by almwhit almwhit wrote:

Nick,
 If I add a great deal more scenery after the initial set up should I run through the complete defrag process again?
 
 
 
 
yes
 
 
 
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.01
Copyright ©2001-2018 Web Wiz Ltd.

This page was generated in 0.188 seconds.