SteveFx

Whenever you make a change to settings within fsx it writes out the config.
 
The dvd version always sets texture max load to a maximum of 1024 when it dos so.
Fsx steam edition has been updated not to do this.
 
This has annoyed people for years. The reason for the check in the diagnostics is to warn you if this has happened.

Hello Alain
 
You have turned on missing texture alert, just turn it off. You can do that either by editing fsx.cfg or by using the fsx.cfg edit screen from the top menu of dx10 controller.
 
If you do the former I think it's in [scenery]
 
If the latter ( which just edits the file for you) there is a tick box for it which you should untick and press ok.

Its a fsx feature called sun glare which works just as you describe.
 
Unfortunately Aces introduced a bug with SP2 and it  is turned on and off  by the same  menu item used for the DX10 preview setting.
So in SP2  it is always off in DX9 and always on in DX10 (as Dx10 preview is off in DX9 => sun glare off and on in DX10 -> sun glare on)
 
There is an option in the fixer misc dialog to hide the effect although this will also disable the rather similar G effects.

Ok, I have a simple workaround...
 
WARNING If you aren't confident copying and renaming files don't try this.
 
The instructions are
 
In the directory <fsx dir>\SimObjects\Airplanes\LHC_Trinidad_TB21GT\texture
 
1)  rename the texture GlobalEnv_AC_Plexi.dds  to something else e.g.  xGlobalEnv_AC_Plexi.dds
 
In the directory <fsx_dir>\Texture
 
2)  create a copy of the texture GlobalEnv_AC_Chrome.dds
 
3) rename that copy to be called GlobalEnv_AC_Plexi.dds  
 
DO NOT rename the original!!!
 
There is some problem with the DX10 engine and the  version of the texture shipped with the aircraft that I don't fully understand. 
I think that DX10 is falling back to the bkg.bmp texture in some way.

You need almost certainly to turn on Super sampling and for DX10 the only way to do that is to set Smart Grid Super Sampling  (other types dont work) which can only be done via Nvidia Inspector.
 
Nvidia Inspector is  an editor for Nvidia profiles and exposes some settings that  the Nvidia Control Panel itself doesn't.  
 
I once went as far as downloading the Nvidia SDK and adding the settings into the DX10 Fixer Control Panel but then I decided that I would spend all my time answering questions about AA so I never actually released it.
 
So the bottom line is that it isn't some fearful complex program that runs whilst you are using FSX - it is just an editor for a config file used by Nvidia.

press the diagnostics button
 
(it should be showing a warning icon I would suspect)

Yes. It's an essential part of fsx that your system is missing.
 
Either
 
A) copy the missing file from another fsx system - if you have steam you can install onto several PCs.
 
B) search the avsim library for by Michael J Swannick called fsx_lights.zip which is a set of replacement light textures including a fx_2.bmp

Yes select Active Sky Next - I will update the text in the next release.
 
No special settings are required for the PMDG 777 on its own - however as you have the 737NGX you should still tick the 737NGX option.
I hope that makes sense

Follow the link in my signature and select purchase from menu

Go into the fixer, select debug options ( prior to v3 it's a button) from v3 its on top menu.
 
Don't change anything just press ok. That will rebuild all the shaders.
 
Whether it's actually necessary with an os change I am not sure but it's harmless and simple to do.

I provided Ken with a hand crafted zip update which has solved the issue.   No-one else has reported an issue so it seems to be a very specific issue.

I have built a beta of 3.1 which does what you want.  Did you purchase from FastSpring or the Flight Sim Store?

All except the last point which contradicts what you have written above it.
 
When you have enabled dual system mode there is no need to uninstall from the first system to install into the second.
 
Prior to the version of the fixer that supported dual systems (or the current version in single system mode ) then yes you would have needed to uninstall from fsx to install into fsx se as it only supported one system - I think that you have a memory of this which is confusing you slightly?

Yes to both, follow the link in my signature and go to the purchase page.

Do you have a camera add on such as ezdok or equivalent if so tick the ezdok box in shadows dialog.
 
If you have eye tracking software tick trackIR.
 
To be honest it's worth just ticking both regardless.
 
Make sure that you have force VC walls ticked.
 
If that doesn't fix it turn off hd shadows and confirm all is ok with all Aircraft.
 
The turn hd shadows back on and test with default aircraft Cessna 737 etc and report back.

No, the only think that need attention is when you install an aircraft or scenery, run the controller to see if it detects any new effects that need converting.

You don't need to do anything. The only thing that matters is if the new scenery introduces new effects that need converting. The fixer monitors your effects directory and will prompt you if this occurs...

I have a 970 which I am happy with! I upgraded from - 660ti
 
This is a very careful answer.
 
In any particular scene there is a cpu cost in preparing the scenery and objects to be drawn and passing them to th gpu, There is also a GPU cost in rendering. It is perhaps more common for the cpu to be the limit than the gpu except if you have to high level of sssgaa enabled and specially if there are a lot of clouds.
 
What I suggest is that you view some scenarios of interest to you with normal AA and a second time with AA disabled. If the fps increases then you were gpu limited and so there would be a benefit. If it is unchanged then in that scene you were cpu limited.
 
So for example in a pmdg at an aerosoft mega airport I predict that you would be cpu bound. In the base Cessna in dense cloud I suspect the gpu would be the limit.

I really didn't mean to cause a complication here  - it was only a passing comment. 
 
For most people by far the simplest method is just to unpack the zip file, find the 10-20 or so BGLs of interest and copy each one into the respective legacy airport where a problem is observed.
 
All I was saying is that if you felt for some reason that  was a little untidy  and you were familiar with creating a scenery area (click on white space etc) you could create a scenery area somewhere above the 10-20 airports and copy the 10-20  BGLs into it. 
 
There is no advantage in doing so  other than a perception of tidiness and its not something I would bother to do myself  but if you did then it would work.

Have you enabled HD shadows?

No, there is no problem with the fixer. have you reinstalled fsx recently? have you perhaps installed fsx and not installed sp1 and sp2.

Jordan is beta testing a fix for this which will be in the next release.

You are correct that there is a problem  in 2.11. I added some more logic in this area to deal with issues and it makes it worse not better...   
 
In a scenario where a fsx system has been uninstalled whilst the fixer thinks the libraries are installed  then in the file
 
c:\program data\dx10sceneryfixer\dx10.ini
 
it has a flag that the libraries are installed and it also has the fsx path.
 
When you run the controller it detects that the fsx path is invalid and blanks it  (new 2.11 behaviour)  but it still looks at the libraries installed flag to decide whether to allow you to change it...   In earlier versions it accepted the old (invalid path)  and the uninstall/install technique would work with some spurious errors.
 
For 2.11 deleting or renaming c:\program data\dx10sceneryfixer\dx10.ini will fix this 
 
Note that its program data not program files and its a hidden directory so you need to tick the hidden items in the file explorer view tab.
 
I will have to prepare a new build of 2.11 to address this properly

how are your file manager skills - if you rename water40.fx to something else, create a copy of the ORIG file and rename it water40.fx that should fix the problem.

I replied on the blog. To your second question, yes you can back it out.