ablackhawk2 Posted April 7, 2016 Share Posted April 7, 2016 The problem I have is when FSX starts you get that first screen. Then the second screen starts this is when the problem happens. As it starts it disappears and FSX does not start. Any idea what is going on? Ken Link to comment Share on other sites More sharing options...
PhantomTweak Posted April 7, 2016 Share Posted April 7, 2016 One thing I've found that can cause that is a fault with the default flight. You can get into your FSX.CFG file with NotePad or similar, NOT a word procesor (they add characters that can totally destroy the usefulness of the file), scan down till you find the heading [uSERINTERFACE]. Under that will be a line that starts thus: SITUATION= Just delete that entire line, everything, save the file, close it out and try to start FSX again and see what happens. I have this situation arise about once a month or so, and this procedure fixes it every time. Pat☺ [sIGPIC][/sIGPIC] Had a thought...then there was the smell of something burning, and sparks, and then a big fire, and then the lights went out! I guess I better not do that again! Sgt, USMC, 10 years proud service, Inactive reserve now :D Link to comment Share on other sites More sharing options...
longbreak754 Posted April 7, 2016 Share Posted April 7, 2016 As Pat has identified, this is normally associated with an error in the default flight. If Pat's solution fails to remedy the problem try the following: Go to the Documents\Flight Simulator X Files folder and delete the three files that are associated with a flight. What files you delete will depend on how you have saved your default flight. For example, I use a naming convention based on the current 'aircraft' I am 'flying' so use a naming convention of aircraft type current (eg B757 Current). The three files, in the instance of the example given, would be B757 Current.FLT, B757 Current.FSSAVE and B757 Current.WX If you didn't give a name to your last saved flights, for example if you just exited with saving or you closed FSX abnormally for some reason, it may have automatically saved copies of the three files using the filename PREVIOUS. If neither solutions work then it maybe due to a corrupted logbook - simply rename the current logbook.bin to logbook_copy.bin and see it that resolves the issue. If it does you could try renaming the origianl changed file back to logbook.bin to see if it works but it probably won't and therefore you will lose any flight details listed in it. Regards Brian Link to comment Share on other sites More sharing options...
PhantomTweak Posted April 7, 2016 Share Posted April 7, 2016 If neither solutions work then it maybe due to a corrupted logbook - simply rename the current logbook.bin to logbook_copy.bin and see it that resolves the issue. If it does you could try renaming the origianl changed file back to logbook.bin to see if it works but it probably won't and therefore you will lose any flight details listed in it. Brian is absolutely correct. That can cause big troubles, especially if you edited an entry in the Logbook. Having said that, there ARE softwares out to repair the logbook problems, so you don't have to loose all the previous entries in your Logbook. Back-up the original Logbook.bin file, and then see if it's the problem. If it IS, download THIS FILE or THIS ONE, both from the library here on this site. They both work well to repair a corrupted Logbook file. Hope that helps a little bit... Pat☺ [sIGPIC][/sIGPIC] Had a thought...then there was the smell of something burning, and sparks, and then a big fire, and then the lights went out! I guess I better not do that again! Sgt, USMC, 10 years proud service, Inactive reserve now :D Link to comment Share on other sites More sharing options...
ablackhawk2 Posted April 8, 2016 Author Share Posted April 8, 2016 Thanks for all your help. I found the problem to be the FSDT. I had to reinstall it and it was fine. Again thanks. Ken Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.