:LMAO:   "My son would be more than happy"!  :lol: 

 

 

I'll bet he has his own XBox and never gets a chance to touch your pc!

 

:lol: :yahoo:

 

pj

Well Rich,

 

I am in a bit of the same boat as you.  Again my machine as proud of it as I am, IS aging,

 

HAVING SAID THAT though. I am really blown away by what I can do with it even now.  BUT only with DX10.  (Maybe DX09 if I spent a lot of time tweaking)  But I am a recovering tweakoholic and my support group would frown on that.

 

What is nice about all I have read here in first with Nick's Bible, then AVSIM Basic FSX Setup Guide, then on to the DX10 Material is that it really gives the user a great benchmark to fine tune what you have, so that the experimentation with the sliders now makes sense.

 

Tedious yes, but I have found out a bunch of cool stuff.

 

For instance.  I was wanting to push my rig and find out how to mitigate stutters out of again, MY rig.

 

One thing I found out was my setup likes

 

TEXTURE_BANDWIDTH_MULT=85

 

[bUFFERPOOLS]

UsePools=1

PoolSize=5242880

RejectThreshold=128000

 

I found this gives me a VERY smooth flight with no stutters flying stock slow aircraft and the Eaglesoft CX 2.0  (Still a work in progress but nice)

 

Sliders as per documentation above.

 

So let's push it now.

 

F18

 

Well to gain the "enth" degree of performance I set my LOD radius slider to small.  But if you get in an aircraft and slew to say 45k.  You get the blurries

so LOD was set to half for the CX2.0

 

Now F18.  I want to do some low high speed work.  LOD, you would GUESS should go to small again.  NO!.  LOD needs to go to MAX.  With it set to MAX there is a lot less autogen popping as it is already set to a quite massive area on startup.

 

Low and slow aircraft can use LOD min, like my Carenado 210.  Too low to notice the blurries but I like the bump in performance.

 

On Texture Resolution. 

 

You'd think you'd want to set that to something like 2M for the F18 work to get best frames right?  Nope.  Looks crappy.  2M would do well for the CX 2.0 as you are almost always up in the cruise altitudes not needing 7cm.  The F18 Work needed the 7CM, for better low altitude appearance.  Etc and so on.

 

So along these lines I started to really think about what Nick Says.  SET FSX FOR YOUR NEEDS and not someone else's per se.

 

So I wrang out my sliders from one end to the other and along the way I found another neet little trick.

 

Now this one is just for me and my taste most who read this wont want to do this.  But it works really well for an old machine like mine and maybe like yours even though you have a lot better equipment.

 

Along all of this reading and learning I became familiar with Airport Design Editor.  The reason is that I really do not care about Aunt Nellie and her farm out on highway 41 being just so, if you will.  I do like airports though with a lot of buildings, and objects, and those airports are located in dense metro areas.  Like KTEB.  (Just outside NYC)

 

So I thought, It sure would be nice to have all the buildings objects etc on our airports, that we get when we max the Scenery Complexity Slider, but, not have the whole entire world go to VERY DENSE or DENSE as well,  Well you can if you know how to use ADE.  Takes about 5 to 10 minutes and ADE is supported well and best of all it is free.  You can change and update anything there and well not there on any stock FSX airport and even make your own fields.

 

So

 

There is a setting in every airport BGL that allows the developer to determine at what slider setting "Scenery Object "X" comes to view.  So I happily went in and changed my airports and other airports I fly to often so that all the items I like to see, appear with the Sparse Setting.  

 

Now I have an in tact entire airport even though my scenery is set to sparse!  What a nice life to live. My airport(S) look dense but my scenery is set to sparse.  EVERYWHERE is set to sparse adding in a heckuva lot more frames.  Since I dont use payware scenery, autogen does the job nicely set to sparse.  What else is neat is that MOST cities have quite a lot of buildings/objects ets,  show at sparse.  Enough to look at for 20 seconds on an approach again in my case.  

 

BTW.  What I carry over from RW flying is that when I am actually flying a jet into a major metro area, the last place I am looking is outside the window, at the scenery passing by.  I am fixed on radios, FMS, and the AP.  I like to look at the scenery with a beer and a burger while I am INSIDE the scenery. LOL.

 

For weather I use Active Sky.

 

Radar Contact does my ATC

 

Then lastly what I do is watch my Frames to see the average and then set it up a tick above that.  Even though the readout says 29 to 33 FPS, it seems and looks like I am pushing 60.

 

Sorry to opine here but as long as you are giving it a go, hopefully this will help.

Wow what a reply lol

 

You made some very interesting comments. I mainly fly airliners 737NGX, Airbus X Extended and of course the 777.

 

I realized quite quickly the importance of a well balanced system especially when I introduced Rex 4 and Active Sky Next.

 

I found an awesome overclocking guide that made me realize I had only done half a job. Now I have a very stable 4.7 OC. MY rig only runs FSX so I never found the need to stress test. For me a 11 hour overnight from Toronto to Russia was good enough

 

I guess where this quest is leading me is that I am very interested in what really makes FSX tick.

 

I like you love to tinker. Steve's DX10 fixer for me was a real game changer.

 

I am going to spend all weekend tinkering and getting some good hours in with my virtual Airline (Air Canada)

 

Happy as a pig in .... Lol

 

Richard

NICE!!  

 

I have a funny story.

 

So In efforts to finally see how the Honeywell Primus FMS works, in preparation for my RW job as a corporate pilot, I downloaded Eaglesoft CX 2.0.  Fabulous Add On.

 

Just so happens my home airport is no longer 9A1 here in the states, it is now KCVC, of course 9A1 was not recognized in the CX 2.0 FMS for one reason or another.  So.  In efforts to change the aiport ICAO I read that Airport Design Editor would do the job.  It's free and relatively easy to learn.  

 

Oh boy did that open a can of worms.  I found myself up late making sure everything was as to the letter on our home field as possible.  ALL over wanting to change the ICAO ident only. All the while chasing this DX10 down it's rabbit hole too.    This now is where I taught myself that neat trick about setting my main scenery slider to sparse and make sure that my airport buidlings and objects show up as normal.  

 

My wife said I need a hobby.  Last time she says that!  

 

I have been around Flight Sim since the olden days when Flight Simulator was owned by Sub Logic which goes back to before 1982.  Not until Microsoft gave up the ghost have we had the ability to really get into the nuts and bolts of it.

 

Good luck with this weekend.  For my aging machine it seems to boil down to in sim sliders (IQ) along with Bufferpools/Reject Threshold, and  TBM.

I have been doing some researching while stuck in a hotel last night (gotta love business trips)

 

I eventually want to end up with a 3 screen setup and I know the 660 TI I have will not cut it so I have decided to upgrade my graphics card which is probably the weak point in my system. The 780 looks to be a viable option. I have narrowed it down to 2 different models and would love Paul's input here

 

1) 

ASUS GeForce GTX 780 3GB GDDR5 (GTX780-DC2OC-3GD5) 
- 889 MHz Clock, 6008MHz Memory 
- PCI Express 3.0, Dual-link DVI-I, DVI-D, HDMI, DisplayPort

 

2) 

EVGA GeForce GTX 780 SC w/ ACX Cooler 3GB GDDR5 (03G-P4-2784-KR) 
- 967 MHz Clock, 6008 MHz Memory 
- PCI Express 3.0, Dual-link DVI, HDMI, DisplayPort

 

From what I can see the main difference seems to be the clock speed, the EVGA being the faster. It is a little more money but is it worth it ? I tend to sway towards Asus products simply because I have used their components for years and have been very impressed with the performance a build quality.

 

You gotta love this hobby, probably would be cheaper to buy my own plane lol

 

Richard

You won't go wrong with either card, Richard. FWIW - mine is a plain jane EVGA, following on the line of success with the 580 and earlier 9800, etc., - zero failures with any of them.

My mobo's are all ASUS and I would not hesitate to purchase an ASUS GPU, but it's not likely that you will notice the slightest difference between them when running FSX.

 

All the Best,

 

pj

Thanks Paul,

 

Looks like there will be a little retail therapy this weekend

Hmmm.  Food for thought.  ESPECIALLY now that I have the background I do with Bufferpools.  TBM.

 

Paul.  Even though Nick has stated that we should marry like kind with like kind if you will.  I get that.  

 

WHAT IF however I were to upgrade to a (Circa 2010 2011) 2 gig or so GTX 580 or even 680? if you could give an opinion on that?

 

I am thinking even though my Phenom II Black Quad is older, it is still a fine chip OC and stable at 4.0?

 

The thought would be to upgrade the card and off load more to it.  ( I love this because it is so widely known that FSX has nothing to do with the GPU and all to do with the CPU )  That was the going knowledge back when I built my rig, and that is why I went cheap(er) with the GTS 450.  It actually does a fine job in my opinion for what it is.

 

Anyhow your thoughts would be well appreciated.

In P3Dv2 Bufferpools are gone - depreciated. I often wonder if it even does anything at all in FSX DX10 mode - I see no change at all on my system with or without. If I switch to DX9 I can immediately see an impact as it will push GPU usage to 99%.  The thing I have yet to test is memory usage. It would seem that if I run the same scenario  then do it with no bufferpools , the memory usage would be lower (since there are no buffers being generated - it gets sent direct to the card)

 

Also I still see people setting a TBM with using unlimited FPS - It is ignored according to Bjote's findings back in time... 

Hi friends,

 

I have read Poul's article about BufferPools - but this is technical language and I don't understand it well, so huge request to you...

 

After install DX10SF, there are some things which I don't know exactly how to resolve:

A. small stutters while fast moving external camera,

B. longer stutters (3-4 sec.) with 10-15 min interval, and

C. serious frames drop in VC when I flight in dense clouds:10-12fps (normally, on ground: 25-30fps).

(all issues in PMDG aircrafts: NGX, 777)

 

Ps. I use nVidia Inspector to limit frames: 35fps. I think there is smoother with limit in Inspector then in FSX.

 

Ok, so I suppose that above problems can be resolve by proper settings of BUFFERPOOLS parameters in fsx.cfg file:

UsePools=

RejectThreshold=

 

..or maybe others parametres?

 

My FSX.CFG:

 

 

[JOBSCHEDULER]
AffinityMask=14

[bufferPools]
RejectThreshold=131072

 

[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]
DisablePreload=1
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=7
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=1326

 

[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

 

 

 

Specification:

i5 2500K 4,3GHz, 8GB RAM, ASUS GTX560 DDR5 1GB DCII OC

Addons: ASN, REX4, UTX and others which rather hasn't affect on graphic...

 

Ok, I think that I have to set UsePools=1, am I right?

 

What about RejectThreshold? Actually I have =131072.

And is it necessary to set PoolSize=?

I don't understand relations between these three parametres?

 

I also don't have set FFTF - is it wrong?

 

If you want to see DX10SF settings, nVidia Inspector settings or other informations, please ask...

 

 

Maybe I'm wrong and there is another solution of above issues? I'll be glad of your suggestions and help.

 

Ps. I'm going to install SweetFX, but I have doubt of negative affect on my fps :(

 

 

Best regards (and sorry for my english )

Lucas

@Jet:

 

The 580 would be a good GPU to aquire new, Jet (but will need a search!) - or even picking up a used one. Ask around here - I got $230 for mine a few months back - and it's still going strong to my knowledge!  It will also work with a 4770K running at 4.6-gig or higher, so it can still have a future.

 

@Slayer:

Hi Steve. BP do indeed work in both DX9 and DX10, Sir!. The reason your GPU usage goes up is because it's now doing all of the graphics processing - that's the major difference between DX9 and DX10. This gives the system back the system memory that was devoted to graphics manipulation under DX9. This was shared between the CPU and the GPU.

 

 

 

(since there are no buffers being generated - it gets sent direct to the card)

 

Of course there are graphics buffers! There may be no user-configuration for buffer parameters in P3D - but that doesn't mean there are no buffers! 

All "UsePools=0" means is that in DX10 the ACES team gave the user the opportunity to manage the buffers (UsePools=1),  or just let the GPU  manage the buffers (UsePools=0).

DX11 is just an enhanced and updated version of DX10 - both are very similar in architecture.

 

 

 

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,  :smile:

 

pj

If using Usepools=0, doesn't the ways setting need to be on something specific? I use the low setting because like NickN said, why have the two extra passes.

The two extra passes are with regard to the water setting needing to be at 6 when using DX9, Eric - to preventing flashing - but that doesn't happen when using DX10. Nick has never explored DX10 - nor BufferPools in the way we have. I wish he would, as it would cut my work in half. It also doesn't work in the way which Bojote describes.

 

When one has a high-end system - say 4.7 to 5-gig+, feeding a 780, and usepools=0 - the thing just flies. 3 gig of graphics memory is ideal. One can easily slow the system or speed it up by changing the buffers. It's a very good tuning tool.

 

 

 

If using Usepools=0, doesn't the ways setting need to be on something specific?

hmm - not quite sure what you're asking here.... what do you mean by "ways setting"? A pm is fine if you want.

 

All the Best, - off to bed! "I'm being called....." :wub:

 

pj

 

 

All the Best, - off to bed! "I'm being called....." :wub:

 

In your dreams! :lol:

The two extra passes are with regard to the water setting needing to be at 6 when using DX9, Eric - to preventing flashing - but that doesn't happen when using DX10. Nick has never explored DX10 - nor BufferPools in the way we have. I wish he would, as it would cut my work in half. It also doesn't work in the way which Bojote describes.

 

When one has a high-end system - say 4.7 to 5-gig+, feeding a 780, and usepools=0 - the thing just flies. 3 gig of graphics memory is ideal. One can easily slow the system or speed it up by changing the buffers. It's a very good tuning tool.

 

 

 

hmm - not quite sure what you're asking here.... what do you mean by "ways setting"? A pm is fine if you want.

 

All the Best, - off to bed! "I'm being called....." :wub:

 

pj

Sorry Paul autocorrect I meant water setting in FSX.