Steve's fixer and Carenado C172N nav and strobe lights

[Stoli151 6]

I have just purchased Steve's fixer and have everything working well. I do have one issue now however. After I installed my Carenado 172n all the lights worked fine, I believe the lights are supposed to have native support for dx10. I closed FSX. I entered the fixer controller to change something and it asked me if I wanted to scan the effects folder and fix problems so I did that. The next time I entered FSX and used my 172 my navs and strobes all had a squarish appearance to them. All the default aircraft I switched to were fine. So I reinstalled my 172 and when the fixer controller asked me if I wanted to scan the changes I selected ignore. Now everything works fine with my 172. So my question is, how do I prevent the fixer from "fixing" the lights on my 172 the next time I add another plane or scenery and it asks me to scan the effects folder?

[aussietomcatter 0]

I have a similar problem with some of my aircraft 

[SteveFx 258]

It's a missing texture, turn on missing texture alert in fsx.cfg, there is an editor in the controller to do so for you.

 

Then note the name of the missing texture and contact the author. Its very common with Carenado for the uninstallation of one aircraft to remove light textures used by another. Many times reinstalling the aircraft with the issue will fix this.

 

In dx9 missing textures aren't shown but in dx10 the use the default texture.