Last updated Jan 9th, 2014

With the advent of the new breed of Intel multi-core processor the i7, and some correspondingly huge

advances in the graphic processor unit, DX9 FSX seemed, at long last to be delivering on Microsofts As real

as it gets sales statement and then along came Steve an inquisitive programmer who wanted nothing

more than to create a blog, simply describing experiments investigating how FSX works.

That was how Steves astounding path to opening the door to FSX DX10 began. Included below are

the links to his site and his more general FSX knowledgebase, links to Steves Shader10 patch, and finally a

link to an outline of Steve's "DX10 Scenery Fixer" - a recently-released commercially available application

which has much more capability.

A "must read" is Phil Taylors Blog on Accelleration-SP2, which is here, (doc) or here (pdf), as it

describes the many improvements that DX10 brings with SP2, and then visit Steves blog-site, as it will

introduce you to a world unseen by most simmers: read about flashing runways; shadows; fencing; AA, and

more. If youve already been there, and now want to take a first step into the new Sim, start here, with this

General How-To guide. I say General, as we all know - what works on mine may well be somewhat different

on yours, but by and large, the adherence to some known fixes, plus patience and a bit of technical moxy at

the end of the tunnel theres a somewhat faster, prettier, more stable sim, fewer, or even no OOMs, with a

lot more going on than DX9 would ever tolerate.. If you have a very powerful machine it will be Nirvana, and

even a low-or-mid-range pc will benefit, as FSX will run smoother, and with settings you never thought

possible.

While we've been using Nvidia Inspector to control or enhance FSX for a few years now - it's all been

"talking DX9", but over the last three or four years - there has been an enormous amount of hardware and

software development in this side of computing, and with FSX having a huge following world-wide, much of the

"tweaking and tuning" has been done by trial and error, some with good results, some with bad results but

here we are with DX10 suddenly working! Aside from Microsoft abandoning FSX, and Lockheed-Martin

developing ESP - along came Steve - and he's made DX10 a reality! We have a new sim!

The impact over the last eighteen months has been nothing short of exciting, with many new FSX-DX10

Discussion forums opening up, new fixes almost every day, patch after patch - and now finally a true repair

being applied to FSX in the guise of the SteveFX DX10 Scenery Fixer.

The fixes available via the free patches thus far are:-

1) Flashing runway/taxiway intersections: 2) Progressive Taxi markings missing :

3) Opaque chain fences: 4) Yellow/white runway markings transparency :

5) Most missing night scenery/semi-transparent dusk scenery (often miss-described as missing night textures)

6) Some addon cars with black headlights: 7). Cockpit shadows: 8) Softer shadows:

9) Eliminated false sun on VC roof and side wall. 10). Darker Water colour.

The fixes available via the SteveFX DX10 Scenery Fixer (DX10 SF) are as above, plus:-

1) Legacy Shader, allowing many fs8 aircraft and scenery packages to be used in FSX:

2). Vastly improved rain and snow: 3). Accurate cockpit shadows; 4). HD Airliner VC shadows:

5). FTX Global Lights: 6). Support for French VFR Vitaly lights: 7). Taxy lines fixed; 8). Milky water - gone!

9). Adjustable Sun/Moon/star water reflections: 10). Changeable AA: 11). Changed effects sensing:

12). Reflections for FS8 aircraft: 13). Adjustable Bloom for reflective, emissive, headlight and Halo light effects:

14). Light visibility for Orbx FTX Global lights dependent upon the weather: 15). Cloud Shader - disables

MSAA, cloud culling, and cloud clipping.

The retail version of the Fixer is available from the FlightSim Store, and incorporates many other

features which will bring life to many older aircraft and scenery's that you may have kissed goodbye to in the

transition to FSX!

Most of the advice below is important and, while occasional changes pop in now and again, it has been tested

and proven by countless "early adopters" of the Patch system over the last eighteen months, and still apply to

the new Fixer.

Note here that, while some similarities do exist, AMD/ ATI gpus settings and advice are not included in

this doc, as Steve has created a very good Summary here , and Charles Earl, (cvearl) has a very, very good

pinned document here.

Most of the testing here was done using a GTX580, and lately using a GTX780, and so Nvidia Inspector

settings are what are quoted.

So Ill start the ball rolling with the necessary changes before we start tweaking.

Prelude

Important -> Do you know if the default DX10 works on your machine?

In Settings ->Display - tick the Preview DX10 box, restart FSX and check that it does work before

applying this modification: If you dont see the option to select DX10 then either your OS, (DX10 does not work

on XP) your FSX Service Pack level, (must be at SP2 or Acceleration), or your hardware doesnt support it. Its

important that you try this out first to avoid a situation where the patch gets the blame!

The Patch:

Once thats successful follow this (v3.2.2), download, save and unzip the file, and then follow the

instructions to install the modified section of the ShadersHLSL file. Be sure to follow the very detailed ReadMe,

backing up the ShadersHLSL folder first.

If, by any chance the ShadersHLSL folder gets messed up heres a brand-new one - stock: just

delete the bad one, unzip this one, and copy it into the old ones place, then delete the two Shaders cache

folders inside your (Windows 7) C:\Users\{your username}\AppData\Local\Microsoft\FSX\.

FSX will then rebuild these two the next time it starts.

The SFX DX10 Fixer:

After purchasing and downloading the retail Fixer, unpack, and simply follow it's manual to setup FSX

to use DX10 as it was intended. This is a good manual, not too difficult to follow, and this doc here will serve

as a supplement for those who need a "bit extra" in order to understand the where's and why'.

If you find that some of the shader check boxes are greyed out, it's probably as the result of using the

Patch system - and the shaders are now non-standard. This being the case - simply uninstall the DX10 Fixer

Libraries, as described in the Fixer manual, delete the FSX\ShadersHLSL folder, and then replace it youre

your backed-up copy - or this stock one here. Don't forget to also delete the shaders cache folders at the same

time, as per "The Patch" paragraph above.

Background processes:

If at all possible also download and setup Ken Salters AlacrityPC, (free) configured such that it kills

as many un-needed services and processes as possible, and then launches either TrackIR, with you launching

FSX, or the other way around. One does not need the Acronis Scheduler, SyncAgent, Nonstop Backup,

Bonjour, Google Updater, Windows Cardspace, iPod, Appl. Identity, Cryptographic, Function Discovery, Fax,

Office Source Engine, Viewpoint, Search, Homegroup services- all running - while FSX is struggling to get 25

or 30 frames! - so I always use AlacrityPC (or from here). It has a very small, 1.5MB footprint, and can be

used to stop all the services and processes that arent needed, and will launch TrackIR, or AS2012 or FSX,

itself.

PMDG Pilots Please note this: in relation to the above recommendation re stopping processes:

we need to warn you that you will have one running process that must not be stopped. PMDG

products need an application called FLEXnet Licensing Service running in order that they can

run. Both GameBooster and Alacrity have the ability to stop this, and you may not be aware of it.

Make very sure that the Action to take is set to Nothing. PMDG advises us that this is a major

source of service requests.

Backup your FSX DX9 User files..!!!

Because were never 1000% sure that we are going to end up with a great sim, we need to make sure

we can get back to FSX as it is at this point a DX9 version. There are a couple of ways to achieve this: my

preferred way is to create a new folder under the

C:\Users\{your_username_here}\AppData\Roaming\Microsoft\FSX\ folder. Name it as something like DX9

Configs.

At this time, then, as we make this folder, we are sitting in the:

C:\Users\{your_username_here}\AppData\Roaming\Microsoft\FSX\ folder, right?

This is where the operational dll.xml, exe.xml, cameras.cfg, scenery.cfg, and fsx.cfg all reside, and we

need to make sure those files are safe, along with a copy of the current Nvidia Inspector profile or your ATI

CCC config. We can do this by simply Copy and Paste that \FSX folder, complete, into the new DX9

Configs folder. Safe!

Nvidia Inspector .nip files:

With that done, lets backup Nvidia Inspector as well, so - choosing our MS Flight Simulator X profile,

shift over to the top-right a bit, and click on the little box with the green arrow pointing up, and select the

Export Current Profile Only, then Browse to the folder which you just made, and save that FSX-DX9 profile in

there as well. This makes it a special profile, and it wont get forgotten - as it might do when mixed in with

fifteen other good profiles in its normal home folder

The above also assumes you have the latest video drivers and software, but here are their links, in

case you dont have them. We need to install a "known good" Nvidia Driver from here: - the latest is 331.82.

Similarly with Nvidia Inspector from here: (guru3d) (or other favourite site.) The latest is 1.9.7.2.

DX10 Anti Aliasing: Nvidia Inspector

After selecting the "MS Flight Simulator X", let's change the header so that you can see all the settings

you need to change on one page - look for, and click on the funnel icon.

Only the settings mentioned below need to be changed, the first being at the top of the screen - seen

above - set AntiAliasing Compatibility (DX1x) to "Bioshock". This will fix the AA for aircraft shadows on the

ground, as per here. ". (Courtesy of "VeryBumpy")

Next, AntiAliasing, where "Behaviour Flags" will be set to "None" and "Gamma Correction" set to "On".

>>>>>> When you are in DX10 mode the main anti-aliasing options in the Nvidia or AMD control panels do not work.

2). Set Inspector to:-

________________________________________________________________________________________

Example 2 You want to set AA to 4x:-

1). Choose your DX10 SF AA setting here:-

This will instantly put the following two lines into the fsx.cfg [GRAPHICS] section:

MultiSampleQuality=0

Example 4 You want to set AA to 8x - (note:- this one is hard on the system.)

1). Choose your DX10 SF AA setting here:-

This will instantly put the following two lines into the fsx.cfg [GRAPHICS] section:

MultiSampleQuality=8

Preventing SGSS Blurring:

This part of Texture Filtering is linked to the SGSS part of AA in the previous two pages, and serves to

correct some of the blurring which happens when using SGSS:

"Driver Controlled LOD Bias" must be Off, and the LOD Bias(DX) should be set according to this table:-

2x SGSSAA: -0.500

4x SGSSAA: -1.000

8x SGSSAA: -1.500

________________________________________________________________________________________

_______________________________________________________________________________________

Common:-

Some flyers find that "unlimited' fps works best for them, but here I recommend letting FSX control

frame rate, and set it just above the 1/2 Refresh Rate: i.e. normally 30 - set it to 31, 2 or 3, as the Driver does

its best to keep as close to the selected rate as possible.

In you only have a single monitor - then set the Multi-display/mixed-GPU acceleration to Single-display

performance mode.

Vertical Sync tear control - Standard.

Vertical Sync - 1/2 Refresh Rate, with "DisablePreLoad=1" set under [Main] in the fsx.cfg. This works very well

for fullscreen vsync - but only in fullscreen.

Note:- Vsync in Windowed Mode needs "ForceWindowedVsync=1" to be set in [Graphics]

________________________________________________________________________________________

Changes to Settings within FSX:

To be honest, although you can begin with your old cfg file, its probably best to err on the side of good

practice, so delete the old one, start FSX, let it make a new one, then fix it. So having done that - open up

the Free Flight screen and load your most normal flight: something like the default C172, at a nottoo-busy

airfield: one of the PNW airfields is fine not too close to Seattle or Vancouver perhaps Skagit or Diamond

Point maybe the Orbx freebee - KHQM Bowerman. Make it day, Summer, Clear skies and save this

as the Default flight. Ok now into settings. Because this is a new fsx.cfg, youll have the crazy music. If you

like it keep it! What concerns us is the more important performance config. You can set up your sound, your

Realism, etc., later, but the performance and looks are what concerns us most, SO

Settings ->Customize ->Graphics->Target frame rate ->30 - 33 or unlimited, dependent upon whether using an

Nvidia or AMD gpu. "30" is Refresh Rate of 99% of all LCD Monitors, and all new drivers will make an

excellent attempt to keep your precious fps in that region. Set it slightly high. Set the AMD/ATI settings as per

Charles' notes above.

"AntiAlias" must be ticked in FSX.

Filtering: Anisotropic..

AntiAliasing: Ticked Set the left side as you like, but un-tick the right side boxes (for now).

Settings ->Customize-> Scenery->Mesh Resolution-> 2M: Water Effects-> Low 2.x, Med 2.x or High 2.x :

Low and Med look pretty good, and dont cause any shimmering, whereas High 2.x causes land

reflection shimmering on most pcs, and will require excessive SGSS to get rid of it.

Land Detail Textures: Ticked Ground Scenery Shadows: Un-ticked

All others: as high as you think may work, as with DX9, but beware full right will give more scenery and AG

than in DX9, (it will take it) so you may happily back them both down - and still have better than DX9.

Settings ->Customize-> Weather-> Cloud Draw Distance: 60 Miles/96km Thermal Vis: None

Rate of change: Medium Detailed Clouds: Ticked Cloud Coverage Density: Maximum.

Settings ->Customize-> Traffic->AI: 20%... GA: 20%... Road: NOT MORE THAN 10%: No red numbers, Ships

or Boats.

It is worth noting here, if your other settings are high-to-maximum then that Road traffic may well

cause flashing and artifacting. Here are the "known frame killers".

Quit FSX, as we now need to add some known fixes to the cfg file

Open up the FSX.CFG using Notepad, Notepad++, TextPad, or other ASCII editor:

... and check, add or modify these lines under each of their respective section headers: As mentioned earlier - to get AA with DX10 it is necessary to set two new parameters in your fsx, so check that the DX10 Fixer has added them, or if using the patches, add the following entries into the fsx.cfg, under the [Graphics] section: MultiSamplesPerPixel=2, 4 or 8 // MSAA amount MultiSampleQuality=0, 8, 16 or 24 // Quality level D3D10=1 // DX10 HIGHMEMFIX=1 // A fix Microsoft forgot. This is a "Must be in the cfg".

TEXTURE_MAX_LOAD=1024 // Can go to 2048 later [Display] TEXTURE_BANDWIDTH_MULT=XXX // Between 40 and 120 in multiples of 5. High-end start at 80.

UPPER_FRAMERATE_LIMIT=30 - 33 // Set in FSX to work with the Nvidia driver RR setting. [Main] FIBER_FRAME_TIME_FRACTION=0.1 // Generally 0.12 0.22 gives very smooth flight: 0.33 is default, but may result in stuttering: Lower than 0.1 may give blurring of ground textures when flying fast at low level. Vsync fix:- "DisablePreload=1" // An issue for some and not for others, as Nvidia Inspector using Refresh Rate, Standard and 30 set in FSX usually fixes it; however for those who are having conniptions with vsync tearing this fix came from "Leonhardt": just add to the [Main] section of your fsx.cfg [JOBSCHEDULER] AffinityMask=14

// 4 Core HT off - 14 3 Main threads 1 worker

// 4 Core HT off - 12 2 Main threads 2 workers

// 4 Core HT on - 254 3 Main threads 1 worker

// 4 Core HT on - 252 2 Main threads 2 workers

Although preached as "HT always off" by many, from a number of tests with DX10 - using HT on, and adding

AM into the config appears to help maintain a framerate stability by an extra 2 - 4%..

____________________________________________________________________________________

BufferPools:

A reasonable summary on how they work is here - it's not a 'heavy' read, and will hopefully create an

understanding of how to tune the darned things! Yes - configuring BP will make a big difference.

Example 1. Example 2.

4.9-gig proc/GTX580 5.0-gig proc/GTX780

[BufferPools] [BufferPools]

UsePools=1 UsePools=0

RejectThreshold=262144

For the very best performance BP does need to be in the cfg, default PoolSize is 8388608 (8MB), and

here are some sizes to test:

PoolSize= 8388608 (8 MB) 20971520 (20MB) 5242880 (5MB) 10485760 (10MB)

RejectThreshold=524288 (512 KB) 786432 (768 KB) 1048576 (1 MB) 262144 (256 KB) 131072 (125 KB)

Finding the right size is time-consuming, but not difficult, because it interacts with other parameters

TBM & Water, for example. TBM is a throttle that increases the graphics data to the GPU. Its pressure.

Depending upon how high texture, mesh, autogen, traffic, weather or set too high a TBM setting may cause

graphics corruption, max is about 120, 80 is good.

Save this config to the Configs folder as the default DX10 Master.

Done!

Now go Fly! From here onward experiment away, using this base: you will find you can move the

scenery complexity, autogen, weather and traffic sliders around with considerably more abandon particularly

if you have a powerful pc. Not only is the experience smoother, the fps variance stays much tighter than in DX9

and with a higher load.

A Couple of Extra Notes:

Nav and Strobe Lights for aircraft which use the MS stock lights:

Are now included in the Patch Version 3.2.2, along with installation instructions

Update: This is fixed in the retail DX10 Scenery Fixer.

Clouds:

Steve has a good comparison between DX9 and DX10 clouds here, and a note on testing.. Post #7.

Following some good research on REX clouds RodO (The Family Man) here, post #14, states that he found

that - after making sure that DXT5 and 1024 x 1024 textures are used the frame drop is gone. The retail

Fixer has (at this moment) three functions which can improve frame rates when in heavy cloud:

Disable MSAA, Cloud Clip, and Cloud Cull.

Rain Fix:

For patch users, you will need to open up the \ShadersHLSL \Terrain folder, and replace the rain40fx

file with this one. Don't forget to delete the Shaders10 cache folder once it's done. The retail Fixer has (at this

moment) a slider for rain brightnes, slow snow, and stretch - for triple moniotors.

Courtesy of Matt Nischan

Runway Lighting:

From a post by Brett Lucas I had approach lights, but no runway lights. So last night I was going

through many of the posts and came across one very important one. If you install Michael Swannicks

fsx_lights.zip, its the Halo bitmap that will fix the runway lights. The trick is, if you use REX or Active Sky 2012,

you need to UNCHECK runway lights so it does not get overwritten. In my case, I use both and unchecked

both, and presto, I had awesome lights again.

Michael Swannicks lights found here: Instructions are included in the zip. The DX10 SF has much better

control over lighting, and can correct for almost any lighting issue.

Incompatible Textures:

Whereas the patch will take care of many incompatible textures, you will find some not many - that

are still incompatible with DX10, and here, if this is a major concern I would suggest you go to

FlightSimTools.com, and download their AddonConverterX. From my experience it has taken care of many,

but not all, by any means, of my FS8 & FS9 port-over aircraft, and didnt work on the two ORBX (free) scenery

packages CEN4 and CEJ4 (NRM). A point to note here, too I have read reports that in demo mode it doesnt

do a very good job, and a second point it causes pale squares to appear in the water as though the coastal

water masks arent right. This is not too much of a concern for me, as I only saw this in the ORBX Skagit

KPAE Anacortes areas, and a). not everyone uses ORBX PNW, and b). not everyone has port-overs.

Update:

99% of all incompatible textures are fixed in the retail DX10 Scenery Fixer.

Orbx PNW custom street lights:

If one does a night flight with the Orbx Night lights selected, when flying west from Fall City (as an

example) at say, 2500 feet, one will notice that clumps of those nice street light flash on and off. Orbx staff

have suggested this is purely a DX10 issue, and therefore will be very low on the totem pole of things to be

fixed however, if one switches back to DX9 you will be noting a frame drop of at least ten maybe fifteen

frames, and those same lights whereas they dont blink on and off now they dim on and off. The effect on

the ambiance is the same.

Update:

These lights are completely fixed in the retail DX10 Scenery Fixer, as are the issues with Orbx's FTX

Global lights. The Fixer also has the automatic ability to reduce the size/glow of various lighting systems in

foggy conditions.

Aircraft Shadows:

I fly mostly in the Orbx PNW-NRM-CRM area, and during testing I noticed (actually on Goheen

southerly approach) that the (default) static aircraft shadowing at some of those airports, was just a black

square. The answer for the non-programmers is to turn off the Orbx aircraft in the respective Control Panel, so

that your UT2 or MTX, W.H.Y aircraft takes their place. I should add - this is not the case at all Orbx airports.

Orbxs free GA traffic bundle unfortunately many of the aircraft are also not compatible with DX10.

Update:

All Orbx GA AI are fixed in the retail DX10 Scenery Fixer, but the shadows found thus far, are under

static aircraft at PAJN and Goheen, caused by tile junctions crossing the airport, and so require an author fix.

Update - Alex Goff has fixed Goheen.

Tool Tips missing:

Yup, it's missing in full screen view! If it's important, you can use this method to "fix" windowed mode so

that it looks exactly like full screen, Avsim Library filename is "pseudo_full_screen.zip" (without quotes).

Bloom:

Extracted from Steves WordPress Site:-

"Its possible to adjust the bloom effect by editing the last few lines in General10.fxh and then recompiling the

DX10 shaders. (Done by deleting the Shaders10 cache folder, which is at:-

C:\Users\{your username}\AppData\Local\Microsoft\FSX\ )

The lines in question are:-

#else

static const float fHdrSpecularScale = 1.11; Change this number. Larger increases bloom.

static const float fHdrEmissiveScale = 6.0;

static const float fHdrCopyScale = 4.25;

static const float fHdrModAlphaScale = 3.92;

#endif

Update:

This is fixed, and is now fully adjustable in the retailDX10 Scenery Fixer, not only for lights, but for

reflections, halo and automobile headlights!

... however... an alternate solution would be to download and install "SweetFX", v1.5.1. It also replaces the

ENBSeries (and "Shade" too, unfortunately!) The official release forum thread is to be found here.

Note: SweetFX will occasionally prevent FSX from launching, and it happens after refreshing FSX using

the "pause:break" button. It seems that the SweetFX_settings.txt file becomes corrupt. I have not noticed this

when switching between windowed and full-screen mode. The answer is to simply note the settings, and copy

in a new one from the downloaded package.

ENBSeries:

Does not work in DX10, and will cause a crash on start-up. I believe the culprit is the d3d10.dll that is

part of its structure, and it can be found in the root folder of FSX and deleted.

Shade:

Works in DX10!

SweetFX:

All versions from 1.3.7 through 1.5.1 work very well, and bring an enormous array of colour and

vibrancy to the sim - a very configurable addon. A desktop link to the SweetFX_settings.txt will allow one to

change any parameter completely on the fly. A search on Google will also turn up a HUI front-end, but I have

not used this.

Blue squares:

While visible blue squares are completely fixed with Patch 3.2.2, there are now occasional black

squares popping up, particularly over water, and Simon - (Avsim member flying_w) noticed a line in the cfg left

over from DX9 was SWAP_WAIT_TIMEOUT=2, so he removed it, and in doing so found another fix, but in

retrospect - I've found that its removal when running BP=0 - I still had small black squares popping up (even

with water at 6 - so I added it back in, set it to 0, 1 and then two, and found at 2 - the squares had gone. There

is a link between this and TBM, so some more testing to do on this one!

Update:

The Blue Squares issue is fixed in the retail DX10 Scenery Fixer.

D3D11.dll Crash-to-Desktop:

This one began to occur around the Nvidia 314.XX series, and apparently impacted other games, too.

Thanks to some diligent work by Steam member "CCentR". The issue is fixed by un-installing Microsoft

Update KB2670838 and watching for it to be re-installed. It needs to be "hidden".

UT2 Traffic and A2A Shockwave Lights:

From gigemaggs99, Nov. 11, 2012: Re: This site, quote from his post below:

If you have A2A shockwave lights and UT2 this is a great set of files you can edit the AI aircraft.cfg files. It

takes a few minutes since there is no auto-installer but I just made sure to make a backup of the original prior

to editing them."

In case their site goes down, you can also get the zipfile here.

From bleedair.de Copyright 2009-2012:-

"To add the effects to your UT2 aircraft please download "ut2_aircraft.zip" and exchange the aircraft.cfg file of

each aircraft within the respective folders following your FSX installation path:

1) For copyright reasons the download does neither contain SHOCKWAVE 3D LIGHTS REDUX program files

nor the complete set of UT2 aircraft but only the respective aircraft.cfg files. Both, UT2 and SHOCKWAVE 3D

LIGHTS REDUX installations, are required to run the modification provided by the data of this download!

2) Some aircraft did not have a [LIGHTS] section within their aircraft.cfg file so there was no chance to change

it. For a resolution all the aircraft would have been necessary to be converted to flyable aircraft. However: More

than 90% of the traffic will show beautiful nav lights, strobes and beacon lights."

Water:

You might have noticed that the DX10 water is much better than DX9. One reason is that it has four

bump maps to DX9s one. Also, the wave speed and white caps effect is linked to wind speed and direction

YES!! - Much better; however a second issue has been raised, that of water colour while being very much

more realistic, and matching the current weather, etc., are generally a much lighter color than in DX9. In his

later patches, therefore, Steve has included a patch to darken the water some, and this works fine for most

people, but - this is a different sim, with different files and code, and so you might also want to make your own

changes: FSWCLite, REX & AS2012 all have the ability to change the color, texture, wave type, etc., to suit

your particular taste. RodO has also noted that for best performance with no visual impediment (him using

REX water textures) make sure they are using DX1 compression.

My personal favourite - ActiveSky 2012 - Waves - 04 "Frequency".

We arent new to water color, of course - or other anomalies, but as mentioned at the beginning if you regard

this as a new sim then you will be successful in your quest for that famous MS As real as it Gets statement!

Update:

The water colour fix, and other water enhancements are included in the retail DX10 Scenery Fixer.

The Future:

This document was created to help new, unsure, or just plain interested simmers to be as successful as

possible when implementing Steves DX10 Patch, released June 7th 2012 or the newer and more capable retail

SteveFX DX10 Scenery Fixer. DX10 is not perfect, but it improves just a little bit more with each of Steve's

releases, with the DX10 SF being constantly under revision. The future of the patches is unsure at this

moment, as the SFX DX10 Scenery Fixer is now on the market, but 3.2.2 will still be available at the Avsim

Library, as well as from the DropBox site mentioned at the beginning of the doc.

If you need further help with most DX10 issues, feel completely free to pm me on the Avsim forums. If

practical, individual TeamSpeak TeamViewer sessions are sometimes available for some hands-on fixin

through the DigitalThemeParks TeamSpeak3 server at ts3.digitalthemepark.com. as long as you remember

that Steve is the genius behind the DX10 Scenery Fixer, and I'm still scratching in the dirt for much of this!

All the Best,

Paul J