October 18, 201015 yr I have had FSX since the initial release and most of the time it boots up successfully. Today for the third time in the last 13 months I am facing a complete uninstall and reinstall from scratch because the sim fails to get past the initial splash screen - the blue and white one which says Flight Simulator X - Acceleration. Once the problem occurs every subsequent attempt to start behaves the same way. It gets as far as is required for the light on my TrackIR device to show that FSX is running, which normally occurs a few seconds before the main menu screen appears, but stays stubbornly on the splash screen. Uninstall and reinstall took four days last time as I have a large number of scenery and aircraft addons but appears to solve the problem at least for six months or so. This doesn't appear to be a crash - there is no error message or graphical glitches, which sometimes happen mid flight, and the PC otherwise behaves normally. I have FSX Deluxe + SP1+ Acceleration. My system is by Cyberpower with Intel Core 2 Quad Q9550 2.83GHz overclocked to 3.4GHz, 4Gb ram, Nvidia GTX260 graphics and single Samsung Syncmaster 245B 24" display, running Windows Vista Home Premium 64bit with SP2. I have UAC turned off and my account has Adminstrator privileges. The problem didn't occur running FSX on my much lower spec previous Dell PC. I would be grateful for any light which could be shed on this problem. I haven't been able to select the right turn of phrase to reveal anything using the search function, but I would like to think I am not the only one in the world with this glitch.Mervyn
October 18, 201015 yr first - REINSTALL as a last resort!second - move the FSX config file to your desktop. start the sim. FS will make a new cfg file. this will fix problems 95% of the time.third - run FSX's 'repair' utility.fourth - remove the last addon installed and then do 'second' step above. keep good records of mods and addons you do to the game. helps 'backtracking' if there is a problem'. i've NEVER done a uninstall / reinstall of FS9. i have only done a uninstall/reinstall of FSX because of a testing issue (beta testing for an addon, a reinstall wasn't necessary ... just a testing issue).fifth - consider reinstalling the game.-- D. Scobie, feelThere support forum moderator: https://forum.simflight.com/forum/169-feelthere-support-forums/
October 18, 201015 yr first - REINSTALL as a last resort!second - move the FSX config file to your desktop. start the sim. FS will make a new cfg file. this will fix problems 95% of the time.third - run FSX's 'repair' utility.fourth - remove the last addon installed and then do 'second' step above. keep good records of mods and addons you do to the game. helps 'backtracking' if there is a problem'. i've NEVER done a uninstall / reinstall of FS9. i have only done a uninstall/reinstall of FSX because of a testing issue (beta testing for an addon, a reinstall wasn't necessary ... just a testing issue).fifth - consider reinstalling the game.--Not quite Scoob!! After the second - the config repair Mervyhn - go find FSXLog.exe - and run it against the logbook. If the logbook is corrupt -= it will also stop the sim from loading. 99% sure this is the issue. I'm looking for the source location at this moment. I'll edit this if I find it - meantime if someone else knows where to get- please post it here.Edit:OK - found it here on the Avsim site:-Filename: fsxlogrecovery11.zipLicense: FreewareAdded: 20th February 2007Downloads: 8522Author: Daniel van OsSize: 230kbThere's a good "readme" that comes with it, but it's as easy as pie. i7 [email protected] | 32GB RAM | EVGA RTX 3080Ti | Maximus Hero VII | 512GB 860 Pro | 512GB 850 Pro | 256GB 840 Pro | 2TB 860 QVO | 1TB 870 EVO | Seagate 3TB Cloud | EVGA 1000 GQ | Win10 Pro | EK Custom water cooling.
October 18, 201015 yr Mervyn, 99.999% of the time I've had this problem, I've simply repaired or deleted the logbook file, like Paul J pointed out. Should fix it. Russell Johnston
October 18, 201015 yr Author Thanks scoob for the helpful suggestions. Number 2 worked a treat. I have noted the logbook fix thanks, but not needed at the moment. You guys saved me so much needless work.Mervyn
Create an account or sign in to comment