Phil Manhart Posted May 27, 2010 Share Posted May 27, 2010 Wondering if anyone has seen this and knows a fix. This occurred after a fsx.cfg file deletion. Any ideas? EDIT: Nevermind! I fixed it by reloading my shaders folder in the Users/Appdata/Roaming/Microsoft/FSX folder... Link to comment Share on other sites More sharing options...
Wolter van der Spoel Posted May 27, 2010 Share Posted May 27, 2010 lol Link to comment Share on other sites More sharing options...
Arismac Posted May 27, 2010 Share Posted May 27, 2010 Hey Phil, I will take two cases of that brew please. Will rubles be OK ;D Link to comment Share on other sites More sharing options...
Phil Manhart Posted May 27, 2010 Author Share Posted May 27, 2010 Ha Ha... I'm not sure what happened... I loaded up FSX after backing up and deleting the fsx.cfg and that is what I saw... ugly. You should have seen the default 747... One of it's wings and landing gear were on a vertical instead of horizontal so it looked like it had a giant speedbrake and wheel coming out the starboard side of the fuselage... And rubles will do just fine... brew is in the mail. Phil Link to comment Share on other sites More sharing options...
Ian Routley Posted May 27, 2010 Share Posted May 27, 2010 We used to see this quite a bit when seeing how high Bufferpools could be set. UsePools=0 could potentially do the same. The interpretation was overload or corruption of VRAM. Glad you got it sorted ... quite alarming these glitches. Link to comment Share on other sites More sharing options...
6297j Posted May 27, 2010 Share Posted May 27, 2010 Interesting, I had the same about a week ago when I was fiddling around with the Shader 3 mod and various lines in my cfg as well as seeing what difference all the changes made with DX9 or DX10. I couldn't get it all back to normal no matter what I tried and I had to do a complete re-install for the second time in about ten days. Only this time I didn't uninstall Acceleration properly first and now I can't reinstall it at all. I've had to go the SP1/SP2 route instead. So far so good but for a day or so earlier this week I thought I had lost FSX forever just as I had bought my first FTX product. Now I've finally got it all back up and working again (better than it ever has before so all the hassle has been kind of worth it) I am finished tweaking forever! Link to comment Share on other sites More sharing options...
timmo32 Posted May 27, 2010 Share Posted May 27, 2010 i know you could fix it phil being the forum guru mate Link to comment Share on other sites More sharing options...
jgutteri Posted May 27, 2010 Share Posted May 27, 2010 I've got this problem as well - how did you reload the Shaders folders? Link to comment Share on other sites More sharing options...
Wolter van der Spoel Posted May 27, 2010 Share Posted May 27, 2010 this is the result when having the SM3.0 files active and rebuilding the fsx.cfg as it has not the entry for adapting to the SM3.0 model entering the line for that and all is sound again Link to comment Share on other sites More sharing options...
John Venema Posted May 28, 2010 Share Posted May 28, 2010 It's the result of tweaking in general. See my best tuning tips from 12 months ago - http://orbxsystems.com/forums/index.php?topic=11307.0 Link to comment Share on other sites More sharing options...
jgutteri Posted May 28, 2010 Share Posted May 28, 2010 Yep I just put in a 5850, and suddenly DX9 wouldn't work! I completely forgot about the shaders tweak I had done before reloading the CFG, so that will be the first thing to change this evening! Link to comment Share on other sites More sharing options...
MrMaestro Posted May 28, 2010 Share Posted May 28, 2010 I've got this problem as well - how did you reload the Shaders folders? It's explained in the Shader Model 3.0 MOD Readme - 2) Edit your fsx.cfg file and add the following lines to enable Shader 3.0 support: [GRAPHICS] ALLOW_SHADER_30=1 SHADER_CACHE_VERSION=9872430 The SHADER_CACHE_VERSION above instructs FSX to re-compile the shaders, this number has to be changed if the ShadersHLSL is modified. The 9872430 is just a random number you can use ANY number, just remember to change it everytime you update anything INSIDE your ShadersHLSL folder OR even if you UNINSTALL IT, so the shaders are re-compiled again. I was having this problem too after I reset the fsx.cfg. Even though I was changing that cache version number to get it to rebuild but it wouldn't fix the graphical errors. Turns out I forgot to put that 'allow shader 3.0' line in. Mike Link to comment Share on other sites More sharing options...
Phil Manhart Posted May 28, 2010 Author Share Posted May 28, 2010 Like John said, it is the result of tweaking gone awry... But for those of us that like to tweak, having something go wrong (like what happened to me above) is always a possibility. @jgutteri Like MrMaestro said to recompile the shaders, simply add to your fsx.cfg: [GRAPHICS] ALLOW_SHADER_30=1 SHADER_CACHE_VERSION=9872430 @timmo32 Thanks for the vote...but there are others far more experienced than I... I owe all of my knowledge to them, like Wolter for example Link to comment Share on other sites More sharing options...
Wolter van der Spoel Posted May 28, 2010 Share Posted May 28, 2010 you give me to much credit Phil, there are more people here on the forums that are much more knowledgable than my lil person Link to comment Share on other sites More sharing options...
Phil Manhart Posted May 28, 2010 Author Share Posted May 28, 2010 you give me to much credit Phil, there are more people here on the forums that are much more knowledgable than my lil person Then I guess we'll have to keep denying any knowledge until the guilty party is found... Phil Link to comment Share on other sites More sharing options...
timmo32 Posted May 28, 2010 Share Posted May 28, 2010 well lets settle on this vote, you are all great guys and your help is the best it can be ,lets help each other if we can . Link to comment Share on other sites More sharing options...
TenBlade Posted May 28, 2010 Share Posted May 28, 2010 Wondering if anyone has seen this and knows a fix. This occurred after a fsx.cfg file deletion. Any ideas? Had the exact same thing happening, quite amusing effects on aircraft http://forums1.avsim.net/index.php?showtopic=278533&hl=mutation Now running UsePools=0, and no problems Bjorn EDIT: Nevermind! I fixed it by reloading my shaders folder in the Users/Appdata/Roaming/Microsoft/FSX folder... Link to comment Share on other sites More sharing options...
Phil Manhart Posted May 28, 2010 Author Share Posted May 28, 2010 LOL! Nice shots of those Bjorn on AVSIM... Are those some next gen experimental aircraft? Link to comment Share on other sites More sharing options...
TenBlade Posted May 28, 2010 Share Posted May 28, 2010 Thanks. That´s right, Phil! But it´s still a bit hush hush, sure you understand And, eh, sorry for sqeezing my reply into the quote. Wasn´t too clear headed after a night shift when posting Bjorn Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.