Quote
Also I still see people setting a TBM with using unlimited FPS - It is ignored according to Bjote's findings back in time...
 
Correct - I see this as well, but all it means is that the user has either made a mistake, or he /she doesn't understand the parameters which can be changed in the fsx.cfg.
 
All the Best, 
 
pj

 

I can attest to this as I was one, until I just sat down and put in the time with experimentation flights.

In reference to my previous post I want to share my experience:

 

1. After added [bufferPools] Usepools=1 (leaving RejectThreshold=131072)
- no result

2. After added FIBER_FRAME_TIME_FRACTION=0.15 ([Main] section)
- no result

3. After changed RejectThreshold=524288
- a little bit better, but still unacceptable (12-15 fps in VC in dense clouds; sometimes increase to 20-22 but I don’t know why the frames suddenly grow up)
Anyway… there are visibly less of stutters.

 

4. After added PoolSize=20971520
- no change according to pt. 3 above.

 

What is your suggestions – which parameter (and decrease or increase) should I change?

Could I ask for help?

 

 

Regards,

Lucas

@Lucas:

Hi: You cannot simply "pronounce" that

"1. After added [bufferPools] Usepools=1 (leaving RejectThreshold=131072)
- no result"  <<<  This is meaningless. How did you test this? It takes most people days - maybe even a week before one finds a spot where the pc/FSX suddenly responds.

 

  To find the right buffer settings one needs to first create a circular test flight, starting with the default C172 in the air, at 1500ft, in an area which has lots of detail, and always produces "low-ish" frame rates. make the route over the center of Seattle, or New York, London, Paris, etc.. Some level of cloud is also neccessary - but not 6 layers of heavy overcast cumulus, just some moderate level of cloud: Road traffic needs to be there, too, and 30 would be a ggod number to start with. These pics are my cicuit, and I go round the center of Vancouver probably a hundred times, six or seven circuits per flight, looking for that sweet spot or any change in frame rate and average frame rate.

 

Next - make an estimate of the performance relationship between the system's main processor and the graphics card.

 

If one believes that the processor is slower than the GPU - then set UsePools=0 first, making the GPU do the work: No testing is needed.

 

If one believes that the performance is approximately equal - then also try UsePools=0 first, fly the saved test flight several, note the results  and then try UsePools=1, with a small RT - fly, then try the next size larger RT - fly, and the next, and the next, noting any change in frame rate or average frame rate or stability - that happens. This is at least six circuits per RT size. You may find that doing these RT tests with a slightly lower (5MB) or slightly higher (10MB) Poolsize, the result looked for - will sometimes come more quickly - meaning it was a good guess!

 

If one considers the processor to be faster than the GPU - then you will need UsePools=1, and an RT, and start testing as above; Reasonable figures for the RT are:-

64KB, 128KB, 256kB, 512kB, 768kB and 1MB. As the figures need to be entered as "Bytes" - use this easy converter.

 

Once you've run through those RT settings at the default Poolsize of 8MB, without significant result, move the PoolSize parameter up to 10MB and then go through each of the RT settings again. Repeat this until a change occurs.

Reasonable figures for the Poolsize are:-

5MB, 10MB, 15MB, 20MB.  Again as the figures need to be entered as "Bytes" - use this easy converter.

 

Lastly - Lucas - you need to read and understand the "How-To" guide. Somewher toward the end (I know - it's a long read) I ask, that if you have a question (such as "What is your suggestions – which parameter (and decrease or increase) should I change?) would you please put your system's description in your User Profile, so that we can all see what hardware you have, and what the processor speed is: then - a screenshot posted somewhere, of your Inspector settings, and finally - post your complete fsx.cfg. All of these are important if you want to get to the bottom of a problem, or are having difficulties with something. We cannot guess "what to change" without knowing what you have - right?

 

Anyway - I hope this helps, and that it's understandable. I've tried to do this in the BufferPools doc attached to my sig, but perhaps it's not written as well as it could be.  :rolleyes:

 

All the Best,

 

pj

Hi Eric; I usually set water at 4 or 5. Whether it takes one or two passes doesn't seem to matter with DX10 - as - like many of us are finding - we can run FXAA, SweetFX or Bloom - all of which "happen" after the initial screen paint occurs, and none of which have any great impact of the framerate. Bloom, in particular - is a huge surprise. In DX9 it is more or less unusable.

 

In my thinking, the fsx.cfg is pretty well mapped now, as far as "which line does, or controls what, exactly?" The odd-ball parameters that I'm still trying to digest or quantify (for DX10) are:-

 

[Graphics]

STALE_BUFFER_THRESHOLD      links with framerate

 

[scenery]

MAX_ASYNC_BATCHING_JOBS

 

[Terrain]

SWAP_WAIT_TIMEOUT   links with FFTF

 

All the Best,

 

pj

Hi Paul,

 

Quick question. When I get my new card should I just uninstall the old nvidia drivers, install the new card then install the new nvidia drivers ?

Hi Paul,

 

Quick question. When I get my new card should I just uninstall the old nvidia drivers, install the new card then install the new nvidia drivers ?

 

I think i fresh driver reinstall from Geforce Experience should be enough...if you don't have problems

Poul,

 

I would like to thank you for reply and detailed explanation.

 

 

How did you test this?

 

After every change in fsx.cfg, I loaded the same flight, same plane in same weather conditions, over the same region and time of day. I didn't know that testing process can be such "complex"... I see that my way isn't good ^_^ 

 

 

you need to read and understand the "How-To" guide.

 

Yes, I read it. My Inspector's settings are based on your document (with "subtle" changes):

 

Poul, as I wrote at the beginning of my post, I have already pasted my hardware specification and CFG file - do you read my previous post (the last one on page 1 of this thread)?

Can you look at them? Maybe you will give me another "instructions" when you will see it :rolleyes: 

 

Best regards,

Lucas

Hi Lucas - Sorry my friend - I'm on this forum 15 hours a day, voluntarily, and the place I go for someone's PC profile is in the User's Profile, appearing on the left side of the screen. This is requested by Avsim that members shall do this to make other members job easier. I am not going to search for someone's pc hardware in another post that I don't know about, or tread two days ago.

 

pj

I'm sorry Poul, you are right. I have updated my profile.

 

...and paste my fsx.cfg file:

 

 

[JOBSCHEDULER]
AffinityMask=14

 

[bufferPools]
Usepools=1
RejectThreshold=524288
PoolSize=20971520

 

[GRAPHICS]
HIGHMEMFIX=1
SHADER_CACHE_PRIMED_10=1693458432
SHADER_CACHE_PRIMED=1693458432
D3D10=1
TEXTURE_MAX_LOAD=2048
NUM_LIGHTS=8
AIRCRAFT_SHADOWS=0
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
MultiSamplesPerPixel=4
MultiSampleQuality=0

 

[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=0
SOUND_FADER1=0.500000
SOUND_FADER2=0.500000
SOUND_FADER3=0.500000
SOUND_FADER4=0.500000
AmbientUIMusic=FSX01

 

[Display]
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=True
InfoParkingBrakesEnable=True
InfoPauseEnable=True
InfoSlewEnable=True
InfoStallEnable=True
InfoOverspeedEnable=True
BLOOM_EFFECTS=0
SKINNED_ANIMATIONS=1
TEXTURE_BANDWIDTH_MULT=40
TextureMaxLoad=30
UPPER_FRAMERATE_LIMIT=0
WideViewAspect=False

 

[Main]
FIBER_FRAME_TIME_FRACTION=0.15
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=17235
PerfBucket=7
HideMenuNormal=0
HideMenuFullscreen=1
HideInfoText=1
Location=120,104,1160,880,\\.\DISPLAY1
Maximized=2

 

[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=1.000000
WeatherServerAddress=fs2k.zone.com
WeatherServerPort=80
WeatherGraphDataInDialog=0
AdjustForMagVarInDialog=1
DynamicWeather=0
DownloadWindsAloft=0
DisableTurbulence=0
CLOUD_DRAW_DISTANCE=6
DETAILED_CLOUDS=1
CLOUD_COVERAGE_DENSITY=8
THERMAL_VISUALS=0

 

[DISPLAY.Device.NVIDIA GeForce GTX 560 .0]
Mode=1280x1024x32
Anisotropic=1
AntiAlias=1

 

[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]
C:\Program Files (x86)\EZCA\EZCA.exe.qnckurrokleewbwblqtrteuiecnazzrlzuzrrkeb=1
F:\FSX\FSCaptain\bin\FSCaptain.dll.anluwoqqzhkuhawrrlqbrocoqzzritbaanelntln=1
F:\FSX\GAUGES\737-400.DLL.cenclhrqcuikqeleolnhzwbocnowiizrroienwue=2
F:\FSX\GAUGES\CCTC2.DLL.nczbznlcwollhakrrttaauuqqaoorowuznkarkrq=2
F:\FSX\GAUGES\FCDU.GAU.ltzobhcaelrnrlazbhbouzebhhrenqatiwweebrb=2
F:\FSX\GAUGES\PMDG_737NGX.DLL.tktwzbchlowneuwbtbqnziooqacahwwnwkqcwabu=2
F:\FSX\GAUGES\PMDG_737NGX_3.DLL.tktwnebwczhwrcztlcarbooqtinnkrltbuuwlhqt=2
F:\FSX\GAUGES\PMDG_777X.DLL.cbentruuqbbrntrenkukwnohbqecnharankntuuq=2
F:\FSX\GAUGES\PMDG_777X_3.DLL.zbhzrbocowkhtntbloeethwkiabiinaintkoheor=2
F:\FSX\GAUGES\PMDG_BAe_JS4100.DLL.qtkaiueckoewtklorlwtlwewuiowanaaqtlbklwo=2
F:\FSX\GAUGES\PMDG_BAe_JS4100_3.DLL.liaeqwlzliaeclabtbeekhareltrruinwieobarz=2
F:\FSX\GAUGES\RadioC210.DLL.nuhnwrilhhaelqueoorhabzbkwbeeqnwaktohhei=2
F:\FSX\GAUGES\XGauge.DLL.clrhoteotohzkkhllwtrwlierbbqqbqioooicniu=2
F:\FSX\Modules\FSCopilot.dll.ehllltkocelrwzbtzaerqkaabnhhoqibikwtceww=1
F:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll.hewioznlaabuirrzckeanqruriqebbrwercannze=1
F:\FSX\PMDG\DLLs\PMDG_Interface.dll.uoibazarrqobuoketcccrwcwaawawzazeqoeutrn=1
F:\FSX\RAASPRO\RAASPRO.dll.haieaerewrhzotaokoonubobtwcbattulczubkhu=1
F:\FSX\fsdreamteam\couatl\couatl.exe.tnihteknethnccrelclouacczqilwahoaqcuaqza=1
F:\FSX\bglmanx.dll.owkowkknietoqirittuucrnwtrweotitnecnlizh=1
F:\FSX\Modules\FSUIPC4.dll.ncaehkcrkrbleiqrkcqauahlrelibkorrzlzquut=1
F:\FSX\as_srv\as_btstrp.dll.ibctiibuwnhrtwzwuacutzbaotkrzhboalawwhtt=1
F:\FSX\as_srv\as_btstrp.dll.uuheutzlkkchcoierqeqkzhihwawerznnakhitha=1

 

[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]
PageID=1
OpenATCOnCreate=0
SHOW_MISSION_CAPTIONS=0
PAUSE_ON_LOST_FOCUS=0
PROMPT_ON_EXIT=1
SITUATION=FLIGHTS\OTHER\FLTSIM
Map_Orientation=2
ShowAllACPaintSchemes=1
SelectAircraftManufacturer=Wszystkie
SelectAircraftPublisher=Wszystkie
SelectAircraftType=Wszystkie

 

[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]
LENSFLARE=0
DAWN_DUSK_SMOOTHING=1
IMAGE_COMPLEXITY=5

 

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

 

[TERRAIN]
LOD_RADIUS=4.500000
MESH_COMPLEXITY=100
MESH_RESOLUTION=24
TEXTURE_RESOLUTION=26
AUTOGEN_DENSITY=3
DETAIL_TEXTURE=1
WATER_EFFECTS=5

 

[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=0
MEASURE=0
[REALISM]
PFactor=1.000000
Torque=1.000000
GyroEffect=1.000000
CrashTolerance=1.000000
General=1.000000
UnlimitedFuel=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=1244

[Misc]
Com_Rate=7

 

[DISPLAY.Device.NVIDIA GeForce GTX 560 .0.0]
AntiAlias=1
Mode=1280x1024x32
Anisotropic=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

 

[MULTIPLAYER]
condAccoutPassword=0

 

Here she is, Lukasz: and here's the Inspector. Thanks for helping with your specs. It makes it so much faster!

 

Try them and get back to us her with the result. You can still play with bufferpools, but having a slow proc and only 1 gig of memory on the GPU doesn't give you many options.

 

All the Best.

 

pj

Paul, you mean I can turn on Bloom within FSX without really any performance penalty? I tried it quickly one time last week when I first started with DX10. I turned it off thinking it was still like it was in DX9?

Hi Lucas,

 

[bufferPools]

Usepools=1
RejectThreshold=524288
PoolSize=20971520

 

I have never programmed in C however I have a good deal experience in other languages.  Hopefully it doesn't matter and someone with knowledge please correct me.  But at least for good form, I would make sure I define the bufferpool first then the RT.  Rather than the RT first then the BP.

 

[bufferPools]
Usepools=1
PoolSize=20971520

RejectThreshold=524288

 

Sometimes compilers are finicky on how they are told what to do.

 

Also, 

 

[Main]
FIBER_FRAME_TIME_FRACTION=0.15

 

Now, there are two reasons to have this, and you have to ask yourself why do I need it.

 

1st Reason.

 

You are having the blurries.  What this command line does is to vary the processor in such a manner as to speed up or slow down the texture loading process so there is more time for rendering or loading depending on the needs of your system.  

 

 

 

2nd Reason.

 

You would like a bump in frames and really have no blurries.

 

If you missed this in the FSX Basic Install guide here it is...

 

Fiber_Frame_Time_Faction=0.33. This is the default setting if you do not add this to

the Main Section. This parameter was made as the default for FSX as the parameter

helped reduce blurry textures in previous versions of FS and found to be the best setting.

Computers systems have gotten a whole lot better since then. The parameter is built into

FSX and does not need to be added unless you want to lower it.

 

This parameter gives more processing time towards scenery versus rendering.

The lower you set this parameter, the more CPU processing is used or diverted to loading textures.

 

Lowering the number can possibly provide an increase in frame rates.

 

If you are seeing blurry textures without the parameter, then you can add this parameter and set it at 0.15. Do not lower this parameter

any lower than 0.10. We recommend leaving this parameter out of the FSX.cfg unless you

are seeing a lot of blurry textures (which could be caused by many other things).

 

THAT SAID, I have used this and I have it set to .12 in my config.  This really gives me smooth flights.  ESPECIALLY in stock aircraft.  However I use Payware from Eaglesoft and Carenado, and this FFTF gives great results.  Where I noticed the biggest change was from .13 and below.  But when you make changes somewhere else in your config, you will more than likely need to change this more or less to suit you goals for your system.

 

FFTF works very well ONLY after you test it and UNDERSTAND it for your system.  And of course only you can do that.  You are the guy defining what you want out of FSXX.  Keep this in mind.  In DX10 Frame rates do not define the end all be all if you will.  They are merely a good way to find out what your system is doing while painting pictures.

 

I have seen FPS down to 14 and had no idea according to what I was looking on screen or "in sim"  I also have had DX10 frames up to 60 and hated it.  Jerky choppy etc.

 

What the goal ought to be when converting over to DX10 is smooth flight smooth frames, stable operations all around, my opinion anyway.  

 

Hope that helps.

Lucas,

 

Me again.  

 

No point in using Buffer Pools, unless you understand this...

 

TEXTURE_BANDWIDTH_MULT=40

 

in relation to Bufferpools.

 

Let me give this a try.

 

Think Automotive Transmissions

 

Bufferpools = 0  is a lot like an automatic transmission.  Set it forget it.  GPU is handling the shifting.

 

TBM is like the accelerator pedal.

 

Bufferpools = 1 is a lot like a manual transmission  BP = X is now like manual gears in a manual transmission and RT is like a clutch kinda.

 

TBM gives RPM/Horsepower

 

BP is your gears

 

RT is how you get more speed out of those gears.

 

If that is clear as mud, then you DO need to understand this.

 

Raise your TBM to at least 80 but no more than 120 or so.  Start with 80

 

Set your Bufferpools to the lowest possible.  Reject threshold to the lowest possible.

 

 

 

Quote From Paul J

 

 

First - leave the Poolsize at 8388608 (8MB and default), so it doesn't need to be entered: Other sizes can be tried if/when no change is seen after going through all the RT numbers below (though BMB is already pretty large)

5242880 5MB, 8388608 8MB, 10485760 10MB, 20971520 20M

 

Then select the first RT at a pretty small number - 128000  128KB

 

Set up your test flight, save it, and then fly it five or six circuits with that number, then go up one, to 256KB (262144), and so on - 512KB, - 1MB,  until something changes in smoothness, stability, spiking, framerate, or framerate average. If there is no change - then move the PoolSize up to 10485760 (10MB) and see which way it goes, and then run through the RT numbers again at this new PoolSize. Also - remember -  increasing the poolsize to 10MB may be ther wrong way, too - you could find that lowering the poolsize may yield a resulting change more quickly.

RejectThreshold=128000 (125KB), 262144 (256KB), 390144 (381KB), 524288 (512KB), 786432 (768KB), 1048576 (1MB)

 

 

Ok hopefully you are still here.

 

You will do your self a big favor by starting with 

 

TBM = 80

 

THEN  

 

One at a time.

 

Bufferpools set to the smallest.  RT set to the smallest per Paul Above.

 

Go on your test flight as Paul says.  Etc.  As Paul stated above, increasing RT one at at time within each BP, until you reach max RT.

 

If you don't get what you are looking for,

 

Bump BP and go back to smallest RT and step it up over and over)

 

Then go on to the next BP then the Next set of RT.

 

Nothing much from those?

 

Bump TBM by 5

 

Start the process over.

 

Over time you will get a feel for the process  and skip a step or two as you get closer to your goal.

 

Yes a process but you will get there and man will you know it when you do!!  

 

Hope this helps.

TEXTURE_MAX_LOAD=2048

 

Before you go to 2048, given your system go with 1024

 

SHHHHHHH

 

dont tell anyone but I actually went to 512 once just for fun.

 

I think I got a little bump, probably not much.  But I had to try it for fun.  

ONE LAST Question.  I promise.

 

What is this...

 

TextureMaxLoad=30

 

Doing in your Display section of your FSX.CFG?

 

I don't mean at all to put you on the spot.  I am curious if there is something I missed in this whole thing or is this something your system does?  

 

I am curious is all.  I don't have that in mine.

 

Thanks.

 

Good luck!

TextureMaxLoad=30   This one has a similar purpose to TBM, i.e. it's a multiplier used by FSX in the algorithym used to calculate how much data it can, or should send to the GPU. Bojote first brought it up a few years back, as a tweak purported to be better than using TBM: Michael Moe more recently was playing around with it, and so did I in some measure, but nothing conclusive came out of my sessions so I've removed it again. I believe the normal setting is 6.

 

Paul, you mean I can turn on Bloom within FSX without really any performance penalty? I tried it quickly one time last week when I first started with DX10. I turned it off thinking it was still like it was in DX9?

Absolutely, Eric! DX10 is a different graphics engine, and can do many things more efficiently than was possible with DX9. Just remember, though - as you make the system do more work - which any post-processing does, (bloom being post-process along with SweetFX, FXAA, etc.,) - there will always be some frame cost, but the thing is, FSX - DX10 doesn't feel it as much as when using FSX - DX9.

 

All the Best,

 

pj

Hey Paul,

 

Happy Friday

 

I just had a thought, before I go shopping I just want to make sure that my OCZ ZT 750W power supply will be up to the job. I am not sure how much more power a GTX 780 needs over my 660 TI

 

Richard

:lol:

 

Yeah - 750 is good, Richard. Just check that it has an 8-pin and a 6-pin power connectors for the top of the card. It needs these.

 

Happy Friday - gonna be a happy whole of next week, too by the sound of it! Watch out, NCIX, CC, Newegg, TigerDirect! :lol:

 

Enjoy!

 

pj