SteveFx

George at fly Tampa suggested you reinstall the airport did you try that?

Jay, well actually there is!
 
As Erich suggest one option is to find a darker texture.
 
But using just the fixer you need to find and edit you dx10.ini file in
 
<your user>\Appdata\Local\DX10SceneryFixer
 
Find the line
DayAmbience= and change it to a percentage lower than 75 so e.g 66 is 66%
 
When you open the fixer water dialog then you will see the value you entered in the box with the slider over to the left hand side, if you move the water slider it will change the value back to above 75 but if you leave it alone then the lower value should persist even if you change something else in the dialog.

when you change the AA level in the GUI it writes it into fsx.cfg.  The GUI then displays what is in fsx.cfg
 
NVI has no bearing on this.
 
If you have changed GPU there may be multiple device entries in your fsx .cfg
 
I would clean all the device group entries out of it and then try
 
they are of the form
 
[DISPLAY.Device.Nvidia GeForce GTX xxx.0.0]  
item=value
etc

Ok  lets try another way
 
Can you open windows file explorer
Go to c:\ProgramData\Dx10SceneryFixer
Delete the file DX10.ini in that directory.  
 
You should then find that the controller can be launched as if it had just been installed.

Yes, you can install over the top,

Dave, you need to uninstall the libraries then you will be able to change the path to the SE path and then install the libraries

Have you checked the num lights setting in fsx.cfg that has been known to lose interior lights.

Ok that means that your general10.fx shader is non standard and therefore DX10SF is leaving it alone - have you previously made changes to it yourself? If you can restore the original file then all should be well.

Have you set ForceVCShadowMap? See pg 55 of manual?

Pedro there is an option in the FSX weather options dialog to select Thermal Visualizations - I imagine that's what you are seeing

It means your general10 shader has been altered and is no longer the correct size. The file is located in the fsx\shadersHLSL\general directory and should be 24218 bytes.
 
You need to locate and restore the original correctly sized shader.
 
Once you have restored the original shader go into the debug screen from dx10 controller and tick the general shader option near the top right.

Turn on missing texture alert in Fsx.cfg. You can do it via the toolbox as well. I would be fairly confident that's the issue here. This thread was about the fixer 1.x

Turn off the Sun Glare Hiding feature for the background to text messages - may fix the axis I haven't tested.

ok save your profile as Jose or something and load the default profile.

The first two settings for HD down to biz jets are pretty safe. All aircraft is as noted in the manual less clearcut. You can create two profiles one with ALL and one with BizJets

Are you saying that 2.5 hasn't fixed the clouds? The problem with aprons in 2.4 was the red axis fix. If 2.5 isn't working with clouds try disabling the axis fix.

You could try turning on missing texture alert

Selecting HD shadows for the aircraft size will minimise it as much as possible, avoid over darkening shadows with any boost.
 
In some scenerios - sun shining along a surface with a slightly raised obstruction then increasing the bias willhide the shadow at the edge of the obstruction.
 
Turning the engine off will minimize movement along the edge but is clearly not a long term solution unless you like gliding!

If you are referring to the bad spiking then its a driver/FSX core engine interaction somehow related to the locking of the cloud vertex buffers used in reflections. It is unrelated to DX10SF which has no interaction at this level and occurs without it installed in native DX10 preview mode.
 
It only applies to AMD GPUs more recent than the 6xxx range that are running drivers post 12.4, The only workaround for a recent AMD GPU that cannot run 12.4 is to set the water slider to no more than 2.low and set aliasing to no more than 4X. This prevents clouds being used in reflections which largely fixes the problem.
 
The only fixes possible are by AMD or Microsoft.

I suspect for Bloom you are looking for the star filter effect? That doesn't occur in DX10 its a much simpler effect which just makes surfaces brighten
 
Most lights in FSX don't illuminate the ground - only landing lights and a few 3rd party aircraft which have special effects.

Is this a legacy plane? What happens if you disable the legacy shader in the main screen?

Ok I found and downloaded it.
 
I don't think its a build19/build24 issue. I think that you had turned on the 8bit fix and after a new install this defaults to off.
Turning it on will fix it but it generally isn't a good idea to leave it turned on as it will affect adversely many legacy airports (although you may not have any)
 
The best solution is to use the toolbox and assuming that you have ImageTool from the SDK use the toolbox function to convert all 8 bit textures to DXT1. I have tested and this fixes the problem. To do this using toolbox you must first set the path to ImageTool and then select the texture directory for the plane to convert. there are two in this case.
 
I would also recommend talking some time afterwards with ImageTool to create mipmaps for the textures - this will improve the IQ.

Yes you are correct.  
 
If you install and select the lights package then it takes copies of all the navlights in the effects directory( this is separate to the backup) before modifying them.
When you uninstall it puts the originals back.
 
If you install and don't select the lights package, then when you uninstall it still tries to put the copies back :( and they don't exist!
 
So its a bug, its entirely harmless but as you say  annoying.  I will fix it in the next few days - I cannot upload new releases directly to the FSS store.

Yes you are correct - it doesn't set the update time if you enable effects together with the libraries.  
 
If you Disable the Effects and then Enable it should work ok from that point on - and that will refresh any that have been missed.
 
I will fix it in build 26.

I will upload a build 25 with adjusted offsets to improve this. Will be early next week.