September 8, 200916 yr I posted this in the CTD forum but got no responses, so I'll try here. I'm so tired of trying to get FSX to run correctly, that I'm thinking of just going back to FS9, but maybe someone has a suggestion I have not tried.Everything worked fine until I installed the FSD Commander/Saratoga aircraft. Now, whenever I select an item from the menu while in full screen mode, FSX freezes. The ESC key unfreezes but I can't open the item (example, World/Map). The menu selections work normally in window mode. I'm using Nvidia 182.5 drivers and nHancer per NickN's setup guide. Here's what I have tried:Uninstalled FSD Commander and Saratoga aircraftCopied, then deleted fsx.cfg, restarted FSXVerified all nHancer FSX profile settings are the same as Global settingsTurned off Tool TipsTried various screen resolutionsDisabled CIE in BIOSTurned off nHancerTurned off all virus/spyware checkersI sent an E-Mail to FSD Support, but no replyAnother post suggested using the ALT key, then keyboard arrows to navigate to the selection, and the enter key to select - doesn't work for me.I did recently install the latest FSUIPC (4.5.3, registered), but I did not change any settings.Anyone found a solution? Any suggestions? Dale
September 8, 200916 yr Have you tried putting in the FSX dvd and doing a repair? 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.
September 8, 200916 yr Indeed, the repair option might be the way to go.Also, if this plane came with an installer, than there will be registry entries that the uninstaller will not remove. I suggest a Registry cleaner. CCleaner or Glary's Utilities work for me. I use both and both are free. Bob Bob i5, 16 GB ram, GTX 960, FS on SSD, Windows 10 64 bit, home built works anyway.
September 8, 200916 yr Author Indeed, the repair option might be the way to go.Also, if this plane came with an installer, than there will be registry entries that the uninstaller will not remove. I suggest a Registry cleaner. CCleaner or Glary's Utilities work for me. I use both and both are free. BobThanks to you and others that made suggestions.I did run CCleaner and repaired some minor issues, but no change.I ran the repair feature from the original disks. It completed, but now I get a fatal error when trying to start FSX. I ran the repair again, this time with the virus checker completely off, but same results - fatal error. This is what it says:Appname fsx.exeAppver 10.0.614720App Stamp 475e17d3Modname simprop.dllModver 10.0.61472.0Modstamp 475e180dIDe Bug 0 Offset 00006da7I have no idea what any of this means, any suggestions would be welcome.Dale Dale
September 8, 200916 yr Thanks to you and others that made suggestions.I did run CCleaner and repaired some minor issues, but no change.I ran the repair feature from the original disks. It completed, but now I get a fatal error when trying to start FSX. I ran the repair again, this time with the virus checker completely off, but same results - fatal error. This is what it says:Appname fsx.exeAppver 10.0.614720App Stamp 475e17d3Modname simprop.dllModver 10.0.61472.0Modstamp 475e180dIDe Bug 0 Offset 00006da7I have no idea what any of this means, any suggestions would be welcome.DaleDelete the Logbook.BIN located in "...\My Documents\Flight Simulator XFiles\". There's also a FSX Logbook Recovery program (FSX Logbook Recovery v1.1 by Daniel Van Os) that analyes and fixes the logbook. I believe this program can be downloaded from the AVSIM Library.Best regards,Jim Young
September 9, 200916 yr Author Delete the Logbook.BIN located in "...\My Documents\Flight Simulator XFiles\". There's also a FSX Logbook Recovery program (FSX Logbook Recovery v1.1 by Daniel Van Os) that analyes and fixes the logbook. I believe this program can be downloaded from the AVSIM Library.Best regards,Jim YoungJim,Thankyou for the suggestion. I ran Logbook Recovery, but it did not find any corrupted files. I took your advice and deleted Logbook.bin,but FSX still shows a fatal error on startup. Simprop.dll seems to be the problem. I've done Google searches and found others with this problem, but they don't say how they fixed it (if they ever did!). Help!! Dale
September 9, 200916 yr Author Based on a suggestion from another web site, I deleted simprop.dll (i made a copy on a cd), then re-ran the MS FSX repair program. No more fatal error - now it won't even try to start and gives a message that files are missing and the program needs to be installed or repaired. I checked and the repair program did create a simprop.dll.Please, does someone have a solution? I would uninstall FSX and start over, but I'm afraid it will affect FS9, which still runs without problem.Dale Dale
September 9, 200916 yr Based on a suggestion from another web site, I deleted simprop.dll (i made a copy on a cd), then re-ran the MS FSX repair program. No more fatal error - now it won't even try to start and gives a message that files are missing and the program needs to be installed or repaired. I checked and the repair program did create a simprop.dll.Please, does someone have a solution? I would uninstall FSX and start over, but I'm afraid it will affect FS9, which still runs without problem.DaleAfter you repaired, make sure you install FSX SP1 and SP2! Sometimes they will even replace missing and/or corrupt files! See You In The Skies...gman!"Impossible things are simply those which so far have never been done." - Elbert Hubbard
September 10, 200916 yr Uninstalling FSX will have zero impact on FS9: they are two completely separate computer programs, just as MS Word does not impact FSX or FS9. Just remember to copy your user files to a safe place first, so you can get them back afterward. You might have 200 hours in the logbook for e.g., and you would be pretty p***** if you lost it. Good luck. 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.
September 10, 200916 yr I agree with Paul - but if you ever do decide to uninstall FSX, be aware that doing so will almost always mess up the FS2004 entries in the Registry.If that happens, it can be easily fixed using the Registry repair tool from the good folks at Flight1:http://www.flight1software.com/files/FS_Registry_Repair.exeHope you find out what is causing you so much grief.
September 10, 200916 yr Author Ok, I think I will try installing sp1 and then Sp2 before I uninstall FSX.Thanks to everyone for their suggestions.Dale Dale
September 10, 200916 yr Author Well, some progress. I re-installed SP1, but the sim still wouldn't run.Next, I uninstalled SP2. Voila! FSX now starts and runs.I defragged the FSX drive, then installed SP2. FSX starts and runsHowever... the menu problem is still there. Works fine in window mode, freezes on any selection in Full Screen.In reviewing my change log, I updated FSUIPC from 4.3 to 4.5.3 around the time the menu problem surfaced. Is there anywhere I can get the old 4.3 version? I'd like to try setting it back to see if it makes a difference.Thanks to gman! for pointing me to the FSX updatesDale Dale
September 11, 200916 yr Well, some progress. I re-installed SP1, but the sim still wouldn't run.Next, I uninstalled SP2. Voila! FSX now starts and runs.I defragged the FSX drive, then installed SP2. FSX starts and runsHowever... the menu problem is still there. Works fine in window mode, freezes on any selection in Full Screen.In reviewing my change log, I updated FSUIPC from 4.3 to 4.5.3 around the time the menu problem surfaced. Is there anywhere I can get the old 4.3 version? I'd like to try setting it back to see if it makes a difference.Thanks to gman! for pointing me to the FSX updatesDaleThe only time I experienced Menu freezing in FSX was due to nVidia video card drivers. So I went with ATI ... no problems.However I don't have any freezing with my 295 running with the 186.18 driver release.
September 11, 200916 yr Author The only time I experienced Menu freezing in FSX was due to nVidia video card drivers. So I went with ATI ... no problems.However I don't have any freezing with my 295 running with the 186.18 driver release.The driver is a suspect, but most folks run ok with the 182.5. It worked for me without any menu freeze ups for at least 2 weeks. There are newer Nvidia drivers I could try - may take a shot at that tomorrow.Dale Dale
Create an account or sign in to comment