Nighthawk117 wrote:Have you tried running check disk? maybe allocation became corrupted. Have you downloaded any new planes last night? there have been time were i would add new plane and it caused issues with start-up and crashing just have to uninstall the plane if you did
Azframer wrote:Nighthawk117 wrote:Have you tried running check disk? maybe allocation became corrupted. Have you downloaded any new planes last night? there have been time were i would add new plane and it caused issues with start-up and crashing just have to uninstall the plane if you did
My first thought. Maybe a bad shut down, the power went out on you, or whatever.
Nighthawk117 wrote:Did you add any aircraft?
Hagar wrote:The first thing I would try is to find fsx.cfg & delete it. Take a backup copy first if you're nervous. FSX should then create a new CFG if & when it starts up.
If this is successful you will have to reset your display settings.
Azframer wrote:Hagar wrote:The first thing I would try is to find fsx.cfg & delete it. Take a backup copy first if you're nervous. FSX should then create a new CFG if & when it starts up.
If this is successful you will have to reset your display settings.
Roger that!
If you are running FSX in windows 8/8.1 click start then run and paste this %AppData%\Microsoft\FSX in and it will take you straight to your FSX.CFG file
I am not sure how you find it in Windows 10.
Canuck1955 wrote:Often a corrupted logbook will cause this. It does no harm if you delete the file. Logbook.BIN found in C:\Users\yourname\Documents\Flight Simulator X Files
Canuck1955 wrote:Often a corrupted logbook will cause this. It does no harm if you delete the file. Logbook.BIN found in C:\Users\yourname\Documents\Flight Simulator X Files
TextRich wrote:Canuck1955 wrote:Often a corrupted logbook will cause this. It does no harm if you delete the file. Logbook.BIN found in C:\Users\yourname\Documents\Flight Simulator X Files
I am thinking a corrupted logbook file as well. I believe there is file that can repair the logbook file once it is confirmed that having FSX create a new logbook solves the problem.
Return to Flight Simulator X (FSX) and Steam
Users browsing this forum: No registered users and 320 guests