Hey all,I went to play FSX today and when I started up the game, all of my payware aicraft add-ons have messed up models (wings sticking out of the roof, misplaced lang gears, etc..) and textures (all of the aircraft are white/light blue like they are all ports and I am trying to run in DX10...which I am not). I first tried rebuilding a new FSX.cfg file, that didn't help. I removed *******'s shaders mod, and followed the procedure for reverting back to the previous files, I tried uninstallig and reinstalling the drivers, I have seeming tried everything and I am at a loss.I haven't installed anything new outside of a GTX480 and it has run fine sice I have had it, ad all of my other games still work great. FSX is the only game that seems to be trashed all of a sudden.Any ideas what would cause this?Thanks!*EDIT* FIXED - I added in a new line in the [GRAPHICS} Section for Shader Version with a random value (changed the last number of *******'s original number) and all is working again. I have no idea what that did, but I'm never touching the Shaders file again. lol

What it did Ark, is to force the shader engine to rebuild it's cache. When the shader cache version number is not the same as the shader cache version number stated in the fsx.cfg - the aircraft graphic display will screw up exactly as yours did - OR - If the line "ALLOW_SHADER_30=1" is mistyped, the same thing happens - OR - If you copy in a new ShadersHLSL folder into the root FSX folder without changing that number, again - the same thing happens. It's a bummer when it happens, (I reinstalled FSX because of this :( ) but it's entirely fixable. :(

What it did Ark, is to force the shader engine to rebuild it's cache. When the shader cache version number is not the same as the shader cache version number stated in the fsx.cfg - the aircraft graphic display will screw up exactly as yours did - OR - If the line "ALLOW_SHADER_30=1" is mistyped, the same thing happens - OR - If you copy in a new ShadersHLSL folder into the root FSX folder without changing that number, again - the same thing happens. It's a bummer when it happens, (I reinstalled FSX because of this :( ) but it's entirely fixable. :(

I hear you. I was within a keyboard's throw of reinstalling FSX....something I did NOT want to have to do. I dread the thought. LOLWhat's interesting is I deleted the "ALLOW_SHADER_30=1" line, deleted the old Shaders folder, re-placed it with the old Shaders Folder (I renamed it), replaced the WaterCostants files with the old one (I renamed that one too), and it still didn't work. What actually worked, was putting ONLY the "SHADER_CACHE_VERSION" line in and changed the last digit. I was't aware that line was even in the FSX.cfg file. In fact, I deleted the old FSX.cfg and had FSX rebuild a new one, and it still did't work.Any ideas why this would occur? I am positive the old Shaders ad WaterConstants file were put back in.

Any ideas why this would occur? I am positive the old Shaders ad WaterConstants file were put back in.

Any time you change the shaders, whether that be changing them, deleting them, reverting to an old version etc...you have to force a recompile, which is done by changing the value in the SHADER_CACHE_VERSION line in the fsx.cfg file. So when you replaced the old versions, a recompile was needed but not done until you changed that line in the config file.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Any time you change the shaders, whether that be changing them, deleting them, reverting to an old version etc...you have to force a recompile, which is done by changing the value in the SHADER_CACHE_VERSION line in the fsx.cfg file. So when you replaced the old versions, a recompile was needed but not done until you changed that line in the config file.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Ahh, ok. So, basically, when I created a new config but did not add in the new Shader_Version change, FSX basically had "nothing" to read, so it essentially projected a mish-mash of shaders.I didn't even know that Shader_Cache_Version line was natively in the CFG file. I thought I added that in myself. I guess my wife is right...I'm not as bright as I look. :( Definitley good to know for the future.Thanks for the explanations, guys.

Any time you change the shaders, whether that be changing them, deleting them, reverting to an old version etc...you have to force a recompile, which is done by changing the value in the SHADER_CACHE_VERSION line in the fsx.cfg file. So when you replaced the old versions, a recompile was needed but not done until you changed that line in the config file.Bob Scott

.. and not forcing a re-compile means that FSX reads the ShadersHLSL cache contents, (which are in the users/yourname/AppData/Local/Microsoft/FSX/Shaders/Shaders10 folder (Win7)) - and those contents will disagree with the contents of the Shaders folder in the main FSX root folder.